Toggling between two uses of one fader.

[tpresto]

Hello, all.

I'm relatively new to Usine, and haven't been able to learn to use a single switch or button to toggle a fader between two separate and independent uses. I'm trying to control two separate guitar processors with the same expression pedal, but when one use is active, I need the other to be inactive. One of them is a whammy pedal and the other a volume. Is there any way I can use a single button to change the use of the pedal (Which is represented in the interface by a fader) between whammy and volume, but never both of these at the same time. I am able to create a grouped switch scheme; however, this seems to require the use of more than one switch -- the reason this is important is because I have a limited number of midi buttons on the pedal that I'm controling this patch with.

Thank you for the help, and I hope I've been clear enough!

Todd

[nay-seven]

here a first step , pass if change and pass modules are in event control tab and not in math/logical



btw, can you please post this kind of question in the patching forum next time, better place..

[tpresto]

Thanks again, Nay-Seven! I'm away from my Usine computer, but will try this as soon as possible. I'm not very familiar with the pass/pass if change and what their implications for the wiring are, so i'm unable to understand WHY this works . This will hopefully help me to understand. Thank you!

[bsork]

The Pass module outputs data inly when the "pass" inlet is on, ie 1. There's also a Stop module that works in the opposite way - you can change the Not -> Pass with that one.

The Pass (only) If Changed module only outputs data when the input is changed. Handy if you for example would like to manually override the value in a fader or whatever that is otherwise controlled by an input value. A typical example is a VST parameter -> fader -> Pass If Changed -> (the same) VST parameter. Without the Pass IF Changed, you would get problems when trying to update the parameter on the VST's GUI; with it you can change the value both ways, They're not really necessary in this example, though.

[nay-seven]

you're right about the stop module bsork , good simplification, but I'm not agree for the pass if change , depending on where are connected the out of the fader , he gone to have some values jump when he use the switch without them..?

[bsork]

he gone to have some values jump when he use the switch without them..?

Good point - didn't think of that.

[tpresto]

Thank you, guys, for the input. I have tried the depicted scheme at the top, and it worked well for a while. Though, after a bit, the faders -- I was representing the expression pedal values on the interface with faders -- were not responing the way they should up was sometimes down and vice versa. Also, the minimums and maximums were not where they should've been. Basically, the set-up became useless. I tried reloading the patch, rewiring the pass if change scheme, replacing the VSTs in the patch -- all was to no avail. Now, the fader (or expression pedal) that isn't connected to the "pass if change" set-up is changing when I am using the fader that is... This is with seemingly correct wiring and "Midi Learns" Uggggghhhhh...

[bsork]

That's mighty strange. I've just created a patch similar to Nay's suggestion (in 5.25) and it's working just fine. Like you (I guess), I exchanged the Data Outs with faders, and they behave exactly as I thought they would: The currently controlled gets updated whenever the "input" fader gets updated - with the mouse or by a MIDI-learned CC, and both the output faders can be updated with the mouse,

Just guessing, but here are a couple of suggestions as to what may be the problem:
- You made MIDI learns on one or both output faders; only the input should have that. (Of course you can use another MIDI message to turn the switch on and off as well.)
- It's in a sub-patch (in which MIDI learns should be OK by now, but it's a quite new feature, so maybe you've stumbled across a bug).

A tip for debugging this sort of stuff is to test how things work without MIDI, ie use the mouse and see if things operate how they should.

[tpresto]

Thanks, Bsork! Short response for now: I'm pretty sure that I've only assigned midi-learns in the in put sort of application. I'll double check, then I'll try your suggestions. Thank you again.

[tpresto]

obvious typo: that's input not "in put."

[tpresto]

It's working great now! thank you!

[bsork]

Good!