Ok great , good to know that mechanism is in place
unfortunately this cannot really remove the need for snapshots though, especially with the addition of the pedalboard.. as an example, lets say you wanted to switch amps from a lead to a clean sound:
you would have to send midi commands to disable the input of the delay, change the amp, bypass the pedal/s and let's say, enable a chorus.
Most midi controllers will send a program change message.. some of them may also allow you to simultaneously send a couple of CC messages.. the issue though is this:
To execute all those commands takes time.. and the entire purpose of doing it is to remove the time delay incurred by changing presets (or the unprofessional sound of your trails cutting off) and the associated load of clearing and reloading all the assets that make up the sound.. Midi is old.. it cant supply data quickly enought to effectively hold the snapshot information in place of that feature in the software.. its not perfect to use snapshots, as it requires a lot more planning to create working sets of sounds and often needs you to load several instances of effects that are not always active, resulting in additional cpu power needed to run the "superpreset" that holds all the elements.. but it does seem to be the solution adopted by the majority of people making these type of plugins and i assume that is just because doing the full spillover feature on preset change is hard to pull off.. one thing i dont understand though, and Mike maybe you know the anwer to this.. whenever I see users request the full spillover feature i see the same reply time and again from devs, that it would require huge CPU and RAM overheads to do, you have to run everything twice etc etc and therefore its not possible.. however.. in the one and only instance that i am aware of where this feature is actually implemented (fully spillover independant of settings or modules loaded) is in the Overloud TH-U plugin & standalone. This plugin, whatever you think of its sounds or whatever (that is not relevent to this point) also happends to be one of, if not THE lowest resource requirement amp sim plugins in existence. It literally runs on the oldest potato of a pc with hardly any cpu requirements and does full spillover on preset change... its really confusing to me to see that. I expect its som kind of fundamental architecture thing that has to be part of the initial design to be efficient.. but it flies in the face of all the assertions that its impossible to do. I would be more than happy with just a snapshot implementation dont get me wrong, but its a point of curiosity that i do not see discussed at all and thought that, since in my opinion S-gear is already the best sounding plugin of this type available, it should be really worthwhile to also look at these kind of features that hugely enhance the usefulness and application of those sounds in different situations.. again i want to state, I am a huge fan of this product, and the philosophy you have employed in its design is really very wise, sound and feel first.. but as the features keep rolling in and it becomes almost capable of being the entire signal chain in one standalone app, it is to these finishing touches that we have to look now to allow S-gear to start becoming the tool for all occasions. I guess I am just interested in whether these issues are on a roadmap for the product, as this will drive my personal decisions regarding how i will use it in future.. I am aware that you can combine s-gear with other products and manage your presets and switching from a 3rd party host, have tried that and understand its limitations.. but to be honest, its super annoying and I will always in the end go back to the all-in-one solutions because its just easier and more reliable. even if *shocking i know* it doesnt sound quite as good....I guess the dream is the S-Gear sound with any solution for seamless switching, all in one standalone..