HEEELp! Ssys Chej Error - bricked G2X?

jamos

My G2X just crashed, again, due to bad data sent from my MPC - long story - but this time, it is down for the count. Sys Chek Error, ready for update.

I have FUCKING WEDDING to play in a week, and my backups are old.

Right now I am fucking frazzled but I need to get this going FAST - can anyone help? (I have read jack Hertz's post on this but it has been so long I can't even remember how to do the update.)

Will be scouring the forum for tips... any help is appreciated! jimjohnson59@protonmail.com

jamos · Posted: Sat Jul 02, 2022 5:59 pm Post subject:

Whew! I am safe, but my heart is still pounding.

In a nutshell - junk data from my MPC crashed my G2x, HARD. As in it wouldn't boot. Fortunately I remembered how to install the OS and, after an initial failure it came up again with no apparent data loss.

I will have a full report n the full story of this bullshit tomorrow... right now I need to do some backups. And have a drink.

blue hell · Posted: Sat Jul 02, 2022 7:28 pm Post subject:

Pwew - lucky escape!

jamos · Posted: Sun Jul 03, 2022 12:01 pm Post subject:

Ugh. Several crashes and reboots later, I still don't know what's going on.

First - this is caused by specific data strings sent from the MPC Live. The weird thing is that it only happens when moving between specific performances, and it is completely repeatable when moving between those performances. In most cases the instrument is fine after a reboot, but in this particular case it wipes out the OS - every single time. (This problem cropped up when we rearranged our set for a wedding we're doing next weekend.)

The MIDI data that causes the problem is below:

blue hell · Posted: Sun Jul 03, 2022 2:52 pm Post subject:

Could it be that the MIDI is too fast for the synth?

jamos · Posted: Sun Jul 03, 2022 3:07 pm Post subject:

Yes, that is what it is. Basically it seems that any MIDI channel data that is received immediately after the program change, causes the crash. In fact, I am operating on a new hypothesis here. The performance name on the G2 changes before the lockup, so that indicates that the patch is at least partially loaded. I have a MIDI zone in this G2 perf that routes channel 6 data from the MPC to another synth. I have turned that off and it seems to work. I have to do a lot of testing to be sure (I've thought I had the fix before). In fact what I am doing now is disabling that zone in the initial variation (by setting the input to Keyboard), and then switch to the correct variation just before real data starts arriving from the MPC.

blue hell · Posted: Sun Jul 03, 2022 3:58 pm Post subject:

Fingers crossed then - but seems to go somewhere :)

jamos · Posted: Tue Aug 16, 2022 10:15 pm Post subject:

To cap this off correctly, if a bit late: it seems that the MPC sends an all notes off message and sustain off message immediately after each program change. By filtering these out... everything works correctly.

blue hell · Posted: Wed Aug 17, 2022 6:44 am Post subject:

Good that it is fix(able/ed) :')

And how did the wedding thing go?

Electromagnetic Wave · Posted: Thu Sep 08, 2022 4:27 pm Post subject:

Hey! I had a similar issue with an old sequencer. The Yamaha RS7000 send MIDI #cc 64 and 66 to MIDI output everytime the'Stop" button is pressed.+ the RS7k send continuous Real Time MIDI message. I no longer had bugs with my heavy performances when filtering these messages. I have also found that keeping G2 memory at a minimum of 20% helps stability for heavy performances.

Cheers