TOPIC: New Features requests!

New Features requests! 1 month 1 week ago #24940

I know this was talked about some years ago, but what is the current thinking re: preset "snapshots" ? it seems that, in the absence of deley/reverb trails across preset changes, this is a sorely needed feature for live use to allow that to be done... of course we will also need a bypass option for room and delay racks that just mutes the input and allows the trails to continue. this seems impossible at the moment so we cannot even midi mute them and allow the tails to finish (unless i am missing something there..) the trails really are a huge issue for live users, I am that 1 feature away from making s-gear my live rig. Is it still on the roadmap? one other idea I would like to field is something i have seen done before, which is that if you have the same or similar reverb/deley settings across 2 presets, when you change between those it will just leave them intact and move knobs rather than clear and reload them, thus providing the spillover feature without requiring overhead of running everything twice.. just a thought..
SIGN-IN TO REPLY

New Features requests! 1 month 1 week ago #24941

Ohh and any chance of a clean boost pedal? :) or maybe just a 1:1 option on the compressor...
Last edit: 1 month 1 week ago by stusaysmoo.
SIGN-IN TO REPLY

New Features requests! 1 month 1 week ago #24942

And what about a proper parametric eq rack?
SIGN-IN TO REPLY

New Features requests! 1 month 1 week ago #24943

stusaysmoo wrote:

we will also need a bypass option for room and delay racks that just mutes the input and allows the trails to continue.

This is possible via MIDI CC message. If you send a value of 0.5, then the delay/reverb input is muted allowing the tails to continue.
See page 70 of the User Manual
  • mike
  • mike's Avatar
  • Offline
  • Administrator
  • Posts: 2299
Last edit: 1 month 1 week ago by mike.
SIGN-IN TO REPLY

New Features requests! 1 month 1 week ago #24944

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..
Last edit: 1 month 1 week ago by stusaysmoo.
SIGN-IN TO REPLY

New Features requests! 1 month 3 days ago #24949

I still like my mock-up from years ago :)

www.scuffhamamps.com/forum/8-wishlist/90...-scenes-or-snapshots

But, programs like Gig Performer solve the problem of snapshots.
  • kierank
  • kierank's Avatar
  • Offline
  • Tone Master
  • Posts: 354
SIGN-IN TO REPLY

New Features requests! 1 month 2 days ago #24951

Hey, um. that's really not the case i'm afraid, snapshots in all the hosts currently will cause dropouts in the audio and the pedalboard currently does not retain the on/off status of the pedals in cantabile or reaper when changing snapshots.. its pretty much unusable for anything serious, you are better off not bothering and just using standalone with presets.

The snapshot feature (or delay spillover on preset change) is sorely needed to allow truly professional sounding seamless changes between multiple sounds.
Last edit: 1 month 2 days ago by stusaysmoo.
SIGN-IN TO REPLY

New Features requests! 1 month 2 days ago #24952

Gig Performer is specifically created to allow a lot of flexibility with plugins. The main preset concept is called a “rackspace”, where you can combine S-Gear with other plugins. You add “widgets” to control specific parameters in any of these plugins e.g. you can add button/switch widgets that are mapped to S-Gear’s pedals on/off.

Then the rackspace “Variation” is like a snapshot of these widget settings. So you can create e.g. Clean and Crunch variations that will switch the pedals on/off and any other plugins/parameters that you have mapped to a widget. You can even trigger the special S-Gear bypass setting for DelayThing and RoomThing so that the tails continue.

If you want a more substantial change (e.g. to change amps) you create a separate rackspace. Gig Performer allows spillover between rackspaces, so you can achieve smooth transitions.
  • kierank
  • kierank's Avatar
  • Offline
  • Tone Master
  • Posts: 354
SIGN-IN TO REPLY
Time to create page: 0.050 seconds
Powered by Kunena Forum