Drum Module Self-Shutdown in YARG - Roland TD50X

[buoyant nebula]

When playing a song in YARG, my module will sometimes try to shut down seemingly on its own, but will then hang on the "Shutting Down" screen on the module itself until I manually restart the module via the power button.

I haven't seen this behavior in any situation other than when I am playing a song in YARG (it's happened maybe eight or so times in the past month or two of daily play), and I haven't found any other people with the same issue with just the module itself through Google searches, both of which make me think it's some sort of miscommunication between YARG and the module causing this issue, but I don't use this module outside of YARG all that much, so I suppose its possible that it could be something going wrong with the module itself, albeit unlikely, given that the issue has consistently occurred while playing a song in YARG and nowhere else.

I've attached the Player.logs for two separate occurrences of this issue:

The first log is just a single module shutdown, after which I closed YARG and archived the log.

The second log (...2.log) is a module shutdown, followed by me rebooting the module via the power button without touching YARG, followed by another module shutdown, after which I closed YARG and archived the Player.log in addition to the Input Device log.

Potentially related bug: #1244315400859025471 message

here's the corresponding YARG log for the second occurance of the issue:

Drum Module Self-Shutdown in YARG - Roland TD50X

[buoyant nebula]

Here's one where my module spontaneously shuts down during a song, then when I go to manually turn it off, YARG crashes:

[green pasture]

i had something similar happen.

i was in the middle of a song. and had to go AFK to deal with some house issues.

it disconnected. and kept disconnecting on every pad hit

and when iw ent to profiles and tried to disconnect. it wouldn't.

but when i left profiles and came back i could reconnect.

TD11k here. so somethins up 🤔

log for that day

[buoyant nebula]

The fix for me if it keeps shutting down after restarting YARG, or even my computer, consistently seems to be to unplug the unit from the power, hit the power button to discharge everything I can, then reconnecting it to power

[green pasture]

thaaaaats about what i had to do last time

[buoyant nebula]

its like fixing a stuck dvd player/vcr lol. weird stuff

[green pasture]

sounds like an odd issue to fix/reproduce too

[green belfry]

@green pasture @buoyant nebula i'm late to this lol
there's no possible way for this to be a YARG issue, MIDI device APIs on the system don't have any sort of low-level control over device function like this

this is either a USB power issue, or some weird driver issue

all YARG can do is receive and send MIDI events, nothing more or less

[green pasture]

i'll blame it on windows then c: the USB is fine. i tested it............extensively

i just didn't know if it was yarg not recieving. cause the drums still worked and made sound and everything in my headphones and on the brain 🤷

[green belfry]

i don't mean something like the cable shorting out, i mean the kit isn't receiving enough power over USB to function correctly

the same issue plagues Alesis kits

[green pasture]

oh

its an 11 tdk. it has its own power supply

[green belfry]

and it's been the bane of my existence for nearly 4 years lol

[green pasture]

own 120v adapater and all that

[green belfry]

Alesis kits also have their own power supply, yet they're extremely sensitive to how much USB power they get

[green pasture]

i just never experienced the issue in all the time i've played clone hero/phaseshift/and score spy

so it hought it was a YARG issue possibly

thanks for the help tho homie c:

[buoyant nebula]

thanks! closing issue

[buoyant nebula]

I asked ChatGPT what could be causing this. I'm going to try setting this to disabled per its advice.

[buoyant nebula]

didn't do shit lol

[green belfry]

rip

[buoyant nebula]

it's a hardware issue

going to have to send in my module for repair

probably a faulty power supply. Thankfully there's a service center about 8 miles from me. Hopefully the wait time isn't too long. In the meanwhile I'll have to set up my old TD-17

[buoyant nebula]

as humiliating as this is to admit, there's a fair chance this could all be chalked up to a bad power cable (the TD50X has an internal AC adapter). The one I got from OEM is only a few months old and has been subject to absolutely no stress, so I never thought to check it. Was preparing to bring the module into the service center after work, but I realized this morning that I should at least try to rule out the power cable. Used a power cable from one of my work monitors. Could not for the life of me recreate the crash after several hours. Took the cable home, tried the monitor cable with all the pads plugged in. 2 hours later, no crash. Either the process of unplugging, packing up the module, and moving it in my car jostled a faulty connection or component around enough to make it look like everything's A-OK, or I've made a very rookie mistake. Fingers crossed that it just works now and there are no internal faults.

[green belfry]

nice!

it's always the part you never think to check lol