PLEASE let us specify the "post-crash" patch that loads after reboot

Picture this: I’m playing live on stage in front of 1000 people. My QC crashes with the “Something went wrong” red box. It reboots (30+ seconds). Time of critical.

The QC (by default) reboots to the FACTORY PRESET setlist, patch 1A “Brit 2203”. This means I have to MANUALLY get on my hands and knees and touch the screen, scroll through folders/Setlists, to get to my ACTUAL patch to continue the show. These are critical seconds that aren’t necessary.

Devs, please fix this by either:

A) Allowing the user to overwrite the “Factory Presets” folder/patches (i.e. let me put my own patch on 1A) or;

B) Allowing the user to specify a ‘default patch’ (i.e. Setlist 4, Patch 2D) that loads upon startup post-crash.

I know it seems trivial, but when you have a crash during a gig, every single second wasted is excruciating.

This makes sense, unit bounces to last patch used or predetermined patch when powered on (not factory preset under any condition) coming off of Fractal FM9 it always rebooted to last patch used…

Unless the designated preset crashes the device, then won’t you be stuck in an endless loop of crash, recover, crash?

If they allow us to specify a “post crash” patch, then no. For my use: I have one patch I use live, and it works 99% of the time (high DSP), but the 1% is a catastrophy.

So I have a SEPARATE PATCH that has LOWER DSP which I would designate as the “post crash” patch. This way, if my main patch crashes, it reboots INTO the “safe” patch… which is 80% of what I would want live, but would get me through the rest of the show.

1 Like

Understood, but the only way for Neural to guaranty (or as close as possible) a preset doesn’t crash is to use a factory preset. You’re an adult sure, but I would guess Neural doesn’t want adults posting about how their QC is bricked and the only way to recover is a factory preset (now THAT would really suck during a show, more than an extra minute of menu navigation).

I understand your request, but it seems to be an edge case, and I also understand why Neural would want to avoid it.

1 Like

I’m sorry some user’s QCs are crashing. This is the most stable piece of electronic gear I’ve ever owned.

1 Like

Its my understanding if a preset exceeds available processing resources, the Quad Cortex will automatically disable specific utility blocks to preserve the primary signal path.
This is according to the Quad Cortex 3.0 User Manual, this similar to what Fractal does, so if a patch is crashing it should self correct unless if the crash is occurring from a tcp or midi timeout or a sw bug…