Database Error with partial installation and no standalone EzDrummer *SOLVED*

[Ian Furniss]

Hi, from the beginning:

I had what appeared to be an initially corrupt installation with some missing midi percussion files.

I tried reinstalling the demo but this failed as the full product was installed.

I then tried removing the installation and doing a fresh install from the product manager.

This succeeded in part, but has left me with a partial installation, no standalone app, database errors for the midi files, and missing percussion images on the main kits.

I can run the installation from Cubase. The percussion midi will play either the default kit, or percussion sounds if I change to a percussion kit from the installed expansion.

I am currently running Big Sur which, whilst not listed, was previously working fine for the first couple of days, or at least until I noticed an error on one of the midi playbacks. That error was something like “sound library is not working correctly” but I didn’t take any real note of it at the time.

The errors I’m getting are shown in the screenshots

TIA

EZdrummer version: 2.2.0

• The post has been modified 2 times, last modified 4 years, 7 months ago by Ian Furniss.

Topic

[Ian Furniss]

Update: (in case it helps someone in the future) most errors are now resolved. Tldr, scroll to last paragraph for remaining error.

The primary solution appears to have been running the update that’s shown in the screenshot, for MacOS 10.9 or above. Doing that has installed the standalone player and also (I’m only 90% sure of this) installed a database folder that I couldn’t previously locate after searching for possible solutions on Google. It might have been there before and I just didn’t see it. Location: Macintosh HD/Library/Application Support/EZDrummer/Database

Within that folder are multiple directories including one named 02_@EZDRUMMER_2_PERCUSSION with a midiDB file that I assume (best guess) is responsible for the return of my percussion images and functionality in the main kits which is now able to direct the software to the correct locations for the files.

That covers all the problems that I was aware of, but I now have an additional niggle rather than a problem which is that although my database appears intact now with the correct libraries, expansions, whatever, showing

within the search function, something is referencing libraries which aren’t there and shouldn’t be there.
I don’t know if this is a result of previously having used the “show web shop midi” search function which is now switched off (although I’m not sure why that would cause it) but i’m guessing (again lol, a bad habit) this could probably be resolved by tracking down the file that is making the search calls and editing the entries. What, and where that file is, I have no idea.

EZdrummer version: 2.2.0

[Ian Furniss]

Further update:

All originally reported problems now solved:

The final problem was resolved by resetting the midi database to the factory default. For some reason, whenever I looked at the option to do this previously, the tab was greyed out. Looking through the menu for something else, I noticed it available, clicked it, and it removed the erroneous entries.

I do still have a problem with the sound panned entirely to the left on the standalone player, but this fault doesn’t reproduce itself when used in Cubase so, I can live with that. At least until I get bored again and start fiddling for a solution.

Hope this helps someone in the future if they should have any of the same problems.

 

UPDATE:

That problem too, is now solved. Turns out it was a setting within the main Audio/Midi setup of the standalone player, found in the main menu bar. See attached screenshot. For some reason, the right side was turned off. I’ve no idea how or why, but switching it on has resolved the problem.

EZdrummer version: 2.2.0

• This post was modified 4 years, 7 months ago by Ian Furniss.
  Reason: additional information

[Scott]

BEST ANSWER

“I do still have a problem with the sound panned entirely to the left on the standalone player”

Make sure you have both output 1 and output 2 assigned in the Audio settings in standalone.

Scott Sibley - Toontrack
Technical Advisor

1

Thanked by: Ian Furniss

[Ian Furniss]

Thanks Scott, much appreciated! Blame it on lockdown but I went back to some ocd fiddling around after posting and that’s exactly what the problem is. All is now working perfectly. Many thanks, & seasons greetings/wishes to you!

1

Thanked by: Scott

[Author]

Replies