c18cc
(1) How to get a visual representation of the settings for Stem FX? I realize I'm able to set the specific effect parameters within the script - eg: padfx "echo out" 80% 1bt "stemfx:vocal"
Is there a way to *see* the effect controls in the same way as the main deck effects when docked?
(2) How do I map a controller to engage a specific pad on a non-visible pad page - eg. "pad 5 on pad page 2"? I've only been able to map the pad button while actually on the corresponding pad page. It would be nice to fire off something from pad page 2, while keeping HOTCUES on pad page 1 on screen (for example). I know I can copy the full script from the pad to a controller mapping, just wondering if it's possible to trigger the pad the script is already assigned to.
Thanks!
Is there a way to *see* the effect controls in the same way as the main deck effects when docked?
(2) How do I map a controller to engage a specific pad on a non-visible pad page - eg. "pad 5 on pad page 2"? I've only been able to map the pad button while actually on the corresponding pad page. It would be nice to fire off something from pad page 2, while keeping HOTCUES on pad page 1 on screen (for example). I know I can copy the full script from the pad to a controller mapping, just wondering if it's possible to trigger the pad the script is already assigned to.
Thanks!
Posted 17 hours ago
PhantomDeejay
About 2:
It's not possible (for a good reason) to trigger a "pad" that's on a page that's not loaded on your "controller" (with GUI also being a controller)
What is possible though, is for each "controller" to use different/indpended pad pages
Therefore you can have your controller switch to "Stems" pad page as an example, while GUI (skin) remains on "Hotcues"
For this behavior, you need to enable "padsSkinIndependent" setting
It's not possible (for a good reason) to trigger a "pad" that's on a page that's not loaded on your "controller" (with GUI also being a controller)
What is possible though, is for each "controller" to use different/indpended pad pages
Therefore you can have your controller switch to "Stems" pad page as an example, while GUI (skin) remains on "Hotcues"
For this behavior, you need to enable "padsSkinIndependent" setting
Posted 12 hours ago