Update 20170501

[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.

"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"

I understand that and I hadn't flashed MD with my settings hence I thought that MDM had some dependence, but of course it does not. However the symptoms described above still stand. I will revert to the previous version just to check.

Reverted to 413 with517 MDM no problems

[dmitri]

Reverted to 413 with517 MDM no problems

What are 413 and 517?

[sbonasuk]

version 20170413 MD and 20170517 MegaDrumManager

[dmitri]

So the problem you have is with firmware version 20170501, not with MDM version 20170501.
I have a guess why you might be having problems with firmware 20170501.
In this new firmware version, to speed up Sysex communication, upon receiving a MIDI message over USB, MegaDrum disables ADC for ~100ms to prepare and send e reply as fast as possible. You normally don't end any MIDI data from a PC to MegaDrum. You only send MIDI to MegaDrum from a PC to configure it. I suspect that you somehow route some MIDI from a PC to MegaDrum. With this new firmware it will cause periodic ADC disabling and as a result missed hits or apparent latency.

[sbonasuk]

Agreed; my error was the assumption of a link between MD and MDM as they were updated at the same time. However 20170501 (MD) which as you describe accelerates the Sysex messages does indeed create missed hits and latency issues. To detail my system MD to PC MDM configured to Addictive drums 2 out to a Focusrite Solo and then to a headphone amp.. Is this issue solvable or configurable or am I doing something wrong?

[dmitri]

Really, there is nothing to fix in MegaDrum - you just need to make sure you don't send any MIDI to MegaDrum. You either created a MIDI loop somewhere in your software setup or some software is sending MIDI data received from MegaDrum back to MegaDrum.

[sbonasuk]

Based on my setup any clues were I should look is AD2 the culprit.

Airflamesred does AD2 send a MIDI signal back to MD. Is the MD options menu where I swhould be looking?

[airflamesred]

Based on my setup any clues were I should look is AD2 the culprit.

Airflamesred does AD2 send a MIDI signal back to MD. Is the MD options menu where I swhould be looking?

Well I can't see any need for it to do so. MD is a controller like a keyboard. Uncheck the midi thru maybe?

[sbonasuk]

Un-checking MIDI thru and changing the MIDI in/out ports in MD from USB MIDI to MIDII2 and the active MIDI ports in AD2 from MIDIING2 to USB MIDI.

Thank you so much for your help guys.

Could you please possibly explain why I had to do this.