Dynamic selectors not refreshing instantly

[RattlesnakeLodge]

Hello!

This is an issue I noticed while using pre-10, involving feedback and dynamic track selectors.

I am using two MCU devices...

• Behringer X-Touch Universal, controlled by 1st ReaLearn instance in monitor FX chain, renamed as "X-Touch". Channels 1 - 8.
• Behringer X-Touch Extender, controlled by 2nd ReaLearn instance in monitor FX chain, renamed as "X-Touch Ext 1". Channels 9 - 16.

I have setup "operation modes" using Parameter 2 in my two Realearn instances, and mapped buttons on my main X-Touch to toggle certain values in both. For example, Send button toggles a value of 4 in Parameter 2 of both ReaLearn instances, to activate mappings to control track sends, Plugin button is mapped to value of 5, to activate plugin mappings, etc.

I have also mapped modifier buttons to other parameters in both ReaLearn instances. For example...

• Parameters 3 - 10 are set as 8 Fader Touch modifiers
• Parameter 11 is on when no modifier buttons are pressed or toggled
• Parameter 12 is on when Shift modifier is pressed or toggled
• Parameter 13 is for Option
• and so on...

All of the above is working as expected, and feedback is instantly refreshed on both X-Touch units.

What appears to be a problem is refreshing the feedback when track banking.

Under normal DAW operation mode, I am targeting tracks using the Dynamic selector, borrowing your Mackie controller preset formula, "p[0] 10000 + 0" for track 1, "p[0] 10000 +1" for track 2, etc.

• ReaLearn instance for my main X-Touch has mappings with dynamic selectors from "+ 0" to "+ 7"
• ReaLearn instance for my X-Touch Extender has mappings with dynamic selectors from "+ 8" to "+ 15"
• Parameter 1 in both instances is controlled by my fader bank buttons.

Scenario...

• Parameter 1 is at a value of 0, or "0.0000%" (both ReaLearn instances). My main X-Touch shows tracks 1-8, X-Touch Extender is showing tracks 9-16.
• I press "Fader Bank Right" once, and my main X-Touch now correctly shows tracks 17-24, but X-Touch Extender is still showing 9-16, when it should be showing tracks 25-32. Values of Parameter 1 in both ReaLearn instances are verified the same ("0.1600%")
• I press Fader Bank Right again, no change as to what is displayed (X-Touch still showing tracks 17-24 when it should be showing 33-40, extender still showing 9-16). Parameter 1 value in both instances is now at "0.3200%"
• I press Fader Bank Left once, changing Parameter 1 value back to "0.1600%", no change in what is displayed. X-Touch showing 17-24, Extender showing 9-16.
• I press Fader Bank Left again, Parameter 1 is back at 0.0000%. X-Touch now correctly displays tracks 1-8, extender showing 9-16.
• When Parameter 1 is at a certain value, and both the X-Touch and Extender are not showing correct track numbers, I noticed that when I click on a different track in Reaper, or click on different plugin, etc, the X-Touch and Extender feedback is refreshed (LCD displays catch up to the correct track numbers, faders refresh accordingly.
• Fader touches on both X-Touch units refreshes their feedback, but independent from each other. Touching a random fader on my main X-Touch refreshes the LCD displays and fader positions of just that X-Touch unit. Touching a random fader on the X-Touch Extender refreshes the LCD and fader positions of just the Extender.
• The command "Send Feedback Now" has no effect on the problem
• This issue is not limited to Parameter 1. I have setup Parameters 19 and 20 the same way, for dynamic selection of track sends and receives, and the issue also occurs here.

Again, I'm not sure when this became an issue. I've slowly been creating a very robust and very detailed mapping scheme for for these control surfaces, and mapped my fader bank buttons possibly as far back as "pre-4" of 2.13, and it worked as expected at the time. I just happened to notice this issue when working in "pre-9" and "pre-10".

[helgoboss]

Thanks for the detailed report. When the bank moved on and the controller still incorrectly displays the old state: If you then do something on your controller, e.g arm a track, does it affect the correct track or still the old track? I basically want to know if this only a feedback issue or also a control issue.

[RattlesnakeLodge]

You're welcome!

I just tried it. So, this is weird. When the tracks are not displayed correctly, pan, rec arm, solo, mute, and faders control the tracks in the old / incorrect track bank.

Fader touch, and Select did refresh the unit to the correct bank. I did test the fader alone by disabling fader touch mappings.

FYI: My "per channel" mapping in normal DAW mode is as follows...

• LCD line 1: Track name (feedback only)
• LCD line 2: Track pan (feedback only), active when respective fader touch modifier is off
• LCD line 2: Track volume (feedback only), active when respective fader touch modifier is on
• V-Pot LED: Track pan (feedback only)
• V-Pot: Track pan (control only)
• V-Select (double press): Reset track pan using increment mode, target min/max at 50% (control only)
• V-Select (fire after 300ms timeout): Reaper action, show track group parameters (control only)
• Rec Arm: Arm track for recording (control+feedback)
• Solo: Track Solo (control+feedback)
• Mute: Track Mute (control+feedback)
• Select: Track Select, exclusive (control+feedback), active when Control modifier is off
• Select: Track Select (control+feedback), active when Control modifier is on
• Fader: Track volume (control+feedback)
• Fader Touch: set automation touch state (control only)
• Fader Touch: activate parameter for fader touch modifier (control only)

Each ReaLearn instance has the following Compartment Parameters...

• Parameter 1: Track
• Parameter 2: Encoder mode
• Parameter 3: Fader Touch 1
• Parameter 4: Fader Touch 2
• Parameter 5: Fader Touch 3
• Parameter 6: Fader Touch 4
• Parameter 7: Fader Touch 5
• Parameter 8: Fader Touch 6
• Parameter 9: Fader Touch 7
• Parameter 10: Fader Touch 8
• Parameter 11: No Modifier Pressed (meaning, this parameter is toggled to 1 when Shift, Option, Control, and Alt are all inactive)
• Parameter 12: Shift
• Parameter 13: Option
• Parameter 14: Control
• Parameter 15: Alt
• Parameter 16: Jog Wheel Mode
• Parameter 17: Cursor Mode
• Parameter 18: Flip
• Parameter 19: Sends (dynamic selector, just like Parameter 1 for track selection)
• Parameter 20: Receives (same as above)
• Parameter 21: Outputs (same as above)

Any control that activates or changes the value of a parameter, is duplicated to change parameters the same way on the other X-Touch unit. For example, Shift button toggles the Shift modifier on ReaLearn instance 1, and a duplicated Shift button mapping controls the Shift modifier on ReaLearn instance 2. So, pressing Shift will activate Shift modifiers on both instances. The exception to this is the fader touch parameters. These parameters are independent on their respective instances, and are activated only by their respective X-Touch units.

I am attaching my sessions, exported as JSON, in case you want to see exactly what my mapping and parameters are. Hope that helps!

One more thing, I maybe did not mention, I did test in both -pre 9 and -pre 10, same behavior with respect to banking and feedback.

X-Touch_JSon.txt X-Touch-Ext_JSon.txt

.

[RattlesnakeLodge]

One other thing: Minimizing REAPER, or bringing up another application in the foreground, THEN bringing REAPER back into the foreground refreshes the track banks. I do have REAPER set to close Audio device when stopped and REAPER is inactive.

[helgoboss]

You are right, there's something wrong with that. Looking into that.

[helgoboss]

Thanks for the report. Should be fixed in upcoming pre.

[RattlesnakeLodge]

Confirmed, pre-11 fixed the issue I was experiencing. Vielen Dank nochmal!