How do I make EZdrummer 3 rescan the *entire* MIDI library (not just user MIDI)?

[soundsgood]

I was getting duplicate grooves in search results, and I discovered that I had duplicate MIDI libraries (both the Americana EZX and Americana MIDI). So, I removed the Americana-MIDI folder (while leaving the EZX version in place). But when I filter for grooves, EZdrummer 3 continues to include grooves from that removed pack—with an orange alert icon and a pop-up that says “Missing groove.”

How do I get EZD3 to re-scan the library, so it no longer looks for that MIDI pack?

All of the instructions I’ve found point to the “Sync File Changes” command under Grooves > User Libraries. But this is not a user-library issue. I’m also aware of the “Restore MIDI Database…” command under Settings > Advanced, but the pop-up states that that function restores the factory database, and this is not a factory-database issue.

Is there no way to make EZD3 simply re-scan all MIDI in the folder?

EZdrummer version: 3.1.0
Operating system: macOS Sequoia (15)

Topic

[Mick Avoidant]

Do the Restore MIDI Database.

[Bear-Faced Cow]

Did you use the program manager to uninstall the MIDI groove pack?

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[soundsgood]

Mick Avoidant wrote:

Do the Restore MIDI Database.

More information would help to foster confidence in your suggestion.

As I mentioned, the pop-up for that function states that it restores the factory database. But “restoring the factory database” doesn’t sound like what I need. I have a massive MIDI library—aside from the factory database—that I don’t want to have to reinstall if this command “restores” my library to factory settings and erases the additional MIDI.

If you believe the command behaves differently than its wording suggests, any additional thoughts from your experience with the command would be very helpful to hear about.

Thanks.

EZdrummer version: 3.1.0
Operating system: macOS Sequoia (15)

[soundsgood]

OK. I heard back from Toontrack support, and the “Restore MIDI Database” command is indeed poorly named. Rather than “restoring the factory MIDI database,” which is what it states it does, it actually rescans and refreshes the database—which is what I needed.

I’ve asked them to consider renaming it to more accurately reflect what’s actually being done.

1

Thanked by: Scott Eshleman

[Bear-Faced Cow]

It is not poorly named. Rescanning your grooves for its information is the process in which it restores the MIDI database.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 1 day, 14 hours ago by Bear-Faced Cow.

[Author]

Replies