COCKOS
CONFEDERATED FORUMS
Cockos : REAPER : NINJAM : Forums
Forum Home : Register : FAQ : Members List : Search :

Go Back   Cockos Incorporated Forums > Other Software Discussion > WDL users forum

Reply
 
Thread Tools Display Modes
Old 12-11-2020, 01:40 PM   #1
Nonlinear
Human being with feelings
 
Join Date: Apr 2018
Posts: 391
Default Bool value of "Bypass" - industry convention?

Is there any convention on what the bool value of "Bypass" should be?

In some plugins Bypass value of TRUE (1) means Bypass is ON - i.e, plugin processing is OFF

In other plugins Bypass value of FALSE (0) means the plugin is OFF (bypassed)


Which is "more correct"?

Last edited by Nonlinear; 12-11-2020 at 05:42 PM.
Nonlinear is offline   Reply With Quote
Old 12-11-2020, 02:26 PM   #2
DarkStar
Human being with feelings
 
DarkStar's Avatar
 
Join Date: May 2006
Location: Surrey, UK
Posts: 18,987
Default

To me,
If a plug-in is Bypassed, then the Bypass state should be TRUE.
__________________
DarkStar ... interesting, if true. . . . Inspired by ...
DarkStar is offline   Reply With Quote
Old 12-11-2020, 06:15 PM   #3
Nonlinear
Human being with feelings
 
Join Date: Apr 2018
Posts: 391
Default

Quote:
Originally Posted by DarkStar View Post
To me,
If a plug-in is Bypassed, then the Bypass state should be TRUE.
Yep, that makes sense. The parameter "Bypass" is On when TRUE.

What had me confused was testing in Reaper. The logic of the plugin "On" checkbox is opposite the bool parameter labeled "Bypass". When the Reaper plugin checkbox is checked (true) the plugin is processing but the state of that parameter is FALSE (0). In other words, Reaper's checkbox is displaying "Processing", not "Bypass", status.

It is all correct but for some reason messes with my head!

Last edited by Nonlinear; 12-12-2020 at 12:37 PM.
Nonlinear is offline   Reply With Quote
Old 12-11-2020, 08:58 PM   #4
Fergler
Human being with feelings
 
Fergler's Avatar
 
Join Date: Jan 2014
Posts: 4,544
Default

Me too, when I automate a bypass I get tripped up every time..
__________________
Check out my hip-hop, funk-rock band Theatre Crisp
Fergler is online now   Reply With Quote
Old 12-13-2020, 07:34 AM   #5
Bobflip
Human being with feelings
 
Join Date: Nov 2016
Posts: 341
Default

I have this in a //TODO: in something I'm working on now. Bypass being active when true and hence not processing the audio data makes perfect sense, but then you have to remember that your button will show as active when the plugin is inactive or have a different image for the button with the states swapped. In the meantime I currently have it renamed to kActive.
Bobflip is offline   Reply With Quote
Old 12-13-2020, 10:25 AM   #6
Nonlinear
Human being with feelings
 
Join Date: Apr 2018
Posts: 391
Default

Quote:
Originally Posted by Bobflip View Post
I have this in a //TODO: in something I'm working on now. Bypass being active when true and hence not processing the audio data makes perfect sense, but then you have to remember that your button will show as active when the plugin is inactive or have a different image for the button with the states swapped. In the meantime I currently have it renamed to kActive.
I tried to eliminate confusion by labeling my Bypass button/parameter as "Process" instead of "Bypass" (similar to your kActive). When that parameter, automation data, etc., shows "On" (1/true) it means processing is On. No ambiguity whatsoever. If(Process) - do something.

Some people didn't like that. They want to see a "Bypass" button because that's what they're used to. Just looks funny to me to have something "On" making it "Off"...

Last edited by Nonlinear; 12-13-2020 at 06:01 PM.
Nonlinear is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:18 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.