GUI Problem / MDrummer with Sonar & Project 5

[Clydewinder]

Hi

I had MDrummer 2.05 working under Reaper, Sonar 6.2 and Project 5 v2.5 perfectly. After installing the 2.06 & 2.07 patches, Reaper still works but Sonar and Project 5 do not. Under Sonar, quick setup, globals, rhythm editor, and rhythm generator work but the drumset editor screen does not appear except for a small box in the lower left corner for the individual drum sound editing. ( The "Basic Drum Parameters" Box. The rest of the previous screen is still visible. For instance, if I go to the "Globals" screen and then select Drumset Editor, most of the Globals screen is still visible except for the Basic Drum Parameters rectangle in the lower left corner. )
It also occasionally gives me an "Error - Unhandled exception" when attempting to access MDrummer via the Synth Rack. It seems to behave better if MDrummer is added directly to a track rather than through the synth rack

Under Project 5, the P5 crashes when selecting the Drumset Editor screen with "An exception has occured in F:\MeldaProduction MDrummer 2 Large\MAudioPlugins.dll. Please save a backup copy of your prohect file, then restart Project5. ( Exception code: c0000005, address: e9ec872:1:8b872.)"

I have tried re-scanning VSTs but it made no difference. I did not try to reinstall the whole package because it still works in Reaper 2.54.

[MeldaProduction]

Ou ou, that's sad. We are just releasing next update and it is too late to take it back. Nevermind, please try it when it is released, if it won't help, we'll have to digg inside...
Anyway thanks for notification!

[Clydewinder]

Hi Vojtech

Tried the 2.08 patch, same behavior with GUI.

I have attached a few pictures to show what is happening in Sonar 6.2:

I inserted MDrummer with the synth rack, loaded kit from quick start page. OK. Went to global page: OK. Went to drumset edit page, and this happened:



If i go to the pattern editor first and then to the drumset page it does this:



When I tried to remove MDrummer from the synth rack with the red X ( remove synth ) button it did this:



Hope this helps!

- Dave -

[MeldaProduction]

Yay, too sad. Well, obviously the bug, except I don't understand how this is possible under one host and not the others. This should be independent.

Btw. did you install MDrummer Small too? The thing is, it crashes when showing plugin based source/effect, which makes the idea, that it is using a different DLL. Please try running MDrummerConfig from the MDrummer Large directory (or start menu) and tell me if it helps. Also if you have the MDrummer Small installed, maybe you should remove it... ou this should be automatized...

Thanks!

[Clydewinder]

No, I didn't install Mdrummer Small on that system. I will try to re-install this afternoon when I get home, possibly a file got corrupted somehow? Very odd that it still works in Reaper, however.

[MeldaProduction]

Hmm, if it works in reaper, that is very weird... I'll test it. But if it won't bother you reinstalling, I'd be graceful.

[Clydewinder]

Hi- just re-installed and i think i figured out what happened. I installed new from the 2.05 installer, and then let it do the on-line update automatically. After that it worked perfectly in Sonar, Project 5, Reaper, and stand-alone.

Previously, I had installed the 2.06 & 2.07 updates from the patch files. I believe what happened was the update partially failed because I had moved the DLL file away from its original folder it was installed in, to a different "VSTi" folder that I had created. This time I let it do the update & afterwards moved the DLL back to the VSTi folder and everything was fine. There are 2 ways to deal with this:

1- always leave the DLL in the original folder it was installed to so MDrummer update can find it.

or

2- temporarily move the DLL when patching and then move it back afterwards.

So it appears that this was mostly "operator error" in this case. Everything functioning 100% at this time.

[MeldaProduction]

Great!
I figured it out at night - there is no version number in the screenshots, so you cannot have the newest DLL.

Heh but good point! This may happen from time to time to someone.
So thanks!