MDM send/get HiHat Pedal Settings - 7x64

[angr77]

I am not saying you are wrong...

[talrusher]

Hi all!

Just a question - talrusher how did it turn out for you? Was your problems the same as mine? My system works fine now without any problems (in 64 bit). (Solution - Adding an active USB-hub between the computer an the MegaDrum box)

Dmitri - If talrusher had the same problem - maybe this should be reflected in the documentation somewhere also?
I also get the feeling that my system triggers better - after injecting the external power(easier to configure right because the baseline where your start optitmize the settings works better directly) and that some other problems went away etc. (MDM Hang ups etc)

I am also using 100% Roland triggers CY8, RT-10S/K and VH-11...and I can see many complains about the Roland stuff which seems to act "too hot" from a signal standpoint ...something that I can't agree on. These triggers works perfect after configure them right. (But, maybe this is an old support issue...old information...and many firmware versions ago!!)

Best Regards

Anders

have still this issue... dont use mdm anymore... lost too much settings because of this.

[angr77]

Hi Talrusher!
I did almost guess this after reading your other threads. The problems I had in MDM has been partly resolved with an external USB hub with separate power. I could then read back the Hihat footcontrol settings from the MD. I spent like 10 hours this weekend with the MegaDRUM and have experienced a lot of problems to save data from MDM to MD. (Reading back from MD>MDM seems to work better) I have pre-configured a good baseline of settings and stored them in a MDS file, which I have been using as a reference. Problem seen: If using "send all" in main panel, much of the settings was not entered in MD - for some reason. It seemed to be impossible to get the PAD parameters to hit MD device.

My work around - When handling the parameters for a separate drum...I made the changes first in MDM...Closed/open the midi channel in MDM again...and then sent the drum settings in the pad panel to each drum. I have then done a recheck on the MD LED display, to see if the actual drum setting was updated. Sometimes the settings were updated...sometimes not...but I continued until everything was there! I have during this weekend been facing 4-5 major lockups/hang-ups of MDM... I had to kill MDM using Microsoft task manager. (Real freeze hangs-ups...)

After sending all drum settings to MD and got everything right...I stopped using MDM. And made the last fine tunings directly on the MD instead. (This works very well! Easy to forget that MDM is just a nice feature - Everything can be done on the MD!)

Yes - I am experiencing some problems in MDM and the communication with MD - Then, if this is depending on my system, USB cables, Win 7 x64, Java, MDM or even MD...seems to be extremely hard to tell and time consuming to track down - But It seems like others on this forum have got it to work with MDM.

Sorry to hear about lost configurations on the MD box - Not nice!! I have not lost any settings yet...but I have not tested your way to reset the MD or load MD...

[talrusher]

so i ordered a new usb 2.0 hispeed cable. maybe its working then.

[angr77]

It is maybe a good idea...i have seen several threads where the solution have been the cable....almost tempted to test this myself.

[angr77]

Hi! I have played around with a certified highspeed USB cable...but with the same negative result as my other 4 USB cables. Still strange behaviors in MDM. It is not the cables.

System: HP 6910p with Windows 7 X64 SP1. USB ports set to support legacy USB devices.
I am running the MD Device in USB + Midi mode and the latency set to 20 Firmware 20120122

Without a USB hub and external power

I can not read the hihat hihat pedal configuration from MD to MDM

With a USB hub and external power

I can read the hihat foot control configuration from MD to MDM

Using the function "send all" in MDM - all configuration in MD is not set - Pad settings is not updated

If sending each drum pad using "send" in PAD panel - I am able to update the configuration for that PAD - Sometimes I need to open/close the midi connection to make it happen.

I will investigate futher why MDM is not is responsing in the way it's supposed to. No big problem...but to become an expert to finetune MD...you need MDM to work in a proper way!

/Anders

[dmitri]

You may try to increase SysEx delay in MDM Options.

[talrusher]

same problem here... have my new usb 2.0 hispeed cable but without solving this. now i have set my midi cable for output and the the megadrum usb for input and the hihat settings coming through...

...i noticed that my md sometimes loosing the connection to cubase. in windows the driver is still there and working, but cubase dont get trigger infos. with the midi calble everythings working like a charm... from there i have to power off and on my md and then set the midi speed to normal. after that cubase gets signal from md. if this work i can set the midi speed to 3 and play for an hour or two till the connection gets broken again and i must repeat steps. it doesnt matter if the usb speed is normal or 3, the connection allways gets lost after a while...

exact the same behavior i had with my old md module. so nothing is broken within.

[dmitri]

the connection allways gets lost after a while...

I can only suspect that electromagnetic noise from a nearby powerful device switching on or off causes the USB to freeze. The difficult thing for me is that I have not experienced this problem myself to be able to address it. My MegaDrum sits connected to a PC for weeks without loosing connectivity.

[angr77]

I will try the sysex delay, but I am also suspecting something which is interfering with the MD device.

Best Regards

Anders