Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by fourdogslong

No pressure at all, but is there an ETA about when this will be complete, or close to it? Just asking cause I was initially installing all exp versions until I didn't have time anymore and for now I'm stocked with a version for which Learn seems broken.
I got some new plugins so I'd like to map them, I'll do it manually for now I think, but if a new version with a working learn system comes out soon I'll wait for it.

Thanks for all the hard work.
I hope after this new learn revamp you'll get a chance to fix the little bugs too (like the VU calibration) and maybe implement some suggestions that were made here. I thought the original learn process was ok to be quite honest but I understand the desire to improve things

Learn should be out soon, hang in there...

It has a new file format so any auto mapping you do would be lost as far as editing, except for manual, of course

[fourdogslong]

Originally Posted by Geoff Waddington

Learn should be out soon, hang in there...

It has a new file format so any auto mapping you do would be lost as far as editing, except for manual, of course

Cool, in that case I will wait for it and it will be a good opportunity to test it better. thanks

[Freex]

Originally Posted by Geoff Waddington

Was thinking of the standard Save and Cancel, agree Close is not the best.

Yeah that'll do it.

[Geoff Waddington]

Thinking of a slight workflow change.

The original thinking was that checking the Assign box would use the defaults from the FXWidgetLayout Zone if the Advanced Window was closed, and the values from the Advanced Window if it were open.

Playing around with the prototype, it feels better to have the Assign box always use the defaults from the FXWidgetLayout Zone, and populate the Advanced Window for editing.

Don't like the defaults ?

Edit the FXWidgetLayout Zone

Which also opens the door to an obvious feature down the road -- drop down to select the FXWidgetLayout Zone, kind of along the lines of templating.

Anyway, back to the present, what do you think of the workflow mentioned above ?

[Funkybot]

Originally Posted by Geoff Waddington

Thinking of a slight workflow change.

The original thinking was that checking the Assign box would use the defaults from the FXWidgetLayout Zone if the Advanced Window was closed, and the values from the Advanced Window if it were open.

Playing around with the prototype, it feels better to have the Assign box always use the defaults from the FXWidgetLayout Zone, and populate the Advanced Window for editing.

Don't like the defaults ?

Edit the FXWidgetLayout Zone

Which also opens the door to an obvious feature down the road -- drop down to select the FXWidgetLayout Zone, kind of along the lines of templating.

Anyway, back to the present, what do you think of the workflow mentioned above ?

Sounds cleaner and more predictable.

[Freex]

Originally Posted by Geoff Waddington

Which also opens the door to an obvious feature down the road -- drop down to select the FXWidgetLayout Zone, kind of along the lines of templating.

Anyway, back to the present, what do you think of the workflow mentioned above ?

If I'm understand you, we could have EQ, Comp, Delay templates....that would be an awesome time saver down the line.

And the work flow looks good.

[UNdark]

Originally Posted by Geoff Waddington

Thinking of a slight workflow change.

The original thinking was that checking the Assign box would use the defaults from the FXWidgetLayout Zone if the Advanced Window was closed, and the values from the Advanced Window if it were open.

Playing around with the prototype, it feels better to have the Assign box always use the defaults from the FXWidgetLayout Zone, and populate the Advanced Window for editing.

Don't like the defaults ?

Edit the FXWidgetLayout Zone

Which also opens the door to an obvious feature down the road -- drop down to select the FXWidgetLayout Zone, kind of along the lines of templating.

Anyway, back to the present, what do you think of the workflow mentioned above ?

Heading right down my road

[MixMonkey]

Originally Posted by Geoff Waddington

Thinking of a slight workflow change.

The original thinking was that checking the Assign box would use the defaults from the FXWidgetLayout Zone if the Advanced Window was closed, and the values from the Advanced Window if it were open.

Playing around with the prototype, it feels better to have the Assign box always use the defaults from the FXWidgetLayout Zone, and populate the Advanced Window for editing.

Don't like the defaults ?

Edit the FXWidgetLayout Zone

Which also opens the door to an obvious feature down the road -- drop down to select the FXWidgetLayout Zone, kind of along the lines of templating.

Anyway, back to the present, what do you think of the workflow mentioned above ?

This sounds fine to me, but I'm not sure why I would want to choose between multiple FXWidgetLayout Zones? It could be that I don't have to deal with font sizes, colors etc?

On a related note, I think you would get universal approval for a drop down to select FX templates. Having the layout and labels already filled in would be a great time saver and would guarantee consistency between FX, benefiting muscle memory.

[fourdogslong]

Originally Posted by MixMonkey

On a related note, I think you would get universal approval for a drop down to select FX templates. Having the layout and labels already filled in would be a great time saver and would guarantee consistency between FX, benefiting muscle memory.

I agree this would be great and I wish I had access to such a feature when I initially mapped my hundreds of plugins. It was hard to be consistent and it took forever.

[Funkybot]

Originally Posted by fourdogslong

I agree this would be great and I wish I had access to such a feature when I initially mapped my hundreds of plugins. It was hard to be consistent and it took forever.

I still think this is one of those "easier said than done" things. Like, take a compressor plugin. Many have stock ratio, attack, release, threshold controls, but just as many don't. Sometimes Threshold is fixed and tied to input gain. Sometimes there is no attack/release, or they're on switches. Reverbs can have multiple decays for different frequencies, or use delay multipliers and others don't.

I TRY very hard to keep the mapping consistent: 1) Reverb mix on widget 1, Pre-Delay on widget 2, Decay widget 3, that type of thing, but I found in practice I was "breaking the rules" due to plugin parameters being different from product to product that having a preset mapping would've just got in the way. Fully parametric EQ's are probably the most consistent (Freq, Q, Gain, HP+LP), but outside of that, it's the wild west with plugin params.

Maybe I'm just being a wet blanket but I think the amount of effort relative to the amount of real world gain is just way out of whack for that feature request and Geoff's time would be better utilized making improvements elsewhere in the short to medium term.

[fourdogslong]

Originally Posted by Funkybot

I still think this is one of those "easier said than done" things. Like, take a compressor plugin. Many have stock ratio, attack, release, threshold controls, but just as many don't. Sometimes Threshold is fixed and tied to input gain. Sometimes there is no attack/release, or they're on switches. Reverbs can have multiple decays for different frequencies, or use delay multipliers and others don't.

I TRY very hard to keep the mapping consistent: 1) Reverb mix on widget 1, Pre-Delay on widget 2, Decay widget 3, that type of thing, but I found in practice I was "breaking the rules" due to plugin parameters being different from product to product that having a preset mapping would've just got in the way. Fully parametric EQ's are probably the most consistent (Freq, Q, Gain, HP+LP), but outside of that, it's the wild west with plugin params.

Maybe I'm just being a wet blanket but I think the amount of effort relative to the amount of real world gain is just way out of whack for that feature request and Geoff's time would be better utilized making improvements elsewhere in the short to medium term.

You are right that this is way easier said than done but just having a naming template would be super useful for naming consistency.
Or maybe that's better done afterwards with a text editor like I did...?

[MixMonkey]

Originally Posted by Funkybot

I still think this is one of those "easier said than done" things.

Whilst I agree that plugins do differ considerably, my experience when mapping plugins has been to boil down the parameter choice to only the essential, most used controls. These are the parameters that would comprise the template.

Also, the template isn't absolute, it can get you 80% of the way there, leaving you to fill in the remaining 20%.

[Funkybot]

Originally Posted by MixMonkey

Whilst I agree that plugins do differ considerably, my experience when mapping plugins has been to boil down the parameter choice to only the essential, most used controls. These are the parameters that would comprise the template.

Also, the template isn't absolute, it can get you 80% of the way there, leaving you to fill in the remaining 20%.

Yeah, but how much faster is that than just 1) enter learn mode, 2) move param, 3) move widget, 4) click assign? Which you'd still need to do anyway. What does it buy you? Renaming the params on the displays automatically? I'm not saying don't do it, I certainly don't decide and this is just discussion anyway, but I think there's just a lot keeping Geoff busy at the moment with this big rewrite to polish, surface support to tighten up, longstanding feature requests I think some of us would all like to see (Invert, hold to retire an action x times per second, etc.). In a world of unlimited resources, I'd be all on board for it! Even trying to find a way to find "like param names" and automap them to the template where possible. But like I said, short to medium term, I just don't see where pursuing this doesn't become a lot of effort just to have relatively minimal benefit. In my head, it's about prioritization and where this falls on a cost/benefit. And I know literally jack about the effort involved. Maybe it's easy and could be quickly implemented. That would certainly change my thoughts on it.

[MixMonkey]

Originally Posted by Funkybot

Yeah, but how much faster is that than just 1) enter learn mode, 2) move param, 3) move widget, 4) click assign? Which you'd still need to do anyway. What does it buy you?

Deciding the layout and typing in the names is what takes the time, that's what it buys you

Maybe it's easy and could be quickly implemented. That would certainly change my thoughts on it.

I totally agree. It's only worth adding at this stage if it's trivial in terms of effort. Otherwise it can wait until everything else has bedded in.

[Geoff Waddington]

Thanks for the discussion everyone !

Yeah, it's definitely a down the road consideration.

[UNdark]

Originally Posted by Funkybot

I still think this is one of those "easier said than done" things. Like, take a compressor plugin. Many have stock ratio, attack, release, threshold controls, but just as many don't. Sometimes Threshold is fixed and tied to input gain. Sometimes there is no attack/release, or they're on switches. Reverbs can have multiple decays for different frequencies, or use delay multipliers and others don't.

I TRY very hard to keep the mapping consistent: 1) Reverb mix on widget 1, Pre-Delay on widget 2, Decay widget 3, that type of thing, but I found in practice I was "breaking the rules" due to plugin parameters being different from product to product that having a preset mapping would've just got in the way. Fully parametric EQ's are probably the most consistent (Freq, Q, Gain, HP+LP), but outside of that, it's the wild west with plugin params.

Maybe I'm just being a wet blanket but I think the amount of effort relative to the amount of real world gain is just way out of whack for that feature request and Geoff's time would be better utilized making improvements elsewhere in the short to medium term.

Interesting - to be totally open - I've found the opposite is true.
FB being very kind, even updating the code for me from v1 to v2 - but I had templates that remain the same even from then - sure the manufacturer calls them different things, but functions are the same and the benefit of looking at the lcd not the plug is where the consistency lies.
This is one thing I've been focused on from day one (as I'm sure everyone has been)
I have all the possible parameters for individual types of plugin in the same place in one template. All the names there but "666" as the number and remove name a required per plugin - replace with NoAction (though that's moved on now I think)
So in your example, the compressor temp would have:

No modifiers

1 "in"
2 "knee"
3 "sidechain"
4 blank
5 "link"
6 "MIX"
7 "limit"
8 : OUT"

CTRL modifier:

1 "IN"
2 "THRESH"
3 "ATT"
4 "REL"
5 "RATIO"
6 " MIX"
7 "blank"
8 " MAKEUP"

Keeping access to IN on both pages - If the compressor had no thresh I'd remove it from the display leaving the "IN" to control the threshold. So on the LCD I have no threshold, making it quite clear I need to use the input. If it didn't have makeup I'd leave that blank rather than replace with OUT - everything in the same place.

I took the most featured comp I had, laid that out and worked back from there - removing text where not required - same for stereo eq's etc. The important thing for me was a structure of modifiers as pages and that echoes MM comment about "muscle memory" and frankly... memory!
I couldn't really do what I've down with actual "pages" and have stuck with my templates using modifiers, which many have taken me up on the offer of downloading from my channel. There's no doubt the switch from mouse to controller is a slow reward. Initially after the novelty wears off, it needs to work and work better in some way than the mouse. I use a combo of mouse/keys/controller, taking the most practical feature of each rather than trying to only use a controller.

"select" steps through the switches. of the widget assigned to fader/rotary
"recarm" is alway ON''Off for that widget
"Solo"and :Mute" for auto gain' equal loudness and alternates per widget

I also realised I could assign the rotary to the same parameter as the fader and still have enough options for the plugins.

Synths work exactly like this too.

I absolutely love how CSI has created a workflow I could never have imagined, with all the crappy work for the mouse being elegantly replaced with the controller.
It is possible to remain consistent across general FX. I think we'd still be looking at gimmick no more advanced than novation's automap if that wasn't true.

We're not.
The specialisation and ability to create consistent templates and workflow is the pinnacle of CSI's ability ... one of
Geoff. You're a F***ing legend mate. I hope the recognition comes from all reaper users when CSI becomes integral to the program.

[MT4U]

I've had similar experiences as FB here, trying to find some common ground when mapping plug-ins other than EQ has gotten me ending up mapping according to the parameter order in the plug-in UI most of the time.

That said, synthesizers in particular (with many SubZones) are the ones that I've been able to keep more consistently-mapped.

[fourdogslong]

Is there a trick to setup a "solo in place" or "solo exclusive" (same thing, different language) with CSI?

I use a script for that that works fine with the mouse but not with the console. I would much rather always be in "solo in place" mode and ctrl+solo or shift+solo to add more soloed track.

[Geoff Waddington]

Originally Posted by fourdogslong

Is there a trick to setup a "solo in place" or "solo exclusive" (same thing, different language) with CSI?

I use a script for that that works fine with the mouse but not with the console. I would much rather always be in "solo in place" mode and ctrl+solo or shift+solo to add more soloed track.

Not sure on that one, hopefully someone will chime in.

[Geoff Waddington]

Here's the latest, seems most natural broken into 4 chunks.

Didn't bother showing the Params dialog -- custom steps, deltas, etc.

Here are the other three:

[Funkybot]

Makes sense. So few surfaces will ever have the ability to modify display colors/fonts.

[MixMonkey]

Originally Posted by Funkybot

Makes sense. So few surfaces will ever have the ability to modify display colors/fonts.

It might never be more than one...

[Funkybot]

Originally Posted by MixMonkey

It might never be more than one...

I think two! The Faderport display widgets that got developed as part of Reasonus have quite a few display properties too. I imagine someday they'll get added to that screen.

[fourdogslong]

I think I found a bug, unless it's something wrong with my config.
This:

    DisplayUpper|               TrackNameDisplay
	DisplayUpper2               NoAction
	DisplayUpper3               NoAction
	DisplayUpper4               NoAction
	DisplayUpper5               NoAction
	DisplayUpper6               NoAction
	DisplayUpper7               NoAction
	DisplayUpper8               NoAction
    DisplayLower|               FXMenuNameDisplay

In my SelectedTrackFXMenu zone does not update the display properly.
When I select a track that has 2 plugins for example and go in my zone SelectedTrackFXMenu, I see the 2 plugins' names fine, but when I then select another track with only 1 plugin on it, the second plugin's name from my initial track selection remains visible.
The display only updates if there is a new plugin to be shown but if there is no plugins to be shown the display keeps showing the plugins' names from my initial track selection.

Is there a fix?

EDIT: I put back the official CSI release and it works, so it must be a bug with the experimental version I was using which was from April.

EDIT2: Looking through this thread, I see there is a new Exp version that probably fixes my issue.
What do I need to change in my config for it to work if I come from the official version? Just trashing the CSI config file and using the new exp version, everything looks messed up and not much work so there must have been changes made to zones or something like that.

[MixMonkey]

Originally Posted by fourdogslong

What do I need to change in my config for it to work if I come from the official version?

A lot has changed, even the basic Zone folder structure. I've attached my MCU folder so you can pull it apart for the differences.

Some of the big changes are:

i) New folder structure
ii) The old Home and Button Zones are combined into a new Home Zone.
iii) Associated Zones are now called GoZones and have their own folder, with GoAssociated Zone changing to GoZone.
iv) Included Zones are now called Home Zones and have their own folder.
v) The learn system has been completely overhauled and is not finished yet.
vi) AutoMap has been removed.

[fourdogslong]

Originally Posted by MixMonkey

A lot has changed, even the basic Zone folder structure. I've attached my MCU folder so you can pull it apart for the differences.

Some of the big changes are:

i) New folder structure
ii) The old Home and Button Zones are combined into a new Home Zone.
iii) Associated Zones are now called GoZones and have their own folder, with GoAssociated Zone changing to GoZone.
iv) Included Zones are now called Home Zones and have their own folder.
v) The learn system has been completely overhauled and is not finished yet.
vi) AutoMap has been removed.

Thanks, I'll backup my config and give that a shot!

[fourdogslong]

Originally Posted by MixMonkey

A lot has changed, even the basic Zone folder structure. I've attached my MCU folder so you can pull it apart for the differences.

Some of the big changes are:

i) New folder structure
ii) The old Home and Button Zones are combined into a new Home Zone.
iii) Associated Zones are now called GoZones and have their own folder, with GoAssociated Zone changing to GoZone.
iv) Included Zones are now called Home Zones and have their own folder.
v) The learn system has been completely overhauled and is not finished yet.
vi) AutoMap has been removed.

Ok I gave this a shot, I was not sure where to put my subzones but leaving them in the top folder seems to work.

The commands seems to work however some of my led are not behaving correctly.
My Stop button flashes a little bit, normally it stays lit unless I hit play.
All of my Select buttons are always lit, pressing one of them works but they still all stay lit.
Same thing goes for my solo buttons, they work but as soon as one track is soloed all solo buttons turn on.

Then when I go in a zone, the associated button does not light up.
EDIT: actually I'm unable to enter any of my zone, I changed GoAssociatedZone to GoZone in my Home.zon and I followed the new folder hierarchy but to no avails.


Did anything also change in the feedback processors in the surfaces mst files?

[Funkybot]

Originally Posted by MixMonkey

i) New folder structure
ii) The old Home and Button Zones are combined into a new Home Zone.
iv) Included Zones are now called Home Zones and have their own folder.

I think these are all technically still optional (as in prior configs will still work in respect to these). You can keep your old folder structure. You can have a separate buttons.zon.

Also, just to be really pedantic: they're still called IncludedZones in zone files.

[MixMonkey]

Originally Posted by fourdogslong

Did anything also change in the feedback processors in the surfaces mst files?

If you have more than one Action defined for a button, you have to add NoFeedback to all but one of the definitions. Check out the Stop definitions in my MCU Home Zone.

[MixMonkey]

Originally Posted by Funkybot

Also, just to be really pedantic: they're still called IncludedZones in zone files.

Good point, so they are.

[fourdogslong]

Looks like I missed that I needed to create a GoZones.zon file and put it in the GoZones folder. So I did that but now Reaper crashes when trying to initiate CSI.
I deleted my CSI.ini file and made a fresh one from the CSI preference interface but as soon as I clicked ok Reaper crashed again.

I'm on Windows 11.
I must be missing a step somewhere.
Here's my config if anyone can look at it and tell me where I messed up I'd appreciate it!

https://stash.reaper.fm/49132/CSI.zip

[fourdogslong]

Originally Posted by MixMonkey

If you have more than one Action defined for a button, you have to add NoFeedback to all but one of the definitions. Check out the Stop definitions in my MCU Home Zone.

Ok, I did not see that, thanks. However as I said in my previous post now Reaper crashes. I'll try it but I doubt it will fix that, we'll see.

[MixMonkey]

Originally Posted by fourdogslong

EDIT: actually I'm unable to enter any of my zone, I changed GoAssociatedZone to GoZone in my Home.zon and I followed the new folder hierarchy but to no avail

Have you created a GoZones.zon file? EDIT: cross post, sorry

[fourdogslong]

Originally Posted by MixMonkey

Have you created a GoZones.zon file?

Yes I posted about it afterwards. I'm now getting crashes since I did that unfortunately. See post 26311

[MixMonkey]

Originally Posted by fourdogslong

Here's my config if anyone can look at it and tell me where I messed up I'd appreciate it!
https://stash.reaper.fm/49132/CSI.zip

Not at home at the moment, can look later though

[fourdogslong]

Originally Posted by MixMonkey

Not at home at the moment, can look later though

No worries, thank you!

[fourdogslong]

Ok I fixed a bunch of stuff and I was able to determine that my TrackFXMenu and SelectedTrackFXMenu zones are the 2 zones that cause Reaper to crash instantly.

Meanwhile I am working on implementing properly the NoFeedback property, I'm getting there.

Here are my 2 problematic zones.
Any cue what can cause these crashes?

Zone "SelectedTrackFXMenu"

	ChannelLeft		    		Reaper 40286	//Track: Go To Previous Track
	ChannelRight		    	Reaper 40285	//Track: Go To Next Track
	BankLeft					Bank Track -8
	BankRight					Bank Track 8
	
	OnZoneDeactivation 	    	HideFXSlot
	OnZoneDeactivation	    	ClearModifiers
	
	
	Esc			    			AllSurfacesGoHome
	
	// To unmap and close the focused FX returning to the previous zone. This prevents the unfocusing FX problem.

	F2                      	Reaper _RSa79773b81ca82d98b618f3bc8b79e3ba8616085a     // MT4U_FX_SHOW_HIDE_CloseFocused.eel
	F2                      	ClearFocusedFX NoFeedback
	
	// Now the actual plug-in movers.

	Up             	      		Reaper _RS95211454bfbef97e0215b0b918446426978d0014      // Script: MT4U_FX_MENU_MoveUp.eel
	Down      		      		Reaper _RScab515c7031f31eec2ec211302e3ca346798462d      // Script: MT4U_FX_MENU_MoveDown.eel
	
	// To swap the focused FX with the next/prev on our list

	Alt+ChannelLeft          	ClearFocusedFX Feedback=No NoFeedback
	Control+Alt+ChannelLeft   	Reaper _RS20a3b18140b5bb47c52beb9c27b387270d07a1f1 Feedback=Yes  // MT4U_FX_FOCUSED_Prev.eel
	Alt+ChannelRight       	    ClearFocusedFX Feedback=No NoFeedback
	Control+Alt+ChannelRight  	Reaper _RS14225070f26ef670af7ca2ec077792ae9f389f05 Feedback=Yes  // MT4U_FX_FOCUSED_Next.eel

ZoneEnd

Zone "TrackFXMenu"
    DisplayUpper|               TrackNameDisplay
    DisplayLower|               FXMenuNameDisplay
    Select|                     TrackUniqueSelect
    RotaryPush|                 ShowFXSlot
	RotaryPush|                 GoFXSlot
	Shift+RotaryPush|           Reaper _S&M_FXBYP|              //Bypass FX Slot
 	
    Up                          Bank TrackFXMenu -1
    Down                        Bank TrackFXMenu 1
	OnZoneDeactivation	    	ClearModifiers 
	Alt+RecordArm1		    	RemapAutoZone	
	Esc			    			AllSurfacesGoHome
// To unmap and close the focused FX returning to the previous zone. This prevents the unfocusing FX problem.

  F2                      		Reaper _RSa79773b81ca82d98b618f3bc8b79e3ba8616085a     // MT4U_FX_SHOW_HIDE_CloseFocused.eel
  F2                      		ClearFocusedFX
ZoneEnd

EDIT: I'm reuploading my CSI config.
I am unable to make my modifiers work in my GoZones. Flip, Shift, Option, Control and Alt do nothing in other zones than Home. Flip is not predictable.

Is that a known issue currently?

[MixMonkey]

Originally Posted by fourdogslong

Here are my 2 problematic zones.
Any cue what can cause these crashes?

I am unable to make my modifiers work in my GoZones. Flip, Shift, Option, Control and Alt do nothing in other zones than Home. Flip is not predictable.

Is that a known issue currently?

Your SelectedTrackFXMenu Zone doesn't really have any relationship to the SelectedTrackFXMenu - there are no FXMenuNameDisplay definitions and no GoFXSlot. You might be better served by turning this into a SubZone in Home, rather than using the SelectedTrackFXMenu context.

The TrackFXMenu looks ok. You probably don't need Select|, as it should still be active via Track.zon.

If you want to troubleshoot this, I'd start by leaving out the SelectedTrackFXMenu Zone and concentrating on the TrackFXMenu. Comment out all the lines except the bare minimum needed to make the Zone work (Displays, GoFXSlot etc) and see if it still crashes.

If the crashing seems really intractable, I'd suggest rebuild the configuration from scratch so that you can isolate the issue.

Regading modifiers, they all seem to be working ok here, nothing out of the ordinary.

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Possible temp fix for fourdogslong crash.

This occurs in the OnZoneDeactivation lines, and is due to an internal bug.

Hacked around it for now -- fingers crossed

You can also take a peek at the new Learn GUI, but is mostly non functional

[fourdogslong]

Originally Posted by MixMonkey

Your SelectedTrackFXMenu Zone doesn't really have any relationship to the SelectedTrackFXMenu - there are no FXMenuNameDisplay definitions and no GoFXSlot. You might be better served by turning this into a SubZone in Home, rather than using the SelectedTrackFXMenu context.

I forgot that my SelectedTrackFXMenu is split accross 2 controller.
Controller 1:

Zone "SelectedTrackFXMenu"

	ChannelLeft		    		Reaper 40286	//Track: Go To Previous Track
	ChannelRight		    	Reaper 40285	//Track: Go To Next Track
	BankLeft					Bank Track -8
	BankRight					Bank Track 8
	
	OnZoneDeactivation 	    	HideFXSlot
	OnZoneDeactivation	    	ClearModifiers
	
	
	Esc			    			AllSurfacesGoHome
	
	// To unmap and close the focused FX returning to the previous zone. This prevents the unfocusing FX problem.

	F2                      	Reaper _RSa79773b81ca82d98b618f3bc8b79e3ba8616085a     // MT4U_FX_SHOW_HIDE_CloseFocused.eel
	F2                      	ClearFocusedFX NoFeedback
	
	// Now the actual plug-in movers.

	Up             	      		Reaper _RS95211454bfbef97e0215b0b918446426978d0014      // Script: MT4U_FX_MENU_MoveUp.eel
	Down      		      		Reaper _RScab515c7031f31eec2ec211302e3ca346798462d      // Script: MT4U_FX_MENU_MoveDown.eel
	
	// To swap the focused FX with the next/prev on our list

	Alt+ChannelLeft          	ClearFocusedFX Feedback=No NoFeedback
	Control+Alt+ChannelLeft   	Reaper _RS20a3b18140b5bb47c52beb9c27b387270d07a1f1 Feedback=Yes  // MT4U_FX_FOCUSED_Prev.eel
	Alt+ChannelRight       	    ClearFocusedFX Feedback=No NoFeedback
	Control+Alt+ChannelRight  	Reaper _RS14225070f26ef670af7ca2ec077792ae9f389f05 Feedback=Yes  // MT4U_FX_FOCUSED_Next.eel

ZoneEnd

Controller 2 (channel 9-16)

Zone "SelectedTrackFXMenu"

    DisplayUpper|               TrackNameDisplay
	DisplayUpper2               NoAction
	DisplayUpper3               NoAction
	DisplayUpper4               NoAction
	DisplayUpper5               NoAction
	DisplayUpper6               NoAction
	DisplayUpper7               NoAction
	DisplayUpper8               NoAction
    DisplayLower|               FXMenuNameDisplay

    Rotary|                     NoAction
    RotaryPush|                 Reaper _S&M_TOGLFLOATFX|        //Float the FX window
    Mute|          			 	Reaper _S&M_FXBYP|              //Bypass FX Slot
    Option+Mute|          		Reaper _S&M_FXOFF|              //Offline FX slot
    RotaryPush|                 GoFXSlot
    Left                        Bank SelectedTrackFXMenu -8
    Right                       Bank SelectedTrackFXMenu 8
	OnZoneDeactivation 	    	HideFXSlot
	OnZoneDeactivation	    	ClearModifiers
	ChannelLeft		    		Reaper 40286	//Track: Go To Previous Track
	ChannelRight		    	Reaper 40285	//Track: Go To Next Track
	BankLeft					Bank Track -8
	BankRight					Bank Track 8
	Alt+RecordArm1		    	RemapAutoZone	
	Esc			    			AllSurfacesGoHome
// To unmap and close the focused FX returning to the previous zone. This prevents the unfocusing FX problem.

	F2                      	Reaper _RSa79773b81ca82d98b618f3bc8b79e3ba8616085a     // MT4U_FX_SHOW_HIDE_CloseFocused.eel
	F2                      	ClearFocusedFX

// These lines provide the Prev/Next plug-in for each slot in the chain.

	Alt+Increase+Rotary1        Reaper _RSc545ff69f595f1cae309546bcdb9179f7429c0e3      // MT4U_FX_MENU_Next_01.eel
	Alt+Increase+Rotary2        Reaper _RS5439e90ffa8d42ed4c792c6b3a3ea73cf00fba3b      // MT4U_FX_MENU_Next_02.eel
	Alt+Increase+Rotary3        Reaper _RS68d54e0a0cfd883a7a32300ad232da0b0b014582      // MT4U_FX_MENU_Next_03.eel
	Alt+Increase+Rotary4        Reaper _RS03d759a19dd784936c0623261989a9d068b506b9      // MT4U_FX_MENU_Next_04.eel
	Alt+Increase+Rotary5        Reaper _RSb2361f8e123048bd39d7939940b69a1bf42c9548      // MT4U_FX_MENU_Next_05.eel
	Alt+Increase+Rotary6        Reaper _RS85f1b59aeae81a32fefe19bf6450a0fa211a6481      // MT4U_FX_MENU_Next_06.eel
	Alt+Increase+Rotary7        Reaper _RSef0d0b1af31dc05cb612426330c91fe07772ba69      // MT4U_FX_MENU_Next_07.eel
	Alt+Increase+Rotary8        Reaper _RS1f833e289409ee010d55aef22db12d40c2682bbc      // MT4U_FX_MENU_Next_08.eel
	Alt+Decrease+Rotary1        Reaper _RS94465c3306bb9b3c9d55b8c7178f5ed761470a11      // MT4U_FX_MENU_Prev_01.eel  
	Alt+Decrease+Rotary2        Reaper _RSa53d4aacb8b072d7a6ab0396a9defe16ad65cdb9      // MT4U_FX_MENU_Prev_02.eel  
	Alt+Decrease+Rotary3        Reaper _RS074637b1b554af8249c502f39f5ed701aa8f31e9      // MT4U_FX_MENU_Prev_03.eel  
	Alt+Decrease+Rotary4        Reaper _RS6c27b24ff350d5e37917f5d04efe37a8cbddc3c8      // MT4U_FX_MENU_Prev_04.eel  
	Alt+Decrease+Rotary5        Reaper _RSe93b961d483b93912ed350205563a80bf3d1ca4f      // MT4U_FX_MENU_Prev_05.eel  
	Alt+Decrease+Rotary6        Reaper _RSc5afaed8eff8f9fe6fadd2aef6113d8fa8cf64e4      // MT4U_FX_MENU_Prev_06.eel  
	Alt+Decrease+Rotary7        Reaper _RSebb16895b121c261b4738e73ad6fc42db29f0909      // MT4U_FX_MENU_Prev_07.eel  
	Alt+Decrease+Rotary8        Reaper _RS8cdd865f8ede7ec4e95a7f433bea329f780d1362      // MT4U_FX_MENU_Prev_08.eel  

// FX Selection. These allow us to select a plug-in, so we can move it up or down whithin the chain.

	Select1                  Reaper _RS5a050d77bb0db671a322ab6afeea1c473e23922b      // MT4U_FX_MENU_Sel_01.eel
	Select2                  Reaper _RS943d149b67e3955639628ad3fcba5ecb09ef0a0e      // MT4U_FX_MENU_Sel_02.eel
	Select3                  Reaper _RS9c174a048d6852aac1146045de404f785820876b      // MT4U_FX_MENU_Sel_03.eel
	Select4                  Reaper _RSc39ebef0a88dcbbb01c9a266ca09f1086bfd06ad      // MT4U_FX_MENU_Sel_04.eel
	Select5                  Reaper _RS50b6875f1a9ec9faec87346b6116d0a98007f32f      // MT4U_FX_MENU_Sel_05.eel
	Select6                  Reaper _RS9cfda924b0efc46db8d57a8bd41e7375304c370e      // MT4U_FX_MENU_Sel_06.eel
	Select7                  Reaper _RS306c3f85913dbdd73e5ad305d2d2b68d63aebad7      // MT4U_FX_MENU_Sel_07.eel
	Select8                  Reaper _RS0088ef7ea422f2bb69a043a6065cb578405e4fa0      // MT4U_FX_MENU_Sel_08.eel

// Now the actual plug-in movers.

	Up             	      		Reaper _RS95211454bfbef97e0215b0b918446426978d0014      // Script: MT4U_FX_MENU_MoveUp.eel
	Down      		      		Reaper _RScab515c7031f31eec2ec211302e3ca346798462d      // Script: MT4U_FX_MENU_MoveDown.eel

// To delete a plug-in.

	Hold+Select1             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select2             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select3             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select4             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select5             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select6             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select7             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
	Hold+Select8             Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel

// To swap the focused FX with the next/prev on our list

	Alt+ChannelLeft          	ClearFocusedFX Feedback=No
	Control+Alt+ChannelLeft   	Reaper _RS20a3b18140b5bb47c52beb9c27b387270d07a1f1 Feedback=Yes // MT4U_FX_FOCUSED_Prev.eel
	Alt+ChannelRight       	    ClearFocusedFX Feedback=No
	Control+Alt+ChannelRight  	Reaper _RS14225070f26ef670af7ca2ec077792ae9f389f05 Feedback=Yes // MT4U_FX_FOCUSED_Next.eel

ZoneEnd

EDIT: forgot to say thank you for taking the time to look into it!