Need your help! --- USB MIDI Problems ---

[dmitri]

I cannot tell without being able to reproduce it.

[dmitri]

I just finished soldering one board, with exactly the same MegaDrum and USB MIDI firmware as in yours, and I could not re-produce your problem. Over USB all 'notes on' are followed by 'notes off' on all inputs.

At this point I cannot think of anything why you might be having the problem. If there were a hardware or firmware problem with the PIC, USB would've not worked at all. If there were a hardware or firmware problem with the Atmega, it would've been there with the standard MIDI as well.

Do you have anything connected to the standard MIDI Out socket when you test it over USB?

[MarcMooga]

I have nothing connected to the standard MIDI Out.
Only 1 Pad and USB is connected while testing.
Same results also with different pads.

[dmitri]

Since you are sure you cannot blame your PCs/OSs/configuration I can only suggest you to send the board back for testing. PM me for this.

[edrumor]

Hi dmitri!

Received friday the 32 channels megadrum, I´m having the same issue than Marcmogaa.
The MD its showing much latency with the MIDI built in USB, it´s unplayable.
I have tryed first PC one with WinXp 32bits and TerratecEWSMT88 with ASIO drivers, the Midi usb has delay.
The second PC Win7 64 bits RME Fireface 800 FW with ASIO at 48/64/128 samples audio latency and there are a latency playing on MD.

Both have worked perfectly , with rear Midi out connector attached to correspondent MIDI IN audio interface.
Only 1 pad conected all the time, a Roland pdx8.

[dmitri]

I'm waiting for the MarcMooga's board to check. Are you also seeing missing Note Off messages?

[edrumor]

There are activity in 2 channels, 10 & 16, when I shot a pad .

Cc reset in channel 16 , note off, note on in loop mode.

And sometimes only messages note off- note on on channel 10...

midiox.JPG[/attachment
[attachment=0]noteoff.JPG

[dmitri]

MegaDrum doesn't know CC Reset and cannot send it. As far as I can see you might have created a loop in MIDI by configuring MegaDrum both as input and output - check in View->Port Routings.

[dmitri]

While I haven't received the MarcMooga's board I did 3 more tests using exactly the same boards as yours with exactly the same MegaDrum and USB firmware. The test is done on a laptop with built-in sound card and ASIO4ALL and using Cubase.

Time between I hit a pad and the sound signal at the headphones out jack using USB MIDI:

MegaDrum-via-USB2-vai-Cubase-via-ASIO4ALL10ms-latency.png

It is 18ms.



Time between I hit a pad and the MIDI signal at the MIDI Out:

MegaDrum-to-MIDI-latency.png

It is 4.5ms



And just as the reference I used my Novation Remote 25 keyboard to measure time between MIDI Out signal out of the keyboard and the sound signal at the headphones out jack:

Novation-MIDIOUT-via-Cubase-via-ASIO4ALL10ms-latency.png

It is 14ms



As you can see out of 18ms for the total latency over USB MIDI, 14ms are contributed by USB-MIDI driver/OS(Windows 7 64bit)/Cubase/built-in sound card with ASIO4ALL. ASIO4ALL (if it can be trusted) is configured to have 9ms latency leaving 5ms to USB-MIDI driver/OS(Windows 7 64bit)/Cubase.

I doubt very much I will find anything different once the MarcMooga's board arrives since it is identical to the one I did the test with.

[edrumor]

You are absolutely right dmitri. Midi ox was configured bad in loop mode.

It was a mistake from me , I think its more a problem setting up the module for trouble the correct pad sensitivity for me.
sorry, you are in the rigth way.
Thank you so much to do the tests, and for your time.