***** TL;DR — Azslow3 has helped me solve the problem — thanks so much! I’m going to post the rest of this for future users who might be having the same problem, because the archives here have helped me so much. I do have one remaining question detailed at the very end, though… ****
Quote:
Originally Posted by azslow3
So can I suggest you to take absolutely "clean" default pattern file (you can find it in Program Files/REAPER/InstallData/OSC)
|
Done.
Quote:
Originally Posted by azslow3
modify just these 2 lines (xxx_FOLLOWS) and try again?
|
Done — when you say “2 lines,” I’m assuming that you mean DEVICE_FX_FOLLOWS FOCUSED mentioned above and also DEVICE_TRACK_FOLLOWS REAPER.
Here is what my modified pattern file now reads:
REAPER_TRACK_FOLLOWS REAPER
DEVICE_TRACK_FOLLOWS MIXER
DEVICE_TRACK_BANK_FOLLOWS DEVICE
DEVICE_FX_FOLLOWS FOCUSED
DEVICE_EQ INSERT
DEVICE_ROTARY_CENTER 0
Everything else in the file has been left untouched.
Quote:
Originally Posted by azslow3
Also check the values you are sending. They should be float 0 to 1.
|
Done, and true for everything that follows.
Quote:
Originally Posted by azslow3
Can you also just try with “/track/volume”?
|
Okay, very interesting! I changed OSCulator to send /track/volume. At the point that command was first sent, track two just happened to be selected. (In hindsight, the significant thing here wasn’t that the track was selected in the mixer, but that this track had most recently had a plugin added.)
The result was that my MIDI controller now controls the volume of track two…AND ONLY TRACK TWO. I can change the selected track in Reaper’s mixer to a different track, or select no track at all…and throughout, track two responds.
To test this out, I restarted Reaper, loaded up seven empty tracks (with no plugins) selected track five in the mixer before turning the MIDI controller for the first time. But this time, the master track responded — and again, only the master track, regardless of which track is selected in the mixer.
But THEN, I added a plugin to a random track…and suddenly, that track’s volume is being changed by the MIDI controller.
And it continues to work: each time I add a new plugin to a new track, the controller begins to control that track’s volume. To be clear, none of these new tracks are being selected in the mixer, and that selection continues to have no impact on the volume control. And it doesn’t seem to matter if the new plugin window is focussed or even open…
So right now, it seems to me that the act of adding a new plugin to a track is what is required to ‘select’ the track from Reaper’s perspective. Simply clicking on the track in the mixer doesn’t do it, but adding any random plugin does.
Inspired by the above discovery, I edited OSCulator to send this command:
/fx/1/fxparam/1/value
I then created a new project, seven empty tracks, and added a plugin to slot one of the fifth track. The midi controller controlled parameter #1. (Already a huge success, compared to where I was this morning.)
I then added a plugin to slot one of track two…and control switched over to track two!
Better yet, I was finally able to switch back and forth between controlling those different plugins by changing which one is focussed at a given moment. HOORAY!
I then started adding more plugins to those two tracks, to make sure only the one in the first slot was being controlled (vs any plugin currently focussed). Not only does it work, but interestingly I found that focussing on any plugin in track five moves control over to the first plugin in track five, even if that first plugin window isn’t focussed. Essentially, focussing on any random plugin on a given track is accomplishing what I would have expected the act of highlighting a track in the mixer window to do.
I closed everything out, restarted, and was able to repeat those results on a clean launch.
My next step is to get feedback flowing in the other direction, but I’ll do that work on my own and start a new thread with questions there if necessary.
MY REMAINING QUESTION: why is simply selecting the track in Reaper’s mixer not fully “selecting” the track from the perspective of OSC control. At this point I’m happy with the workaround of launching/focussing a plugin window to initiate the change, but in my perfect world I’d be leaving the windows closed and simply selecting tracks in the mixer. (I will be using the controller strictly for EQ plugins, and I’d almost rather be forced to use my ears when making those decisions.) It’s partially academic at this point, but I’d love to hear if there’s an easy fix that I’m missing…
Once again, thanks to Azslow3 for the help!