Page 1 of 2

New Megadrum Manager 20170501

PostPosted: Mon May 01, 2017 5:33 pm
by karlarsch
Hi Dmitri and Friends,
on Mac the new MDM always gives SYSEX-Timeout, the device with also newest firmware connects correctly, when i switch from open to close midi, but any transmission fails Any Idea?
Best regards
Karl (MDM-Lover since Years on Mac 10.9.5 Mavericks).

Re: New Megadrum Manager 20170501

PostPosted: Mon May 01, 2017 9:14 pm
by dmitri
Please post screenshot of Options. And what hardware version is your MegaDrum?

Re: New Megadrum Manager 20170501

PostPosted: Mon May 01, 2017 9:55 pm
by stefan1982
I am not having problems this far... Using it for 2-3 hours so far and seems to work on my Mac.

Re: New Megadrum Manager 20170501

PostPosted: Mon May 01, 2017 10:03 pm
by sbonasuk
I think there may be a problem all the sensitivity has gone, hit a tom or cymbal no sound hit again and it plays but at a much lower velocity

Re: New Megadrum Manager 20170501

PostPosted: Mon May 01, 2017 11:00 pm
by dmitri
sbonasuk wrote:I think there may be a problem all the sensitivity has gone, hit a tom or cymbal no sound hit again and it plays but at a much lower velocity

I don't quite get it. You think it is caused by the new MDM version?

Re: New Megadrum Manager 20170501

PostPosted: Tue May 02, 2017 7:16 am
by sbonasuk
Updated MD with 501 and the dynamics suffered. (I use pots between the piezo and MD to cool them) my settings have been static for some time now and it was if I had turned up the pots and over cooled them. Hadn't seen MDM 517 so thought it was a mismatch so updated MDM better but still no dynamics, the first hit seems to get lost and then improves with the second. Its as if the latency has suddenly increased.

Re: New Megadrum Manager 20170501

PostPosted: Tue May 02, 2017 9:15 am
by dmitri
sbonasuk wrote:Updated MD with 501 and the dynamics suffered. (I use pots between the piezo and MD to cool them) my settings have been static for some time now and it was if I had turned up the pots and over cooled them. Hadn't seen MDM 517 so thought it was a mismatch so updated MDM better but still no dynamics, the first hit seems to get lost and then improves with the second. Its as if the latency has suddenly increased.

MDM cannot be possibly the cause of this - after applying setting from MDM to MegaDrum, MDM has no affect on triggering and you can actually exit MDM after applying settings to MegaDrum. If you're having problems with triggering, create a separate topic and describe the problem there.

Re: New Megadrum Manager 20170501

PostPosted: Wed May 03, 2017 8:02 am
by karlarsch
Options.tiff
Hi Dmitri, excuse my delay, but had to work....
reverted to MDM 5/16 with corresponding firmware, everything is fine again. My MCU is STM32F103RCT6, i attached the options-screenshot, but i donĀ“t think that the problem is there. When i transmit single instruments, everything is fine, but get all or send all ends in a sys-ex error. I changed USB-cables and SYSEX-delay, but no luck. Will have to do some more research, best regards.
Karl
P.S.: Attachment can only be seen in Safari, not in Firefox (God only knows why).

Re: New Megadrum Manager 20170501

PostPosted: Wed May 03, 2017 8:56 am
by dmitri
I do almost all development on Macbook and so most of the testing is done on Mac OSX. I'm on OSX 10.11.6 and MDM works fine here.

Re: New Megadrum Manager 20170501

PostPosted: Wed May 03, 2017 9:43 am
by stefan1982
I can replicate some of the SysEx Errors..
I *suspect* that you have "Live update" on, and trying to send data more than one time. Using another "Send all" to MD, or something? Could that be it?
It noticed more SysEx errors than with the former firmware/MDM, but that is most likely because I am trying to send data to MD using "Live updates" and with the "Send", or "Send all"..
See if it helps, once you'll be bit more patient between send/reading from the MD inside MDM.