Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by fourdogslong

Has any new features been added, or bugs been resolved in this new release or is it still mostly to experiment with the new learn setup?

Almost exclusively Learn mode experimentation.

[Geoff Waddington]

Originally Posted by Cragster

Hi Geoff

Giving the new exp version a try. Im only getting one way communication ? If i move a param on screen with the mouse the surface control ring and param value move accordingly but when i move anything on the surface nothing happens ?

Any idea whats causing that ?

But the features seem to work . I was able to change the param name in real time . The show boxes work. I havnt tried the step drop down yet.

Also everyone should be aware that the old FXRowLayout doesnt work with this. I know it was said that the name of the zone changed from FXLayouts to the above mentioned but i wasnt aware that the contents of that zone changed as well. Took me a while to realize that after looking at your Xtouch zone. The number of channels after every line needs to be deleted.
Just thought id mention that in case someone else gets caught with that as it had me stuck for while.

Everything looks cool . Just need to figure out why its only working moving onscreen with the mouse ??

Thanks Geoff. its looking really cool though !!

Oh and thought id mention that the FXMenu display doesnt update when switching channels. If the slot is blank it will display the FXmenu that was there from the previous channel.It only updates if theres a new FX in that slot. If i explained that correctly.

Thanks for testing, and for the bug report !

As of right now, the Learn Window is totally experimental, so don't expect much to work.

Matter of fact, just came up with a much improved AutoMap file format, so think of any Auto mapping that you do as experimental only.

[fourdogslong]

Originally Posted by Geoff Waddington

Almost exclusively Learn mode experimentation.

Ok thank you.

[Ilya Kuznetsov]

Good day to all!

If I understand correctly, there is currently no version of CSI for Linux. I wanted to ask if there are any plans to support this OS?

Ilya.

[Geoff Waddington]

Originally Posted by Ilya Kuznetsov

Good day to all!

If I understand correctly, there is currently no version of CSI for Linux. I wanted to ask if there are any plans to support this OS?

Ilya.

Right now, CSI is receiving a major rewrite, Linux is on the to do list.

[Ilya Kuznetsov]

Originally Posted by Geoff Waddington

Right now, CSI is receiving a major rewrite, Linux is on the to do list.

This is very cool news! I'll be waiting for updates on the topic.

[Geoff Waddington]

Finally, finally, think there is a feasible solution to the psychedelic displays problem.

Internally CSI will store the Cells in one container.

So, for instance, if you had an MCU device and defined Rotary1, RotaryPush1, and Fader1, as well as DisplayUpper1 and DisplayLower1, here's how it would work.

Since Rotary1 is defined first, Auto Map would map all parameters to the Rotaries, using DisplayUpper for name and DisplayLower for value, pretty standard stuff.

But wait there's more

The new Learn window is free form.

For instance you could assign RotaryPush1 to bypass and display the value on DisplayUpper1.

Then you could assign Rotary1 to Wet/Dry, with no displays, the feedback would be via the ring LEDs.

Finally, you could assign Fader1 to, let's say, Output and display the value on DisplayLower1.

Super flexible, and since the displays will be accessed via a dropdown, we can show only available ones.

This is going to be a winner !

[spicytripe]

Sounds awesome! Looking forward to this!

[MixMonkey]

Originally Posted by Geoff Waddington

Super flexible, and since the displays will be accessed via a dropdown, we can show only available ones.

This is going to be a winner !

Sounds comprehensive!

[MT4U]

Originally Posted by Geoff Waddington

Finally, you could assign Fader1 to, let's say, Output and display the value on DisplayLower1.

Super flexible, and since the displays will be accessed via a dropdown, we can show only available ones.

This is going to be a winner !

Fader1 would show the value on DisplayLower1 on Touch, is that right? Sounds really cool, like having more encoders for Auto-Mapping.

[Geoff Waddington]

Originally Posted by MT4U

Fader1 would show the value on DisplayLower1 on Touch, is that right? Sounds really cool, like having more encoders for Auto-Mapping.

I was trying to keep it simple, but yes, you could do Fader on Touch, which would free up the other display for, let's say Mute;

Rotary1 -> Wet/Dry     -- no display, feedback via ring LEDs.
RotaryPush1 -> Bypass  -- value shows in DisplayUpper1
Mute1 -> Power         -- value displayed on DisplayLower1
Fader1 -> Output       -- value displayed when fader is touched

Notice how, for this contrived example, we don't even need to display any param names, they are self explanatory -- Bypass enabled/disabled, Power On/Off.

For the Fader, you could even grab both the Upper and Lower Displays temporarily.

That's a lot of power in a tight package

[Funkybot]

Sounds great!

[MT4U]

Originally Posted by Geoff Waddington

For the Fader, you could even grab both the Upper and Lower Displays temporarily.

That's a lot of power in a tight package

Even better!

[UNdark]

Originally Posted by Geoff Waddington

I was trying to keep it simple, but yes, you could do Fader on Touch, which would free up the other display for, let's say Mute;

Rotary1 -> Wet/Dry     -- no display, feedback via ring LEDs.
RotaryPush1 -> Bypass  -- value shows in DisplayUpper1
Mute1 -> Power         -- value displayed on DisplayLower1
Fader1 -> Output       -- value displayed when fader is touched

Notice how, for this contrived example, we don't even need to display any param names, they are self explanatory -- Bypass enabled/disabled, Power On/Off.

For the Fader, you could even grab both the Upper and Lower Displays temporarily.

That's a lot of power in a tight package

This is how I've been thinking of CSI too - really maximising Controls and always having a display to account for them - Excellent solutions - well done

[Tomás Mulcahy]

Hi folks, can you please tell me what is the most up to date .mst for the Icon Platform Nano?

Edit: found one on Reaper stash. Needs a little work...
https://stash.reaper.fm/v/47521/Icon...0CSI%203.0.zip

Originally Posted by WaveTrans

I also attach my updated full Icon Nano set, including FX zones.

Thank you for this I got it to work.

[yimbot]

Just a feature question. I haven't installed CSI to test with my UF8 yet and have just been looking through the wiki, but I couldn't find the answer there.

Is it possible to filter the track view at all? Much like I might filter the MCP to reduce the number of tracks I'm viewing, I'd like to do the same thing with a control surface. I could imagine dedicating shortcut keys to filter views would make navigating the session a whole lot easier!

[fourdogslong]

Originally Posted by yimbot

Just a feature question. I haven't installed CSI to test with my UF8 yet and have just been looking through the wiki, but I couldn't find the answer there.

Is it possible to filter the track view at all? Much like I might filter the MCP to reduce the number of tracks I'm viewing, I'd like to do the same thing with a control surface. I could imagine dedicating shortcut keys to filter views would make navigating the session a whole lot easier!

You could use SWS snapshots for that and assign recalls to some buttons on your controller.

[yimbot]

Originally Posted by fourdogslong

You could use SWS snapshots for that and assign recalls to some buttons on your controller.

Thanks Fourdogslong. So are you saying that the MCP view and the CSI Control Surface are linked in visibility?

[fourdogslong]

Originally Posted by yimbot

Thanks Fourdogslong. So are you saying that the MCP view and the CSI Control Surface are linked in visibility?

Yes, I'm not at the computer right now but I believe there is a preference in CSI that links either TCP or MCP to the controller.

[TheFancyWolf]

hey @geoff!

Remember a couple months back when we started to support the multiple displays on the Icon D4 for the P1-M and we were waiting for a firmware update to move further? Welp, they finally did it.

It now works properly when using DrivenByMoss. I switched back to CSI and we have some display issues on the bottom displays. I contacted them and they said they did not change the LCD Protocol in the update.

I posted the LCD protocol here with an image of the current issue: https://fancywolfeffects.com/lcd-protocol/

Do you see anything we can do to fix?

[Jonathan S Colombera]

Hello everyone I am a complete beginner here when it comes to the coding side of the CSI side of things

I want to be able to change the colours of the lCD to correspond to the colours on my project

for example

Drums are purple, (x touch displays them as Blue.
Guitars are orange, (x touch displays them as red. etc

some tracks in my project are the correct colour

I have tried following the Github CSI https://github.com/GeoffAWaddington/CSI30Wiki/wiki

however I have had no luck

I have spent around 3 hours scratching my head to get this to work

If anyone could please assist me that would be appreciated

I also understand things better if it is a screen shot or very detailed

Thank you

[ldhall1856]

Originally Posted by TheFancyWolf

hey @geoff!

Remember a couple months back when we started to support the multiple displays on the Icon D4 for the P1-M and we were waiting for a firmware update to move further? Welp, they finally did it.

It now works properly when using DrivenByMoss. I switched back to CSI and we have some display issues on the bottom displays. I contacted them and they said they did not change the LCD Protocol in the update.

I posted the LCD protocol here with an image of the current issue: https://fancywolfeffects.com/lcd-protocol/

Do you see anything we can do to fix?

Could you please post your config files? I would love to try it out! I could never get my config to work properly and didn’t have time to spend to get it running. Currently using drive by moss

[Geoff Waddington]

Originally Posted by TheFancyWolf

hey @geoff!

Remember a couple months back when we started to support the multiple displays on the Icon D4 for the P1-M and we were waiting for a firmware update to move further? Welp, they finally did it.

It now works properly when using DrivenByMoss. I switched back to CSI and we have some display issues on the bottom displays. I contacted them and they said they did not change the LCD Protocol in the update.

I posted the LCD protocol here with an image of the current issue: https://fancywolfeffects.com/lcd-protocol/

Do you see anything we can do to fix?

Cool, will add it to the to do list.

[Geoff Waddington]

Originally Posted by Jonathan S Colombera

Hello everyone I am a complete beginner here when it comes to the coding side of the CSI side of things

I want to be able to change the colours of the lCD to correspond to the colours on my project

for example

Drums are purple, (x touch displays them as Blue.
Guitars are orange, (x touch displays them as red. etc

some tracks in my project are the correct colour

I have tried following the Github CSI https://github.com/GeoffAWaddington/CSI30Wiki/wiki

however I have had no luck

I have spent around 3 hours scratching my head to get this to work

If anyone could please assist me that would be appreciated

I also understand things better if it is a screen shot or very detailed

Thank you

X-Touch only has 8 colours total, including black and white, so CSI gets as close as it can

[TheFancyWolf]

Originally Posted by ldhall1856

Could you please post your config files? I would love to try it out! I could never get my config to work properly and didn’t have time to spend to get it running. Currently using drive by moss

Config file hasn't been altered yet. Just waiting to get the display working first. Also using DrivenByMoss in the mean time.

Thanks @geoff!

[Geoff Waddington]

Methinks I'm overthinking this

Here is the latest Learn Window with the Advanced panel opened:



The grid is there to show you the display usage.

It's meant to "help" prevent overwriting a previously assigned display -- one that was assigned to a "sibling" control.

Seeing it live, makes me think it just confuses things.

I think I'll move the 2 drop downs to the main screen, the advanced section will be for colours and fonts only.

So, the new rule is, when you assign a display, it just overwrites any previous assignment.

What do you think ?

[MixMonkey]

Originally Posted by Geoff Waddington

I think I'll move the 2 drop downs to the main screen, the advanced section will be for colours and fonts only.

So, the new rule is, when you assign a display, it just overwrites any previous assignment.

What do you think ?

Good idea! Display assignment should be on the main screen. Overwriting previous assignments is fine too

[spicytripe]

As a new user to Reaper and CSI, I can't really wrap my head around how the work flow will be until I use it. BUT! I'm totally excited about this and looking forward to the new functionality! This is really awesome. Great work.

[Geoff Waddington]

Ok, here's the latest, and, unless anyone hates it , likely close to final.

A lot of folks will only open the top left main Learn Window.

The right Window is for Colours/Fonts.

Both of those Windows are non modal and edit the surface in real time.

The Params dialog (bottom) is modal.

Interested in your thoughts:

[jakeman19]

Originally Posted by Geoff Waddington

Ok, here's the latest, and, unless anyone hates it , likely close to final.

A lot of folks will only open the top left main Learn Window.

The right Window is for Colours/Fonts.

Both of those Windows are non modal and edit the surface in real time.

The Params dialog (bottom) is modal.

Interested in your thoughts:

Looks good to me Geoff. Great work as usual.

Jd

[spicytripe]

As a new Reaper and CSI user 😁, looking at this makes a lot more sense now. This is awesome! Can't wait to see if the uf8 will support the font/colors.

[fourdogslong]

This seems great, good job!

[UNdark]

Originally Posted by Geoff Waddington

Ok, here's the latest, and, unless anyone hates it , likely close to final.

A lot of folks will only open the top left main Learn Window.

The right Window is for Colours/Fonts.

Both of those Windows are non modal and edit the surface in real time.

The Params dialog (bottom) is modal.

Interested in your thoughts:

it looks great to me!!!

[Funkybot]

I dig it.

[MixMonkey]

Looks good!

[Geoff Waddington]

FYI progress update.

The AutoMap/Learn basic file format is now finalized.

It just mimics the FXWidgetLayout file:

Zone FXWidgetLayout
	Rotary FXParam RingStyle=Dot
	DisplayUpper FixedTextDisplay
	DisplayLower FXParamValueDisplay
ZoneEnd

#WidgetTypes Rotary RotaryPush Fader
#DisplayRows DisplayUpper DisplayLower
#RingStyles Dot Fill BoostCut Spread

The one change is that the FixedTextDisplay params now include a param num so that CSI can match them up to the appropriate control Widget.

It reads a lot cleaner than the old style, and is much less complex programmatically.

Zone "VST: UAD Fairchild 660 (Universal Audio, Inc.)" "Fairchild 660"
	OnZoneActivation SetXTouchDisplayColors Cyan
	OnZoneActivation ToggleUseLocalModifiers
	Plugin ClearFXSlot

#Begin auto generated section
	Rotary1 FXParam 12 RingStyle=Dot
	RotaryPush1 FXParam 0 [ 0 0.5 1 ]
	Fader1 FXParam 8
	DisplayUpper1 FXParamValueDisplay 0 
	DisplayLower1 FXParamValueDisplay 8 

	Rotary2 FXParam 1 [ 0 0.05 0.1 0.15 0.2 0.25 0.3 0.35 0.4 0.45 0.5 0.55 0.6 0.65 0.7 0.75 0.8 0.85 0.9 0.95 1 ] RingStyle=Dot
	RotaryPush2 NoAction
	Fader2 NoAction
	DisplayUpper2 FixedTextDisplay "Input" 1 
	DisplayLower2 FXParamValueDisplay 1 

	Rotary3 FXParam 2 RingStyle=Dot
	RotaryPush3 NoAction
	Fader3 NoAction
	DisplayUpper3 FixedTextDisplay "Thresh" 2 
	DisplayLower3 FXParamValueDisplay 2 

	Rotary4 FXParam 3 [ 0 0.2 0.4 0.6 0.8 1 ] RingStyle=Dot
	RotaryPush4 NoAction
	Fader4 NoAction
	DisplayUpper4 FixedTextDisplay "Time Const" 3 
	DisplayLower4 FXParamValueDisplay 3 

	Rotary5 FXParam 4 RingStyle=Dot
	RotaryPush5 NoAction
	Fader5 NoAction
	DisplayUpper5 FixedTextDisplay "SC Filt" 4 
	DisplayLower5 FXParamValueDisplay 4 

	Rotary6 FXParam 5 RingStyle=Dot
	RotaryPush6 NoAction
	Fader6 NoAction
	DisplayUpper6 FixedTextDisplay "Bal" 5 
	DisplayLower6 FXParamValueDisplay 5 

	Rotary7 FXParam 6 RingStyle=Dot
	RotaryPush7 NoAction
	Fader7 NoAction
	DisplayUpper7 FixedTextDisplay "DC Thr" 6 
	DisplayLower7 FXParamValueDisplay 6 

	Rotary8 FXParam 7 RingStyle=Dot
	RotaryPush8 NoAction
	Fader8 NoAction
	DisplayUpper8 FixedTextDisplay "Output" 7 
	DisplayLower8 FXParamValueDisplay 7 



	Shift+Rotary1 FXParam 8 RingStyle=Dot
	Shift+RotaryPush1 NoAction
	Shift+Fader1 NoAction
	Shift+DisplayUpper1 FixedTextDisplay "Mix" 8 
	Shift+DisplayLower1 FXParamValueDisplay 8 

	Shift+Rotary2 FXParam 9 [ 0 0.17 0.33 0.5 0.67 0.83 1 ] RingStyle=Dot
	Shift+RotaryPush2 NoAction
	Shift+Fader2 NoAction
	Shift+DisplayUpper2 FixedTextDisplay "Headroom" 9 
	Shift+DisplayLower2 FXParamValueDisplay 9 

	Shift+Rotary3 FXParam 10 [ 0 1 ] RingStyle=Dot
	Shift+RotaryPush3 NoAction
	Shift+Fader3 NoAction
	Shift+DisplayUpper3 FixedTextDisplay "Power" 10 
	Shift+DisplayLower3 FXParamValueDisplay 10 

	Shift+Rotary4 FXParam 11 [ 0 1 ] RingStyle=Dot
	Shift+RotaryPush4 NoAction
	Shift+Fader4 NoAction
	Shift+DisplayUpper4 FixedTextDisplay "Bypass" 11 
	Shift+DisplayLower4 FXParamValueDisplay 11 

	Shift+Rotary5 FXParam 12 RingStyle=Dot
	Shift+RotaryPush5 NoAction
	Shift+Fader5 NoAction
	Shift+DisplayUpper5 FixedTextDisplay "Wet" 12 
	Shift+DisplayLower5 FXParamValueDisplay 12 

	Shift+Rotary6 FXParam 13 [ 0 1 ] RingStyle=Dot
	Shift+RotaryPush6 NoAction
	Shift+Fader6 NoAction
	Shift+DisplayUpper6 FixedTextDisplay "Delta" 13 
	Shift+DisplayLower6 FXParamValueDisplay 13 

	Shift+Rotary7 NoAction
	Shift+RotaryPush7 NoAction
	Shift+Fader7 NoAction
	Shift+DisplayUpper7 NoAction
	Shift+DisplayLower7 NoAction

	Shift+Rotary8 NoAction
	Shift+RotaryPush8 NoAction
	Shift+Fader8 NoAction
	Shift+DisplayUpper8 NoAction
	Shift+DisplayLower8 NoAction



	Control+Rotary1 NoAction
	Control+RotaryPush1 NoAction
	Control+Fader1 NoAction
	Control+DisplayUpper1 NoAction
	Control+DisplayLower1 NoAction

	Control+Rotary2 NoAction
	Control+RotaryPush2 NoAction
	Control+Fader2 NoAction
	Control+DisplayUpper2 NoAction
	Control+DisplayLower2 NoAction

	Control+Rotary3 NoAction
	Control+RotaryPush3 NoAction
	Control+Fader3 NoAction
	Control+DisplayUpper3 NoAction
	Control+DisplayLower3 NoAction

	Control+Rotary4 NoAction
	Control+RotaryPush4 NoAction
	Control+Fader4 NoAction
	Control+DisplayUpper4 NoAction
	Control+DisplayLower4 NoAction

	Control+Rotary5 NoAction
	Control+RotaryPush5 NoAction
	Control+Fader5 NoAction
	Control+DisplayUpper5 NoAction
	Control+DisplayLower5 NoAction

	Control+Rotary6 NoAction
	Control+RotaryPush6 NoAction
	Control+Fader6 NoAction
	Control+DisplayUpper6 NoAction
	Control+DisplayLower6 NoAction

	Control+Rotary7 NoAction
	Control+RotaryPush7 NoAction
	Control+Fader7 NoAction
	Control+DisplayUpper7 NoAction
	Control+DisplayLower7 NoAction

	Control+Rotary8 NoAction
	Control+RotaryPush8 NoAction
	Control+Fader8 NoAction
	Control+DisplayUpper8 NoAction
	Control+DisplayLower8 NoAction



	Option+Rotary1 NoAction
	Option+RotaryPush1 NoAction
	Option+Fader1 NoAction
	Option+DisplayUpper1 NoAction
	Option+DisplayLower1 NoAction

	Option+Rotary2 NoAction
	Option+RotaryPush2 NoAction
	Option+Fader2 NoAction
	Option+DisplayUpper2 NoAction
	Option+DisplayLower2 NoAction

	Option+Rotary3 NoAction
	Option+RotaryPush3 NoAction
	Option+Fader3 NoAction
	Option+DisplayUpper3 NoAction
	Option+DisplayLower3 NoAction

	Option+Rotary4 NoAction
	Option+RotaryPush4 NoAction
	Option+Fader4 NoAction
	Option+DisplayUpper4 NoAction
	Option+DisplayLower4 NoAction

	Option+Rotary5 NoAction
	Option+RotaryPush5 NoAction
	Option+Fader5 NoAction
	Option+DisplayUpper5 NoAction
	Option+DisplayLower5 NoAction

	Option+Rotary6 NoAction
	Option+RotaryPush6 NoAction
	Option+Fader6 NoAction
	Option+DisplayUpper6 NoAction
	Option+DisplayLower6 NoAction

	Option+Rotary7 NoAction
	Option+RotaryPush7 NoAction
	Option+Fader7 NoAction
	Option+DisplayUpper7 NoAction
	Option+DisplayLower7 NoAction

	Option+Rotary8 NoAction
	Option+RotaryPush8 NoAction
	Option+Fader8 NoAction
	Option+DisplayUpper8 NoAction
	Option+DisplayLower8 NoAction



#End auto generated section

	OnZoneDeactivation RestoreXTouchDisplayColors
	OnZoneDeactivation ToggleUseLocalModifiers
ZoneEnd

[Funkybot]

Looking good!

[Geoff Waddington]

Design question.

Should CSI write out properties before writing out all of the [ ] stuff ?

Seems likely that anyone manually editing would be less intimidated if the properties came before steps, acceleration, etc.

Just a readability thing.

What say you folks ?

[MT4U]

Originally Posted by Geoff Waddington

Design question.

Should CSI write out properties before writing out all of the [ ] stuff ?

Seems likely that anyone manually editing would be less intimidated if the properties came before steps, acceleration, etc.

Just a readability thing.

What say you folks ?

Does CSI need them in any particular order or would it be just for ease or editing the generated zones?

[Geoff Waddington]

Originally Posted by MT4U

Does CSI need them in any particular order or would it be just for ease or editing the generated zones?

The params can be in any order, it's just for the visual.