Control Surface Integration (CSI) Technical Feature Discussion

[MT4U]

Originally Posted by Funkybot

Other Actions page created:

https://github.com/GeoffAWaddington/.../Other-Actions

This was mostly just consolidating what was already on the wiki into a single page. Note: I've never used the FixedRGBColourDisplay action and couldn't think of a use-case for it so that example is a little matter of fact.

Great, Funkybot. Only thing to point out is that "Redo" says "Undo" (The infamous copy paste devil)

Zone "Buttons"
    Shift+Undo     Undo
ZoneEnd

[Funkybot]

Originally Posted by MT4U

Great, Funkybot. Only thing to point out is that "Redo" says "Undo" (The infamous copy paste devil)

Zone "Buttons"
    Shift+Undo     Undo
ZoneEnd

Thank you very much for noticing and notifying me. Fixed!

[Funkybot]

Made updates to the VCA page to remove the ToggleVCAMode action and cover the new CycleTrackVCAFolderModes and the corresponding display actions:

https://github.com/GeoffAWaddington/...-and-VCA-Spill

Special thanks to MixMonkey for explaining the TrackVCAFolderModeDisplay a few pages back in this thread. I basically plagiarized what he wrote here for that entire section.

[MT4U]

Hi.

Whenever I have some free time I keep improving my FX mapping application (while I keep mapping my VSTs) and I have a question for you CSI wizzards.

When I generate a Zone with stepped parameters, I generate them this way:

[ (1) 0.00 0.13 0.25 0.38 0.50 0.63 0.75 0.88 1.0 ]

It's not mentioned here (https://github.com/GeoffAWaddington/...rs-and-Toggles), but I know that the "(1)" at the begining makes my encoders iterate through the single FX values with every encoder "tick".

Are there any other values other than "(1)" that have any real world use to you?

[Geoff Waddington]

Originally Posted by Funkybot

Made updates to the VCA page to remove the ToggleVCAMode action and cover the new CycleTrackVCAFolderModes and the corresponding display actions:

https://github.com/GeoffAWaddington/...-and-VCA-Spill

Special thanks to MixMonkey for explaining the TrackVCAFolderModeDisplay a few pages back in this thread. I basically plagiarized what he wrote here for that entire section.

Great stuff, as always !

Might want to remove the last line, just checked the code and it looks like only one level of VCA's is supported, unless I'm misreading the code -- it has happened before

Also, for both VCA and folders, when you go into the mode, the Bank/Channel controls bank the VCA spill/child Folder Tracks.

No extra Actions are needed, it is built in.

[Funkybot]

Originally Posted by MT4U

Hi.

Whenever I have some free time I keep improving my FX mapping application (while I keep mapping my VSTs) and I have a question for you CSI wizzards.

When I generate a Zone with stepped parameters, I generate them this way:

[ (1) 0.00 0.13 0.25 0.38 0.50 0.63 0.75 0.88 1.0 ]

It's not mentioned here (https://github.com/GeoffAWaddington/...rs-and-Toggles), but I know that the "(1)" at the begining makes my encoders iterate through the single FX values with every encoder "tick".

Are there any other values other than "(1)" that have any real world use to you?

Just my two cents on that: I think it would be nice if that could be a variable with a global default as it really depends on the encoder sensitivity on the hardware and the preferences of the user. On the MIDI Fighter Twister for example, a value of 1 would be way too sensitive and I'd likely overshoot the value I want. I've gone so far as to use values of 15 or 20. On the SCE24, I think I use values of 3 to 5.

[Funkybot]

Originally Posted by Geoff Waddington

Great stuff, as always !

Might want to remove the last line, just checked the code and it looks like only one level of VCA's is supported, unless I'm misreading the code -- it has happened before

Also, for both VCA and folders, when you go into the mode, the Bank/Channel controls bank the VCA spill/child Folder Tracks.

No extra Actions are needed, it is built in.

Added info!

I'm pretty certain that at one point VCA Spill worked on multiple levels, but I think that was removed (maybe during the 1.1 development cycle). I recall you used to be able to go multiple levels in but then when you tried to go back, you'd end up at the top-level (versus next level up). Rather than remove the line entirely, I just updated the last sentence to call out that VCA Spill only works one-level deep for now. This way if someone tries to spill down into a second level and thinks it's a bug, they'll hopefully see that it's by design.

[Geoff Waddington]

Originally Posted by Funkybot

Added info!

I'm pretty certain that at one point VCA Spill worked on multiple levels, but I think that was removed (maybe during the 1.1 development cycle). I recall you used to be able to go multiple levels in but then when you tried to go back, you'd end up at the top-level (versus next level up). Rather than remove the line entirely, I just updated the last sentence to call out that VCA Spill only works one-level deep for now. This way if someone tries to spill down into a second level and thinks it's a bug, they'll hopefully see that it's by design.

Looks good !

[MixMonkey]

Originally Posted by Geoff Waddington

Might want to remove the last line, just checked the code and it looks like only one level of VCA's is supported, unless I'm misreading the code -- it has happened before

I think you might be I seem to be able to have VCAs within VCAs (ie a VCA leader is also a VCA follower of another VCA leader)

Spilling the followers seems to work fine; I end up with the VCA leaders on the LHS with followers to the right. If one of the followers is also a leader and I spill it, I get the first VCA leader on the LHS (with its followers now hidden) with the newly spilt VCA leader to its right with its followers to its right.

I only got to about three levels down but it all seems to work predictably (actually a lot easier than on screen with Reaper) Un-splilling just reverses the process described above, one level at a time.

[Funkybot]

Originally Posted by MixMonkey

I think you might be I seem to be able to have VCAs within VCAs (ie a VCA leader is also a VCA follower of another VCA leader)

Spilling the followers seems to work fine; I end up with the VCA leaders on the LHS with followers to the right. If one of the followers is also a leader and I spill it, I get the first VCA leader on the LHS (with its followers now hidden) with the newly spilt VCA leader to its right with its followers to its right.

I only got to about three levels down but it all seems to work predictably (actually a lot easier than on screen with Reaper) Un-splilling just reverses the process described above, one level at a time.

So the original Wiki entry WAS right!

I really should just suck it up and ditch the Artist Mix for an X-Touch so I can actually test these things on my own.

[MT4U]

Originally Posted by Funkybot

Just my two cents on that: I think it would be nice if that could be a variable with a global default as it really depends on the encoder sensitivity on the hardware and the preferences of the user. On the MIDI Fighter Twister for example, a value of 1 would be way too sensitive and I'd likely overshoot the value I want. I've gone so far as to use values of 15 or 20. On the SCE24, I think I use values of 3 to 5.

Understood. Great info. Thanks!!!

[Geoff Waddington]

Originally Posted by Funkybot

So the original Wiki entry WAS right!

I really should just suck it up and ditch the Artist Mix for an X-Touch so I can actually test these things on my own.

Make you a deal, you do that if you wish and I'll learn to read my own code

[Geoff Waddington]

Originally Posted by MixMonkey

I think you might be I seem to be able to have VCAs within VCAs (ie a VCA leader is also a VCA follower of another VCA leader)

Spilling the followers seems to work fine; I end up with the VCA leaders on the LHS with followers to the right. If one of the followers is also a leader and I spill it, I get the first VCA leader on the LHS (with its followers now hidden) with the newly spilt VCA leader to its right with its followers to its right.

I only got to about three levels down but it all seems to work predictably (actually a lot easier than on screen with Reaper) Un-splilling just reverses the process described above, one level at a time.

Thanks for correcting my sorry a**

[MixMonkey]

Originally Posted by Geoff Waddington

Thanks for correcting my sorry a**

No worries. There's a lot of features to keep track of these days (and that's a good thing)

EDIT: I'm currently trying to think of a way of replicating it on screen.

[MixMonkey]

Originally Posted by Funkybot

I really should just suck it up and ditch the Artist Mix for an X-Touch so I can actually test these things on my own.

...or you could use my iPad Mixer (it's in the support files) It's good for checking stuff out without having to power up a whole studio to do it

[Funkybot]

Originally Posted by MixMonkey

...or you could use my iPad Mixer (it's in the support files) It's good for checking stuff out without having to power up a whole studio to do it

Trust me, it's just pure laziness on my part and not wanting to flip between OSC templates. I should get better about it.

[Funkybot]

Hi Geoff, sounds like the X-Touch One files are working for folks and can be included in the Support files. I made an update today that includes some troubleshooting notes in the Home.zon in case people run into issues.

[Geoff Waddington]

Originally Posted by Funkybot

Hi Geoff, sounds like the X-Touch One files are working for folks and can be included in the Support files. I made an update today that includes some troubleshooting notes in the Home.zon in case people run into issues.

Done !

[Geoff Waddington]

New support files are up

CSI Support Files.zip

X-Touch_One files added.

[Funkybot]

Just made a quick round of Wiki updates to the Send and Receive pages to list out what each individual action does down at the bottom.

https://github.com/GeoffAWaddington/...iki/Send-Zones

https://github.com/GeoffAWaddington/.../Receive-Zones

Please review for typos, copy/paste errors, and just provide feedback in general.

I think we've now officially got every single CSI documented on the Wiki for the first time ever.

Next up is adding some details around Feedback Processor types and then I think it may be done until new features are added. Unless folks have other thoughts or suggestions of course!

[MixMonkey]

Originally Posted by Funkybot

Just made a quick round of Wiki updates to the Send and Receive pages to list out what each individual action does down at the bottom.

https://github.com/GeoffAWaddington/...iki/Send-Zones

https://github.com/GeoffAWaddington/.../Receive-Zones

Please review for typos, copy/paste errors, and just provide feedback in general.

I think we've now officially got every single CSI documented on the Wiki for the first time ever.

Next up is adding some details around Feedback Processor types and then I think it may be done until new features are added. Unless folks have other thoughts or suggestions of course!

More excellent work! Quick question, are there display Actions that go with:

TrackSend/ReceiveStereoMonoToggle
TrackSend/ReceiveInvertPolarity

..so that their status can be monitored from the surface?

In the same manner as:

TrackSendPrePost
TrackSendPrePostDisplay

[Geoff Waddington]

Originally Posted by Funkybot

Just made a quick round of Wiki updates to the Send and Receive pages to list out what each individual action does down at the bottom.

https://github.com/GeoffAWaddington/...iki/Send-Zones

https://github.com/GeoffAWaddington/.../Receive-Zones

Please review for typos, copy/paste errors, and just provide feedback in general.

I think we've now officially got every single CSI documented on the Wiki for the first time ever.

Next up is adding some details around Feedback Processor types and then I think it may be done until new features are added. Unless folks have other thoughts or suggestions of course!

Looks excellent, as usual !

Had a quick tour through the whole wiki, gotta say it's very close to complete, superb !!

A few loose ends to tie up, but very, very close !

[Funkybot]

There were some references to Eucon on the Virtual Widget page, so I removed those then added examples.

https://github.com/GeoffAWaddington/...irtual-Widgets

[Geoff Waddington]

Originally Posted by Funkybot

There were some references to Eucon on the Virtual Widget page, so I removed those then added examples.

https://github.com/GeoffAWaddington/...irtual-Widgets

Another loose end bites the dust !

[Funkybot]

Originally Posted by Geoff Waddington

Another loose end bites the dust !

I actually had a question pop up while editing this page: is there any restriction saying Virtual Widgets only work in a Home.zon or did we just kind of collectively end up using them that way because it just kind of makes sense to have them there? If the former I can call that out somewhere on the page just to document.

[Geoff Waddington]

Originally Posted by Funkybot

I actually had a question pop up while editing this page: is there any restriction saying Virtual Widgets only work in a Home.zon or did we just kind of collectively end up using them that way because it just kind of makes sense to have them there? If the former I can call that out somewhere on the page just to document.

It's kind of funky

Theoretically, they can be used anywhere, but the Zone must be active when the virtual "trigger" occurs.

For instance, OnInitialization triggers when CSI loads, so Home is the Active Zone at that time.

So, once again, in short, the Zone that contains the virtual Widget must be Active when the trigger occurs.

[themathpotato]

I just got an X-Touch a few days ago (my first control surface (and this is my first post on this forum)) and I've been working hard to improve the X-touch zones files, fixing some bugs, adding missing features eg. there was no function on the jog wheel and I've added zoom and scrub functionality etc., and doing some more complex multipage FX mappings for things like the Waves SSL strip. Hopefully this should be finished in the next few days.

In the meantime, a few questions about VCA:
- There's 3 modes, track, folder and "CA". What is this third mode? All the faders are down and screens are blank when this is selected.

- In folder mode, tracks without subtracks are hidden. For example if I have a drum folder, a guitar folder for L+R, and a bass track, only drum and guitar is shown. Is this intentional and is there a way for tracks that are not folders or inside folders to also be included in this view, as these tracks are on the same hierarchy level as the folders, they just don't happen to contain any subtracks?

[MixMonkey]

Originally Posted by themathpotato

I just got an X-Touch a few days ago (my first control surface (and this is my first post on this forum)) and I've been working hard to improve the X-touch zones files, fixing some bugs, adding missing features eg. there was no function on the jog wheel and I've added zoom and scrub functionality etc., and doing some more complex multipage FX mappings for things like the Waves SSL strip. Hopefully this should be finished in the next few days.

In the meantime, a few questions about VCA:
- There's 3 modes, track, folder and "CA". What is this third mode? All the faders are down and screens are blank when this is selected.

Welcome to the forum!

"CA" is VCA mode. Any tracks that have been included in a group and assigned as VCA leaders will appear in this mode. The leaders can be "spilt" to show their followers, to the right of the leader.

- In folder mode, tracks without subtracks are hidden. For example if I have a drum folder, a guitar folder for L+R, and a bass track, only drum and guitar is shown. Is this intentional and is there a way for tracks that are not folders or inside folders to also be included in this view, as these tracks are on the same hierarchy level as the folders, they just don't happen to contain any subtracks?

Only tracks that are folder tracks are shown in folder mode. This is intentional.

[sanmiguel]

To Geoff or Funkybot - can you please let me know where I can find SCE24.mst? Thanks

[themathpotato]

I've attached my improved files for the X-Touch, fixing bugs and adding missing key features. Full changes and additions below:



Added 26 new vst mappings including multipage Waves SSL Channel (dynamics page, EQ page, settings page, pushing encoders located near switches on the UI toggles the nearby switches which are also all found on the settings page).
Added zoom and scub zones, toggling zoom allows zooming rather than scrolling with the directional buttons, toggling scrub changes whether the jog wheel scrolls continuously or snapped to the grid.


Changes to original Geoff Waddington support files:

Buttons.zon:
Added zoom and scub zones
Removed line "GlobalView _S&M_TOGLFXCHAIN" as I want all fx windows to close when GlobalView is pressed.
Added the following lines:
Hold+Rewind Reaper "40042" // Go to start of project
Hold+FastForward Reaper "40043" // Go to end of project
JogWheelRotaryCW Reaper "40647" // Move cursor right to grid division
JogWheelRotaryCCW Reaper "40646" // Move cursor left to grid division
Left Reaper "40140" // Scroll view left
Right Reaper "40141" // Scroll view right
Up Reaper "40138" // Scroll view up
Down Reaper "40139" // Scroll view down


Marker.zon:
Added functionality to F1-F8 buttons mapping to go to markers 1-8.

SelectedTrackFXMenu.zon:
Added "RotaryPush| Reaper "_S&M_FLOATFX|"" so that the relevant FX window is opened when selected (only works for first 8 FX on a track, maybe this can be extended with banks somehow)

Removed this line on SelectedTrackFXMenu.zon and TrackFXMenu.zon: "Fader| NoAction"

[themathpotato]

I'll also upload the Waves SSL zones separately here because they serve as another nice example of using FX Subzones.

[Geoff Waddington]

Originally Posted by themathpotato

I've attached my improved files for the X-Touch, fixing bugs and adding missing key features. Full changes and additions below:

Cool, thanks for the contribution, curious as to what bugs you found, didn't see any mention of them in the rest of your post, maybe I missed them.

[Funkybot]

Originally Posted by sanmiguel

To Geoff or Funkybot - can you please let me know where I can find SCE24.mst? Thanks

Here are my SCE-24 including the .mst and a few hundred fx.zon's.

https://www.dropbox.com/s/hfbbz2i8xu...SI_v2.zip?dl=0

As always, feel free to customize as needed. And if you have any suggestions, improvements, etc., I'm all ears!

[themathpotato]

Originally Posted by Geoff Waddington

curious as to what bugs you found

I was assuming this line:

GlobalView       Reaper _S&M_TOGLFXCHAIN

on buttons.zon was intended to perform the functionality as with adding

RotaryPush| Reaper "_S&M_FLOATFX|"

on SelectedTrackFXMenu.zon, but maybe that's wrong, I couldn't quite understand what the purpose of the former line was.

Also what is the syntax with "quotation marks" on actions, it seems to work with and without, is there a difference?.

[fr33sp1r1t]

I have a quick question:-

Is there any reason in the X-Touch.mst file why

Widget Rewind
	Press 90 5b 7f 90 5b 00
	FB_TwoState 90 5b 00 90 5b 00
WidgetEnd

Widget FastForward
	Press 90 5c 7f 90 5c 00
	FB_TwoState 90 5c 00 90 5c 00
WidgetEnd

Does not have the 7f in the FB_TwoState code as in

Widget Rewind
	Press 90 5b 7f 90 5b 00
	FB_TwoState 90 5b 7f 90 5b 00
WidgetEnd

Widget FastForward
	Press 90 5c 7f 90 5c 00
	FB_TwoState 90 5c 7f 90 5c 00
WidgetEnd

as then it gives feedback/lights up when you Fast Forward/Rewind?

[MixMonkey]

Originally Posted by fr33sp1r1t

I have a quick question:-

Is there any reason in the X-Touch.mst file why

Widget Rewind
	Press 90 5b 7f 90 5b 00
	FB_TwoState 90 5b 00 90 5b 00
WidgetEnd

Widget FastForward
	Press 90 5c 7f 90 5c 00
	FB_TwoState 90 5c 00 90 5c 00
WidgetEnd

Does not have the 7f in the FB_TwoState code as in

Widget Rewind
	Press 90 5b 7f 90 5b 00
	FB_TwoState 90 5b 7f 90 5b 00
WidgetEnd

Widget FastForward
	Press 90 5c 7f 90 5c 00
	FB_TwoState 90 5c 7f 90 5c 00
WidgetEnd

as then it gives feedback/lights up when you Fast Forward/Rewind?

Oops! My bad Cut'n'paste error when I was adding the button feedback to the X-Touch.mst. Probably the reason that Geoff couldn't get his FFWD/REW buttons to light up when we were working on the new FFWD/REW functionality.

Prime example of why you shouldn't work on files for surfaces you don't own. Apologies all round

[MT4U]

Originally Posted by Funkybot

Here are my SCE-24 including the .mst and a few hundred fx.zon's.

https://www.dropbox.com/s/hfbbz2i8xu...SI_v2.zip?dl=0

As always, feel free to customize as needed. And if you have any suggestions, improvements, etc., I'm all ears!

Hi there Funkybot.

I'm working on "Importing" existing FX configurations in my application, and was checking other people's FX zones to do some testing and your files made me think again about the stepped parameters.

In your zones you use something like this:

RtrA1 FXParam 0 [ (0.001,0.001,0.01,0.05,0.1,0.15,0.25,0.5) ]
RtrPushA1 NoAction

I usually generate stepped parameters like this:

Rotary2 FXParam 1 [ 0.0 0.05 0.11 0.16 0.21 0.26 0.32 0.37 0.42 0.47 0.53 0.58 0.63 0.68 0.74 0.79 0.84 0.89 0.95 1.0 ]

and if I want to configure my rotary steps I would use something like:

Rotary2 FXParam 1 [ (1) 0.0 0.05 0.11 0.16 0.21 0.26 0.32 0.37 0.42 0.47 0.53 0.58 0.63 0.68 0.74 0.79 0.84 0.89 0.95 1.0 ]

Could you please explain what does the [ (0.001,0.001,0.01,0.05,0.1,0.15,0.25,0.5) ] syntax mean?

Thank you very much!

[Geoff Waddington]

Originally Posted by themathpotato

I was assuming this line:

GlobalView       Reaper _S&M_TOGLFXCHAIN

on buttons.zon was intended to perform the functionality as with adding

RotaryPush| Reaper "_S&M_FLOATFX|"

on SelectedTrackFXMenu.zon, but maybe that's wrong, I couldn't quite understand what the purpose of the former line was.

Also what is the syntax with "quotation marks" on actions, it seems to work with and without, is there a difference?.

I honestly forget that one, went to look it up and SWS extensions are gone in my system, just upgraded Reaper to 6.64 and OS to 12.5, the SWS dylib will no longer drop into the folder

Anyone remember this one ?

As far as quotes, they're optional as long as the parameter has no spaces, so it's generally good practice to use them.

[Geoff Waddington]

New support files build is up.

CSI Support Files.zip

Fixed X-Touch.mst Rewind and FastForward feedback processor definitions.

Thanks fr33sp1r1t !

[Funkybot]

Originally Posted by MT4U

Hi there Funkybot.

I'm working on "Importing" existing FX configurations in my application, and was checking other people's FX zones to do some testing and your files made me think again about the stepped parameters.

In your zones you use something like this:

RtrA1 FXParam 0 [ (0.001,0.001,0.01,0.05,0.1,0.15,0.25,0.5) ]
RtrPushA1 NoAction

I usually generate stepped parameters like this:

Rotary2 FXParam 1 [ 0.0 0.05 0.11 0.16 0.21 0.26 0.32 0.37 0.42 0.47 0.53 0.58 0.63 0.68 0.74 0.79 0.84 0.89 0.95 1.0 ]

and if I want to configure my rotary steps I would use something like:

Rotary2 FXParam 1 [ (1) 0.0 0.05 0.11 0.16 0.21 0.26 0.32 0.37 0.42 0.47 0.53 0.58 0.63 0.68 0.74 0.79 0.84 0.89 0.95 1.0 ]

Could you please explain what does the [ (0.001,0.001,0.01,0.05,0.1,0.15,0.25,0.5) ] syntax mean?

Thank you very much!

Those aren't parameter steps, that's encoder acceleration.