Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by Funkybot

Geoff, yes, the files were visible in the dropdown.

Now that I removed the spaces from the file names and the folder name, stuff is now happening. Namely: transport controls work.

And yes, now I can get the no-op action to run. It did nothing before.

I can also see things like Fader and Rotary movements in the Learn window, but I haven't figured out how to actually get the faders to do anything yet. But this is definitely progress.

EDIT: I tried figuring out how to add Fader1 from the left to the Zone to control Channel 1 (things look off) and when I clicked Fader1 then Add to Zone, it crashed Reaper.

Great, glad you got going.

Ok folks, let's not use any spaces for now in the .mst/.ost/.zon files and folders.

I've posted this often, and will again here -- Learn Mode window is experimental -- folks wanted a sneak peek -- that's why it's hard to get to -- be careful.

[WaveTrans]

Ok, in my hands, only the full MCU.mst with 8 channels works as it should with the Icon platform Nano-single fader controller. Not yet understanding why it needs the 8 channels for a single fader, but I´m ready to accept it.

Good news, I got sends working now.
Found out, when opening the sends menu manually.

-Now I´m wondering how to make the menu open automatically when hitting the send button. Is this possible at all? or just my setup?

-Next question: only the first volume fader is under control.
How to switch to the next send volume fader?

Would appreciate any answers, cheers.

[n0ne]

Originally Posted by WaveTrans

Ok, in my hands, only the full MCU.mst with 8 channels works as it should with the Icon platform Nano-single fader controller. Not yet understanding why it needs the 8 channels for a single fader, but I´m ready to accept it.

Good news, I got sends working now.
Found out, when opening the sends menu manually.

-Now I´m wondering how to make the menu open automatically when hitting the send button. Is this possible at all? or just my setup?

-Next question: only the first volume fader is under control.
How to switch to the next send volume fader?

Would appreciate any answers, cheers.

Hi WaveTrans,

Attached my zone and layout files for the platform Nano. Renamed a bunch of the widgets to make more sense for this controller and removed some of the faders/buttons that aren't on the controller. The buttons, fader+vu, masterfader (without vu) all work. Might help!

@Geoff:
- For me the shift option (or any combination of buttons) doesn't seem to work.
- For some reason there seemed to be hanging of some state for the controller. For my current 'test' setup (attached) the name/db value displays weren't working. They started working again after I loaded the standard MCU zone file and left the send menu that was still activated. Then reloading my own 'test' setup back and the names worked again.

[WaveTrans]

Cheers, n0ne!
will look into it this evening.
From here, it looks very similar to what I have tried as setup.
Well, we will see...

Cordially, WT

[WaveTrans]

Originally Posted by n0ne

Hi WaveTrans,

Attached my zone and layout files for the platform Nano. Renamed a bunch of the widgets to make more sense for this controller and removed some of the faders/buttons that aren't on the controller. The buttons, fader+vu, masterfader (without vu) all work. Might help!

@Geoff:
- For me the shift option (or any combination of buttons) doesn't seem to work.
- For some reason there seemed to be hanging of some state for the controller. For my current 'test' setup (attached) the name/db value displays weren't working. They started working again after I loaded the standard MCU zone file and left the send menu that was still activated. Then reloading my own 'test' setup back and the names worked again.

Thanks for the files, n0ne!

Both Work in general as they should.

But I must take a closer look, since the record button does not work.

Will also try to implement send and FXmenu.

Cheers, again.

[WaveTrans]

Originally Posted by WaveTrans

Thanks for the files, n0ne!

Both Work in general as they should.

But I must take a closer look, since the record button does not work.

Will also try to implement send and FXmenu.

Cheers, again.

Ok. First achievment, record record was not in the zone file.
Now record button works.

and...

REAPER 6 is out

[WaveTrans]

Got zoom working, using jogwheelhack from n0ne´s files.
Set jogwheel to scroll left right.
Tried to use scrub for up down scroll, but that did not work, although the button code is sent

.mst

....
Widget Up
	Press 90 60 7f
WidgetEnd

Widget Down
	Press 90 61 7f
WidgetEnd

Widget Left
	Press 90 62 7f
WidgetEnd

Widget Right
	Press 90 63 7f
WidgetEnd

Widget Zoom
	Press 90 64 7f 90 64 00
	FB_TwoState 90 64 7f 90 64 00
WidgetEnd

Widget Scrub
	Press 90 65 7f 90 65 00
	FB_TwoState 90 65 7f 90 65 00
WidgetEnd

Widget JogWheelRotaryCW
	Press b0 3c 01
WidgetEnd

Widget JogWheelRotaryCW2
	Press b0 3c 02
WidgetEnd

Widget JogWheelRotaryCW3
	Press b0 3c 03
WidgetEnd

Widget JogWheelRotaryCW4
	Press b0 3c 04
WidgetEnd

Widget JogWheelRotaryCW5
	Press b0 3c 05
WidgetEnd

Widget JogWheelRotaryCW6
	Press b0 3c 06
WidgetEnd

Widget JogWheelRotaryCW7
	Press b0 3c 07
WidgetEnd

Widget JogWheelRotaryCCW
	Press b0 3c 41
WidgetEnd

Widget JogWheelRotaryCCW2
	Press b0 3c 42
WidgetEnd

Widget JogWheelRotaryCCW3
	Press b0 3c 43
WidgetEnd

Widget JogWheelRotaryCC4
	Press b0 3c 44
WidgetEnd

Widget JogWheelRotaryCCW5
	Press b0 3c 45
WidgetEnd

Widget JogWheelRotaryCCW6
	Press b0 3c 46
WidgetEnd

Widget JogWheelRotaryCCW7
	Press b0 3c 47
WidgetEnd
...

.zon

...
Zone JogWheelHack
/ scroll view left
	JogWheelRotaryCW Reaper 40140
	JogWheelRotaryCW2 Reaper 40140	
	JogWheelRotaryCW3 Reaper 40140	
	JogWheelRotaryCW4 Reaper 40140
	JogWheelRotaryCW5 Reaper 40140
	JogWheelRotaryCW6 Reaper 40140
	JogWheelRotaryCW7 Reaper 40140

/scroll view right
	JogWheelRotaryCCW Reaper 40141	
	JogWheelRotaryCCW2 Reaper 40141
	JogWheelRotaryCCW3 Reaper 40141
	JogWheelRotaryCCW4 Reaper 40141	
	JogWheelRotaryCCW5 Reaper 40141	
	JogWheelRotaryCCW6 Reaper 40141	
	JogWheelRotaryCCW7 Reaper 40141	

	Zoom+Up Reaper 40111
	Zoom+Down Reaper 40112
	Zoom+Right Reaper 1012
	Zoom+Left Reaper 1011
ZoneEnd
...

Had issues with power drive failure blue screens (win 10) during testing.
Guess it´s the antivirus.

[Funkybot]

I've got a Steinberg CMC-QC, and outside of Cubase, it's just a tricky device to setup (probably Steinberg crippling features).

The CMC-QC shows up as 3 separate MIDI devices in Windows. The device called "Steinberg CMC-QC-1" transmits the knob values. "Steinberg CMC-QC-2" transmits button presses. No idea what "QC-3" does (probably something Cubendo specific - my guess is the device those DAWs use to communicate to the unit) - so I'm not even worried about that one. I'm just focusing on CMC-QC-1 and QC-2 for now.

So question: because they're totally different MIDI devices/ports, I'd have to setup two different devices in CSI for this right? Then combine them in CSI?

Might take another stab at this with the QC since it's only a few knobs and buttons.

[n0ne]

@WaveTrans cool to see its working for you! I'm changeing a lot still, but some worhwile things for you to check might be adding

Select1 TrackUniqueSelect

To you channel zone. That solves the problem I had with the display not updating.

You can also control the sends with the fader if you want: On the Platform Nano I've mapped the <<8 an 8>> buttons to select the tracks, but in send mode (press send button) you can use the |< and >| buttons to go through the sends. Only annoying thing is that you have to go back to send 1 when you leave the send menu to get the volume fader back (|< and >| buttons actually change the fader on the hardware device to represent fader1 through 8. Only fader1 is used to control track volume). Also note that when I load/refresh the surface it starts in send mode, leave that first to control the tracks as expected.

I've attached what I'm currently working with. Added back faders 2 till 8 widgets because they're needed for the sends. Good luck!

[n0ne]

On another note... is it possible to update the selected track with actions/scripts?

If I select a track from an action or script the control surface doesn't reflect the newly selected track. The only work around I've found now is creating an action that focuses the last touched track, and go's to next and then previous track

[CraigGE]

Originally Posted by Geoff Waddington

Been thinking about MasterTrack.

FWIW, I've updated my XTouchMini zon file to include this adjustment... latest version can be found in my signature.

[WaveTrans]

Originally Posted by n0ne

@WaveTrans cool to see its working for you! I'm changeing a lot still, but some worhwile things for you to check might be adding

Select1 TrackUniqueSelect

To you channel zone. That solves the problem I had with the display not updating.

You can also control the sends with the fader if you want: On the Platform Nano I've mapped the <<8 an 8>> buttons to select the tracks, but in send mode (press send button) you can use the |< and >| buttons to go through the sends. Only annoying thing is that you have to go back to send 1 when you leave the send menu to get the volume fader back (|< and >| buttons actually change the fader on the hardware device to represent fader1 through 8. Only fader1 is used to control track volume). Also note that when I load/refresh the surface it starts in send mode, leave that first to control the tracks as expected.

I've attached what I'm currently working with. Added back faders 2 till 8 widgets because they're needed for the sends. Good luck!

Thanks for files and tips.
My current setup is quite different from yours, but also starts in active Send mode; no clue why. Apart from that sends work fine for the first channel. Tried Send switch through as you described, but couldn´t get it to work. attached are my current files. Tried the variation with different Send1, Send2, sendn+1 zones but that didn´t work properly either.

Unfortunately I don´t know anything about that track selection stuff, but I found out that if you include "Rotary| TrackSendPan" in the send zone, you get send-pan

[WaveTrans]

Had first success with fxzones during the afternoon till 20 minutes ago, since then nothing works anymore. very strange.

Midi output is a continuous stream of 90 00 00
learn Window opens with full menues and reaper crashes.
volume faders are -inf.
clean new project doesn´t change anything.

really strange.

resetted firmware to 1.08 and everything behaves like before...

curiouser and curiouser

[Geoff Waddington]

Originally Posted by WaveTrans

TrackSendBank is TrackBank for Sends.

...a bit embarassing...and not hard to find, if you know, but the thread is very long indeed. Post #3226 explains it all; suggest to also put it into the MCU.zon stock file

https://forum.cockos.com/showpost.ph...postcount=3226

playing around, one can reach the first send channel pressing assigned Send button, then switching through send channels with channelLeft/Right also works; switching back just works to send2. to get back to Send1, one has to leave Sends and enter sends again. Switching from Send2 to Send1 via TrackSenBank, switches to the next track instead of Send1 and track numbers are disarrayed after that; Reaper crashed frequently afterwards.

If it's not in the Action list in the doc -- I try to keep it up to date -- please don't use it, as you have discovered

[lubvic]

hi guys,
i'vebeen out of the games for a long time, today i checked this new version and found it fantastic... i'd like to be stick with it, but... i can't tweak my plugins anymore from my XTOUCH, no way... i need to assign to widget my focused fx, here is my .zon, where i'm wrong?


MCU.zon

Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
MasterChannel
Buttons
Channel|1-8
IncludedZonesEnd
ZoneEnd

Zone MasterChannel
MasterTrackNavigator
MasterFader TrackVolume
TrackTouch+MasterFader TrackVolume
MasterFaderTouch TrackTouch
ZoneEnd

Zone Buttons
Plugin MapFocusedFXToWidgets
Instrument Reaper _S&M_SELFXNEXT
Shift+Plugin Reaper 40298
Send ToggleMapSelectedTrackSends
Track GoZone Home
ChannelLeft TrackBank -1
...
...


and in my plugin .zon:

Zone "VST: ReaComp (Cockos)" ReaComp
FocusedFXNavigator
Rotary1 FXParam 0 Thresh
Rotary2 FXParam 2 Attack
...
...


if i use FXmenu mode, things goes well but can't show param names in displays.
Hope to stay here for much more time from now ;-)

[WaveTrans]

fd

Originally Posted by Geoff Waddington

That's what was preventing ANY metering from showing

I discovered you could turn on only the signal LED so I tried that first, as you know.

Now CSI will turn on both the LED and the display.

Originally Posted by Geoff Waddington

If it's not in the Action list in the doc -- I try to keep it up to date -- please don't use it, as you have discovered

Erased all the outdated commands from my .zon file. still works fine.
Sorry about being confused - it´s not easy to keep up with this fast paced project...

[MixMonkey]

Originally Posted by lubvic

Zone "VST: ReaComp (Cockos)" ReaComp
FocusedFXNavigator
Rotary1 FXParam 0 Thresh
Rotary2 FXParam 2 Attack
...
...

You need to add a definition for the displays in the FX .zon file:

Zone "VST: ReaComp (Cockos)" ReaComp
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay 0
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0 Thresh

....

In my experience, the FX menu method is more reliable/predictable than the focused FX method. The FX menu uses the SelectedTrackNavigator instead of the FocusedFXNavigator, so you'll need to change that in the FX .zon files. The FXMenu Zone looks something like:

Zone FXMenu|1-8
		SelectedTrackNavigator
		DisplayUpper| FXNameDisplay |
		DisplayLower| NoAction
		Rotary| NoAction
                RotaryPush| GoFXSlot |
ZoneEnd

Good luck!

[Funkybot]

Is there a way to add comments to the code in an .mst file? The Stienberg CMC-QC has a weird setup in regards to what MIDI Device and CC's are transmitted based on the state of some other buttons. I feel like documenting this somewhat unique behavior somewhere would be key if anyone was trying to use it. I suppose I could include me a readme.txt if I were to share this, but was wondering if we could add comments to the .mst as a potential alternative.

[WaveTrans]

Originally Posted by Funkybot

Is there a way to add comments to the code in an .mst file? The Stienberg CMC-QC has a weird setup in regards to what MIDI Device and CC's are transmitted based on the state of some other buttons. I feel like documenting this somewhat unique behavior somewhere would be key if anyone was trying to use it. I suppose I could include me a readme.txt if I were to share this, but was wondering if we could add comments to the .mst as a potential alternative.

Text preceded by / is regarded as comment, as in .zon files.

[WaveTrans]

Hej!
Sends appear to work fine by now, so I started on Fx on the Icon Nano.

With the setup below, I can control a single FX (ReaComp or ReaEQ);
if there is more than one FX, I can not switch between them; Only the last FX on the list can be controlled.

Both Sends and FXMenu appear activated on startup and have to be inactivated. If I then toggle Pan (ToggleMapSelectedTrackFX)
and enter the FXmenu with Plugin (ToggleMapSelectedTrackFXMenu), I can control, for instance, Threshold on ReaComp, if it´s the only FX on the track.
GoFXSlot appears to do nothing.
Once in the FXMenu, I can go back through a GoZone Home button but the display remains set to ReaComp or ReaEQ.

Further, tracknames are no longer displayed; only names of first FX.

Please, any hints, where my files are wrong, are most appreciated...

Here is my present setup

Zone Home
	OnTrackSelection MapSelectedTrackSendsToWidgets
	OnTrackSelection MapSelectedTrackFXToMenu
	/OnTrackSelection MapSelectedTrackFXToWidgets 
	/OnFXFocus MapFocusedFXToWidgets
	/OnFXFocus SetShowFXWindows
	IncludedZones
		Buttons
		JogWheelHack
		Channel
		MasterChannel
	IncludedZonesEnd
ZoneEnd

....

Zone Buttons
	/Track MonoStereo
	Track Reaper 40917
	Send ToggleMapSelectedTrackSends
		/GlobalView 
	Pan ToggleMapSelectedTrackFX
	Plugin ToggleMapSelectedTrackFXMenu
		/EQ 
		/RightCol6
	Instrument GoZone Home
        ...
ZoneEnd
.....
Zone Channel
	TrackNavigator
	Plugin MapSelectedTrackFXToWidgets
	DisplayUpper  TrackPanDisplay
	DisplayLower  TrackNameDisplay 
	TrackTouch+DisplayUpper  TrackVolumeDisplay
	Rotary1 TrackPan 0
	RotaryPush1 GoZone PanWidth
	RecordArm1  TrackRecordArm
	Solo1  TrackSolo
	Mute1 TrackMute
	Fader1  TrackVolume
	Select1 TrackUniqueSelect
	TrackTouch+Fader1  TrackVolume
	FaderTouch1 TrackTouch
	VUMeter1 TrackOutputMeter
	
ZoneEnd
......
Zone FXMenu|1-8
	SelectedTrackNavigator
	DisplayUpper|  FXNameDisplay |
	DisplayLower| NoAction
	EQ| GoFXSlot|
ZoneEnd

And FX.zones
ReaComp

 
Zone "VST: ReaComp (Cockos)" ReaComp
   SelectedTrackNavigator
   DisplayUpper1 FXParamNameDisplay 0 "Thresh"
   DisplayLower1 FXParamValueDisplay 0
   Fader1 FXParam 0 Thresh
   Rotary2 FXParam 2 Attack
   Rotary3 FXParam 3 Release
   RotaryPush3 FXParam 16 AutoRelease
   Rotary4 FXParam 1 Ratio
   Rotary5 FXParam 19 Bypass
   Rotary6 FXParam 20 Wet
ZoneEnd

ReaEQ

Zone "VST: ReaEQ (Cockos)" ReaEQ 
    SelectedTrackNavigator
    DisplayUpper1 FXParamNameDisplay 0 "Frequ1"
    DisplayLower1 FXParamValueDisplay 0
    Rotary1 FXParam 0 "Freq-Band 1"
    Rotary2 FXParam 1 "Gain-Band 1"
    Rotary3 FXParam 2 "Q-Band 1"
    Rotary4 FXParam 3 "Freq-Band 2"
    Rotary5 FXParam 4 "Gain-Band 2"
    Rotary6 FXParam 5 "Q-Band 2"
    Rotary7 FXParam 6 "Freq-Band 3"
    Rotary8 FXParam 7 "Gain-Band 3"
    Fader1 FXParam 8 "Q-Band 3"
....
ZoneEnd

[MixMonkey]

Originally Posted by WaveTrans

Please, any hints, where my files are wrong, are most appreciated...

Get rid of:

 Pan ToggleMapSelectedTrackFX

This Action will map ALL a channel's FX parameters to widgets. For instance, if you had a compressor and EQ on each channel, all their parameters will be mapped to the surface at once.

Get rid of:

Plugin MapSelectedTrackFXToWidgets

in Zone Channel. You already have it Zone Buttons, which is an included Zone that will be active along with Zone Channel.

It's probably worth pointing out that there are essentially three methods for mapping FX to widgets:

i) MapSelectedTrackFXToWidgets- maps all a channel's FX parameters to widgets in one go. Uses the SelectedTrackNavigator.

ii) MapSelectedTrackFXToMenu c/w GoFXSlot. Maps channel FX to a menu across channels 1 to n. Individual FX mapped using GoFXSlot. Uses the SelectedTrackNavigator. I'm not sure how you would use this with a single channel surface.

iii) MapFocusedFXToWidgets. Maps the Focused FX to widgets (focused window, usually, although selecting the FX in the FX chain window works as well) Uses the FocusedFXNavigator.

Whilst these aren't neccessarily mutually exclusive, it's probably a good idea to pick one to start with.

[lubvic]

Thanks MixMonkey, i'll use FXmenu method, everythig seems to work great now, even scribble strips, with your advice! :-)

Originally Posted by MixMonkey

You need to add a definition for the displays in the FX .zon file:

Zone "VST: ReaComp (Cockos)" ReaComp
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay 0
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0 Thresh

....

In my experience, the FX menu method is more reliable/predictable than the focused FX method. The FX menu uses the SelectedTrackNavigator instead of the FocusedFXNavigator, so you'll need to change that in the FX .zon files. The FXMenu Zone looks something like:

Zone FXMenu|1-8
		SelectedTrackNavigator
		DisplayUpper| FXNameDisplay |
		DisplayLower| NoAction
		Rotary| NoAction
ZoneEnd

Good luck!

[MixMonkey]

Originally Posted by lubvic

Thanks MixMonkey, i'll use FXmenu method, everythig seems to work great now, even scribble strips, with your advice! :-)

Glad you got it working

If you want the FX window to open when you select the slot, you can double up on the Push Action:

	Zone FXMenu|1-8
		SelectedTrackNavigator
		DisplayUpper| FXNameDisplay |
		DisplayLower| NoAction
		Rotary| NoAction	
		RotaryPush| GoFXSlot |
		
/Float FX window for selected slot		
		RotaryPush1 Reaper _S&M_FLOATFX1
		RotaryPush2 Reaper _S&M_FLOATFX2
		RotaryPush3 Reaper _S&M_FLOATFX3
		RotaryPush4 Reaper _S&M_FLOATFX4
		RotaryPush5 Reaper _S&M_FLOATFX5
		RotaryPush6 Reaper _S&M_FLOATFX6
		RotaryPush7 Reaper _S&M_FLOATFX7
		RotaryPush8 Reaper _S&M_FLOATFX8
	ZoneEnd

Note the use of the longhand form (the shorthand | won't work with the SWS Action)

Just realised I left the RotaryPush line out of my original reply (I'll correct that) but I guess you figured that out

I have a button mapped that closes all the floating FX windows, to clean up:

SomeButton Reaper _S&M_WNCLS3

[MixMonkey]

@Geoff

Just noticed that modifiers don't work in the context of the FX menu.

So:

Shift+RotaryPush1 Reaper _S&M_FXBYP1

doesn't work from Zone FXMenu|1-8, but does work from Zone Home.

[WaveTrans]

Thanks for helping me out, MixMonkey.
(I daresay, your explanations will be helpful for others as well.)

I tried all variations I could think off now.

Sends work only if ontrackselection MapSelectedTrackSendsToWidgets is in home zone and toggles reliably with Send ToggleMapSelectedTrackSends.

The FX matter was more reluctant. The MapSelectedTrack.. commands using SelectedTrackNavigator did apparently not work.
So I tried MapFocusedFXToWidgets with which selected FX Menues can be controlled, using FocusedFXNavigator in the FX zones. Not shure if that´s the correct behaviour but at least it works somehow. Will continue testing.

Cheers, again.

Originally Posted by MixMonkey

Get rid of:

 Pan ToggleMapSelectedTrackFX

This Action will map ALL a channel's FX parameters to widgets. For instance, if you had a compressor and EQ on each channel, all their parameters will be mapped to the surface at once.

Get rid of:

Plugin MapSelectedTrackFXToWidgets

in Zone Channel. You already have it Zone Buttons, which is an included Zone that will be active along with Zone Channel.

It's probably worth pointing out that there are essentially three methods for mapping FX to widgets:

i) MapSelectedTrackFXToWidgets- maps all a channel's FX parameters to widgets in one go. Uses the SelectedTrackNavigator.

ii) MapSelectedTrackFXToMenu c/w GoFXSlot. Maps channel FX to a menu across channels 1 to n. Individual FX mapped using GoFXSlot. Uses the SelectedTrackNavigator. I'm not sure how you would use this with a single channel surface.

iii) MapFocusedFXToWidgets. Maps the Focused FX to widgets (focused window, usually, although selecting the FX in the FX chain window works as well) Uses the FocusedFXNavigator.

Whilst these aren't neccessarily mutually exclusive, it's probably a good idea to pick one to start with.

[MixMonkey]

Originally Posted by WaveTrans

Sends work only if ontrackselection MapSelectedTrackSendsToWidgets is in home zone and toggles reliably with Send ToggleMapSelectedTrackSends.

That's interesting. I may have been mistaken about the exact function of OnTrackSelection MapSelectedTrackSendsToWidgets. It was based on assumptions drawn from my system, which has a separate surface for FX and Sends. I probably need to do some testing with just a single MCU to get a better idea of what's going on.

Glad you got it working ok

EDIT: I was mistaken about the function of OnTrackSelection. I was confusing its function with the Auto Map Sends option in the prefs. The OnTrackSelection commands (MapSelectedTrackSendsToWidgets, MapSelectedTrackFXToMenu) need to be present for those Actions to operate, whether you choose to toggle them or have them map automatically. Sorry for the confusion.

I'll remove the incorrect info from my original post, if you could remove your quote of it that would be most appreciated

[MixMonkey]

Originally Posted by WaveTrans

The FX matter was more reluctant. The MapSelectedTrack.. commands using SelectedTrackNavigator did apparently not work.
So I tried MapFocusedFXToWidgets with which selected FX Menues can be controlled, using FocusedFXNavigator in the FX zones.

Using the FocusedFX method probably makes most sense with the single fader surface. It isn't really meant to work with the FX menu, though.

The usual way it works is with:

OnFXFocus MapFocusedFXToWidgets

in Zone Home and either the Auto Map Focused FX option turned on in the prefs or:

SomeButton ToggleMapFocusedFX

in Zone Home or Zone Buttons (if you have one)

"focusing" the FX usually involves clicking in an open FX window or on an FX name in an FX chain window. When the FX is "focused" the parameters map to the surface according to the relevant FX .zon file. The FX .zon file must contain:

 FocusedFXNavigator

[Funkybot]

Originally Posted by WaveTrans

Text preceded by / is regarded as comment, as in .zon files.

Thanks! I was having some issues with this, but it looks like it's because the whole line needs to begin with the /. Otherwise, you'll get an error (like if trying to append this on the same line as a widget.

So I've gotten the transport controls and buttons mapped and working with the Stienberg CMC-QC. Now to try to figure out what to do with the knobs.

[WaveTrans]

Originally Posted by Funkybot

Thanks! I was having some issues with this, but it looks like it's because the whole line needs to begin with the /. Otherwise, you'll get an error (like if trying to append this on the same line as a widget.

So I've gotten the transport controls and buttons mapped and working with the Stienberg CMC-QC. Now to try to figure out what to do with the knobs.

Yes, there was a post from Geoff a while ago that it should be used for full lines only. So used to it now that I forgot to mention it. Sorry, for that.
Good to hear your stuff works

[WaveTrans]

Dear MixMonkey, I adapted the quote in my post acccording to your corrections.

Since you mention the AutoMap function; is it correct to assume that activated AutoMap Sends in the prefs is responsible for automatic activation of the sends menu on startup of CSI?

So maybe I can deactivate AutoMap in the prefs, since there is OnTrackSelection MapSelectedTrackSendsToWidgets in the homeZone and a button assigned to ToggleMapSelectedTrackSends?

Will dig deeper into that matter and the FocusFX thingy in the evening.

Originally Posted by MixMonkey

Using the FocusedFX method probably makes most sense with the single fader surface. It isn't really meant to work with the FX menu, though.

The usual way it works is with:

OnFXFocus MapFocusedFXToWidgets

in Zone Home and either the Auto Map Focused FX option turned on in the prefs or:

SomeButton ToggleMapFocusedFX

in Zone Home or Zone Buttons (if you have one)

"focusing" the FX usually involves clicking in an open FX window or on an FX name in an FX chain window. When the FX is "focused" the parameters map to the surface according to the relevant FX .zon file. The FX .zon file must contain:

 FocusedFXNavigator

[UNdark]

HI - followed from day one but not in my knowledge area this.. I've set the mcu up to work well for me using cycle actions till now...Send works great from the installer file, but If anyone could advise on how i might get the jog wheel working and specifically - opening the plugin window of a selected channel (not floating single fx) toggled with the plugin button on the mcu, that would be fantastic. I thought about copying and pasting from the post, but didn't want to make an issue!
Thanks

[WaveTrans]

Originally Posted by UNdark

HI - followed from day one but not in my knowledge area this.. I've set the mcu up to work well for me using cycle actions till now...Send works great from the installer file, but If anyone could advise on how i might get the jog wheel working and specifically - opening the plugin window of a selected channel (not floating single fx) toggled with the plugin button on the mcu, that would be fantastic. I thought about copying and pasting from the post, but didn't want to make an issue!
Thanks

As far as I understood, jogwheel is not implemented yet, but the Jogwheel hack works fine and you can copy it from post #5487
https://forum.cockos.com/showpost.ph...postcount=5487

If the cycle actions work for you, how did you set them up? like it is described in malcolms wiki?

don´t know about this window opening stuff, but would be interesting to know how this works.

[MixMonkey]

Originally Posted by WaveTrans

Dear MixMonkey, I adapted the quote in my post acccording to your corrections.

Thanks for changing that, I'm doing my best not to spread inaccurate info

Since you mention the AutoMap function; is it correct to assume that activated AutoMap Sends in the prefs is responsible for automatic activation of the sends menu on startup of CSI?

Yes, the Auto Map boxes in the prefs cause the relevant function to be activated on track selection (only really makes sense if the sends/FX are mapping to a separate surface from faders/pans etc).

So maybe I can deactivate AutoMap in the prefs, since there is OnTrackSelection MapSelectedTrackSendsToWidgets in the homeZone and a button assigned to ToggleMapSelectedTrackSends?

Yep, disable the Auto function, then enable/disable using Toggle when you need it.

[MixMonkey]

Originally Posted by UNdark

and specifically - opening the plugin window of a selected channel (not floating single fx) toggled with the plugin button on the mcu

When you say "plugin window (not floating single fx)" do you mean the FX chain window?

If so, you can map the SWS action:

_S&M_TOGLFXCHAIN

to the plugin button:

Plugin Reaper _S&M_TOGLFXCHAIN

Also:

_S&M_SELFXPREV
_S&M_SELFXNEXT

will step back/forward through the plugins in the FX window.

[lubvic]

Thanks MixMonkey :-)
Clever solution to open GUI!

Originally Posted by MixMonkey

Glad you got it working

If you want the FX window to open when you select the slot, you can double up on the Push Action:

	Zone FXMenu|1-8
		SelectedTrackNavigator
		DisplayUpper| FXNameDisplay |
		DisplayLower| NoAction
		Rotary| NoAction	
		RotaryPush| GoFXSlot |
		
/Float FX window for selected slot		
		RotaryPush1 Reaper _S&M_FLOATFX1
		RotaryPush2 Reaper _S&M_FLOATFX2
		RotaryPush3 Reaper _S&M_FLOATFX3
		RotaryPush4 Reaper _S&M_FLOATFX4
		RotaryPush5 Reaper _S&M_FLOATFX5
		RotaryPush6 Reaper _S&M_FLOATFX6
		RotaryPush7 Reaper _S&M_FLOATFX7
		RotaryPush8 Reaper _S&M_FLOATFX8
	ZoneEnd

Note the use of the longhand form (the shorthand | won't work with the SWS Action)

Just realised I left the RotaryPush line out of my original reply (I'll correct that) but I guess you figured that out

I have a button mapped that closes all the floating FX windows, to clean up:

SomeButton Reaper _S&M_WNCLS3

[UNdark]

Originally Posted by WaveTrans

As far as I understood, jogwheel is not implemented yet, but the Jogwheel hack works fine and you can copy it from post #5487
https://forum.cockos.com/showpost.ph...postcount=5487

If the cycle actions work for you, how did you set them up? like it is described in malcolms wiki?

don´t know about this window opening stuff, but would be interesting to know how this works.

PLEASE FEEL FREE TO MOVE THIS IS IT'S TO FAR OFF TOPIC..

Thanks WaveTrans - I explained in another post a few days back as these all stopped working in reaper 6 but went back to 5 and all is good...
In short - I have been modding them/ setting them up for over a year to get by till I got enough brains to work this stuff out I'm happy to upload the config file for you (mines mac) i do a lot of mixing and like to see instrument groups quickly and it works like this:
KEYS 1 TO 0 are 1-bass tracks - any tracks with bass in the name then zooms only tracks with actual items in 2 is drums - same concept - till i get to 9 then 0 is my final drum/music/master busses zoom (toggled) A is overview all tracks b is all busses. The MCU follows this perfectly. plugs are f13 to f17 floating windows of sorted plugs into uses - window closes when plug is selected.
That's very briefly it. The remote sl25 is programmed for plugin type as well so i just dial into that the type of plug and it's all labelled. I only need the MCU to try and replace the keyboard / mouse for all other functions and with the hard work done already on this it's very nearly there.
Even just having the SENDS working like they do with with the CSI absolutely brilliant. I want to transfer the hotkeys assigned to all these into the buttons on the MCU. There's stacks more i 've done and not explained here that refine the process - all adds up to faster more tactile mixing

[UNdark]

THANKS MixMonkey - that's exactly what i was looking for

[WaveTrans]

Originally Posted by MixMonkey

Thanks for changing that, I'm doing my best not to spread inaccurate info

You´re welcome

Originally Posted by MixMonkey

Yes, the Auto Map boxes in the prefs cause the relevant function to be activated on track selection (only really makes sense if the sends/FX are mapping to a separate surface from faders/pans etc).


Yep, disable the Auto function, then enable/disable using Toggle when you need it.

Good news! It works!

With AutoMap functions disabled and buttons defined (Code is below), I can control selected and focused FX now.
Double feature Plugin button opens FX window automatically, FX prev and FX next implied.
Very nice.

Many Thanks MixMonkey.

Due to this, a question arose:
How to define the parameters to create a zone file for JS: plugins?

I had an attempt on "JS: Volume Adjustment" without success.

here is the non-functioning .zon file

Zone "JS: Volume Adjustment" 
    FocusedFXNavigator
	DisplayUpper1 FXParamNameDisplay 0 "Adj"
	DisplayLower1 FXParamValueDisplay 1 "Max Vol"
   	Rotary1 FXParam 0 Adjustment (dB)
        Rotary2 FXParam 1 Max Volume (dB)
ZoneEnd

In case someone wants to set up a single fader controller like the icon platform Nano with basic Send and FX control, I post the code.
(The right hand button row of the Icon Nano is used. Send=Send. Pan=Fxprev. Plugins=Open and enter FX Window. EQ= FXnext; disable AutoMapping functions in preferences)

Zone Home
	OnTrackSelection MapSelectedTrackSendsToWidgets
	OnFXFocus MapFocusedFXToWidgets
		IncludedZones
		Buttons
		JogWheelHack
		Channel
		MasterChannel
	IncludedZonesEnd
ZoneEnd

Zone Buttons
	...
	Send ToggleMapSelectedTrackSends
	Pan Reaper _S&M_SELFXPREV
	Plugin ToggleMapFocusedFX
	Plugin Reaper _S&M_TOGLFXCHAIN
        EQ Reaper _S&M_SELFXNEXT 
        Instrument GoZone Home 
        ...
ZoneEnd

Zone FXMenu|1-8
	SelectedTrackNavigator
	DisplayUpper|  FXNameDisplay |
	DisplayLower| NoAction
....
ZoneEnd

[MixMonkey]

Originally Posted by WaveTrans

Good news! It works!

With AutoMap functions disabled and buttons defined (Code is below), I can control selected and focused FX now.
Double feature Plugin button opens FX window automatically, FX prev and FX next implied.
Very nice.

Many Thanks MixMonkey.

You're welcome, glad you got it working

Due to this, a question arose:
How to define the parameters to create a zone file for JS: plugins?

I had an attempt on "JS: Volume Adjustment" without success.

here is the non-functioning .zon file

Zone "JS: Volume Adjustment" 
    FocusedFXNavigator
	DisplayUpper1 FXParamNameDisplay 0 "Adj"
	DisplayLower1 FXParamValueDisplay 1 "Max Vol"
   	Rotary1 FXParam 0 Adjustment (dB)
        Rotary2 FXParam 1 Max Volume (dB)
ZoneEnd

Remove "Adjustment (dB)" and "Max Volume (dB)", leaving:

Zone "JS: Volume Adjustment" 
    FocusedFXNavigator
	DisplayUpper1 FXParamNameDisplay 0 "Adj"
	DisplayLower1 FXParamValueDisplay 1 "Max Vol"
   	Rotary1 FXParam 0
        Rotary2 FXParam 1
ZoneEnd

CSI only understands parameter numbers, the names are purely for human consumption

[WaveTrans]

Thanks for the hint

I tried it with no names and since this didn´t work, all kinds of variations on the parameter names but those didn´t work either
Could be some difference between JS and Cockos Plugins, but that´s just a wild guess.

The names of the FX parameters can be taken from the menues found under in the plugin param/FXlist.

Meanwhile two more questions came up:

- is there an action to open the routing/send menu,, like the FX menu?

- why does the LED of the button assigned to the two actions below
blink wildly?

Plugin ToggleMapFocusedFX
Plugin Reaper _S&M_TOGLFXCHAIN

Originally Posted by MixMonkey

You're welcome, glad you got it working



Remove "Adjustment (dB)" and "Max Volume (dB)", leaving:

Zone "JS: Volume Adjustment" 
    FocusedFXNavigator
	DisplayUpper1 FXParamNameDisplay 0 "Adj"
	DisplayLower1 FXParamValueDisplay 1 "Max Vol"
   	Rotary1 FXParam 0
        Rotary2 FXParam 1
ZoneEnd

CSI only understands parameter numbers, the names are purely for human consumption