Does the pause when switching patches get on your nerves? Yes, I know you can work with scenes, but then you have to build a thousand functions into a preset, which just makes it cumbersome. The Nanocortex shows how cool it is to just be able to work with presets.
Can’t you just build it so that only two cores (the top two rows) are used? This would make it possible to preload the next preset into the other two cores.
In order for the QC to know which preset should be recalled or preloaded next, you would have to modernize the QC’s grotty setlist construct at the same time. The implementation of the VST host Gig Performer could be used as a guide here. There, presets and setlists are completely separate. You build each of your songs in such a way that you tell the tool which parts it consists of. Each part can then be assigned corresponding presets, midi commands and the like. If something needs to be changed in a preset in a song part, a scene attached to the song part can record the changes to the patch. Any setlists can then be created from the songs.
The QC would then finally be 100% user-friendly, not only in sound creation but also in live operation. The dear effect device programmers like to lose sight of live operation because it is more important to program the 200th echo.