Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by Cragster

I dont know if this will work . But in an fx zone FXParamNameDisplay takes control of the display. You can type anything you want in there. I use it all the time with a dummy param number. So if i have an open track display in my fx zone ill put DisplayUpperwhatevertracknumber FXParamNameDisplay 1(dummy param number) and then wgat i want in the display wrapped in quotes. I use it for say "shift" on the upper and "mode" on the lower. Just a trick because my modifier buttons dont stay lit and it keeps me from being lost. Maybe it will work in a regular zone ?? Worth a try

Nice hack, but FXParam "0" is always a real parameter

Does it still work if you use FXParam "999999" ?

If so, use "999999".

[Mike@Ossarium]

Originally Posted by Geoff Waddington

If you think about it, one important thing Hold needs is a release message.

That way, if you just tap it, the Hold action doesn't occur.

It's waiting, ready to go, but it's hopes are dashed when it receives that release message before it has a chance to trigger the Action.

Then it just resets the timer and waits again patiently

You need something like this:

Widget Click
	Press 90 59 7f 90 59 00
	FB_TwoState 90 59 7f 90 59 00
WidgetEnd

AND the widget actually has to generate the release - use input monitor to be sure.

Ahhh - damn. You are right - as always :-)

I thought i've tested that.
Now its fine.
Thanks.

[Geoff Waddington]

Originally Posted by spkr4thdd

Geoff, thanks for the quick response. I got there with the volume/pan display in the lower display.

How can a 'force' text in to a display? For example if I want it to read "Volume" or "FX Slot 1"?

DisplayUpper1     "Volume"

doesn't work...

Can you enter text to be shown on the display rather than a parameter passed by Reaper?

OK, so you just want fixed text on the display when you activate the Zone that contains ?

DisplayUpper1

[Mike@Ossarium]

Originally Posted by spkr4thdd

Geoff, thanks for the quick response. I got there with the volume/pan display in the lower display.

How can a 'force' text in to a display? For example if I want it to read "Volume" or "FX Slot 1"?

DisplayUpper1     "Volume"

doesn't work...

Can you enter text to be shown on the display rather than a parameter passed by Reaper?

Hi Grae,

you can do:

DisplayLower8	FXParamNameDisplay   "9999"	"Active"

Thne only the text "Active" will be displayed.

[Geoff Waddington]

Originally Posted by Mike@Ossarium

Hi Grae,

you can do:

DisplayLower8	FXParamNameDisplay   "9999"	"Active"

Thne only the text "Active" will be displayed.

Cool, I might just add a simple Action for convenience:

[Edit] -- Just added it -- will be in next build.

DisplayLower8	FixedTextDisplay  "Active"

[Mike@Ossarium]

Originally Posted by Geoff Waddington

Cool, I might just add a simple Action for convenience:

DisplayLower8	FixedDisplay  "Active"

Cool - that would be very nice.

[Mike@Ossarium]

Originally Posted by Geoff Waddington

Cool, I might just add a simple Action for convenience:

DisplayLower8	FixedDisplay  "Active"

Is there a way to handle log text in the display?
E.g. sho every 1second a part of it or split it also on th lower display.

That would be good for example for lang Track and effekt parameter names :-)

[spkr4thdd]

Originally Posted by Geoff Waddington

OK, so you just want fixed text on the display when you activate the Zone that contains ?

DisplayUpper1

Yes, but on any of the 8 upper displays...

I've set up the following zon to mimic the MCU Channel View activated by pressing the 'Track' button:

Zone "TrackView"
	SelectedTrackNavigator
/ ASSIGNMENTS

	Track				GoZone			"Home"
	EQ				Reaper			"41757"
	Send	 			ToggleMapSelectedTrackSends
	Plugin				ToggleMapSelectedTrackFXMenu
	Instrument			NoAction


/ FUNCTIONS

	Fn1				Reaper			"_S&M_TOGLFLOATFX1"
	Fn2				Reaper			"_S&M_TOGLFLOATFX2"
	Fn3				Reaper			"_S&M_TOGLFLOATFX3"
	Fn4				Reaper			"_S&M_TOGLFLOATFX4"	

/ Rotaries & Displays

	DisplayUpper1			"Volume"
	DisplayLower1			TrackVolumeDisplay
	Rotary1				TrackVolume
	
	DisplayUpper2			"Pan"
	DisplayLower2			TrackPanDisplay
	Rotary2				TrackPan

	DisplayUpper3			NoAction
	DisplayLower3			FXNameDisplay 1
	Rotary3				NoAction
	RotaryPush3			GoFXSlot 1
	RotaryPush3			Reaper			"_S&M_TOGLFLOATFX1"

	DisplayUpper4			"FX 2"
	DisplayLower4			FXNameDisplay 2
	Rotary4				NoAction
	RotaryPush4			GoFXSlot "2"
	RotaryPush4			Reaper			"_S&M_TOGLFLOATFX2"

	DisplayUpper5			"FX 3"
	DisplayLower5			FXNameDisplay 3
	Rotary5				NoAction
	RotaryPush5			GoFXSlot "3"
	RotaryPush5			Reaper			"_S&M_TOGLFLOATFX3"

	DisplayUpper6			Display "Send 1"
	DisplayLower6			TrackSendVolumeDisplay 0
	Rotary6				TrackSendVolume 0

	DisplayUpper7			"Send 2"
	DisplayLower7			TrackSendVolumeDisplay 1
	Rotary7				TrackSendVolume 1

	DisplayUpper8			"Send 3"
	DisplayLower8			TrackSendVolumeDisplay 2
	Rotary8				TrackSendVolume 2

ZoneEnd

All the rotaries work, the rotary push for FX 1-3 work. The lower displays work. I just want to be able to tell it to show the text I've got against the 8 DisplayUppers.

[Mike@Ossarium]

Originally Posted by spkr4thdd

Yes, but on any of the 8 upper displays...

I've set up the following zon to mimic the MCU Channel View activated by pressing the 'Track' button:

Zone "TrackView"
	SelectedTrackNavigator
/ ASSIGNMENTS

	Track				GoZone			"Home"
	EQ				Reaper			"41757"
	Send	 			ToggleMapSelectedTrackSends
	Plugin				ToggleMapSelectedTrackFXMenu
	Instrument			NoAction


/ FUNCTIONS

	Fn1				Reaper			"_S&M_TOGLFLOATFX1"
	Fn2				Reaper			"_S&M_TOGLFLOATFX2"
	Fn3				Reaper			"_S&M_TOGLFLOATFX3"
	Fn4				Reaper			"_S&M_TOGLFLOATFX4"	

/ Rotaries & Displays

	DisplayUpper1			"Volume"
	DisplayLower1			TrackVolumeDisplay
	Rotary1				TrackVolume
	
	DisplayUpper2			"Pan"
	DisplayLower2			TrackPanDisplay
	Rotary2				TrackPan

	DisplayUpper3			NoAction
	DisplayLower3			FXNameDisplay 1
	Rotary3				NoAction
	RotaryPush3			GoFXSlot 1
	RotaryPush3			Reaper			"_S&M_TOGLFLOATFX1"

	DisplayUpper4			"FX 2"
	DisplayLower4			FXNameDisplay 2
	Rotary4				NoAction
	RotaryPush4			GoFXSlot "2"
	RotaryPush4			Reaper			"_S&M_TOGLFLOATFX2"

	DisplayUpper5			"FX 3"
	DisplayLower5			FXNameDisplay 3
	Rotary5				NoAction
	RotaryPush5			GoFXSlot "3"
	RotaryPush5			Reaper			"_S&M_TOGLFLOATFX3"

	DisplayUpper6			Display "Send 1"
	DisplayLower6			TrackSendVolumeDisplay 0
	Rotary6				TrackSendVolume 0

	DisplayUpper7			"Send 2"
	DisplayLower7			TrackSendVolumeDisplay 1
	Rotary7				TrackSendVolume 1

	DisplayUpper8			"Send 3"
	DisplayLower8			TrackSendVolumeDisplay 2
	Rotary8				TrackSendVolume 2

ZoneEnd

All the rotaries work, the rotary push for FX 1-3 work. The lower displays work. I just want to be able to tell it to show the text I've got against the 8 DisplayUppers.

Have you cheked my lates version for the X-touch?

There is an example on how this works.
ReaEQ and ReaComp for example show their parameters on th displays.

You can see that on my Youtube video:
https://www.youtube.com/watch?v=QD1o0JenoNE

[spkr4thdd]

Originally Posted by Mike@Ossarium

Hi Grae,

you can do:

DisplayLower8	FXParamNameDisplay   "9999"	"Active"

Thne only the text "Active" will be displayed.

YES!!!! Thank you!! That's been driving me mad!

Just tried it and it works.

[Geoff Waddington]

Originally Posted by Mike@Ossarium

Is there a way to handle log text in the display?
E.g. sho every 1second a part of it or split it also on th lower display.

That would be good for example for lang Track and effekt parameter names :-)

Probably something to think about after 1.0.

[Geoff Waddington]

Originally Posted by spkr4thdd

YES!!!! Thank you!! That's been driving me mad!

Just tried it and it works.

And this will be in the next build

DisplayUpper4	FixedTextDisplay  "FX 2"

[spkr4thdd]

Originally Posted by Mike@Ossarium

Is there a way to handle log text in the display?
E.g. sho every 1second a part of it or split it also on th lower display.

That would be good for example for lang Track and effekt parameter names :-)

There's definitely a way to do it on the MCU (and the X-Touch) which is implemented in both Logic and Harrison Mixbus32. They just get split across displays in 7 character chunks, for instance...

"Eisosis| e2 De|esser |"

There's also a way to show a message each time the view/focus or assignment changes (Channel View, FX Menu, etc). But not that I've found in Reaper/CSI yet...

[spkr4thdd]

Originally Posted by Cragster

I dont know if this will work . But in an fx zone FXParamNameDisplay takes control of the display. You can type anything you want in there. I use it all the time with a dummy param number. So if i have an open track display in my fx zone ill put DisplayUpperwhatevertracknumber FXParamNameDisplay 1(dummy param number) and then wgat i want in the display wrapped in quotes. I use it for say "shift" on the upper and "mode" on the lower. Just a trick because my modifier buttons dont stay lit and it keeps me from being lost. Maybe it will work in a regular zone ?? Worth a try

Hey! Thanks! Missed your message, but saw the related responses. That works a treat, and we've even managed to get Geoff to integrate fixed text displays in to the next build

[Cragster]

Originally Posted by Geoff Waddington

Nice hack, but FXParam "0" is always a real parameter

Does it still work if you use FXParam "999999" ?

If so, use "999999".

I usually count all the parameters on the UI and then use a number afrer that. But ive also used numbers of parameters im not mapping on that particular plugin. Fxparamnamedisplay worked with any number since im not adding the actual fxparam. Idk just thought maybe its something he coukd try. Couldnt hurt right ? I use that trick whenever i want extra info to show on the display to help me out. I even add tracktouch so i can have 3 displays lol. Upper being param nane...lower being what controller is mapped..ie fader rotary push or button...abd then tracktouch lower will shiw the value...its CSI right ? The possibilities are almost endless of what u can do

[Geoff Waddington]

Originally Posted by Cragster

I usually count all the parameters on the UI and then use a number afrer that. But ive also used numbers of parameters im not mapping on that particular plugin. Fxparamnamedisplay worked with any number since im not adding the actual fxparam. Idk just thought maybe its something he coukd try. Couldnt hurt right ? I use that trick whenever i want extra info to show on the display to help me out. I even add tracktouch so i can have 3 displays lol. Upper being param nane...lower being what controller is mapped..ie fader rotary push or button...abd then tracktouch lower will shiw the value...its CSI right ? The possibilities are almost endless of what u can do

Man, you guys are SO creative !!

Yup, that's exactly what CSI is for -- total personal workflow customization

[Cragster]

Originally Posted by spkr4thdd

Hey! Thanks! Missed your message, but saw the related responses. That works a treat, and we've even managed to get Geoff to integrate fixed text displays in to the next build

No problem just glad u got it working the way u want. And nice !!! Thanks Geoff

[tdc]

Originally Posted by Cragster

I usually count all the parameters on the UI and then use a number afrer that.

:-) My head still hurts after spending an hour or so last night building a Zon file for Fabfilter's Pro-Q 3. It has around 490 Parameters. I tried to be smart and build from the work that FunkyBot had already done, but I wanted some other parameters so had to simply count until the Cat wanted to be stroked.

1, 2, 3, 4, 5, ...... 234, 235, 236, Meow, 23.... umm ... Arse!

In the end I made my FX Window a size that showed 50 Parameters at a time and then just counted the times I paged down. Then took a guess at the parameter number, and watched where it moved and then adjusted from there :-)

Its frustrating because you can see a spreadsheet list of all the parameters in the Project Bay window, but there is no export or Copy and Paste possible in there.

[Cragster]

Originally Posted by tdc

:-) My head still hurts after spending an hour or so last night building a Zon file for Fabfilter's Pro-Q 3. It has around 490 Parameters. I tried to be smart and build from the work that FunkyBot had already done, but I wanted some other parameters so had to simply count until the Cat wanted to be stroked.

1, 2, 3, 4, 5, ...... 234, 235, 236, Meow, 23.... umm ... Arse!

In the end I made my FX Window a size that showed 50 Parameters at a time and then just counted the times I paged down. Then took a guess at the parameter number, and watched where it moved and then adjusted from there :-)

Its frustrating because you can see a spreadsheet list of all the parameters in the Project Bay window, but there is no export or Copy and Paste possible in there.

Haha i feel your pain. Im in the middle ,well almost done, of mapping an all in one kind of plugin. 7 modules and a UI 10 miles long. So i hearing you. Lots of subzones in this one. Btw shout out to MIXMONKEY for that subzone idea. Working beautifully

[tdc]

Originally Posted by Geoff Waddington

Actually those numbers are RGB and any Widget that supports RGB should work.

Hi Mike,

Sorry - I had not known that these worked for other displays. Doh. Exciting though. So you can set widgets colour using the six digits like this.

{ r g b R G B ]

The Lowercase are the values for the Widget's OFF state, and the Uppercase are for the ON state. Its important to appreciate that the Widget's state is defined by CSI. This is straightforward if you are assigning the widget to a two-state button like a Bypass. But if you are mapping it to a Reaper Action, then this action needs to have two states ( like a toggle of a FX Window being hidden or shown.

Best of luck!

SomeButton Reaper "ShowFXWindows" { 0 0 0 127 127 127 }

You can get some indication of this state if you look in your Actions Window, there is a column in the right hand side that shows the Actions State (if it has one) Now, a lot of times you may want to colour the Widget even though it only has one state. Geoff may correct me on this method, but I have found success in using something like this.

Press1 Reaper. "_S&M_WNCLS5" { 0 255 0 0 255 0 } // Close all float FX for Selected Track (Bright Green)

Here we are calling the SWS Script to Close all Floated FX for a Selected Track, and colouring it Bright Green by using the same three colour values in both states.

Sometimes you may have the desire to Colour a Widget for formatting purposes to help draw attention to an area on the surface, or maybe you want to make sure this Widget is cleared out when changing Zones. You can simply define an action that assigns a non existent FXParam, so something like "9999", and give both On and Off states the same colour.

Press15. FXParam "9999" { 0 0 0 0 0 0 } // Black}

[MixMonkey]

Originally Posted by tdc

:-) My head still hurts after spending an hour or so last night building a Zon file for Fabfilter's Pro-Q 3. It has around 490 Parameters. I tried to be smart and build from the work that FunkyBot had already done, but I wanted some other parameters so had to simply count until the Cat wanted to be stroked.

1, 2, 3, 4, 5, ...... 234, 235, 236, Meow, 23.... umm ... Arse!

In the end I made my FX Window a size that showed 50 Parameters at a time and then just counted the times I paged down. Then took a guess at the parameter number, and watched where it moved and then adjusted from there :-)

Its frustrating because you can see a spreadsheet list of all the parameters in the Project Bay window, but there is no export or Copy and Paste possible in there.

Would this help?

VST: FabFilter Pro-Q 3 (FabFilter)
0~Band 1 Used
1~Band 1 Enabled
2~Band 1 Frequency
3~Band 1 Gain
4~Band 1 Dynamic Range
5~Band 1 Dynamics Enabled
6~Band 1 Threshold
7~Band 1 Q
8~Band 1 Shape
9~Band 1 Slope
10~Band 1 Stereo Placement
11~Band 1 Speakers
12~Band 1 Solo
13~Band 2 Used
14~Band 2 Enabled
15~Band 2 Frequency
16~Band 2 Gain
17~Band 2 Dynamic Range
18~Band 2 Dynamics Enabled
19~Band 2 Threshold
20~Band 2 Q
21~Band 2 Shape
22~Band 2 Slope
23~Band 2 Stereo Placement
24~Band 2 Speakers
25~Band 2 Solo
26~Band 3 Used
27~Band 3 Enabled
28~Band 3 Frequency
29~Band 3 Gain
30~Band 3 Dynamic Range
31~Band 3 Dynamics Enabled
32~Band 3 Threshold
33~Band 3 Q
34~Band 3 Shape
35~Band 3 Slope
36~Band 3 Stereo Placement
37~Band 3 Speakers
38~Band 3 Solo
39~Band 4 Used
40~Band 4 Enabled
41~Band 4 Frequency
42~Band 4 Gain
43~Band 4 Dynamic Range
44~Band 4 Dynamics Enabled
45~Band 4 Threshold
46~Band 4 Q
47~Band 4 Shape
48~Band 4 Slope
49~Band 4 Stereo Placement
50~Band 4 Speakers
51~Band 4 Solo
52~Band 5 Used
53~Band 5 Enabled
54~Band 5 Frequency
55~Band 5 Gain
56~Band 5 Dynamic Range
57~Band 5 Dynamics Enabled
58~Band 5 Threshold
59~Band 5 Q
60~Band 5 Shape
61~Band 5 Slope
62~Band 5 Stereo Placement
63~Band 5 Speakers
64~Band 5 Solo
65~Band 6 Used
66~Band 6 Enabled
67~Band 6 Frequency
68~Band 6 Gain
69~Band 6 Dynamic Range
70~Band 6 Dynamics Enabled
71~Band 6 Threshold
72~Band 6 Q
73~Band 6 Shape
74~Band 6 Slope
75~Band 6 Stereo Placement
76~Band 6 Speakers
77~Band 6 Solo
78~Band 7 Used
79~Band 7 Enabled
80~Band 7 Frequency
81~Band 7 Gain
82~Band 7 Dynamic Range
83~Band 7 Dynamics Enabled
84~Band 7 Threshold
85~Band 7 Q
86~Band 7 Shape
87~Band 7 Slope
88~Band 7 Stereo Placement
89~Band 7 Speakers
90~Band 7 Solo
91~Band 8 Used
92~Band 8 Enabled
93~Band 8 Frequency
94~Band 8 Gain
95~Band 8 Dynamic Range
96~Band 8 Dynamics Enabled
97~Band 8 Threshold
98~Band 8 Q
99~Band 8 Shape
100~Band 8 Slope
101~Band 8 Stereo Placement
102~Band 8 Speakers
103~Band 8 Solo
104~Band 9 Used
105~Band 9 Enabled
106~Band 9 Frequency
107~Band 9 Gain
108~Band 9 Dynamic Range
109~Band 9 Dynamics Enabled
110~Band 9 Threshold
111~Band 9 Q
112~Band 9 Shape
113~Band 9 Slope
114~Band 9 Stereo Placement
115~Band 9 Speakers
116~Band 9 Solo
117~Band 10 Used
118~Band 10 Enabled
119~Band 10 Frequency
120~Band 10 Gain
121~Band 10 Dynamic Range
122~Band 10 Dynamics Enabled
123~Band 10 Threshold
124~Band 10 Q
125~Band 10 Shape
126~Band 10 Slope
127~Band 10 Stereo Placement
128~Band 10 Speakers
129~Band 10 Solo
130~Band 11 Used
131~Band 11 Enabled
132~Band 11 Frequency
133~Band 11 Gain
134~Band 11 Dynamic Range
135~Band 11 Dynamics Enabled
136~Band 11 Threshold
137~Band 11 Q
138~Band 11 Shape
139~Band 11 Slope
140~Band 11 Stereo Placement
141~Band 11 Speakers
142~Band 11 Solo
143~Band 12 Used
144~Band 12 Enabled
145~Band 12 Frequency
146~Band 12 Gain
147~Band 12 Dynamic Range
148~Band 12 Dynamics Enabled
149~Band 12 Threshold
150~Band 12 Q
151~Band 12 Shape
152~Band 12 Slope
153~Band 12 Stereo Placement
154~Band 12 Speakers
155~Band 12 Solo
156~Band 13 Used
157~Band 13 Enabled
158~Band 13 Frequency
159~Band 13 Gain
160~Band 13 Dynamic Range
161~Band 13 Dynamics Enabled
162~Band 13 Threshold
163~Band 13 Q
164~Band 13 Shape
165~Band 13 Slope
166~Band 13 Stereo Placement
167~Band 13 Speakers
168~Band 13 Solo
169~Band 14 Used
170~Band 14 Enabled
171~Band 14 Frequency
172~Band 14 Gain
173~Band 14 Dynamic Range
174~Band 14 Dynamics Enabled
175~Band 14 Threshold
176~Band 14 Q
177~Band 14 Shape
178~Band 14 Slope
179~Band 14 Stereo Placement
180~Band 14 Speakers
181~Band 14 Solo
182~Band 15 Used
183~Band 15 Enabled
184~Band 15 Frequency
185~Band 15 Gain
186~Band 15 Dynamic Range
187~Band 15 Dynamics Enabled
188~Band 15 Threshold
189~Band 15 Q
190~Band 15 Shape
191~Band 15 Slope
192~Band 15 Stereo Placement
193~Band 15 Speakers
194~Band 15 Solo
195~Band 16 Used
196~Band 16 Enabled
197~Band 16 Frequency
198~Band 16 Gain
199~Band 16 Dynamic Range
200~Band 16 Dynamics Enabled
201~Band 16 Threshold
202~Band 16 Q
203~Band 16 Shape
204~Band 16 Slope
205~Band 16 Stereo Placement
206~Band 16 Speakers
207~Band 16 Solo
208~Band 17 Used
209~Band 17 Enabled
210~Band 17 Frequency
211~Band 17 Gain
212~Band 17 Dynamic Range
213~Band 17 Dynamics Enabled
214~Band 17 Threshold
215~Band 17 Q
216~Band 17 Shape
217~Band 17 Slope
218~Band 17 Stereo Placement
219~Band 17 Speakers
220~Band 17 Solo
221~Band 18 Used
222~Band 18 Enabled
223~Band 18 Frequency
224~Band 18 Gain
225~Band 18 Dynamic Range
226~Band 18 Dynamics Enabled
227~Band 18 Threshold
228~Band 18 Q
229~Band 18 Shape
230~Band 18 Slope
231~Band 18 Stereo Placement
232~Band 18 Speakers
233~Band 18 Solo
234~Band 19 Used
235~Band 19 Enabled
236~Band 19 Frequency
237~Band 19 Gain
238~Band 19 Dynamic Range
239~Band 19 Dynamics Enabled
240~Band 19 Threshold
241~Band 19 Q
242~Band 19 Shape
243~Band 19 Slope
244~Band 19 Stereo Placement
245~Band 19 Speakers
246~Band 19 Solo
247~Band 20 Used
248~Band 20 Enabled
249~Band 20 Frequency
250~Band 20 Gain
251~Band 20 Dynamic Range
252~Band 20 Dynamics Enabled
253~Band 20 Threshold
254~Band 20 Q
255~Band 20 Shape
256~Band 20 Slope
257~Band 20 Stereo Placement
258~Band 20 Speakers
259~Band 20 Solo
260~Band 21 Used
261~Band 21 Enabled
262~Band 21 Frequency
263~Band 21 Gain
264~Band 21 Dynamic Range
265~Band 21 Dynamics Enabled
266~Band 21 Threshold
267~Band 21 Q
268~Band 21 Shape
269~Band 21 Slope
270~Band 21 Stereo Placement
271~Band 21 Speakers
272~Band 21 Solo
273~Band 22 Used
274~Band 22 Enabled
275~Band 22 Frequency
276~Band 22 Gain
277~Band 22 Dynamic Range
278~Band 22 Dynamics Enabled
279~Band 22 Threshold
280~Band 22 Q
281~Band 22 Shape
282~Band 22 Slope
283~Band 22 Stereo Placement
284~Band 22 Speakers
285~Band 22 Solo
286~Band 23 Used
287~Band 23 Enabled
288~Band 23 Frequency
289~Band 23 Gain
290~Band 23 Dynamic Range
291~Band 23 Dynamics Enabled
292~Band 23 Threshold
293~Band 23 Q
294~Band 23 Shape
295~Band 23 Slope
296~Band 23 Stereo Placement
297~Band 23 Speakers
298~Band 23 Solo
299~Band 24 Used
300~Band 24 Enabled
301~Band 24 Frequency
302~Band 24 Gain
303~Band 24 Dynamic Range
304~Band 24 Dynamics Enabled
305~Band 24 Threshold
306~Band 24 Q
307~Band 24 Shape
308~Band 24 Slope
309~Band 24 Stereo Placement
310~Band 24 Speakers
311~Band 24 Solo
312~Processing Mode
313~Processing Resolution
314~Gain Scale
315~Output Level
316~Output Pan
317~Output Pan Mode
318~Bypass
319~Output Invert Phase
320~Auto Gain
321~Analyzer Show Pre-Processing
322~Analyzer Show Post-Processing
323~Analyzer External Spectrum
324~Analyzer Range
325~Analyzer Resolution
326~Analyzer Speed
327~Analyzer Tilt
328~Analyzer Freeze
329~Analyzer Show Collisions
330~Spectrum Grab
331~Display Range
332~Receive Midi
333~Solo Gain
334~Band 1 External Side Chain
335~Band 2 External Side Chain
336~Band 3 External Side Chain
337~Band 4 External Side Chain
338~Band 5 External Side Chain
339~Band 6 External Side Chain
340~Band 7 External Side Chain
341~Band 8 External Side Chain
342~Band 9 External Side Chain
343~Band 10 External Side Chain
344~Band 11 External Side Chain
345~Band 12 External Side Chain
346~Band 13 External Side Chain
347~Band 14 External Side Chain
348~Band 15 External Side Chain
349~Band 16 External Side Chain
350~Band 17 External Side Chain
351~Band 18 External Side Chain
352~Band 19 External Side Chain
353~Band 20 External Side Chain
354~Band 21 External Side Chain
355~Band 22 External Side Chain
356~Band 23 External Side Chain
357~Band 24 External Side Chain
358~Bypass
359~Wet

[tdc]

Originally Posted by MixMonkey

Would this help?

VST: FabFilter Pro-Q 3 (FabFilter)
0~Band 1 Used
1~Band 1 Enabled
2~Band 1 Frequency

<snip>

MixMonkey! How on earth did you obtain that !!

[tdc]

Originally Posted by Cragster

Btw shout out to MIXMONKEY for that subzone idea. Working beautifully

Hey Cragster, I have just gone back a few hundred posts, but kind find the MixMonkey SubZone reference - care to share?

[Cragster]

Originally Posted by MixMonkey

Ok, I think I get it

You could split the various modules into in sub-zones like this:

Zone "VST: Oxford Dynamics (Sonnox)" "OxDyn"
SelectedTrackNavigator
/
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-1"
DisplayLowerA1 FXParamValueDisplay 45 
RotaryA1 FXParam 45 
Toggle+RotaryPushA1 FXParam 44 
/  
DisplayUpperA2 NoAction 
DisplayLowerA2 NoAction 
RotaryA2 NoAction 
Toggle+RotaryPushA2 NoAction 
/  
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
Toggle+RotaryPushA3 NoAction 
/  
DisplayUpperA4 NoAction 
DisplayLowerA4 NoAction 
RotaryA4 NoAction 
Toggle+RotaryPushA4 NoAction 
/  
DisplayUpperA5 FXParamNameDisplay 39 "EQ_Sig"
DisplayLowerA5 FXParamValueDisplay 39 
RotaryA5 FXParam 39 
Toggle+RotaryPushA5 FXParam 39 
/  
DisplayUpperA6 FXParamNameDisplay 30 "Input"
DisplayLowerA6 FXParamValueDisplay 30 
RotaryA6 FXParam 30 
Toggle+RotaryPushA6 NoAction 
/  
DisplayUpperA7 FXParamNameDisplay 32 "LFQ"
DisplayLowerA7 FXParamValueDisplay 32 
RotaryA7 FXParam 32 
Toggle+RotaryPushA7 FXParam 37 
/  
DisplayUpperA8 FXParamNameDisplay 33 "HFQ"
DisplayLowerA8 FXParamValueDisplay 33 
RotaryA8 FXParam 33 
Toggle+RotaryPushA8 FXParam 38 
/  
DisplayUpperB1 FXParamNameDisplay 42 "Warmth"
DisplayLowerB1 FXParamValueDisplay 42 
RotaryB1 FXParam 42 
Toggle+RotaryPushB1 FXParam 41 
/  
DisplayUpperB2 FXParamNameDisplay 43 "WTrim"
DisplayLowerB2 FXParamValueDisplay 43 
RotaryB2 FXParam 43 
Toggle+RotaryPushB2 NoAction 
/  
DisplayUpperB3 FXParamNameDisplay 1 "Dither"
DisplayLowerB3 FXParamValueDisplay 1 
RotaryB3 FXParam 1 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushB3 FXParam 1 [ 0.0 0.50 1.0 ] 
/  
DisplayUpperB4 NoAction 
DisplayLowerB4 NoAction 
RotaryB4 NoAction 
Toggle+RotaryPushB4 NoAction 
/  
DisplayUpperB5 FXParamNameDisplay 40 "EQ_SC"
DisplayLowerB5 FXParamValueDisplay 40 
RotaryB5 FXParam 40 
Toggle+RotaryPushB5 FXParam 40 
/  
DisplayUpperB6 FXParamNameDisplay 29 "SC_In"
DisplayLowerB6 FXParamValueDisplay 29 
RotaryB6 FXParam 29 
Toggle+RotaryPushB6 FXParam 29 
/  
DisplayUpperB7 FXParamNameDisplay 31 "LF"
DisplayLowerB7 FXParamValueDisplay 31 
RotaryB7 FXParam 31 
Toggle+RotaryPushB7 FXParam 37 
/  
DisplayUpperB8 FXParamNameDisplay 34 "HF"
DisplayLowerB8 FXParamValueDisplay 34 
RotaryB8 FXParam 34 
Toggle+RotaryPushB8 FXParam 38 
/  
DisplayUpperC1 FXParamNameDisplay 25 "LThrsh"
DisplayLowerC1 FXParamValueDisplay 25 
RotaryC1 FXParam 25 
Toggle+RotaryPushC1 FXParam 24 
/  
DisplayUpperC2 NoAction 
DisplayLowerC2 NoAction 
RotaryC2 NoAction 
Toggle+RotaryPushC2 NoAction 
/  
DisplayUpperC3 FXParamNameDisplay 26 "LAtt"
DisplayLowerC3 FXParamValueDisplay 26 
RotaryC3 FXParam 26 
Toggle+RotaryPushC3 NoAction 
/  
DisplayUpperC4 FXParamNameDisplay 27 "LHold"
DisplayLowerC4 FXParamValueDisplay 27 
RotaryC4 FXParam 27 
Toggle+RotaryPushC4 NoAction 
/  
DisplayUpperC5 FXParamNameDisplay 28 "LRel"
DisplayLowerC5 FXParamValueDisplay 28 
RotaryC5 FXParam 28 
Toggle+RotaryPushC5 NoAction 
/  
DisplayUpperC6 NoAction 
DisplayLowerC6 NoAction 
RotaryC6 NoAction 
Toggle+RotaryPushC6 NoAction 
/  
DisplayUpperC7 FXParamNameDisplay 35 "LFGain"
DisplayLowerC7 FXParamValueDisplay 35 
RotaryC7 FXParam 35 
Toggle+RotaryPushC7 NoAction 
/  
DisplayUpperC8 FXParamNameDisplay 36 "HFGain"
DisplayLowerC8 FXParamValueDisplay 36 
RotaryC8 FXParam 36 
Toggle+RotaryPushC8 NoAction 
/  
DisplayUpperD1 FXParamNameDisplay 16 "CThrsh"
DisplayLowerD1 FXParamValueDisplay 16 
RotaryD1 FXParam 16 
Toggle+RotaryPushD1 FXParam 15 
/  
DisplayUpperD2 FXParamNameDisplay 20 "CRatio"
DisplayLowerD2 FXParamValueDisplay 20 
RotaryD2 FXParam 20 
Toggle+RotaryPushD2 NoAction 
/  
DisplayUpperD3 FXParamNameDisplay 17 "CAtt"
DisplayLowerD3 FXParamValueDisplay 17 
RotaryD3 FXParam 17 
Toggle+RotaryPushD3 NoAction 
/  
DisplayUpperD4 FXParamNameDisplay 18 "CHold"
DisplayLowerD4 FXParamValueDisplay 18 
RotaryD4 FXParam 18 
Toggle+RotaryPushD4 NoAction 
/  
DisplayUpperD5 FXParamNameDisplay 19 "CRel"
DisplayLowerD5 FXParamValueDisplay 19 
RotaryD5 FXParam 19 
Toggle+RotaryPushD5 NoAction 
/  
DisplayUpperD6 FXParamNameDisplay 22 "CKnee"
DisplayLowerD6 FXParamValueDisplay 22 
RotaryD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ]
Toggle+RotaryPushD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ] 
/  
DisplayUpperD7 FXParamNameDisplay 23 "CType"
DisplayLowerD7 FXParamValueDisplay 23 
RotaryD7 FXParam 23 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushD7 FXParam 23 [ 0.0 0.50 1.0 ] 
/  
DisplayUpperD8 FXParamNameDisplay 21 "CMkeUp"
DisplayLowerD8 FXParamValueDisplay 21 
RotaryD8 FXParam 21 
Toggle+RotaryPushD8 NoAction 
/
ZoneEnd
/
Zone "VST: Oxford Dynamics (Sonnox)-2"
SelectedTrackNavigator
ParentZone "VST: Oxford Dynamics (Sonnox)"
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-2"
DisplayLowerA1 FXParamValueDisplay 45 
RotaryA1 FXParam 45 
Toggle+RotaryPushA1 FXParam 44 
/  
DisplayUpperA2 NoAction 
DisplayLowerA2 NoAction 
RotaryA2 NoAction 
Toggle+RotaryPushA2 NoAction 
/  
DisplayUpperA3 NoAction 
DisplayLowerA3 NoAction 
RotaryA3 NoAction 
Toggle+RotaryPushA3 NoAction 
/  
DisplayUpperA4 NoAction 
DisplayLowerA4 NoAction 
RotaryA4 NoAction 
Toggle+RotaryPushA4 NoAction 
/  
DisplayUpperA5 NoAction 
DisplayLowerA5 NoAction 
RotaryA5 NoAction 
Toggle+RotaryPushA5 NoAction 
/  
DisplayUpperA6 NoAction 
DisplayLowerA6 NoAction 
RotaryA6 NoAction 
Toggle+RotaryPushA6 NoAction 
/  
DisplayUpperA7 NoAction 
DisplayLowerA7 NoAction 
RotaryA7 NoAction 
Toggle+RotaryPushA7 NoAction 
/  
DisplayUpperA8 NoAction 
DisplayLowerA8 NoAction 
RotaryA8 NoAction 
Toggle+RotaryPushA8 NoAction 
/  
DisplayUpperB1 NoAction 
DisplayLowerB1 NoAction 
RotaryB1 NoAction 
Toggle+RotaryPushB1 NoAction 
/  
DisplayUpperB2 NoAction 
DisplayLowerB2 NoAction 
RotaryB2 NoAction 
Toggle+RotaryPushB2 NoAction 
/  
DisplayUpperB3 NoAction 
DisplayLowerB3 NoAction 
RotaryB3 NoAction 
Toggle+RotaryPushB3 NoAction 
/  
DisplayUpperB4 NoAction 
DisplayLowerB4 NoAction 
RotaryB4 NoAction 
Toggle+RotaryPushB4 NoAction 
/  
DisplayUpperB5 NoAction 
DisplayLowerB5 NoAction 
RotaryB5 NoAction 
Toggle+RotaryPushB5 NoAction 
/  
DisplayUpperB6 NoAction 
DisplayLowerB6 NoAction 
RotaryB6 NoAction 
Toggle+RotaryPushB6 NoAction 
/  
DisplayUpperB7 NoAction 
DisplayLowerB7 NoAction 
RotaryB7 NoAction 
Toggle+RotaryPushB7 NoAction 
/  
DisplayUpperB8 NoAction 
DisplayLowerB8 NoAction 
RotaryB8 NoAction 
Toggle+RotaryPushB8 NoAction 
/  
DisplayUpperC1 FXParamNameDisplay 3 "GThrsh"
DisplayLowerC1 FXParamValueDisplay 3 
RotaryC1 FXParam 3 
Toggle+RotaryPushC1 FXParam 2 
/  
DisplayUpperC2 NoAction 
DisplayLowerC2 NoAction 
RotaryC2 NoAction 
Toggle+RotaryPushC2 NoAction 
/  
DisplayUpperC3 FXParamNameDisplay 4 "GAtt"
DisplayLowerC3 FXParamValueDisplay 4 
RotaryC3 FXParam 4 
Toggle+RotaryPushC3 NoAction 
/  
DisplayUpperC4 FXParamNameDisplay 5 "GHold"
DisplayLowerC4 FXParamValueDisplay 5 
RotaryC4 FXParam 5 
Toggle+RotaryPushC4 NoAction 
/  
DisplayUpperC5 FXParamNameDisplay 6 "GRel"
DisplayLowerC5 FXParamValueDisplay 6 
RotaryC5 FXParam 6 
Toggle+RotaryPushC5 NoAction 
/  
DisplayUpperC6 FXParamNameDisplay 7 "GRange"
DisplayLowerC6 FXParamValueDisplay 7 
RotaryC6 FXParam 7 
Toggle+RotaryPushC6 NoAction 
/  
DisplayUpperC7 NoAction 
DisplayLowerC7 NoAction 
RotaryC7 NoAction 
Toggle+RotaryPushC7 NoAction 
/  
DisplayUpperC8 NoAction 
DisplayLowerC8 NoAction 
RotaryC8 NoAction 
Toggle+RotaryPushC8 NoAction 
/  
DisplayUpperD1 FXParamNameDisplay 9 "EThrsh"
DisplayLowerD1 FXParamValueDisplay 9 
RotaryD1 FXParam 9 
Toggle+RotaryPushD1 FXParam 8 
/  
DisplayUpperD2 FXParamNameDisplay 13 "ERatio"
DisplayLowerD2 FXParamValueDisplay 13 
RotaryD2 FXParam 13 
Toggle+RotaryPushD2 NoAction 
/  
DisplayUpperD3 FXParamNameDisplay 10 "EAtt"
DisplayLowerD3 FXParamValueDisplay 10 
RotaryD3 FXParam 10 
Toggle+RotaryPushD3 NoAction 
/  
DisplayUpperD4 FXParamNameDisplay 11 "EHold"
DisplayLowerD4 FXParamValueDisplay 11 
RotaryD4 FXParam 11 
Toggle+RotaryPushD4 NoAction 
/  
DisplayUpperD5 FXParamNameDisplay 12 "ERel"
DisplayLowerD5 FXParamValueDisplay 12 
RotaryD5 FXParam 12 
Toggle+RotaryPushD5 NoAction 
/  
DisplayUpperD6 FXParamNameDisplay 14 "ERange"
DisplayLowerD6 FXParamValueDisplay 14 
RotaryD6 FXParam 14 
Toggle+RotaryPushD6 NoAction 
/  
DisplayUpperD7 NoAction 
DisplayLowerD7 NoAction 
RotaryD7 NoAction 
Toggle+RotaryPushD7 NoAction 
/  
DisplayUpperD8 NoAction 
DisplayLowerD8 NoAction 
RotaryD8 NoAction 
Toggle+RotaryPushD8 NoAction 
/
ZoneEnd

@TDC here you go...subzones

[Cragster]

Originally Posted by MixMonkey

Pt2
The original Zone, "VST: Oxford Dynamics (Sonnox)" has the compressor, limiter, SC EQ and Warmth. The sub-Zone, "VST: Oxford Dynamics (Sonnox)-2" has the Gate and Expander. I switch between the Zones using the Marker and ChanStrip buttons.

You make as many sub-zones as you like, just make sure each has a different name (I just use numbers tagged on to end of the original Zone name) and put the ParentZone line in each of the sub-zones to make sure they are de-activated when the original Zone is de-activated.

@TDC and this

[tdc]

Re the Strange MIDI Output in the Console.

Originally Posted by Geoff Waddington

Can you please check which Widgets those are (b0 01, b4 01, etc.) and which actions they are mapped to at the time of the capture

Attached is the ZON and associated MST file that can cause this message stream.
TDC_MFT_ReaEQ.zon.zip
MFTwisterTDC.mst.zip

A few further tests reveal:

1. This is a SelectedTrackNavigator and as we have found these will hang around, even when you move to another track that doesn't have a FX plugin, it only gets pushed off the stack when you GoZone "Home", or deselect all tracks.

2. The constant stream of MIDI data Is not being sent out the MIDI Port but is displayed in the CSI Console (Show Output to Surfaces). The initialisation data is in the console and seen at the MIDI output, but then the cycling of data is shown in the Console but isn't output physically.

I have narrowed it down to something to do with mapping a Rotary Encoder to a TrackOutputMeter... Its not cut and dry though. As I can execute the following.

Press1 Reaper "_S&M_WNCLS5" { 0 255 0 0 255 0 } // Close all float FX for Selected Track
Press1 Reaper "40297" // Unselect All Tracks // Green
Press1 Reaper "_S&M_WNMAIN" // Set Focus to Main Window.
Press1 GoZone "Home"
Rotary1 TrackOutputMeter
ShiftRotary1 FXParam "9999"

When I move to this zone, I see the rogue data. But then I can comment out the Rotary1 TrackOutputMeter data, RefreshSurfaces, and the behaviour is still there. Until a reboot.

I should also add, that this stream of data also happens on channels that have no audio, or plugins upstream. I thougght this could be a denormalisation related issue. But I just tried a clean new audio track, with ReaEQ on it, then whilst playing deleted the plugin. The stream continues until I press stop. ( :-) hope the is of some assistance )

[tdc]

Latest Beta: Feedback

Just spent some time with the latest beta. EuCon seems to be a little strange on Refresh Surfaces. The EuCOn surface, S3, will only come online if I CMD-Tab to another Application other than Reaper.

[tdc]

Philosophical Approach Question

This is a question aimed at all you experienced CSI'ers out there. I have now managed to build some rudimentary config files that allow display and control across a number of devices. (Avid S3 16ch control surface with side car Transport, Midi Fighter Twister and a couple of iOS devices running the OSC development app "Lemur")

I have also built many zone files for various plugins and overview style displays for the currently selected track or Focused FX Parameter.

Now, I am wondering how best to implement all these options? I am sure there are many amazing setups in use by you clever folks and I am interested to hear how you designed your implementation of CSI.

As primarily a mix engineer for music, I typically am concerned with quick tactile control of my processing chain. How do you suggest I move from channel to channel and get the appropriate FX Slot Zone file to be mapped to a controller? At present I have tried the Focused FX and the SelectedTrack Navigator methods, but I can't see how to best to streamline the operation when moving from channel to channel quickly.

Should I consider, building a hardware proxy? With one device dedicated to a class of DSP. So when I go from channel to channel, the EQ will always map to the left Midi surface, or the Dynamics to the Right iPad? How does this handle multiple instances of a class, like a few different compressors?

So many choices hey! Thanks to you all for helping me get this far ( and Geoff for imagining and making CSI ), I am excited at what all this freedom for ideas and empowerment will lead to.

[MixMonkey]

Originally Posted by tdc

Philosophical Approach Question

This is a question aimed at all you experienced CSI'ers out there. I have now managed to build some rudimentary config files that allow display and control across a number of devices. (Avid S3 16ch control surface with side car Transport, Midi Fighter Twister and a couple of iOS devices running the OSC development app "Lemur")

I have also built many zone files for various plugins and overview style displays for the currently selected track or Focused FX Parameter.

Now, I am wondering how best to implement all these options? I am sure there are many amazing setups in use by you clever folks and I am interested to hear how you designed your implementation of CSI.

As primarily a mix engineer for music, I typically am concerned with quick tactile control of my processing chain. How do you suggest I move from channel to channel and get the appropriate FX Slot Zone file to be mapped to a controller? At present I have tried the Focused FX and the SelectedTrack Navigator methods, but I can't see how to best to streamline the operation when moving from channel to channel quickly.

Should I consider, building a hardware proxy? With one device dedicated to a class of DSP. So when I go from channel to channel, the EQ will always map to the left Midi surface, or the Dynamics to the Right iPad? How does this handle multiple instances of a class, like a few different compressors?

So many choices hey! Thanks to you all for helping me get this far ( and Geoff for imagining and making CSI ), I am excited at what all this freedom for ideas and empowerment will lead to.

My setup is pretty simple. I have 1 x MCU, 5 x MCUXT and 1 x C4. The C4 auto maps sends and the FX menu across its bottom two rows, so when you select a channel on any of the MCU/XTs you see the see the sends and FX slots for that channel.

Sends for the selected channel can be adjusted directly on rotaries on the C4 (send mute on push) or on faders on the MCU by pushing the 'Send' button on the MCU (send mute on channel mute button)

The individual FX slots are accessed by pushing the relevant rotary on the C4, which causes that particular slot's FX to map to the C4's 32 rotaries/pushes. When an FX Slot is accessed, the FX window opens.

A lower C4 button returns to the FX menu so you can move between FX slots.

From the FX menu row on the C4, individual FX slots can be bypassed or offlined by shift or option pushing the relevant rotary.

Four other lower C4 buttons access FX sub-zones and a further four (with LEDs) access the four modifiers.

The last lower C4 button closes all FX windows.

[MixMonkey]

Originally Posted by tdc

MixMonkey! How on earth did you obtain that !!

It's generated by that spreadsheet I mentioned. Unfortunately it relies on a feature currently missing from CSI.

[tdc]

Originally Posted by MixMonkey

My setup is pretty simple. I have 1 x MCU, 5 x MCUXT and 1 x C4. The C4 auto maps sends and the FX menu across its bottom two rows, so when you select a channel on any of the MCU/XTs you see the see the sends and FX slots for that channel.

Thanks for taking to time MixMonkey, that was really instructive. The overall architecture CSI is clearer now that I can see the impetus for many of the methods. TBH I had not kept up with the Mackie gear for years so I am unfamiliar with the line up, thus the use cases for the FXMenu wasn't obvious to me.

When you are going from channel to channel, do you keep having to select your chosen slot? And how are you handling the display and hiding of the FX windows in Reaper. ( And how the hell do you get them to appear in one location )

I think you need to reconsider your use of the word Simple to btw.

Thanks again!

[tdc]

Reading through this long thread, I have seen reference to an Action called "GainReductionDB". I have tried implementing it but all I get is the same value as the Threshold.

Has it been deprecated?

Also - what is the syntactical reason for having the pipe one space away from the action in this statement?
"DisplayUpper| FXNameDisplay |"

[MixMonkey]

Originally Posted by tdc

When you are going from channel to channel, do you keep having to select your chosen slot?

Yes, I have to choose the slot for each newly selected channel but that suits my workflow best. I could have all the plugins on a track map to the C4 directly (not via the FX menu) by using:

MapSelectedTrackFXToWidgets

....but this would restrict the plugin layout on the C4 (to avoid mapping collisions) For the sake of one more button push, I prefer the layout flexibility.

I could probably set it to always open a particular FX slot on channel selection, using:

GoFXSlot 1 (say)

..but I've found this kind of thing to be more of a hinderance than a help really.

And how are you handling the display and hiding of the FX windows in Reaper. ( And how the hell do you get them to appear in one location )

When I select an FX slot from the menu, the FX appears in an FX chain window- this retains its position. People have asked for years to be able to set the position of an opening FX floating window- no luck yet As I've got more used to the C4 mapping, I'm less inclined to have the FX window open automatically, but that's how it's set at the moment. FXMenu Zone is:

Zone "FXMenu|1-8"
        SelectedTrackNavigator
        DisplayUpperD|                  FXNameDisplay |
        DisplayLowerD|                  NoAction
        RotaryD|                        NoAction
        RotaryPushD|                    GoFXSlot |
        RotaryPushD|                    Reaper "_S&M_SHOWFXCHAIN|"
        Shift+RotaryPushD|              Reaper "_S&M_FXBYP|"            //Bypass FX Slot
        Option+RotaryPushD|             Reaper "_S&M_FXOFF|"            //Offline FX slot
ZoneEnd

A lower C4 button closes the FX chain window.

What I'd really like to be able to do is get rid of the acres of white space in certain Reaper windows (like FXChain), as I have quite a dark theme and it's pretty jarring.

I think you need to reconsider your use of the word Simple

Simple in the sense of only 3 different surfaces (and two of those are nearly identical) I like the Mackies and they're cheap as chips on ebay.



I retro-fitted them with LuxMuzik displays (higher quality LCD and no-fade LED backlight) and power them all from a single 20A 7.5V industrial PSU I got for 40 quid

MIDI is handled by a MOTU MIDI Express 128 (5 x MCUXT+C4) and USB for the MCU.

[tdc]

Originally Posted by MixMonkey

Yes, I have to choose the slot for each newly selected channel but that suits my workflow best. I could have all the plugins on a track map to the C4 directly (not via the FX menu) by using:

Post saved for future reference.

Fantastically helpful post MixMonkey. It all makes sense and is clear as to the way the system can be implemented. As you are finding, getting the hardware to the point where it feels tactile and intuitive is the ultimate goal as we can then use our ears and not eyes. Seeing you making this all work in what looks like a production environment is encouraging.

Very tidy setup too by the way!

Thanks for sharing.

[MixMonkey]

Originally Posted by tdc

Post saved for future reference.

Fantastically helpful post MixMonkey. It all makes sense and is clear as to the way the system can be implemented. As you are finding, getting the hardware to the point where it feels tactile and intuitive is the ultimate goal as we can then use our ears and not eyes. Seeing you making this all work in what looks like a production environment is encouraging.

It's working really well now When Geoff added the stepped parameter construct I managed to map FX parameters that had previously been inaccessible to the inc/dec encoders. I've done about 400 plugins now and I haven't come across anything that CSI couldn't handle.

The VCA mode feature completely changed how I lay out projects in Reaper. Previously I had all the VCA masters grouped together at one end of the mixer (so I didn't have to hunt for them) now I just leave them wherever, because VCA mode shows them all and hides everything else (and any of them can be spilt to show their contents)

Very tidy setup too by the way!

Thanks. Actually nailing down what your workflow is going to be is one of the most challenging parts of CSI. There are many different ways of achieving the same thing, depending on your preferences, what surfaces you have and what kind of work you do.

[tdc]

The results are a testament to your tenacity MixMonkey and indeed the whole CSI movement.

I completely agree that you need to start with a vision of the end goal in mind. Having thoughts about how I would like to work are what motivated me to consider moving from the Avid ecosystem. I campaigned for years for the encoders on all the later series's (S3, S6 etc) to have their scaling issues fixed. They had a strange curve and acceleration to them that after hours of working made me want to throw the surfaces out. Grr. After only a few days of getting deep with the CSI system, Geoff implements the custom step array! Brilliant.

I have yet to get into the CSI VCA implementation yet, but I can see it is going to be great. I have always preferred a nested system of mix assets, so VCA spill be perfect for that.

Random question: I am at the start of exploring the FXMenu system, and have a list of displays that are populated with the appropriate FX plugins (well at least the ones I have made for this device). And I am wondering how I implement the GoFXSlot in the sense of how do the params map to the widgets? All the examples I can see have widget names that don't exist.

For example:

Zone "VST: ReaComp (Cockos)" "ReaComp"
SelectedTrackNavigator
Threshold FXParam "0" "Thresh"
Attack FXParam "2" "Attack"
Release FXParam "3" "Release"
Ratio FXParam "1" "Ratio"
Compressor FXParam "19" "Bypass"
Parallel FXParam "20" "Wet"
CompressorMeter FXParam "GainReductionDB"
ZoneEnd

How do I map the "Threshold" in this example to DisplayUpper1 on my device? Or do they just replace the Displays that the List of FX Slots were just using with as many params as they can fit?

Thanks,

[MixMonkey]

Originally Posted by tdc

How do I map the "Threshold" in this example to DisplayUpper1 on my device?

What you're looking at is an FX Zone for the Softube Console1, which doesn't have any displays. My C4 Zone would look like this.

DisplayUpperD1 FXParamNameDisplay 0 "Thresh"
DisplayLowerD1 FXParamValueDisplay 0 
RotaryD1 FXParam 0 [ 0.0-1.0 ]
Toggle+RotaryPushD1 NoAction

....where "Thresh" is what is shown in the upper line of the display (I keep my names to a max of 6 characters to fit the LCD on the Mackie)

When you GoFXSlot, the FX menu is replaced by the FX map for the FX in that slot.

[tdc]

Originally Posted by MixMonkey

What you're looking at is an FX Zone for the Softube Console1, which doesn't have any displays. My C4 Zone would look like this.

DisplayUpperD1 FXParamNameDisplay 0 "Thresh"
DisplayLowerD1 FXParamValueDisplay 0 
RotaryD1 FXParam 0 [ 0.0-1.0 ]
Toggle+RotaryPushD1 NoAction

....where "Thresh" is what is shown in the upper line of the display (I keep my names to a max of 6 characters to fit the LCD on the Mackie)

When you GoFXSlot, the FX menu is replaced by the FX map for the FX in that slot.

Gotcha, thanks.

[Geoff Waddington]

Originally Posted by tdc

:-) My head still hurts after spending an hour or so last night building a Zon file for Fabfilter's Pro-Q 3. It has around 490 Parameters. I tried to be smart and build from the work that FunkyBot had already done, but I wanted some other parameters so had to simply count until the Cat wanted to be stroked.

1, 2, 3, 4, 5, ...... 234, 235, 236, Meow, 23.... umm ... Arse!

In the end I made my FX Window a size that showed 50 Parameters at a time and then just counted the times I paged down. Then took a guess at the parameter number, and watched where it moved and then adjusted from there :-)

Its frustrating because you can see a spreadsheet list of all the parameters in the Project Bay window, but there is no export or Copy and Paste possible in there.

Improved the FX Param spill in the build just put up.

Just open the Edit Mode Window, select "Show FX Params when Inserted" -- or whatever it actually says

Then each FX you insert will spill params into ReaConsole.

In this build I added the param numbers for those long nasty lists

[Geoff Waddington]

Originally Posted by tdc

Re the Strange MIDI Output in the Console.



Attached is the ZON and associated MST file that can cause this message stream.
Attachment 40123
Attachment 40124

A few further tests reveal:

1. This is a SelectedTrackNavigator and as we have found these will hang around, even when you move to another track that doesn't have a FX plugin, it only gets pushed off the stack when you GoZone "Home", or deselect all tracks.

2. The constant stream of MIDI data Is not being sent out the MIDI Port but is displayed in the CSI Console (Show Output to Surfaces). The initialisation data is in the console and seen at the MIDI output, but then the cycling of data is shown in the Console but isn't output physically.

I have narrowed it down to something to do with mapping a Rotary Encoder to a TrackOutputMeter... Its not cut and dry though. As I can execute the following.



When I move to this zone, I see the rogue data. But then I can comment out the Rotary1 TrackOutputMeter data, RefreshSurfaces, and the behaviour is still there. Until a reboot.

I should also add, that this stream of data also happens on channels that have no audio, or plugins upstream. I thougght this could be a denormalisation related issue. But I just tried a clean new audio track, with ReaEQ on it, then whilst playing deleted the plugin. The stream continues until I press stop. ( :-) hope the is of some assistance )

Yeah, there is definitely something going on with relinquishing Zones, I've noticed a few whacky ones i the last couple of days are myself.

In order to help all of us when these things are encountered, output monitor has now been beefed up to include a lot more info.