Yes, I meant plug-ins inserted in sequence – or that other tracks in the DAW have much latency (which means that the DAW must keep the EZD/EZB track in sync with those).
Latency makes the sound come out later than when it is processed/produced. The GUI in EZD/EZB shows the “processing state” in those plug-ins, so it is natural that the GUI is earlier than the sound coming out. In some plug-in formats it is possible for the plug to ask the host what the latency before and after the plug is, so that it may delay its GUI (playhead, etc.) accordingly. This is not something we have implemented but it could explain why some other plugs look more synced.
These crashes don’t seem to have anything to do with your drum setup or what library you are using. One crash was when SD3 was starting to read its MIDI databases and one when it was going to read its sound databases. If it doesn’t crash in standalone, I’d guess something else is causing a memory corruption in your DAW.
So the problem is my core library? The 240 gb package?That’s at another drive. And as you can see in the shot, the EZDrummer files are at drive C.
What is the solution here?
Apart from deleting and reinstalling the library, a quick fix that may work (unless some of its files have been overwritten so that it won’t sound/work correctly) is to go into the Sounds folder in the library (SL-SuperiorDrummer3) and delete the file “soundstats” (but leave “soundstats.dat”, which must remain there).
A “Superior Drummer 3” authorization dialog with a close button is an authorization dialog for the core library, but it should not need authorization, so it means that there are files from some other library inside the core library that should not be there.
Get all the latest on new releases, updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.
