Change Bypass button to "Power"

Official support for: bluecataudio.com
Post Reply New Topic
RELATED
PRODUCTS
PatchWork$99.00Buy

Post

Hi everybody

What is the code that I have to add to the file layout.inc, or to titlebar.inc, for make reversed the bevaviour of the main Bypass button? I want to turn it to a "Power" button.
By default it turns off with a value 127, but I want to use 0 instead and 127 for turn on.

So far, I've changed it name on titlebar.inc to "Power" and the reverse="true" to "false" (which is the same that delete it).

Code: Select all

            <!-- Bypass -->
            <REPEAT count="$show_bypass$!=0">
                <IMAGE_PARAM_BUTTON param_id="dsp.input0" image="$THEME_PATH$/titlebar/power_button.png" image_hover="$THEME_PATH$/titlebar/power_button_hi.png"  image_focus="$THEME_PATH$/titlebar/power_button_hi.png" reverse="false" cursor="system::hand">
                    <TOOLTIP text="Power"/>
                </IMAGE_PARAM_BUTTON>
            </REPEAT>
Cheers

Post

I guess this is for MIDI & automation control, right? In this case, you may want to simply change the range of the Bypass parameter in the global settings from off=>on to on=>off.

The GUI is independent from external control, so removing the reverse attribute will simply revert the button (it will show power off when the plug-in is actually on), which is probably not what you want.

Post

That's right! Thank you!!

Post

It does work on the standalone version, but not with the VSTs (x32 or x64), and they are using the same global settings:
Bypass
· Control Min: On
· Control Max: Off

Post

I've downloaded the last VST demo, and I can confirm it: it ONLY work on the standalone, not with the VSTs.

- V S T -
Default settings
Control Min: OFF
Control Max: ON
send it a 7f message -> button OFF (not processing)
send it a 00 message -> button ON (processing)

Modified settings
Control Min: ON
Control Max: OFF
send it a 7f message -> button ON (not processing) <- fail
send it a 00 message -> button OFF (processing) <- fail


With the VSTs, it only change the behaviour of the bypass button, but is not processing the incoming audio with a 7f message, but with a 00.

However, the standalone do works well.

- S T A N D A L O N E -
Default settings
Control Min: OFF
Control Max: ON
send it a 7f message -> button OFF (not processing)
send it a 00 message -> button ON (processing)

Modified settings
Control Min: ON
Control Max: OFF
send it a 7f message -> button ON (PROCESSING) <- Correct !
send it a 00 message -> button OFF (NOT processing) <- Correct !

Post

This is odd... Have you double checked the settings inside each instance? (as you may have noticed each plug-in type has its own settings, and standalone and VST for example will not share the same settings). Also, I am not sure I understand: do you mean that the bypass button has the right state, but processing is not bypassed accordingly?

Post

modified-0).jpg
modified-1) send 7f = PW button on (but is not processing).jpg
modified-2) send 00 = PW button off (but is processing, when it should not).JPG
Now I'm just working with one instance in a audio track (where a midi track on my daw output to PW VST for allow it receive midi messages).

Modified settings
Control Min: ON
Control Max: OFF
send it a 7f message -> button ON (but is not processing) <- fail, should be PROCESSING
send it a 00 message -> button OFF (but processing) <- fail, it should NOT be processing

I've done different tests, and I also used VMPK and MIDI translator PRO and yeah, on the VST (x32 or x64) the button shows ON but is on bypass mode, and when is OFF, is when is processing the incoming audio. It's still using the old behaviour. Not problem with the standalone though, after of modify the settings (Control Min: ON, Control Max: OFF), it works great.

I guess that's something you'll have to fix for the next release.
You do not have the required permissions to view the files attached to this post.

Post

Thanks for the details. That's crystal clear now. Will have to check if there is a bug specific to the VST version here.

Post

It was indeed a bug specific to the VST version, good catch! We will issue a new preview version shortly including a fix for this issue.

Post

A new " Preview" has been uploaded and should be available from the "next release preview" link on the full version download page (link received by email upon purchase). Do you mind checking if it actually fixes the issue for you?

Post Reply

Return to “Blue Cat Audio”