Using FaderBox & ParmMod

[m5tevens]

I'm figuring out how to use a FaderBox in conjunction with ParamMod to give me more control over my external controllers than using "Learn Midi CC" directly ...

When enabled, Quantize limits fader movement to one unit. For the default range, this limits it to top, middle, and bottom. If I change the range to -8/8, I can get 16 quantized steps. Which is great, but now the output is no longer what I need it to be. Is quantize going to have a divisor associated with it at some point?.

I'm being picky here, but having the "Min Val" parameter placed above the "Max Val" parameter in the FaderBox control panel seems counter-intuitive.

Specifically what I'm trying to do;
1) Control the LFO period with a knob, set an arbitrary range, eg, 1 ~ 16, and quantize it to integer values. I can do this by turning off AutoScale on the ParamMod and setting the range of the FaderBox slider to 1 ~16, but it would be preferable to define the range outside of the FaderBox so I can use a single fader to control multiple parameters. Also, with the range set to values other than the default, the faders no longer respond correctly to controller mapping ( works fine again if I put them back the way I found them. )

2) Control LFO phase with a fader, quantized to 45 degree divisions. I'm guessing a fader range -180/180 and a Binary OP would do it, but that seems a bit of a long way around it.

[jim]

Specifically what I'm trying to do;
1) Control the LFO period with a knob, set an arbitrary range, eg, 1 ~ 16, and quantize it to integer values. I can do this by turning off AutoScale on the ParamMod and setting the range of the FaderBox slider to 1 ~16, but it would be preferable to define the range outside of the FaderBox so I can use a single fader to control multiple parameters.

If you want to control multiple params from one source, it is best to setup a default range of -1 to +1 (unquantized) at the source (whether it is a FaderBox, ModSeq, LFO etc), then either let the ParamMod auto-scale (and quantize) it, or manually process and scale the values w/ the operator modules -- more on that below...

Also, with the range set to values other than the default, the faders no longer respond correctly to controller mapping ( works fine again if I put them back the way I found them. )

Assuming you mean MIDI CC control (via MIDI Learn), it works fine over here, if you have an example that shows otherwise, I definitely want to see it.

2) Control LFO phase with a fader, quantized to 45 degree divisions. I'm guessing a fader range -180/180 and a Binary OP would do it, but that seems a bit of a long way around it.

I can think of two ways to handle this, assuming you're using the FaderBox:

1. Set a fader to run -4 to +4 (quantize on), multiply the output by 45 to get a range of -180 to +180, then feed that into a ParamMod with auto-scale off.

2. Set the fader to run -180 to 180, then use a BinaryOp with "Int Divide" by 45 -- the output of that will then be -4 to +4, quantized. Take that result, multiply by 45 to get back to the full value range, then feed to a ParamMod with auto-scale off.

Both, of course, have some tradeoffs. In the first case, you get a fixed set of values on the FaderBox, but those are 'artificial' values. In the second case, you get real values, but they are not quantized to the exact values you want. I'd probably go for the first case, as that value range (-4 to +4) is pretty easy to live with, and is properly quantized. OTOH, version 2 would be very useful for taking a generic value range (-1 to +1), then tweaking it to match a specific parameter.

Cheers,
Jim

[m5tevens]

I went with #1, which works fine, although I had to use 0 ~ 8 for the fader range to make it work ( the LFO wants to see 0 ~ 360 for the phase value. ) Thanks for the hints, I wasn't clear on what the FaderBox is meant to deal with on its own and what's meant to be massaged externally. Those are some pretty sweet "Ops" modules, btw!

Never mind the controller mapping bit, it seems to have cleared itself up. I've had a few instances of things acting strangely with cc mapping, which I've been ignoring for now, as the controller I'm using is only for testing until I pick something permanent up, and I have reasons to suspect it.

[jim]

I went with #1, which works fine, although I had to use 0 ~ 8 for the fader range to make it work ( the LFO wants to see 0 ~ 360 for the phase value. ) Thanks for the hints, I wasn't clear on what the FaderBox is meant to deal with on its own and what's meant to be massaged externally. Those are some pretty sweet "Ops" modules, btw!

Yes, the operator modules are super-handy!

Cheers,
Jim