Control Surface Integration (CSI) Technical Feature Discussion

[MixMonkey]

Originally Posted by cjewellstudios

The only surface is your ost and the only zon files are the ones you provided

Yes, sorry, you did say that. Some setting in Reaper? (grasping at straws here)

[Geoff Waddington]

New build is up

CSI Exp.zip

Possible fix for TrackSendVolumeDisplay et al.

Also did anyone get to check if GoCurrentFXSlot now broadcast/receives properly ?

[MixMonkey]

Originally Posted by Geoff Waddington

Also did anyone get to check if GoCurrentFXSlot now broadcast/receives properly ?

Sorry, bit tied up today with work, so can't do the big navigator change over.

[MixMonkey]

Originally Posted by Geoff Waddington

So that's where to focus your effort -- the OSC Fader definition and associated Zones

Except he's using the same defs as me.

[Geoff Waddington]

Originally Posted by MixMonkey

Except he's using the same defs as me.

Maybe something in the touchOSC file -- I'm sure you've checked, but just in case...

[Funkybot]

Originally Posted by Geoff Waddington

New build is up

CSI Exp.zip

Possible fix for TrackSendVolumeDisplay et al.

Also did anyone get to check if GoCurrentFXSlot now broadcast/receives properly ?

First thing's first, TrackSendVolumeDisplay is working now in my SelectedTrackSendSlot zone.

Going to play around with MixMonkey's iPad Mixer setup and see if I can recreate cjewellstudio's issue here. If I can figure out the broadcast GoCurrentFXSlot thing in my own setup, I'll see if I can give it a go.

[Freex]

Originally Posted by MixMonkey

Except he's using the same defs as me.

Is he using the same TouchOSC layout on the tablet as you, maybe there is something a miss in that?

[cjewellstudios]

Originally Posted by Geoff Waddington

Maybe something in the touchOSC file -- I'm sure you've checked, but just in case...

I mean those are the same too.

I'm unsure what to try next. I suppose I can start breaking down MM's ost zones down to basically nothing.

It also seems to me there are reaper prefs that have to do with track selection/volume changes. I'll look into that.

[MixMonkey]

Originally Posted by Funkybot

Going to play around with MixMonkey's iPad Mixer setup and see if I can recreate cjewellstudio's issue here. If I can figure out the broadcast GoCurrentFXSlot thing in my own setup, I'll see if I can give it a go.

Bear in mind my setup doesn’t have the updated navigators.
Also, if you would, regarding GoCurrentSlot, see if that Zone I posted on the last page works, the one with Select | triggering the GoCurrentSlot.

[Geoff Waddington]

Originally Posted by Funkybot

First thing's first, TrackSendVolumeDisplay is working now in my SelectedTrackSendSlot zone.

Excellent, thanks for testing.

Wow, just looked at the bug list -- just your FX Focus bug and various display cleanup issues, making good progress...

[Funkybot]

Originally Posted by MixMonkey

Bear in mind my setup doesn’t have the updated navigators.
Also, if you would, regarding GoCurrentSlot, see if that Zone I posted on the last page works, the one with Select | triggering the GoCurrentSlot.

I'm calling it on OSC for the day with no resolution. Just going to let MixMonkey and cjewellstudio's take that lead on those weird touch messages and GoCurrentFXSlot.

I updated the navigators, and then other things were misbehaving. The zones look ok so maybe the network. But after an hour playing around with the network and two different tablets I'm giving up for now.

Originally Posted by Geoff Waddington

Wow, just looked at the bug list -- just your FX Focus bug and various display cleanup issues, making good progress...

Some much appreciated great news!

[Geoff Waddington]

Here's what I get https://www.youtube.com/watch?v=19EKBrgWWME using the following Zones, seems to work fine, wondering what's different:

Zone "Home"
	OnFXFocus		MapFocusedFXToWidgets
        ...
ZoneEnd

Zone "VST: UAD Fairchild 660 (Universal Audio, Inc.)" "F660"
	FocusedFXNavigator
	Threshold 		FXParam 2 "Thresh"
	Output 			FXParam 7 "Output"
	Meter			FXParam 0 "Meter"
	Attack 			FXParam 4 
	Release			FXParam 6	
	Input 			FXParam 1 "Input"
	Ratio 			FXParam 3 "Time Const"
	InvertFB+Compressor	FXParam 11 "Bypass" [ 0.0 1.0 ]
	WetDry	 		FXParam 8 "WetDry"
ZoneEnd

Zone "VST: UAD Harrison 32C (Universal Audio, Inc.)" "Har32C"
	FocusedFXNavigator
	HiCut 			FXParam "1" 	"HiPass"
	LoCut 			FXParam "2" 	"LowPass"
	HiGain 			FXParam "12" 	"HiGain"
	HiFrequency 		FXParam "11" 	"HiFreq"
	HiMidGain 		FXParam "10"	"HiMidGain"
	HiMidFrequency 		FXParam "9" 	"HiMidFreq"
	LoMidGain 		FXParam "8" 	"LoMidGain"
	LoMidFrequency 		FXParam "7" 	"LoMidFreq"
	Shift+LoGain 		FXParam "5" 	"LowGain"
	LoFrequency 		FXParam "4" 	"LowFreq"
	InvertFB+Equalizer	FXParam "16" 	"Bypass" [ 0.0 1.0 ]
	Parallel 		FXParam "17" 	"Wet"
ZoneEnd

Zone "VST: UAD Pultec EQP-1A (Universal Audio, Inc.)" "EQP1A"
	FocusedFXNavigator
	HiGain 			FXParam "7" "HF Atten"
	HiFrequency 		FXParam "6" "HF Atten Freq"
	HiMidGain 		FXParam "4" "HF Boost"
	HiMidFrequency 		FXParam "3" "High Freq"
	HiMidQ 			FXParam "5" "HF Q"
	LoMidGain 		FXParam "2" "LF Atten"
	LoMidFrequency 		FXParam "0" "Low Freq"
	LoGain 			FXParam "1" "LF Boost"
	LoFrequency 		FXParam "0" "Low Freq"
	InvertFB+Equalizer	FXParam "10" "Bypass" [ 0.0 1.0 ]
	Parallel 		FXParam "11" "Wet"
ZoneEnd

Zone "VST: UAD Teletronix LA-2A Silver (Universal Audio, Inc.)" "LA2ASlv"
	FocusedFXNavigator
	Threshold 		FXParam "0"
	Output	 		FXParam "1"
	Meter 			FXParam "4"
	Attack 			FXParam "3"
	Ratio 			FXParam "2"
	InvertFB+Compressor 	FXParam "6" "Bypass" [ 0.0 1.0 ]
	WetDry			FXParam "7"
ZoneEnd

[Funkybot]

Originally Posted by Geoff Waddington

Here's what I get...

Do the widgets on the Console 1 do anything when not focused to FX and do they still work after an unfocus? Here's a quick overview of my setup:

MIDI Fighter Twister
Bank A controls Selected Channel values (volume, pan), and mostly some Reaper actions. This is called from a Button zone, a Sellected Channel zone, all from included zones at home.

Focus an FX - all those Bank A widgets get reassigned to the FX as expected. Now A1 controls whatever on the plugin instead of Selected Track Volume.

Note: I keep my mixer docked and open.

Now, click the mixer. The focus FX clears, but the Home zone isn't back. All those widget assignmemts are gone.

So A1 went from controlling Selected Track Volume, to controlling Decay Time on a reverb (assuming that's what I focus), but clicking back on the mixer doesn't bring A1 back to Selected TrackVolume.

Imagine this [nonsensical for your Console One] setup...

Zone Home
     OnFXFocus MapFocusedFXToWidgets
     IncludedZones
       "SelectedChannel"
	  "Buttons"
     IncludedZonesEnd
ZoneEnd

Zone "SelectedChannel"
	SelectedTrackNavigator
	Threshold 		TrackPan
	Output 			TrackVolume
	Attack 			TrackPanLeft 
	Release			TrackPanRight
	Compressor	     TrackSolo
ZoneEnd

Zone "Buttons"
	Equalizer	Reaper 1157  // Snap
ZoneEnd

Zone "VST: UAD Fairchild 660 (Universal Audio, Inc.)" "F660"
	FocusedFXNavigator
	Threshold 		FXParam 2 "Thresh"
	Output 			FXParam 7 "Output"
	Meter			FXParam 0 "Meter"
	Attack 			FXParam 4 
	Release			FXParam 6	
	Input 			FXParam 1 "Input"
	Ratio 			FXParam 3 "Time Const"
	InvertFB+Compressor	FXParam 11 "Bypass" [ 0.0 1.0 ]
	WetDry	 		FXParam 8 "WetDry"
ZoneEnd

...this obviously wouldn't be a very good CSI setup but I'm trying to create something you can test with.

Using that kind of setup, if you start out at Home, compressor Threshold controls trackpan, and compressor Output controls volume. When you enter the Fairchild 660 mode, the FocusedFX should take those over. When you click on the mixer again...does Threshold go back to controlling trackpan and Output controlling trackvolume [for the selected track]? If yes, is it consistently?

If no, what happens if you focus a different FX now? Does it kind of get "locked up?"

[Funkybot]

Short version: here it clears out the widgets. But it doesn't reassign them to what they were assigned to before [focusing FX] in my Home zone. I'm expecting them not just to clear, but to go back to their previous assignments.

[Geoff Waddington]

Originally Posted by Funkybot

Short version: here it clears out the widgets. But it doesn't reassign them to what they were assigned to before [focusing FX] in my Home zone. I'm expecting them not just to clear, but to go back to their previous assignments.

Got it.

The Console 1 is a bad way to test your use case, I'll whip up something more like what you have.

[Funkybot]

Originally Posted by Geoff Waddington

Got it.

The Console 1 is a bad way to test your use case, I'll whip up something more like what you have.

Thanks! Appreciate your stick-to-it-edness. Let me know if there's anything else I can do to help. If needed, I could probably knock together an MCU inspired-zone that is analogous.

[Geoff Waddington]

New build is up.

CSI Exp.zip

Possible fix for FocusedFX not resetting issue.

[MixMonkey]

I just swapped out the Navigator names, but now none of them work. Was there something else to change, other than the new dylib?

Zone "FXMenu"
    SelectedTrackFXMenuNavigator
        DisplayUpper|      FXMenuNameDisplay
        DisplayLower|      NoAction
        Rotary|            NoAction
        RotaryPush|        Reaper "_S&M_SHOWFXCHAIN|"
        RotaryPush|        Reaper "_S&M_SELFX|"
        Shift+RotaryPush|  Reaper "_S&M_FXBYP|"             //Bypass FX Slot
        Option+RotaryPush| Reaper "_S&M_FXOFF|"             //Offline FX slot
        RotaryPush|        GoFXSlot
ZoneEnd

Zone "FXMenuSlot"
    TrackFXMenuSlotNavigator
    DisplayUpper|               TrackNameDisplay
    DisplayLower|               FXMenuNameDisplay
    Select|                     TrackUniqueSelect
    Select|                     GoCurrentFXSlot
    BankLeft                    FXMenuSlotBank -1
    BankRight                   FXMenuSlotBank 1
ZoneEnd

Zone "Send"
    SelectedTrackSendNavigator
    DisplayUpper|               TrackSendNameDisplay
    DisplayLower|               TrackSendPanDisplay
    FaderTouch+DisplayLower|    TrackSendVolumeDisplay
    Mute|						TrackSendMute
    Rotary|                     TrackSendPan	[ (0.2, 0.2, 0.2, 0.2, 0.2, 0.2, 0.2, 0.2, 0.2, 0.2) ]
    Fader|                      TrackSendVolume
ZoneEnd

Zone "SendSlot"
    TrackSendSlotNavigator
    DisplayUpper|               TrackNameDisplay
    DisplayLower|               TrackSendNameDisplay
    FaderTouch+DisplayLower|    TrackSendVolumeDisplay
    Mute|                       TrackSendMute
    Fader|                      TrackSendVolume
    BankLeft                    SendSlotBank -1
	BankRight                   SendSlotBank 1
ZoneEnd

[Funkybot]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Possible fix for FocusedFX not resetting issue.

Halfway fixed! I feel like you got the hard part done and this next bit will be a relative cakewalk.

So before: if I clicked out of the focus FX zone, I wouldn't go back Home (or to prior zone). That's resolved.

But now, if I click back on the FocusedFX, it's not regaining focus.

To reproduce:

1. Load up some tracks in a setup similar to mine
2. Load a FocusedFX - all good everything maps
3. Click on the mixer - all good, we're right back home
4. Click back on the prior FocusedFX (if it matters, I had the FX window set to floating and left it open the whole time)

Result: no dice.

Thanks again for the work on this!

[spkr4thdd]

Originally Posted by MixMonkey

You can have it floating if you prefer:

Zone "FXMenu"
        FXMenuNavigator
        RotaryPushD|        Reaper "_S&M_SELFX|"
        RotaryPushD|        Reaper "_S&M_FLOATFXEL|" 
        DisplayUpperD|      FXMenuNameDisplay
        DisplayLowerD|      NoAction
        RotaryD|            NoAction
        Shift+RotaryPushD|  Reaper "_S&M_FXBYP|"             //Bypass FX Slot
        Option+RotaryPushD| Reaper "_S&M_FXOFF|"             //Offline FX slot
        RotaryPushD|        GoFXSlot
ZoneEnd

...although the attraction of the FX Chain window is that it only has to be positioned once, whereas the floating windows always appear top left and have to be moved.

Should this work on V1.0? I get it to load up my fx zon file and map the controls correctly (although the changes in syntax over the past 12 months mean I've a hell of a lot of regain to do!), but I can't get it to open the FX chain, or float the FX?

[MixMonkey]

Originally Posted by spkr4thdd

Should this work on V1.0? I get it to load up my fx zon file and map the controls correctly (although the changes in syntax over the past 12 months mean I've a hell of a lot of regain to do!), but I can't get it to open the FX chain, or float the FX?

Yes, this will work on V1.0. What does your FXMenu Zone look like?

[MixMonkey]

Originally Posted by MixMonkey

I just swapped out the Navigator names, but now none of them work. Was there something else to change, other than the new dylib?

Ok, got it It was the Zone names. Now have everything except:

Zone "TrackFXMenuSlot"
    TrackFXMenuSlotNavigator
    DisplayUpper|               TrackNameDisplay
    DisplayLower|               FXMenuNameDisplay
    Select|                     TrackUniqueSelect
    Select|                     GoCurrentFXSlot
    BankLeft                    FXMenuSlotBank -1
    BankRight                   FXMenuSlotBank 1
ZoneEnd

What (exactly) is the mapping Action for this?
Is it "MapTrackFXMenuSlotToWidgets"?
or maybe "MapTrackFXMenusSlotToWidgets"?
I've tried both with no luck.

[Geoff Waddington]

Originally Posted by MixMonkey

Ok, got it It was the Zone names. Now have everything except:

Zone "TrackFXMenuSlot"
    TrackFXMenuSlotNavigator
    DisplayUpper|               TrackNameDisplay
    DisplayLower|               FXMenuNameDisplay
    Select|                     TrackUniqueSelect
    Select|                     GoCurrentFXSlot
    BankLeft                    FXMenuSlotBank -1
    BankRight                   FXMenuSlotBank 1
ZoneEnd

What (exactly) is the mapping Action for this?
Is it "MapTrackFXMenuSlotToWidgets"?
or maybe "MapTrackFXMenusSlotToWidgets"?
I've tried both with no luck.

MapTrackFXMenusSlotToWidgets, and you've discovered a bug, hopefully fixed now

[Geoff Waddington]

Originally Posted by Funkybot

Halfway fixed! I feel like you got the hard part done and this next bit will be a relative cakewalk.

So before: if I clicked out of the focus FX zone, I wouldn't go back Home (or to prior zone). That's resolved.

But now, if I click back on the FocusedFX, it's not regaining focus.

To reproduce:

1. Load up some tracks in a setup similar to mine
2. Load a FocusedFX - all good everything maps
3. Click on the mixer - all good, we're right back home
4. Click back on the prior FocusedFX (if it matters, I had the FX window set to floating and left it open the whole time)

Result: no dice.

Thanks again for the work on this!

Ah, if only it were that easy

If you have 2 FX Windows open you can easily see what's going on.

When you have an FX window focused and you click away, it unmaps, all good.

If you then click back on it, it doesn't map -- that's because Reaper isn't sending CSI an OnFXFocus message -- as far as Reaper is concerned it is already focused, nothing has changed.

Here's how to prove it.

Focus FX A

Click on mixer.

FX A unmaps.

Click on FX B

It maps fine since Reaper WILL send and OnFXFocus in this case -- there is a new FX focused.

The outcome of all this is... ugghh

The Focused FX saga is not over.

We now have to figure out a way to find out when a previously Focused FX that lost Focus is back

I'll think about this some more, but I think we will need some more API support, not sure, but seems like it...

[Geoff Waddington]

New build is up.

CSI Exp.zip

Hopefully fixed TrackFXMenuSlot bug.

Cleaned up a lot of the "unmaps", see if the "left over artifacts" issues are improving.

[Funkybot]

Geoff, we're already light years ahead of where we were just a few hours ago so I appreciate the effort. FocusedFX work perfectly fine when I switch form Effect 1 to Mixer, or from Effect 1 to Effect 2, or from Effect 1 to mixer to Effect 2...that's a big improvement.

The only scenarios where it doesn't work is Effect 1 to mixer back to Effect 1. Or effect 1, close effect 1, reopen effect 1. So huge progress!

Originally Posted by Geoff Waddington

We now have to figure out a way to find out when a previously Focused FX that lost Focus is back

I'll think about this some more, but I think we will need some more API support, not sure, but seems like it...

I doubt this tidbit will be helpful but Reaper itself can already do this (note: I'm not suggesting the API can yet). If I use Reaper's own internal Learn system and reproduce the steps, it correctly knows when to focus and unfocus.

I just confirmed with a synth called Invader2 which I've got mapped to my Roland System-8 keyboard using Reaper's built in MIDI/OSC Learn. When I use the "focus" option in Reaper itself, the mapping activates when focused, but if I click the mixer, the focus is lost, disabling the mapping. Then, if I click back to refocus the plugin, it picks right up where it left off with the mapping active again.

Hopefully something they can also communicate to CSI via the API.

[spkr4thdd]

Originally Posted by MixMonkey

Yes, this will work on V1.0. What does your FXMenu Zone look like?

Basically I ripped what you posted and tried that, so it's like this:

Zone "FXMenu"
	FXMenuNavigator
	DisplayUpper|		NoAction
	DisplayLower|		FXMenuNameDisplay
	Rotary|			NoAction
        RotaryPush|		Reaper 		"_S&M_SELFX|"
        RotaryPush|		Reaper 		"_S&M_FLOATFXEL|" 
	RotaryPush|		GoFXSlot
        Shift+RotaryPush|	Reaper 		"_S&M_FXBYP|" //Bypass FX Slot
        Option+RotaryPush|	Reaper 		"_S&M_FXOFF|" //Offline FX slot
ZoneEnd

As I mentioned, I get the FX across my scribble strips/rotaries in slot order, but clicking a rotary then only maps the controls from the FXzon file and doesn't open the FX/float window.

[cjewellstudios]

Hello. It's me. I was wondering if after all these years you'd...

I have solved ONE mystery. I *think there's just one left.

Deleting the Faderport XT drivers from Reaper>Prefs>Control/OSC/Web got rid of the the fxmenu flickering. That was caused by the track being selected a bazillion times when adjusted via mouse.

Mystery 2-

Still not registering a touch. This should definitely work and show on the input monitoring of CSI. Here's my widget:

Widget Fader1
    Control /Home/Fader1
    FB_Processor /Home/Fader1
    Touch /Home/Fader1/z
WidgetEnd

Oh yeah and Geoff you mentioned maybe something in the TouchOSC file. I opened the layout up in the editor and saw that the faders were set to relative and not absolute. I changed to absolute just in case. The result, as Funkybot would say, no dice.

(That's great that they can be relative though )

[cjewellstudios]

Originally Posted by spkr4thdd

Basically I ripped what you posted and tried that, so it's like this:

Zone "FXMenu"
	FXMenuNavigator
	DisplayUpper|		NoAction
	DisplayLower|		FXMenuNameDisplay
	Rotary|			NoAction
        RotaryPush|		Reaper 		"_S&M_SELFX|"
        RotaryPush|		Reaper 		"_S&M_FLOATFXEL|" 
	RotaryPush|		GoFXSlot
        Shift+RotaryPush|	Reaper 		"_S&M_FXBYP|" //Bypass FX Slot
        Option+RotaryPush|	Reaper 		"_S&M_FXOFF|" //Offline FX slot
ZoneEnd

As I mentioned, I get the FX across my scribble strips/rotaries in slot order, but clicking a rotary then only maps the controls from the FXzon file and doesn't open the FX/float window.

Floating the FX window like MixMonkey has it set up requires SWS Extensions. Do you have those installed? (just checking, I didn't see the rest of the discourse about this)

[ivanmihaljevic]

Installed the new experimental build and updated all the navigator names. It seems to work well.

Here are several bugs I ran into:

- TrackReceiveNameDisplay shows the name of the selected track instead of the name of the track that's being received.
So, if I have Track4 receiving from Tracks 1, 2 and 3. I would want TrackReceiveNameDisplay to show:

Track1    Track2    Track3

instead it shows:

Track4    Track4    Track4    Track4    Track4    Track4    Track4    Track4

- SelectedTrackFXMenu uses as many displays as there are effects slots, but then instead of blanking the rest of the displays, it keeps showing track names which makes orientation difficult.
As an example, let's say I have 3 plugins on my track. As I open SelectedTrackFXMenu, I want my display to show:

Plugin1    Plugin2    Plugin3

but instead it shows:

Plugin1    Plugin2    Plugin3    Track4    Track5    Track6    Track7    Track8

I tried:

    DisplayUpper|               NoAction
    DisplayUpper|               FXMenuNameDisplay

but it just made all the displays show nothing ignoring the second line. Reversing the order of the two lines makes it just ignore the second line again, so we go back to the original problem.

[spkr4thdd]

Originally Posted by cjewellstudios

Floating the FX window like MixMonkey has it set up requires SWS Extensions. Do you have those installed? (just checking, I didn't see the rest of the discourse about this)

Definitely worth checking, but yes I do

[cjewellstudios]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Hopefully fixed TrackFXMenuSlot bug.

Cleaned up a lot of the "unmaps", see if the "left over artifacts" issues are improving.

I don't have an FX Menu at all in this new build. I know a bunch of navigators were added and some changed but I didn't see where FXMenuNavigator changed at all. Unless it did?

....

Also my apologies if this isn't the type of feedback you were looking for

- TrackNames and TrackVolumeDisplays stay when you exit reaper or open a new project (until they are overwritten)

[MixMonkey]

Originally Posted by spkr4thdd

Basically I ripped what you posted and tried that, so it's like this:

Zone "FXMenu"
	FXMenuNavigator
	DisplayUpper|		NoAction
	DisplayLower|		FXMenuNameDisplay
	Rotary|			NoAction
        RotaryPush|		Reaper 		"_S&M_SELFX|"
        RotaryPush|		Reaper 		"_S&M_FLOATFXEL|" 
	RotaryPush|		GoFXSlot
        Shift+RotaryPush|	Reaper 		"_S&M_FXBYP|" //Bypass FX Slot
        Option+RotaryPush|	Reaper 		"_S&M_FXOFF|" //Offline FX slot
ZoneEnd

As I mentioned, I get the FX across my scribble strips/rotaries in slot order, but clicking a rotary then only maps the controls from the FXzon file and doesn't open the FX/float window.

Let me try and reproduce this on the MCU. At the moment all this takes place on my C4.

[ivanmihaljevic]

Originally Posted by cjewellstudios

I don't have an FX Menu at all in this new build. I know a bunch of navigators were added and some changed but I didn't see where FXMenuNavigator changed at all. Unless it did?

....

Also my apologies if this isn't the type of feedback you were looking for

- TrackNames and TrackVolumeDisplays stay when you exit reaper or open a new project (until they are overwritten)

It did change! It should be SelectedTrackFXMenuNavigator now

You can find the reference sheet for the new navigators here: https://i.imgur.com/ce0qVM9.png

[MST]

Good day, I'm glad about the new naming of things, makes everything much more intuitive, devil is in the details, but now one can give a glans over all the functions in the zone files and think, makes sense,, I can do that, exciting stuff.

I have a question, the MFTwister and Launchpadmini3 have special feedback processors so the 2-state buttons can have the button-colors altered in the zone files.
The on/of color states are altered by adding 2 new rgb values like { 90 255 0 255 50 0 }.

Is there also a possibility to alter the FB_TwoState on/of colors in a zone file ?
Something like { 15 35 } for the midi controllers that use just 1 7bit color index (like the Launchpads in normal mode, and most others)?

[spkr4thdd]

Originally Posted by MixMonkey

Let me try and reproduce this on the MCU. At the moment all this takes place on my C4.

Thanks. Other than weird LED illumination/flashing, this is pretty much the last big thing before I delve fully into the 1.1 version of zones and FX sub zones...

[cjewellstudios]

Originally Posted by ivanmihaljevic

It did change! It should be SelectedTrackFXMenuNavigator now

You can find the reference sheet for the new navigators here: https://i.imgur.com/ce0qVM9.png

DOH!

Thank you!

[MixMonkey]

Originally Posted by cjewellstudios

Hello. It's me. I was wondering if after all these years you'd...

I have solved ONE mystery. I *think there's just one left.

Deleting the Faderport XT drivers from Reaper>Prefs>Control/OSC/Web got rid of the the fxmenu flickering. That was caused by the track being selected a bazillion times when adjusted via mouse.

Mystery 2-

Still not registering a touch. This should definitely work and show on the input monitoring of CSI. Here's my widget:

Widget Fader1
    Control /Home/Fader1
    FB_Processor /Home/Fader1
    Touch /Home/Fader1/z
WidgetEnd

Oh yeah and Geoff you mentioned maybe something in the TouchOSC file. I opened the layout up in the editor and saw that the faders were set to relative and not absolute. I changed to absolute just in case. The result, as Funkybot would say, no dice.

(That's great that they can be relative though )

Have you enabled touch in the TouchOSC prefs?

[cjewellstudios]

Originally Posted by MST

Good day, I'm glad about the new naming of things, makes everything much more intuitive, devil is in the details, but now one can give a glans over all the functions in the zone files and think, makes sense,, I can do that, exciting stuff.

I have a question, the MFTwister and Launchpadmini3 have special feedback processors so the 2-state buttons can have the button-colors altered in the zone files.
The on/of color states are altered by adding 2 new rgb values like { 90 255 0 255 50 0 }.

Is there also a possibility to alter the FB_TwoState on/of colors in a zone file ?
Something like { 15 35 } for the midi controllers that use just 1 7bit color index (like the Launchpads in normal mode, and most others)?

Sort of!

I was playing around with my behringer CMD Touch a while back. If I changed a widget in my mst from this:

Widget ButtonA1
		Press 90 0C 7F 90 0C 00
		FB_TwoState 90 0C 7F 90 0C 00
WidgetEnd

to this:

Widget ButtonA1
		Press 90 0C 7F 90 0C 00
		FB_TwoState 90 0C 64 90 0C 00
WidgetEnd

The on state would be green instead of yellow.

But other than that, no not currently. Although with the eventual "send messages out to devices" feature being discussed somewhere down the line I'm sure that'd be possible.

[cjewellstudios]

Originally Posted by MixMonkey

Have you enabled touch in the TouchOSC prefs?

***laughs maniacally***

***crying intensifies***

I just didn't realize that was a thing. Or rather, I've forgotten that was a thing.

Man do I feel dumb.

Anyhow that obviously solved it.

Thank you very much for your persistence! Thanks to everyone that took some time to ponder this "mystery" and my apologies for any time wasted.

***crawls back into hole***