New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it possible to quickly bypass a single plugin #52
Comments
I think I'll add some menu options for this and other useful functions as well. |
+1. it would be even nicer to have one button that's always visible for this. |
+1, very important and seems pretty straightforward too |
👍 that would be very useful with FX to quickly switch between original sound and modified sound. |
+1 |
This sorta now possible with the new plugin skins. |
a small "B" button on the side of dry/wet (colored red/green) ? |
having a knob isn't the same as having a bypass button, it takes more time/precision, it's harder to restore the original wet/dry value and the knob interaction in carla isn't very good to begin with. a bypass button, preferrably next to (or even supplanting) the power button, is still a must. For touchscreen interaction though it shouldn't be too close in case you accidentally press the power button instead of the bypass. |
the current Carla UI is not meant to be touch-friendly. I can make the dry/wet knob clickable, so that: how's that sound? |
is the dry/wet knob visible in the 'rack' or only when the ui of a particular plugin is open? imo, what's most useful is something that can be clicked from the rack. otherwise it sounds good. |
the dry/wet is visible on the rack, yes |
I'm fine with that in theory but I am worried that i will accidentally scroll the knobs instead of clicking then. If you implement this then we can test it. |
double click maybe? |
double click sounds good to me. |
Double click? Ugh. +1 for separate button. Also, while touch and mouse certainly need different things to be taken into consideration, a rack-type UI where there's a single row of controls per plugin can be accessible to both without much extra effort, can't it? |
I'm not interested on making the default Carla UI usable on touch interfaces. |
Fair enough, it's your call after all. Double click, while generally quite a disagreeable interaction, is still better than nothing :-) |
Chiming in here rather than creating a new issue, it would be great to be able to change the wet/dry level with a MIDI signal (just like with plugin parameters)! My use case is guitar + MIDI footswitch, and at the moment there's no easy way to quickly toggle an effect. |
I agree with egasimus. Double-click is better than nothing, but in the future I'd suggest not discounting touch interfaces; having touch-friendly audio apps could end up being one of LAU's most unique points (speculation) and having to develop distinct UIs for each interface is inefficient. |
You can already control the dry/wet via MIDI CC, it's just not documented yet (carla keeps slowly changing so I'm waiting to finish 2.0 before doing any docs). "breath" (CC 2) controls dry/wet activate/deactivate is the only "parameter" that can't be automated because doing so is not RT safe. |
@falkTX that works great, but would it be possible to assign different CC messages for individual plugins? Example: tremolo + delay, tremolo's dry/wet is on CC 12, delay's dry wet is on CC 13, send CC 13 0 to bypass delay and have tremolo still running (rather than CC 2 0 and bypass both). Something like how it is possible at the moment to specify the channel for breath/volume/balance, but being able to select the CC note for each of those, for each plugin? |
btw, you can now right-click a plugin slot and click "bypass". |
if bypass is checked and you uncheck it, the dry/wet knob is restored to 100% wet. The value should return to what it was before bypass was checked. |
Just a couple of questions: Regarding: Also when bypass is selected does it remove the processing power consumed by the plugin? Thanks |
bypass does not stop from processing the plugin, because we want click-less dry/wet changes. |
ah ok, yep will use the disable options (unfortunately this crashes all my plugins but that's fine for now) |
Hi Got my VST2 plugins to stop shutting down when I "I/O disable" it (commented out the timeout code for now). Probably a strange request but anyway to automate the I/O disable button (some midi message or sysex?) Thanks |
there's no way to automate it via midi messages because disabling the plugin is not a realtime operation. |
no worries, nah it's not important. thanks |
Hello falktx much respect first of all!! You are really making a big difference in linux audio world and, thanks to you I never need windows anymore!!! Whoop whoop.. When I am in Berlin I want to meet you. Anyway I still have problems controllign the dry wet knob with my midi controller.. I'm shure it's something simple I'm doing wrong.. I patched it up in the bay and set control channel to 2 but don't understand how to link it to a specific controller knob on my midi mixer yet??? Nothing happens |
the dry/wet knob is currently fixed at CC#10 ('breath'). midi-learn for general parameters is not implemented yet, but it's coming very soon. |
I still don't understand it?? How can I use one knob on my midi mixer for the wet level of one plugin and another knob for the wet level of another plugin?? Already looking forward to the update :) |
you send them to different midi channels. |
Ok I really feel like a noob now.. Let's see how she goes |
Lol found it :) To everyone who has trouble with this watch this vid --> EDIT: Only found how to map different parameters but not the dry wet level because my controller doesn't have cc#10 on the knobs where I want it. Well I guess I'll have to live with it until carla 2 comes out :P I tried to use MapCC to get cc59 to control cc10 but didn't work :( |
@falkTX how does it work in continuous rack mode? if i set the second plugin to channel 2, it does not work. i guess because the first plugin takes it all? |
yes, first plugin takes it. if one plugin has no midi outputs, then the next one will receive the same midi data as the previous one. |
and if there is a midi output? |
then the midi ouput is the midi data for the next plugin |
Hm, this isnt working. I have a midi controller, send cc2 on channel 1 and 2 (different knobs). I have loaded two times calf reverb (for testing). First one set to midi channel 1, second to midi channel 2. I use carla in continuous rack mode. When i send on channel 1, i can bypass reverb 1. but channel 2 cannot bypass reverb 2. |
@falkTX It is working with ZynReverb and TalReverb. So there is only a problem when the plugin has a midi output |
I can confirm I was successfully able to use the OSC "/set_active" command today on Windows 10. |
falkTX, with all due respect for your fantastic plugin... which is great... audio engineers need to a/b bypass. Audio enthusiasts want to. It is good to have the bypass function in the right-click menu. However, since it's not hard to do, and nobody seems to have submitted a patch, it's now on my stack of things to do. Thanks for this awesome software, sir. |
Now it's possible to 'disable' a plugin. It would be nice if you could bypass a plugin in the same fast way.
The text was updated successfully, but these errors were encountered: