Just like how the limiter has an automatable bypass.
I think it would be interesting to turn a bunch of effects on and off at once and still pass signal. You can use the matrix mixer, but I feel would allow for a different kind of organization and layout. I feel this functionality would complement the matrix mixer rather than overlap.
Hi Jonah,
Please propose how you think this might work.
For me the issue with adding "bypass" has been that it doesn't always make sense from a gain structure point of view. Bypassing some contraptions might give a really quiet signal OR A REALLY LOUD ONE and this has never seemed to me to be a desirable thing. On other cases it's unclear what bypass even means (what does it mean to bypass a crossfader?) -- are you imagining that this is a global feature, or something that's added to more contraptions.
Sometimes an A/B function would be nice, but you can achieve this with presets.
there are vsts which either have no bypass function or that ( because of some design superficiality) don't release cpu consumption when they are in bypass mode.
A contramption bypass (remoteable) button would be very useful.
regarding gain difference, this is something to manage in any bypass situation so it shouldn't be the reason not to make it.
The gain issue is a good one. I wasn't thinking about bypass so much as a utility or AB function as much as a live performance one. Where you could either use the metasurface or automation to dynamically change the sound.
I got the idea because I was using the bypass option from the context menu and then ctrl+z to undo it while using the different looper/recorders for rhythmically cutting up the sound.
I was imagining it as a button on the contraptions. If it worked just like the right click bypass option works, except you don't have to worry about undoing it that would suit me fine.
As a for instance, I've been using PulseCombs a lot and if I want the un processed signal only I have to use a lot of mixer channels and wires. I don't mind starting from scratch with the different types of mixers and using presets, but if I'm playing around and decide I want the unprocessed sound all the wires can be visually hard to manage. I mean, if I'm going to use the matrix mixer I have to start with it as the center of my project.
I guess in the interest of user ear safety, :) mixers, cross faders, etc., maybe just use the first inputs either stereo or mono or not have bypass. I'm not sure how the bypass context menu works now because I've never bypassed a mixer. :)
Luca wrote:
>>> there are vsts which either have no bypass function or that ( because of some design superficiality) don't release cpu consumption when they are in bypass mode.<<<
Releasing CPU is a separate issue. Do you really expect a bypass to release CPU? What if it's something like a delay or reverb? Do you expect the tail to get messed up just because you bypassed it?
Personally I would *not* expect bypass to have any impact on CPU. It sounds like you're asking for "disable" not bypass.
Another point: you can already implement bypass type behavior using Matrix contraptions or crossfaders, with full control over gain structure.
>>> regarding gain difference, this is something to manage in any bypass situation so it shouldn't be the reason not to make it. <<<
Sure it's something to manage (usually by having separate gain for bypassed and non-bypassed modes). I am not keen to add a separate "bypassed gain" to every contraption -- can you think of another solution to managing bypass gain?
Jonah wrote:
>>> I wasn't thinking about bypass so much as a utility or AB function as much as a live performance one. Where you could either use the metasurface or automation to dynamically change the sound.<<<
Just use a crossfader? If you want fast switching with the Metasurface I think that would be better addressed by having a separate mode for each parameter in the metasurface: interpolated or switched -- this has been suggested before and I would like to do it.
As an aside, perhaps "Bypass" in the patcher should be called something else like "Route around"
this is an interesting point of view ( which I don't agree about) from a respectable vst developer:
http://www.kvraudio.com/forum/viewtopic.php?p=5206387#5206387
If this is true and it is a potential trend in the vst developer community, then I think missing the chance to bypass a contraption would really become a problem.
Hi Ross! I am building a loopstation using AM and Mobius where i can map parameter controls for effects on both the input and output to any slider i choose on a Quneo, and i can do it in real-time. I have used Mainstage, Logic, Ableton, Logic again (using environment), then finally audiomulch combined with Bome's Mid Translator. Every time i switched it was because of efficiency or stability issues.
In Ableton Live i can disable plugs, or plugin chains so that they stop using CPU, so i can just add as many options as i want, but in Audiomulch i quickly reach a limit. Especially since i have keep the latency at a minimum for live looping.
How about an a setting to bypass (or disable, as you suggested) effects when they are not recieving any audio for a certain time. In that situation you would use a gain/x-fader/matrix like normal, but the bypassed effect would stop using cpu after say 5 seconds without recieving any sound.
Or you just add a "disable" parameter for all plugins. It would do exactly the same as bypass, eccept you could controll it with midi.
A solution to this problem would be worth everything for me! Thanks for a great software!
/ Jonatan
A
Hi Jonatan,
Thanks very much for your feedback. When the time comes to revisit this issue I will consider it.
Thanks,
Ross.