[FR] using ui_switch instead of ui_button

Suggestions for future products, updates, revisions, and anything else.
Forum rules
Please keep your suggestions reasonable. Refrain from trash-talking current features (people worked hard on those!), and refrain from trash-talking suggestions; keep it positive. Most of all, PLEASE search for your idea before posting it; chances are, someone may have already said it.
User avatar
Junior Member
Posts: 2
Joined: January 2nd, 2017, 3:44 pm
Location: Montreal
OS: Windows 10
DAW: Reaper

[FR] using ui_switch instead of ui_button

Postby kaeru » January 3rd, 2017, 2:06 am

This is a feature request for VSCO2, albeit a very non-exciting one.

I would like to use automation on the mic, reverb and filter options of the VSTis in order to control them from my MIDI controller. This works already for the parameters, but not for their toggle switches. Trying to figure out why I couldn't assign host automation slots to the on/off buttons, I came across this information:
Kontakt 4 Player Developer Guide.pdf (p.27 section 5.2)
New User Interface Controls
In the KONTAKT 4 script update, two new controls have been introduced: Sliders and switches.[...]
Switches are virtually identical to buttons, but have the added benefit of being automatable.

Would there be a way through find+replace command to swap the Microphone (for multi-miced instruments), Filter and Reverb toggles to ui_switch instead of ui_button? I realize this request might be totally unfeasible, but I am throwing it out here anyway just in case it's actually easy through a batch command. I am also running on the pure assumption that this is the reason those toggle buttons are not assignable to the host automation panel of kontakt.

Thank you for taking the time to read this fr !


Small LICEcap of what I need to be able to do ! Thanks for checking it out !
VSCO_HostAutomation.gif (218.01 KiB) Viewed 159 times

Return to “THE Suggestion Forum”

Who is online

Users browsing this forum: No registered users and 1 guest