Megadrum intermittently stops transmitting

[DonGui]

Same question as for jaidhar: when you plug it and just leave it idle for 10 or more minutes 1.5-2 hours and try to communicate with it after that, does it respond?

If I power up the computer, launch everything in order to play but do not touch a thing, than come back 2 hours later, the problem has occured in the meantime and I've lost connectivity with MD.

[airflamesred]

You guys must be doing something wrong, I have mine on for 12 hours some days and I've never lost conectivity - ever.

[dmitri]

Same question as for jaidhar: when you plug it and just leave it idle for 10 or more minutes 1.5-2 hours and try to communicate with it after that, does it respond?

If I power up the computer, launch everything in order to play but do not touch a thing, than come back 2 hours later, the problem has occured in the meantime and I've lost connectivity with MD.

1. Is MegaDrum USB is still in the list of devices when it happens?
2. If you re-launch MDM when it happens (without reconnecting MegaDrum) can you re-establish communication?

[DonGui]

1. Is MegaDrum USB is still in the list of devices when it happens?

Once the midi stops getting to AD2, Megadrum is still in the list of devices. (I should say that I only left the computer powered up and came back periodically, so I wasn't there at the very time the deconnexion occured. So I cannot say if maybe megadrum was deconnected then reconnected automatically)

2. If you re-launch MDM when it happens (without reconnecting MegaDrum) can you re-establish communication?

If I do so, MDM is able to establish communication with MD, I tried doing a "get all" which worked correctly. AD2 doesn't get its communication back though, I still have to do the usual trick in AD2's settings. (MDM wasn't open at the time of the loss of connectivity with MD. I only opened it afterwards. As previously stated, if MDM is opened at the time of the deconnexion, it loses connectivity. I don't remember the details of its behaviour though, if needed I can do another test with MDM opened at the time of the deco.)

Thanks !

[dmitri]

For troubleshooting I can create a test firmware version which will be showing on the LCD number of seconds since the last time MegaDrum firmware restarted. Shall I?

[dmitri]

Anyway, this is a test firmware:

test_firmware.zip

When LCD is in VU-Meter mode it will be showing a number of seconds since the last time the firmware restarted. It can show maximum 65535 seconds (~18 hours).
You can use it to check if the firmware restarted for any reason after MegaDrum was powered up.

[Tatoupulus]

Hi Dmitri,

sorry for answering late....

no issues with MDM closed till now - I will keep testing it

Why didn't you update it there if you were still having the problem?

The loss of midi-connection occurs very seldom to me - also I was/I am thinking of my usb-audio-interface to be causing this. On the other hand I never had this with my roland-module. To restart my audio-interface fixes the problem...
I never got a "disconnect" - "connect" sound in windows. So for me my MD was not responsible for that. But now we have different people with that issue...


I found my megadrum-display do dim sometimes (The VU-meter is getting lucent - touching/moving the "power-toggle" got the vu-meter working normally again.) Any ideas for that behaviour?
So maybe my megadrum restarts sometimes or stops because of an internal connection failure.
I will first open the MD and fix all connections and then test it with your test-firmware.

I appreciate MD and your affords to help us!

Greetings

T.

[Tatoupulus]

again:

installed the test-firmware

after 2300 seconds I got the issue. No restart by MD! The counter was still "alive".
MDM was still receiving midi!

I went into AD2 and changed the latency from 2 ms to 4 ms and AD2 started working again.
So resetting my asio-driver was again the way to fix the issue.

So I guess - as I wrote above - MD is nor responsible for the issue!
Maybe I had this never before I went to the MD, because of a higher latency in my asio-driver in the past. (When I changed to MD I forced the asio-driver to work with the lowest latency possible).

I think I will go and buy a new asio-interface with a win10 certified driver.

So guys - please try resetting your asio-interface if it happens- It would be interesting, if this is the reason for your probs too.

Regards!

T.

[dmitri]

Could it be related to Windows "power save" settings?

[Tatoupulus]

Could it be related to Windows "power save" settings?

I don't think so - my screen was on and I don't have sleep-options on.