Control Surface Integration (CSI) Technical Feature Discussion

[MixMonkey]

Originally Posted by Geoff Waddington

Matter of fact, I'm going to take it easy today, need to

Put your feet up (and give the rest of us a chance to catch up)

[Funkybot]

Speaking of catching up...big updates to the Change Log:

https://github.com/GeoffAWaddington/.../CSI-Changelog

Let me know if I missed anything, or something could be made more clear.

Note: I intentionally left out the X32 code updates for now just so users don't get the impression the X32 is now fully supported. Think it's best to hold off on that until it's fully working and we have a set of support files. Will definitely call out all the great work and contributions from jacksoonbrowne at that time! Didn't want you to think I forgot about those updates or your contributions!

[Geoff Waddington]

Originally Posted by Funkybot

Speaking of catching up...big updates to the Change Log:

https://github.com/GeoffAWaddington/.../CSI-Changelog

Let me know if I missed anything, or something could be made more clear.

Note: I intentionally left out the X32 code updates for now just so users don't get the impression the X32 is now fully supported. Think it's best to hold off on that until it's fully working and we have a set of support files. Will definitely call out all the great work and contributions from jacksoonbrowne at that time! Didn't want you to think I forgot about those updates or your contributions!

Great stuff, as always.

Might want to add that AutoScan should only be turned on whilst you actually want to scan, then turned off when you are finished scanning.

[Funkybot]

Originally Posted by Geoff Waddington

Great stuff, as always.

Might want to add that AutoScan should only be turned on whilst you actually want to scan, then turned off when you are finished scanning.

Added!

Just an FYI - at some point, I may create some dummy.fx zones like you did for the UAD plugins and use that to generate additional step files for plugins I haven't mapped yet. I own a silly amount of plugins.

[Freex]

I noticed someone say about encoders being inverted,

Would this be a good time to remind you about adding an option to invert/reverse encoders for those plugins with pesky back to front movements?

On a single encoder in a FXzone, rather than golbally.

[JP_]

Originally Posted by MixMonkey

ZIP up your CSI folder and I'll take a look.

Thanks mate! Since the BankLeft/Right function has now been replaced by RotaryA15 I'd love to know how to get my channel bank/track move functions working again too!

I've managed a workaround by using:
RotaryA15 TrackBank -8
RotaryA16 TrackBank 8

But can't see how to do a left/right twist for -/+ movement on just the one rotary.

I've also noticed that EVERY light now turns off on the button release signal, but when the same function is done with a mouse the lights stay on.

CSI File:
https://www.dropbox.com/s/q6w4y112apyvlx6/CSI.zip?dl=0

[JP_]

Does anyone know how to use the CSI MIDI controllers to trigger actions in reaper? As now we can't use MIDI Learn, how do we do that?

[Cragster]

Hey guys
I posted this a few times on the CSI Help thread and maybe it got missed and or forgotten. Geoff did say he was investigating.

so sorry for posting here but im desperate and about to head back in time to the old CSI before all these new changes.

Whwn i have less tracks in the project then i do on surfaces the scrolling into view stops working. It seems ok when i have more tracks then i have on surfaces. Im using MCU + 2 XTs. I havnt seen anybody posting about this so ill assume its me.

But does anyone have any ideas or suggestions of what this might be ? ive gone over evrything a few times and all seems good.So im stumped

Thanks for any bread crumbs thrown my way.

[Geoff Waddington]

Originally Posted by Cragster

Hey guys
I posted this a few times on the CSI Help thread and maybe it got missed and or forgotten. Geoff did say he was investigating.

so sorry for posting here but im desperate and about to head back in time to the old CSI before all these new changes.

Whwn i have less tracks in the project then i do on surfaces the scrolling into view stops working. It seems ok when i have more tracks then i have on surfaces. Im using MCU + 2 XTs. I havnt seen anybody posting about this so ill assume its me.

But does anyone have any ideas or suggestions of what this might be ? ive gone over evrything a few times and all seems good.So im stumped

Thanks for any bread crumbs thrown my way.

Sorry I haven't gotten to this, been super busy here.

I think MixMonkey has a similar setup, hopefully he'll chime in.

[Puck]

Originally Posted by JP_

Does anyone know how to use the CSI MIDI controllers to trigger actions in reaper? As now we can't use MIDI Learn, how do we do that?

Normally in your buttons zone you would do something like this:

Button1 Reaper "40454"    
Button2 Reaper "_0e5b196e7f67994bab6de09c49f05926"    
Button3 Reaper "_SWSTL_SHOWALL"

Widget name, then Reaper, then the action_ID in quotes.

[Funkybot]

Originally Posted by Puck

Normally in your buttons zone you would do something like this:

Button1 Reaper "40454"    
Button2 Reaper "_0e5b196e7f67994bab6de09c49f05926"    
Button3 Reaper "_SWSTL_SHOWALL"

Widget name, then Reaper, then the action_ID in quotes.

Yes. But the quotes are unnecessary and we’re trying to encourage against the unnecessary characters just to avoid any extra clutter. They do still work of course.

[MixMonkey]

Originally Posted by JP_

Hey man! I'm actually having some issues! The LED panning lights don't match the track panning in Reaper

Get rid of this from your Track Zone:

RotaryA|    TrackPan

...as you also have:

RotaryA|    MCUTrackPan

..and the select buttons turn the light off when you remove your finger from them.

Can't see anything for this one. Do the mute/solo/record arm buttons behave the same way? If they don't, try swapping the assignment to see if the fault follows it.

[JP_]

Originally Posted by MixMonkey

Get rid of this from your Track Zone:

RotaryA|    TrackPan

...as you also have:

RotaryA|    MCUTrackPan

Can't see anything for this one. Do the mute/solo/record arm buttons behave the same way? If they don't, try swapping the assignment to see if the fault follows it.

They do behave the same way, everything lights up when clicked with a mouse and turns off if I use the button to do the same thing, but only on the release signal.

Removing the line you suggested didn't fix the LED unfortunately, it also stopped the track panning, so I need to delete the MCU version instead. it worked before in MCU mode though.

Originally Posted by Puck

Normally in your buttons zone you would do something like this:

Button1 Reaper "40454"    
Button2 Reaper "_0e5b196e7f67994bab6de09c49f05926"    
Button3 Reaper "_SWSTL_SHOWALL"

Widget name, then Reaper, then the action_ID in quotes.

Brilliant thanks!

[MixMonkey]

Originally Posted by JP_

I've also noticed that EVERY light now turns off on the button release signal, but when the same function is done with a mouse the lights stay on.

If you quit Reaper, with the X-Touch Compact still attached and turned on, do the buttons on surface turn the lights on and off?

[Funkybot]

Originally Posted by JP_

They do behave the same way, everything lights up when clicked with a mouse and turns off if I use the button to do the same thing, but only on the release signal.

Removing the line you suggested didn't fix the LED unfortunately, it also stopped the track panning, so I need to delete the MCU version instead. it worked before in MCU mode though.

MCUTrackPan was depreciated so that went away. That's why it's not working. It's been replaced with TrackPanAutoLeft/TrackPanAutoRight and the ToggleChannel/Toggle modifier. See below.

Try this as your new Track.zon...

Zone "Track"
    DisplayUpper|               TrackNameDisplay
    FaderA|Touch+DisplayLower|  TrackVolumeDisplay
    DisplayLower|               TrackPanAutoLeftDisplay
    Toggle+DisplayLower|        TrackPanAutoRightDisplay
    Shift+DisplayLower|         TrackAutoModeDisplay
    
    VUMeter|                    TrackOutputMeterMaxPeakLR
    
    FaderA|                     TrackVolume 
    
    RotaryPush|                 ToggleChannel    
    RotaryA|                    TrackPanAutoLeft
    RotaryA|                    WidgetMode Dot
    Toggle+RotaryA|             TrackPanAutoRight
    Toggle+RotaryA|             WidgetMode Dot    
    
    ButtonA_A|                  TrackSolo
    ButtonB_A|                  TrackMute
    ButtonC_A|                  TrackUniqueSelect
    ButtonD_A|                  TrackRecordArm
    Shift+ButtonD_A|            CycleTrackAutoMode    
      
    Select|                     TrackToggleVCASpill
    Shift+Select|               TrackRangeSelect
    Control+Select|             TrackSelect
ZoneEnd

...does that fix the Pan issue?

Also, you have ButtonC_A assigned to TrackUniqueSelect instead of the Select button, which you have assigned to TrackToggleVCASpill. That may be causing the button weirdness. If that's not intentional, you may even want to try this instead...

Zone "Track"
    DisplayUpper|               TrackNameDisplay
    FaderA|Touch+DisplayLower|  TrackVolumeDisplay
    DisplayLower|               TrackPanAutoLeftDisplay
    Toggle+DisplayLower|        TrackPanAutoRightDisplay
    Shift+DisplayLower|         TrackAutoModeDisplay
    
    VUMeter|                    TrackOutputMeterMaxPeakLR
    
    FaderA|                     TrackVolume 
    
    RotaryPush|                 ToggleChannel    
    RotaryA|                    TrackPanAutoLeft
    RotaryA|                    WidgetMode Dot
    Toggle+RotaryA|             TrackPanAutoRight
    Toggle+RotaryA|             WidgetMode Dot    
    
    ButtonA_A|                  TrackSolo
    ButtonB_A|                  TrackMute
    ButtonC_A|                  TrackToggleVCASpill
    ButtonD_A|                  TrackRecordArm
    Shift+ButtonD_A|            CycleTrackAutoMode    
      
    Select|                     TrackUniqueSelect
    Shift+Select|               TrackRangeSelect
    Control+Select|             TrackSelect
ZoneEnd

[MixMonkey]

Originally Posted by JP_

Removing the line you suggested didn't fix the LED unfortunately, it also stopped the track panning, so I need to delete the MCU version instead. it worked before in MCU mode though.

Yes, sorry, my bad MCUTrackPan was removed. TrackPan should still work though and there's a whole new auto mode as well when you're ready

EDIT: I see @funkybot has laid out the auto mode for you

[Geoff Waddington]

Originally Posted by Cragster

Hey guys
I posted this a few times on the CSI Help thread and maybe it got missed and or forgotten. Geoff did say he was investigating.

so sorry for posting here but im desperate and about to head back in time to the old CSI before all these new changes.

Whwn i have less tracks in the project then i do on surfaces the scrolling into view stops working. It seems ok when i have more tracks then i have on surfaces. Im using MCU + 2 XTs. I havnt seen anybody posting about this so ill assume its me.

But does anyone have any ideas or suggestions of what this might be ? ive gone over evrything a few times and all seems good.So im stumped

Thanks for any bread crumbs thrown my way.

Ok, got a moment now.

If you have less Tracks in the project than you have channels on your combined surfaces, what is there to scroll ?

I must be misunderstanding something here.

Or do you have a very tiny TCP/MCP Window ?

[Cragster]

Originally Posted by Geoff Waddington

Sorry I haven't gotten to this, been super busy here.

I think MixMonkey has a similar setup, hopefully he'll chime in.

Thanks Geoff. No worries i know you busy

Mix monkey i think you have the same setup as me with the MCUs.. Are you having any issues with selecting a track and not scrolling to the track and put it in view when there are less tracks in the project then on the surfaces ?

Sry guys this is just driving me batty lol. if you have any ideas thank you

[Cragster]

Originally Posted by Geoff Waddington

Ok, got a moment now.

If you have less Tracks in the project than you have channels on your combined surfaces, what is there to scroll ?

I must be misunderstanding something here.

Or do you have a very tiny TCP/MCP Window ?

I have MCU + 2 XTs .so 24 tracks..
in the project now i have 21 tracks so they all are not in view on the screen.

[Cragster]

Originally Posted by Geoff Waddington

Ok, got a moment now.

If you have less Tracks in the project than you have channels on your combined surfaces, what is there to scroll ?

I must be misunderstanding something here.

Or do you have a very tiny TCP/MCP Window ?

Sso if i select say track 18 on the surface which is not in view on the screen it doesnt scroll to it. it always did before.

if i have more then 24 tracks it seems to work fine

[Geoff Waddington]

Originally Posted by Funkybot

MCUTrackPan was depreciated so that went away.

Thanks for reminding me to be super nit-picky

I keep forgetting to mention this every time I see it on the Wiki, shows how important it is in the grand scheme of things

Still... it's Deprecated, not Depreciated.

I know, I know, I just can't help myself

[JP_]

Originally Posted by MixMonkey

If you quit Reaper, with the X-Touch Compact still attached and turned on, do the buttons on surface turn the lights on and off?

Same behaviour, push = light on, release = light off

Originally Posted by Funkybot

Try this as your new Track.zon...

Zone "Track"
    DisplayUpper|               TrackNameDisplay
    FaderA|Touch+DisplayLower|  TrackVolumeDisplay
    DisplayLower|               TrackPanAutoLeftDisplay
    Toggle+DisplayLower|        TrackPanAutoRightDisplay
    Shift+DisplayLower|         TrackAutoModeDisplay
    
    VUMeter|                    TrackOutputMeterMaxPeakLR
    
    FaderA|                     TrackVolume 
    
    RotaryPush|                 ToggleChannel    
    RotaryA|                    TrackPanAutoLeft
    RotaryA|                    WidgetMode Dot
    Toggle+RotaryA|             TrackPanAutoRight
    Toggle+RotaryA|             WidgetMode Dot    
    
    ButtonA_A|                  TrackSolo
    ButtonB_A|                  TrackMute
    ButtonC_A|                  TrackUniqueSelect
    ButtonD_A|                  TrackRecordArm
    Shift+ButtonD_A|            CycleTrackAutoMode    
      
    Select|                     TrackToggleVCASpill
    Shift+Select|               TrackRangeSelect
    Control+Select|             TrackSelect
ZoneEnd

...does that fix the Pan issue?

It doesn't, the LEDs still don't line up

Originally Posted by Funkybot

Also, you have ButtonC_A assigned to TrackUniqueSelect instead of the Select button,

That's because that IS the select button, "select" isn't a widget anymore, it's replaced by the new name. The rotary toggle works to swap between pan/width, but what is "auto" mode?

[Geoff Waddington]

Originally Posted by Cragster

Sso if i select say track 18 on the surface which is not in view on the screen it doesnt scroll to it. it always did before.

if i have more then 24 tracks it seems to work fine

Ok, so you have a very small Window when this happens, is that what you are saying ?

I think most folks have a larger TCP/MCP window, that's probably why it hasn't been mentioned.

I'll have a look tomorrow.

Oh wait, please post your CSI.ini file contents, you might be missing a new option.

[Cragster]

Originally Posted by Geoff Waddington

Ok, so you have a very small Window when this happens, is that what you are saying ?

I think most folks have a larger TCP/MCP window, that's probably why it hasn't been mentioned.

I'll have a look tomorrow.

Oh wait, please post your CSI.ini file contents, you might be missing a new option.

if your meaning my screen ? i have 2 screens. one views TCP/edit
the other views the MCP/mixer.
it always worked before ..if it wasnt on screen it would scroll to it.

And thanks Geoff i really appreciate it. i know you busy with the new CSI stuff.Ill check back tmr hopfully get it sorted

[Cragster]

Originally Posted by Geoff Waddington

Ok, so you have a very small Window when this happens, is that what you are saying ?

I think most folks have a larger TCP/MCP window, that's probably why it hasn't been mentioned.

I'll have a look tomorrow.

Oh wait, please post your CSI.ini file contents, you might be missing a new option.

Version 2.0

NoAutoScan

MidiSurface "MCUXT" 3 4 
MidiSurface "MCUXT2" 2 3 
MidiSurface "MCU" 1 2 
MidiSurface "PlatformM" 5 6 
MidiSurface "PlatformB" 7 8 
MidiSurface "PlatformB2" 11 11 
MidiSurface "C4" 4 5 
OSCSurface "iPad C4" 8000 9000 192.168.1.205
OSCSurface "Phone Remote" 8001 9001 192.168.1.186

Page "Home" UseScrollLink 
"MCUXT" 8 0 "MCU_XT.mst" "MCUXT" 
"MCUXT2" 8 8 "MCU_XT.mst" "MCUXT" 
"MCU" 8 16 "MCU.mst" "MCU" 
"PlatformM" 8 0 "QconPlatformM.mst" "PlatformM" 
"PlatformB" 0 0 "QconPlatformB.mst" "PlatformB" 
"PlatformB2" 0 0 "QconPlatformB2.mst" "PlatformB_2" 
"C4" 24 0 "C4.mst" "C4" 
"iPad C4" 8 0 "iPad_C4.ost" "iPad_C4" 
"Phone Remote" 1 0 "CSIPhoneRemote.ost" "CSIPhoneRemote"

[Puck]

Originally Posted by Funkybot

Yes. But the quotes are unnecessary and we’re trying to encourage against the unnecessary characters just to avoid any extra clutter. They do still work of course.

Thanks FB!

I do recall that now. I Pulled these from the Wiki, just so ya know.

[MixMonkey]

Originally Posted by JP_

Same behaviour, push = light on, release = light off

I see. Humour me, switch to MC mode and see if the behaviour changes (without Reaper running)

[MixMonkey]

Originally Posted by JP_

but what is "auto" mode?

Auto mode makes the surface follow the pan mode set in Reaper on a per channel basis. It can only use the 'Dot' Widget mode though. So you can Toggle between pan and width, pan Left and pan right etc.

[Funkybot]

Originally Posted by Geoff Waddington

Thanks for reminding me to be super nit-picky

I keep forgetting to mention this every time I see it on the Wiki, shows how important it is in the grand scheme of things

Still... it's Deprecated, not Depreciated.

I know, I know, I just can't help myself

I always thought of it as...

Depreciate is to remove value from something. Which is what removing a feature does, removes its value by removing it's function.

Deprecate means to disapprove of or belittle. We didn't make the feature feel bad about itself, we removed it.

...but the grammar police on the internet disagree with my thinking. So even though they're wrong about other people being wrong, I will begin to use deprecated on the wiki.

[MixMonkey]

Originally Posted by Cragster

Sso if i select say track 18 on the surface which is not in view on the screen it doesnt scroll to it. it always did before.

if i have more then 24 tracks it seems to work fine

I can confirm this happens. If I have 33 tracks, the onscreen mixer will always scroll to the selected track if it is off screen.

As far as I can tell, the last surface has to be more than half full or the screen won't follow.

Regarding the screen setup that might require this, some people like to have a single mixer channel strip to the left or right of the TCP (mixer docked to side) This strip follows whichever track is selected in the TCP (or surface, ideally).

Is there any particular reason why creating a bunch of dummy tracks to fill out the surfaces isn't an option?

[Geoff Waddington]

Originally Posted by Funkybot

I always thought of it as...

Depreciate is to remove value from something. Which is what removing a feature does, removes its value by removing it's function.

Deprecate means to disapprove of or belittle. We didn't make the feature feel bad about itself, we removed it.

...but the grammar police on the internet disagree with my thinking. So even though they're wrong about other people being wrong, I will begin to use deprecated on the wiki.

You are 100% right, deprecate means to disapprove of or belittle.

Then, somehow, the software world hijacked it to mean -- "Will not be supported, no further development on this feature, will likely be removed in the future".

So in the software world, deprecated now means a feature that will be removed soon, better not to use it.

What we really should say in most of the Wiki cases is "Removed", at least I think so

If we say "Depreciated", it seems to imply it is still there, just lessened somehow, but, in fact, it is now completely gone.

At least, that's my 2c.

[MixMonkey]

Originally Posted by Funkybot

I always thought of it as...

Depreciate is to remove value from something. Which is what removing a feature does, removes its value by removing it's function.

Deprecate means to disapprove of or belittle. We didn't make the feature feel bad about itself, we removed it.

...but the grammar police on the internet disagree with my thinking. So even though they're wrong about other people being wrong, I will begin to use deprecated on the wiki.

Both words mean the same thing and are interchangeable. However, the software world has plumped for "deprecated" as the term for redundant, removed, superceded or replaced features. So I guess, in time, the words will start to mean different things.

Language, it's all basically slang in the end (I can feel my 3rd form English teacher spinning in his grave about now)

EDIT: I see Geoff beat me to it

[JP_]

Originally Posted by MixMonkey

I see. Humour me, switch to MC mode and see if the behaviour changes (without Reaper running)

no lights, on startup, press, whatever, none at all.

[Geoff Waddington]

Originally Posted by MixMonkey

Both words mean the same thing and are interchangeable. However, the software world has plumped for "deprecated" as the term for redundant, removed, superceded or replaced features. So I guess, in time, the words will start to mean different things.

Language, it's all basically slang in the end (I can feel my 3rd form English teacher spinning in his grave about now)

Yup, I say we use "Removed" in order to remove all doubt.

[Funkybot]

Will switch to removed on the wiki.

[Cragster]

Originally Posted by MixMonkey

I can confirm this happens. If I have 33 tracks, the onscreen mixer will always scroll to the selected track if it is off screen.

As far as I can tell, the last surface has to be more than half full or the screen won't follow.

Regarding the screen setup that might require this, some people like to have a single mixer channel strip to the left or right of the TCP (mixer docked to side) This strip follows whichever track is selected in the TCP (or surface, ideally).

Is there any particular reason why creating a bunch of dummy tracks to fill out the surfaces isn't an option?

OK thanks
It always worked before so I was thinking maybe something wrong or I set up the new build wrong.
I'll just deal with it or head back to the older build.
Thanks for you all help

[MixMonkey]

Originally Posted by JP_

no lights, on startup, press, whatever, none at all.

That's as it should be. I'm afraid it rather looks like the native mode of the X-Touch Compact enables some kind of local control of the LEDs. I hope I'm wrong.

[MixMonkey]

I'm not having any luck with this:

AssignmentDisplay    GlobalModeDisplay

All I get in the AssignmentDisplay is "SE" when changing between Track, VCA and Folder modes.

Did anything else change that might affect it?

[jacksoonbrowne]

Hi Geoff,

Ok, just to get my testing started on the new X32 heartbeat code encapsulation as you suggested.
I added the changes you mentioned, but this piece of code fails to compile:

void ControlSurface::RequestUpdate()
{
....

    if (GetName().find("X32") != string::npos || GetName().find("x32") != string::npos)
        surfaceIO->SendX32HeartBeat();
....
}

..... 'surfaceIO': undeclared identifier


Am getting brain fog now, any thoughts?

[Geoff Waddington]

Originally Posted by MixMonkey

I'm not having any luck with this:

AssignmentDisplay    GlobalModeDisplay

All I get in the AssignmentDisplay is "SE" when changing between Track, VCA and Folder modes.

Did anything else change that might affect it?

Yup, back on September 11.

GlobalModeDisplay now displays "SE" for Selected and "GL" for Global.

It displays the state of the Global modifier.

This was done as part of the work (your suggestion I think) that now that VCA and Folders are Associated Zones, they are radio buttons, just like all the other Associated Zones.

Here is the X-Touch buttons Zone excerpt:

//  Encoder Assign Buttons

    Track                       GoHome
    Track                       Reaper _S&M_WNCLS4          // Closes all(!) FX chain windows
    Track                       Reaper _S&M_WNCLS3          // Closes all(!) floating FX windows  
    Pan                         GoVCA
    EQ                          GoFolder
    Send                        GoSelectedTrackSend
    Global+Send                 GoTrackSend
    Plugin                      GoSelectedTrackFXMenu
    Global+Plugin               GoTrackFXMenu
    Instrument                  GoSelectedTrackReceive
    Global+Instrument           GoTrackReceive

// Automation Buttons

    Read                        TrackAutoMode 1
    Write                       TrackAutoMode 3
    Trim                        TrackAutoMode 0
    Touch                       TrackAutoMode 2
    Latch                       TrackAutoMode 4
    Group                       TrackAutoMode 5
    Global+Read                 GlobalAutoMode 1
    Global+Write                GlobalAutoMode 3
    Global+Trim                 GlobalAutoMode 0
    Global+Touch                GlobalAutoMode 2
    Global+Latch                GlobalAutoMode 4  
    Global+Group                GlobalAutoMode 5