Hi. As a normal FX in the control track. Then - on opening the Smart Knobs script - it will detect the faderbox and use that track and faderbox to control your plugin parameters. So you just need to learn your controller to the faderbox parameters.

The CC options are 0-31, 32-63 etc. (for the 32 faders in the faderbox). I guess it depends on the controller what channel it receives on - it may be the same as the sending channel. I'm pretty sure SRD who I originally developed this for uses an XTouch - so it certainly should be able to talk back to the controller - I'm just not sure how he set it up - but the options should be there to get it working.

EDIT: Also of course you need to route MIDI from the control track to your controller.

EDIT: Also of course you need to route MIDI from the control track to your controller.

Thanks. I'll try this later....... Midi feedback works but only to my faders.

Would it be possible for the script to work without the FaderBox having focus? I see that if I close the Faderbox window, I lose control over the plugin. The same happens if I close down the lua script. Could they run in the background?
(The native Reaper MidiLearn works in the background....I don't have to have any other windows open)
Just a thought.

Thanks. I'll try this later....... Midi feedback works but only to my faders.

Would it be possible for the script to work without the FaderBox having focus? I see that if I close the Faderbox window, I lose control over the plugin. The same happens if I close down the lua script. Could they run in the background?
(The native Reaper MidiLearn works in the background....I don't have to have any other windows open)
Just a thought.

Sorry for delay in replying - been mega busy on lots of things and missed this edit.

Well - the Lua script must be running - otherwise it cannot monitor and translate the Faderbox values onto the selected parameters. You can of course adjust its size to make it small - and hide it somewhere - however - this is not possible to add as part of the script (you cannot alter the script window in code yet).

As for faderbox needing focus - this shouldn't have to be the case - as you simply learn the controls of the faderbox using Reaper's native learn routines - it should just work. Make sure though that when learning the faderbox controls that you don't have the 'Enable only when effect configuration is focused' option set - this would probably be the cause of requiring Faderbox to be focused.

Make sure though that when learning the faderbox controls that you don't have the 'Enable only when effect configuration is focused' option set - this would probably be the cause of requiring Faderbox to be focused.

You always want your controller controlling the Faderbox whatever else might be focused. You then just require the Smart Knobs script to be running - and this takes care of routing any faderbox sliders to the relevant parameters of any focused effect.

lb0 Any way to display more than 4 faders in the Faderbox? Would make learning easier. At the moment you have to go through the menu(Param/FX parameter list/Learn/F1) for every controller which is a minor PITA.

lb0 Any way to display more than 4 faders in the Faderbox? Would make learning easier. At the moment you have to go through the menu(Param/FX parameter list/Learn/F1) for every controller which is a minor PITA.

Yep - edit the faderbox text file - and remove the '-' at the end of each slider intialisation line (before the Fn text descriptor).

So from:

slider5:1<0,1,0.00001>-F5

to

slider5:1<0,1,0.00001>F5

Of course - you should only need to do the learning once if you save the setup to a project template.

Thanks. I can just hide them when I'm finished learning the controls. Makes life a little easier. So Save Track as Template or Save Mappings as Default would work to save?

Not 100% sure if a track template will recall global learned parameters. Might be something to test.

A Project template should though. Or the save as default (if that will work globally).

I personally use an Automap controller which remembers the mappings for the Faderbox plugin (which is wrapped in ReaJS which is wrapped in the automap required wrapper). So setting up for me is a little different.

I am using this in conjunction with your LBX FX Positioner and actually Realearn from Helgoboss as well (I'll detail that at the end here)

What I would love to see in the LBX FX Positioner is when you click next or previous that it also focuses the plugin. I can't really find an easy way to focus the plugin apart from clicking on it. Focusing the plugin obviously sends the parameter data to the Smart Knobs script and in turn sends midi feedback to my midi twister. So it would be incredible if the positioner script also focused on the plugin in single mode. I know not everyone would use it in single mode so that may present a problem.

******

Sidenote here:

I used Helgoboss' Realearn to map the twister to the faderbox plugin. It does an impeccable job of minimizing parameter jumps and the feedback seemed to be easier to implement. I'm just saying this because it works insanely well and in case anyone was having trouble with parameter jumps like I was. (a classic midi controller fallback)

But this, the positioner, and the stripper are insanely awesome, Leon. Very very well done!

I am using this in conjunction with your LBX FX Positioner and actually Realearn from Helgoboss as well (I'll detail that at the end here)

What I would love to see in the LBX FX Positioner is when you click next or previous that it also focuses the plugin. I can't really find an easy way to focus the plugin apart from clicking on it. Focusing the plugin obviously sends the parameter data to the Smart Knobs script and in turn sends midi feedback to my midi twister. So it would be incredible if the positioner script also focused on the plugin in single mode. I know not everyone would use it in single mode so that may present a problem.

******

Sidenote here:

I used Helgoboss' Realearn to map the twister to the faderbox plugin. It does an impeccable job of minimizing parameter jumps and the feedback seemed to be easier to implement. I'm just saying this because it works insanely well and in case anyone was having trouble with parameter jumps like I was. (a classic midi controller fallback)

But this, the positioner, and the stripper are insanely awesome, Leon. Very very well done!

Thanks. I'll see what I can do regarding focussing the visible plugin. I think it should be possible, but not 100% - need to look into.

ahh sorry! i ment exactly the opposite of what i asked :/
I still didn't try the script but seems like i have to focus a plugin in order to the fader to control that effect parameter. So an hardware fader can control 1 or more plugin parameter, on any track. What i meant is: if you are considering: An hardware fader controls only 1 parameter of a specific plugin in a specific track and no need to be focused on any fx nor any track selected.
Basically the default behaviour of osc/learn in reaper (in my previous gif: no checkboxes checked).

ahh sorry! i ment exactly the opposite of what i asked :/
I still didn't try the script but seems like i have to focus a plugin in order to the fader to control that effect parameter. So an hardware fader can control 1 or more plugin parameter, on any track. What i meant is: if you are considering: An hardware fader controls only 1 parameter of a specific plugin in a specific track and no need to be focused on any fx nor any track selected.
Basically the default behaviour of osc/learn in reaper (in my previous gif: no checkboxes checked).

Sorry - still not fully understanding your suggestion. If you want a hardware fader controlling a single plugin (on specific track) parameter - why not just use the default Reaper learn system? I'm obviously not quite understanding right.

"why not just use the default Reaper learn system?"
Hi!
1) because native feature don't allow feedback to the hardware
2) with this script we have a list (more easily manageble)
3) you have more flexibility to make new stuff : ) more cc modes like ranges , target CC value get's effective after the old value as been reached (like some synths do)
4) you have good GUI tradition :P

"why not just use the default Reaper learn system?"
Hi!
1) because native feature don't allow feedback to the hardware
2) with this script we have a list (more easily manageble)
3) you have more flexibility to make new stuff : ) more cc modes like ranges
4) you have good GUI tradition :P

Thanks

So what you want is a list of faders that can be assigned to anywhere all the time? (ie. doesn't matter if you change track/plugin focus etc)

So what you want is a list of faders that can be assigned to anywhere all the time? (ie. doesn't matter if you change track/plugin focus etc)

i think every native option is valid. My scenario is just 1 way.

in my case yes i have this scenario:
- i want the hardware fader to control specific(s) parameters on specific tracks
ex: fader controls vol from track 1
or maybe fader controls vol from track 1 and 2(never used)
And no need for track or item to be selected

- If i duplicate this track, osc/learn is copied too. So both are working. So a way to enable just 1 of them is what i do, and that surge the need of what i refer by "target CC value get's effective after the old value as been reached", like some synths do. A way where i can switch between those 2 tracks (exclusively) and just one of them is responding to the fader. So that moving the fader is ignored until the CC as reached the value it holds and not right away like natively happens. (if you don't see what i am saying i will try to find a better way to explain: nord lead works this way? between ABCD patches knobs just start changing sound after the previous/last cc as been reached)

Anyway! the second point i refer is my own homework maybe! 1st point is the most important part i think. Thanks for listening : )