Trying to make Faderport Classic better-er (SOLVED)

[mcoyle]

As you may know, the original Faderport is supported as a control surface in Reaper, but a few buttons are not assigned to any function: Window views for Mix, Project, a couple other. I was trying to use ReaLearn to access those buttons and assign events to them, but I can't seem to get ReaLearn to recognize the faderport, plus it looks like it's an either-or situation.

Either the faderport is an OSC Control Surface OR it's a MIDI device handled by ReaLearn.

As is often the case when I have a problem, I wonder if it's a quirk to Linux.

If any of you are using the original Faderport, are you using ReaLearn or OSC? Any tips?

[DuX]

I've been using FaderPort for about 12y and it's easy to assign different functions to the buttons. Just select it as a control interface in Reaper's settings, which you've already done and then go into "actions" menu > "show actions", find an action you want to assign (like "toggle mixer") to the button, click "add" then press the button on the FaderPort. Done. Find next "action"...

One button you can't assign is the "output" button as it is hard wired to exchange the fader (vol to pan and back) and the knob (pan to vol and back).

I hope this will help you,

Cheers!

[mcoyle]

Originally Posted by DuX

I hope this will help you,
Cheers!

Are you friggin kiddin me!!

Every time I have a question or problem with Reaper, the solutions are amazing and elegant.

Not only does this solve my problem, it opens up a bunch of other possibilities for assigning controllers.

Thanks!

[DuX]

It is very flexible and useful, yes. My reaction was similar when I discovered it. Like, could it be that easy??

There are not many buttons you have to assign that way. Just Mix, Proj and Trns. but those get used a lot. Especially Mix, of course.

Cheers!