Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by MixMonkey

Works very nicely here Title bar changes when different FX are focused (the window itself is blank, but that's correct yes?). It would be good if the window could remember its size. It's going to be a pain dragging it out to see the last two channels everytime...

Great !

The Window remembers its size and position for an open project here, does it not there ?

As far as the initial size upon project load, that will be calculated based on:

Zone FXRowLayout
	Channels 8
...

When I finish the coding

[MixMonkey]

Originally Posted by Geoff Waddington

The Window remembers its size and position for an open project here, does it not there ?

Actually it seems to have something to do with the column widths changing. When I open the window initially, I can see 6 columns. So I drag the window out to show all 8. The next time I open the window, the size an position seem the same , but the column widths have changed and now I can only see 6 columns again. Not something to worry about now

As far as the initial size upon project load, that will be calculated based on:

Zone FXRowLayout
	Channels 8
...

When I finish the coding

This will probably solve it

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Primitive implementation demo for Windows.

If you thought the resize was ugly on Mac, just wait until you see the Windows version

Ignore that and concentrate on the title bar.

You must focus an FX before you press the button mapped to LearnFocusedFX.

Then you can focus another FX and you should see the Learn Window title bar reflect the change.

You can also press the Edit Alias button to change the Alias.

That's all for now

Just want to confirm the workflow.

[Freex]

Originally Posted by Geoff Waddington

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Primitive implementation demo for Windows.

If you thought the resize was ugly on Mac, just wait until you see the Windows version

Ignore that and concentrate on the title bar.

You must focus an FX before you press the button mapped to LearnFocusedFX.

Then you can focus another FX and you should see the Learn Window title bar reflect the change.

You can also press the Edit Alias button to change the Alias.

That's all for now

Just want to confirm the workflow.

Can confirm window opens and title bar changes as expected when switching FX


I don't have any of the "Learn" zones setup on my system as up until now, manual editing has seemed faster,
Looks l;ike im gonna have to add them

[jacksoonbrowne]

Hey Geoff,

How can I get the "action context" when I am in either of these:

class X32_Fader_OSC_MessageGenerator : public CSIMessageGenerator
class OSC_X32FaderFeedbackProcessor  : public OSC_FeedbackProcessor

Cheers,
Roy

[Geoff Waddington]

Just an FYI, the following Zones will be in a folder named Learn, cleans up the main Zone folder:

FXEpilogue.zon
FXPrologue.zon
FXRowLayout.zon
FXWidgetLayout.zon
LearnFocusedFX.zon

[MT4U]

Originally Posted by Geoff Waddington

Just an FYI, the following Zones will be in a folder named Learn, cleans up the main Zone folder:

FXEpilogue.zon
FXPrologue.zon
FXRowLayout.zon
FXWidgetLayout.zon
LearnFocusedFX.zon

Great

[jacksoonbrowne]

Hi Geoff,

Code changes to make X32 Track Select (the odd X32 OSC message ) to be more robust.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
class OSC_X32IntFeedbackProcessor : public OSC_IntFeedbackProcessor
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
{
public:
    OSC_X32IntFeedbackProcessor(CSurfIntegrator *const csi, OSC_ControlSurface *surface, Widget *widget, const char *oscAddress) : OSC_IntFeedbackProcessor(csi, surface, widget, oscAddress) {}
    ~OSC_X32IntFeedbackProcessor() {}

    virtual const char *GetName() override { return "OSC_X32IntFeedbackProcessor"; }
    
    virtual void ForceValue(const PropertyList &properties, double value) override
    {
        lastDoubleValue_ = value;
        
        if (oscAddress_.find("/-stat/selidx/") != string::npos  && value != 0.0)
        {
            string selectIndex = oscAddress_.substr(oscAddress_.find_last_of('/') + 1);
            surface_->SendOSCMessage(this, "/-stat/selidx", (int)atoi(selectIndex .c_str()));
        }
        else
            surface_->SendOSCMessage(this, oscAddress_.c_str(), (int)value);
    }
};

[Geoff Waddington]

Originally Posted by jacksoonbrowne

Hi Geoff,

Code changes to make X32 Track Select (the odd X32 OSC message ) to be more robust.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
class OSC_X32IntFeedbackProcessor : public OSC_IntFeedbackProcessor
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
{
public:
    OSC_X32IntFeedbackProcessor(CSurfIntegrator *const csi, OSC_ControlSurface *surface, Widget *widget, const char *oscAddress) : OSC_IntFeedbackProcessor(csi, surface, widget, oscAddress) {}
    ~OSC_X32IntFeedbackProcessor() {}

    virtual const char *GetName() override { return "OSC_X32IntFeedbackProcessor"; }
    
    virtual void ForceValue(const PropertyList &properties, double value) override
    {
        lastDoubleValue_ = value;
        
        if (oscAddress_.find("/-stat/selidx/") != string::npos  && value != 0.0)
        {
            string selectIndex = oscAddress_.substr(oscAddress_.find_last_of('/') + 1);
            surface_->SendOSCMessage(this, "/-stat/selidx", (int)atoi(selectIndex .c_str()));
        }
        else
            surface_->SendOSCMessage(this, oscAddress_.c_str(), (int)value);
    }
};

Thanks, will be in next commit.

[Geoff Waddington]

CSI has close to 8 years of bloat and cobwebs.

Part of the Reaper inclusion exercise aims to improve that situation.

First off, don't worry, we won't be changing the FX zones, folks have a lot of those, but they are relatively straightforward, no Included Zones, no Associated Zones, just the possibility of a SubZone or two.

If you saw the code for parsing Zones you would either get dizzy or sick to your stomach, or both

Which leads to the following.

I'm proposing some fairly substantial changes to what we now call Included and Associated Zones.

Keep in mind, this is mostly relatively hard coded stuff that gets distributed in the CSI folder, most folks won't ever modify it.

1) Do we really need a separate Buttons zone, seems like it should just be part of the Home definition.

2) Consider this Zone for Learn:

Zone FXRowLayout
	Channels 8
	"" ""
	"Shift" ""
	"Control" ""
	"Option" ""
ZoneEnd

This is metadata for generating/editing FX Zones.

We could apply the same technique to Associated Zones, which really should be called radio button Zones, since they are mutually exclusive:

Zone RadioButton
        Home
       	SelectedTracks
       	SelectedTrackSend
       	SelectedTrackReceive
       	SelectedTrackFXMenu
       	MasterTrackFXMenu
       	TrackSend
       	TrackReceive
       	TrackFXMenu
       	VCA
       	Folder
       	SelectedTrackTCPFX
       	SelectedTrackTCPFXTemplate
	CustomAux
	CustomBuses
	CustomOutputs
	CustomLayoutSmallCompressor
ZoneEnd

This approach allows a lot more freedom in defining what was previously an Associated Zone, and there would be no need for the "Custom" tag we hacked in there.

3) Do any other Zones except Home need Included Zones ?

The only reason Home actually needs these is because a Zone can only have one Navigator -- Track and MasterTrack need their own Navigators.

We could do something like this:

Zone HomeIncluded
	Track
        MasterTrack
ZoneEnd

4) Speaking of track, consider the other metadata Zone for Learn:

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

Notice the the '|' symbol is nowhere to be found.

That's because the 2 metadata files for Learn, when taken together, render that construct redundant.

So a Track file could look like this:

Zone "Track"
    VUMeter                 TrackOutputMeterMaxPeakLR
    DisplayUpper            TrackNameDisplay
    Fader                   TrackVolume 
    Touch+DisplayLower      TrackVolumeDisplay
    Flip+Fader              TrackPan 

    Rotary                  TrackPanAutoLeft RingStyle=Dot   // Pan
    Toggle+Rotary           TrackPanAutoRight RingStyle=Dot  // Width
    DisplayLower            TrackPanAutoLeftDisplay
    Toggle+DisplayLower     TrackPanAutoRightDisplay

    RotaryPush              ToggleChannel
    Control+RotaryPush      TrackPan [ 0.5 ]
    Option+RotaryPush       TrackPanWidth [ 1.0 ]

    ...

    ZoneEnd

What do you think ?

[Funkybot]

Originally Posted by Geoff Waddington

1) Do we really need a separate Buttons zone, seems like it should just be part of the Home definition.

Did we ever really NEED it? I always thought buttons could be defined in the Home zone but we just kept it separate to make things tidier and easier to find. Which makes sense to me. Otherwise, the Home zone can get very scary looking.

Originally Posted by Geoff Waddington

2) Consider this Zone for Learn:

Zone FXRowLayout
	Channels 8
	"" ""
	"Shift" ""
	"Control" ""
	"Option" ""
ZoneEnd

This is metadata for generating/editing FX Zones.

We could apply the same technique to Associated Zones, which really should be called radio button Zones, since they are mutually exclusive:

Zone RadioButton
        Home
       	SelectedTracks
       	SelectedTrackSend
       	SelectedTrackReceive
       	SelectedTrackFXMenu
       	MasterTrackFXMenu
       	TrackSend
       	TrackReceive
       	TrackFXMenu
       	VCA
       	Folder
       	SelectedTrackTCPFX
       	SelectedTrackTCPFXTemplate
	CustomAux
	CustomBuses
	CustomOutputs
	CustomLayoutSmallCompressor
ZoneEnd

This approach allows a lot more freedom in defining what was previously an Associated Zone, and there would be no need for the "Custom" tag we hacked in there.

Food for thought: why do we need the channel count in there at all? It's already defined at the device level in Preferences and in the csi.ini. Why can't CSI just assume if you have an 8 channel surface that it will use 8 channels everywhere? Is anyone defining a different number for FX?

Originally Posted by Geoff Waddington

3) Do any other Zones except Home need Included Zones ?

What about included SubZones? I've only ever called SubZones from either Buttons.zon (which gets covered by custom zones) and FX zones. Nothing else needs IncludedZones. At least, nothing that comes to mind.

Originally Posted by Geoff Waddington

4) Speaking of track, consider the other metadata Zone for Learn:

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

Notice the the '|' symbol is nowhere to be found.

That's because the 2 metadata files for Learn, when taken together, render that construct redundant.

So a Track file could look like this:

Zone "Track"
    VUMeter                 TrackOutputMeterMaxPeakLR
    DisplayUpper            TrackNameDisplay
    Fader                   TrackVolume 
    Touch+DisplayLower      TrackVolumeDisplay
    Flip+Fader              TrackPan 

    Rotary                  TrackPanAutoLeft RingStyle=Dot   // Pan
    Toggle+Rotary           TrackPanAutoRight RingStyle=Dot  // Width
    DisplayLower            TrackPanAutoLeftDisplay
    Toggle+DisplayLower     TrackPanAutoRightDisplay

    RotaryPush              ToggleChannel
    Control+RotaryPush      TrackPan [ 0.5 ]
    Option+RotaryPush       TrackPanWidth [ 1.0 ]

    ...

    ZoneEnd

What do you think ?

What about instances where a user wants to target a particular fader? Easiest example: utilizing Fader1 for FocusedFXParam, then leaving Faders2-8 alone. Would that still be possible?

Lots of "what about" questions in there but just trying to see if there are holes that can be poked into this. Otherwise, what you're proposing works for me!

Hopefully Undark sees this. His setup is much more complex than mine.

[Geoff Waddington]

Originally Posted by Funkybot

Did we ever really NEED it? I always thought buttons could be defined in the Home zone but we just kept it separate to make things tidier and easier to find. Which makes sense to me. Otherwise, the Home zone can get very scary looking.

Well, once we remove Included and Associated Zones, Home would get pretty sparse by itself:

Zone Home
    OnInitialization	ToggleRestrictTextLength 7
    OnInitialization 	ToggleEnableFocusedFXMapping
    OnInitialization    ToggleUseLocalModifiers
    OnInitialization    SetLatchTime 100
ZoneEnd

Originally Posted by Funkybot

Food for thought: why do we need the channel count in there at all? It's already defined at the device level in Preferences and in the csi.ini. Why can't CSI just assume if you have an 8 channel surface that it will use 8 channels everywhere? Is anyone defining a different number for FX?

Sorry, wasn't clear enough.

I am saying the RadioButton Zone replaces the Associated Zones in Home, nothing to do with channel count, but rather, illustrating the use of metadata Zones -- both FXRowLayout and RadioButton are metadata Zones.

[edit] I also see what you mean, will remove:

	Channels 8

from FXRowLayout.

Originally Posted by Funkybot

What about included SubZones? I've only ever called SubZones from either Buttons.zon (which gets covered by custom zones) and FX zones. Nothing else needs IncludedZones. At least, nothing that comes to mind.

Yes, we would keep SubZones.

Originally Posted by Funkybot

What about instances where a user wants to target a particular fader? Easiest example: utilizing Fader1 for FocusedFXParam, then leaving Faders2-8 alone. Would that still be possible?

Lots of "what about" questions in there but just trying to see if there are holes that can be poked into this. Otherwise, what you're proposing works for me!

Hopefully Undark sees this. His setup is much more complex than mine.

Yes, Fader1 is fine in a FocusedFXParam Zone, I'm talking strictly about Zones where wildcards are presently used -- Track, TrackSend, etc.

[MT4U]

Originally Posted by Funkybot

What about included SubZones? I've only ever called SubZones from either Buttons.zon (which gets covered by custom zones) and FX zones. Nothing else needs IncludedZones. At least, nothing that comes to mind.

Same here, I only call SubZones from FX SubZones and the Buttons zones.

[Geoff Waddington]

Originally Posted by MT4U

Same here, I only call SubZones from FX SubZones and the Buttons zones.

Cool, that should work, since Buttons and Home have the same Navigator.

So, you will now be calling SubZones from Home instead of Buttons.

FX SubZones will remain unchanged.

[Geoff Waddington]

One more FYI.

Actions will now provide feedback, unless specifically instructed not to do so.

This only matters if a Widget triggers more than one Action.

SomeWidget AnAction
SomeWidget AnotherAction Feedback=No

I think this is reasonable, since very few folks -- who know what they are doing, mostly -- will be utilizing this feature.

[fourdogslong]

It looks like there will be a lot of major changes, may I respectfully ask why?
I mean, it worked fine before, there are a couple of missing features (like touch+flip showing current value) or things that could be improved (like meters calibration), but did it really need to be changed so much?

Won't that be a lot of trouble to rearrange the whole config that most of us probably spent a lot of time on?

I'm not complaining, I'm just wondering why all the back and forth trying to change the way things work, as they say, if it ain't broke don't fix it.

[Freex]

What about the likes of Scrub, Nudge and Zoom zones.
Subzones (from buttons) so they should still be fine RIGHT?

[Geoff Waddington]

Originally Posted by fourdogslong

It looks like there will be a lot of major changes, may I respectfully ask why?
I mean, it worked fine before, there are a couple of missing features (like touch+flip showing current value) or things that could be improved (like meters calibration), but did it really need to be changed so much?

Won't that be a lot of trouble to rearrange the whole config that most of us probably spent a lot of time on?

I'm not complaining, I'm just wondering why all the back and forth trying to change the way things work, as they say, if it ain't broke don't fix it.

Well, it ain't broke on the outside...

Aiming to improve improve the internal code quality to try and approach the lofty Reaper standard, believe me, it's a good thing

Most configs should only require minor changes.

[Geoff Waddington]

Originally Posted by Freex

What about the likes of Scrub, Nudge and Zoom zones.
Subzones (from buttons) so they should still be fine RIGHT?

Yup

[Funkybot]

Originally Posted by Geoff Waddington

Well, it ain't broke on the outside...

Aiming to improve improve the internal code quality to try and approach the lofty Reaper standard, believe me, it's a good thing

Most configs should only require minor changes.

Part of me kind of hopes that adding CSI to Reaper will eventually mean that there will be no more breaking changes in the future so this will be the last major re-arch of the code. The Reaper team is pretty good about not deprecating functionality unless absolutely needed so if one last cleanup gets us to a point where that becomes the future of CSI, then I'm all for it. But for the love of God, no more after this please! No one's looking at the code but Geoff, Roy, and maybe Justin/Schwa in the future. We just desire working CSI configs that aren't in constant flux. Don't let perfect be the enemy of good and all that jazz.

[Geoff Waddington]

Originally Posted by Funkybot

Part of me kind of hopes that adding CSI to Reaper will eventually mean that there will be no more breaking changes in the future so this will be the last major re-arch of the code. The Reaper team is pretty good about not deprecating functionality unless absolutely needed so if one last cleanup gets us to a point where that becomes the future of CSI, then I'm all for it. But for the love of God, no more after this please! No one's looking at the code but Geoff, Roy, and maybe Justin/Schwa in the future. We just desire working CSI configs that aren't in constant flux. Don't let perfect be the enemy of good and all that jazz.

It won't be included in Reaper until it meets a certain standard, period.

After that, there will be no more breaking changes.

I totally get your frustration, but until the standard is met, it won't get added.

[Funkybot]

I wouldn't even say it's frustration - so apologies if it comes across that way. I look at it as advocacy for not making breaking changes when possible.

It's all intended as being some good-natured food for though/consideration. I totally support and look forward to the new direction and future of CSI, especially being included in Reaper!

[Geoff Waddington]

Originally Posted by Funkybot

I wouldn't even say it's frustration - so apologies if it comes across that way. I look at it as advocacy for not making breaking changes when possible.

It's all intended as being some good-natured food for though/consideration. I totally support and look forward to the new direction and future of CSI, especially being included in Reaper!

Thanks.

Onward Ho !!

[MT4U]

As a developer myself I totally understand (and don't envy ) what Geoff is doing right now. Specially with such a broad use-cases scenario as CSI, that adapts to ANY Surface and workflow.

It's a great time to show our support.

[Geoff Waddington]

Originally Posted by MT4U

As a developer myself I totally understand (and don't envy ) what Geoff is doing right now. Specially with such a broad use-cases scenario as CSI, that adapts to ANY Surface and workflow.

It's a great time to show our support.

Thanks man, appreciate it !

[Geoff Waddington]

It would be a great help if as many folks as possible post their SubZones, and how they call them.

That would ensure I get things right.

Thanks!

[Funkybot]

Originally Posted by MT4U

It's a great time to show our support.

Indeed! Donation sent!

[fourdogslong]

Originally Posted by Geoff Waddington

Well, it ain't broke on the outside...

Aiming to improve improve the internal code quality to try and approach the lofty Reaper standard, believe me, it's a good thing

Most configs should only require minor changes.

I understand, thanks for all the hard work! I`m sure it will be worth it in the end.

[fourdogslong]

Originally Posted by Geoff Waddington

It would be a great help if as many folks as possible post their SubZones, and how they call them.

That would ensure I get things right.

Thanks!

Here are mine:

Mode (this changes what my arrows and jobwheel do)

Zone Mode
    Down                    	Reaper 40111                // Zoom in vertical                                            
  	Up                  		Reaper 40112                // Zoom out vertical                                                       
    Right                  		Reaper 1012                 // Zoom in horizontal                                      
    Left                   		Reaper 1011                 // Zoom out horizontal	
                                      
	Decrease+JogWheel           Reaper 40840                // Move edit cursor back one measure (no seek)  
    Increase+JogWheel           Reaper 40839                // Move edit cursor forward one measure (no seek)  
	
    Shift+Decrease+JogWheel    	Reaper 1011                 // Zoom out horizontal           
    Shift+Increase+JogWheel    	Reaper 1012                 // Zoom in horizontal                
    Option+Decrease+JogWheel    Reaper 40112                // Zoom out vertical   
    Option+Increase+JogWheel    Reaper 40111                // Zoom in vertical   	
	
	Control+Decrease+JogWheel   Reaper _SWS_SCROLL_L10      // SWS: Scroll left 10%
    Control+Increase+JogWheel   Reaper _SWS_SCROLL_R10      // SWS: Scroll right 10%   
    Alt+Decrease+JogWheel       Reaper _XENAKIOS_TVPAGEUP   // Xenakios/SWS: Scroll track view up (page)
    Alt+Increase+JogWheel       Reaper _XENAKIOS_TVPAGEDOWN // Xenakios-SWS: Scroll track view down
     
    Mode		   				LeaveSubZone
ZoneEnd

Scrub zone: (changes the jogwheel navigation behaviour)

Zone Scrub
    Decrease+JogWheel     Reaper 40084                // Rewind a little bit  
    Increase+JogWheel     Reaper 40085                // Forward a little bit    

	Scrub			    LeaveSubZone			
ZoneEnd

FX mode zone (gives me visual feedback for my FX categories on each track, uses the MT4U script)

Zone FXMode
		    
	RotaryPush1		 	    				Reaper _RS4a59873d8a864b25ad252cf47f7bed5a73c17cbf      // MT4U_F_FX4.eel
	Alt+RotaryPush1	 	    				Reaper _RS94d36270a59c05e387a234a4a359347c63cb2273		// MT4U_F_FX4_Add.eel

	RotaryPush2			    				Reaper _RS87571b848a098b379fa88401f9884989becf701c      // MT4U_F_FX5.eel
	Alt+RotaryPush2		    				Reaper _RS5fbaef55bfde55c2ebdd2ba5a7f3ef84e1684df9		// MT4U_F_FX5_Add.eel

	RotaryPush3			    				Reaper _RS3d5b56e2458a161a4e2191dc32c52f5aa9726bd6      // MT4U_F_FX6.eel
	Alt+RotaryPush3		    				Reaper _RSa65abfe8faf42eeffddef53188b1646c7ca9d81d		// MT4U_F_FX6_Add.eel

	RotaryPush4			    				Reaper _RS3a001acbac4ded63ca2187d0290fce88dbc713cc      // MT4U_F_FX7.eel
	Alt+RotaryPush4		    				Reaper _RSa13088123d871028400c1ffeb126af7f58d627d1		// MT4U_F_FX7_Add.eel

	RotaryPush5			    				Reaper _RS81348526f4d175fa6d40bbfcb4051dea643c6ac4      // MT4U_F_FX8.eel
	Alt+RotaryPush5		    				Reaper _RS173b2f63134d8e63d55783518c1b61a328a33751		// MT4U_F_FX8_Add.eel

	RotaryPush6			    				Reaper _RSc761747e39961c41fe2919a6330954754c0dd28d      // MT4U_F_FX9.eel
	Alt+RotaryPush6		    				Reaper _RS3064fad6946f480771ec28ec13eebfce92221b86		// MT4U_F_FX9_Add.eel
	
	RotaryPush7			    				Reaper _RS70deecde9d1768ba2e1fc7c32dbe5e5ebffe02a3      // MT4U_F_FX10.eel
	Alt+RotaryPush7		    				Reaper _RSfd2aee83062555058002371a7cd46ad9f7aff08b		// MT4U_F_FX10_Add.eel
	
	RotaryPush8			    				Reaper _RS46fd31e460a025da8b02d46b4266ad1f4e6db9a6      // MT4U_F_FX11.eel
	Alt+RotaryPush8		    				Reaper _RSdf35b4848af3dc6d07971386f976fffb023c98ca		// MT4U_F_FX11_Add.eel
	
	DisplayUpper1				FixedTextDisplay Inst
	DisplayUpper2				FixedTextDisplay 
	DisplayUpper3				FixedTextDisplay EQ
	DisplayUpper4				FixedTextDisplay 
	DisplayUpper5				FixedTextDisplay 
	DisplayUpper6				FixedTextDisplay 
	DisplayUpper7				FixedTextDisplay Dyn
	DisplayUpper8				FixedTextDisplay Harmo

    DisplayLower1               FixedTextDisplay Correct
    DisplayLower2               FixedTextDisplay FX
    DisplayLower3               FixedTextDisplay Delay
    DisplayLower4               FixedTextDisplay Verb
    DisplayLower5               FixedTextDisplay Utility
    DisplayLower6               FixedTextDisplay Tape
    DisplayLower7               FixedTextDisplay Field
    DisplayLower8               FixedTextDisplay Meters
	



// These lines provide the Prev/Next plug-in for each slot in the chain.

  Alt+Increase+Rotary1        	Reaper _RSc545ff69f595f1cae309546bcdb9179f7429c0e3      // MT4U_FX_MENU_Next_01.eel
  Alt+Increase+Rotary2        	Reaper _RS5439e90ffa8d42ed4c792c6b3a3ea73cf00fba3b      // MT4U_FX_MENU_Next_02.eel
  Alt+Increase+Rotary3	        Reaper _RS68d54e0a0cfd883a7a32300ad232da0b0b014582      // MT4U_FX_MENU_Next_03.eel
  Alt+Increase+Rotary4	        Reaper _RS03d759a19dd784936c0623261989a9d068b506b9      // MT4U_FX_MENU_Next_04.eel
  Alt+Increase+Rotary5	        Reaper _RSb2361f8e123048bd39d7939940b69a1bf42c9548      // MT4U_FX_MENU_Next_05.eel
  Alt+Increase+Rotary6	        Reaper _RS85f1b59aeae81a32fefe19bf6450a0fa211a6481      // MT4U_FX_MENU_Next_06.eel
  Alt+Increase+Rotary7	        Reaper _RSef0d0b1af31dc05cb612426330c91fe07772ba69      // MT4U_FX_MENU_Next_07.eel
  Alt+Increase+Rotary8	        Reaper _RS1f833e289409ee010d55aef22db12d40c2682bbc      // MT4U_FX_MENU_Next_08.eel
  Alt+Decrease+Rotary1	        Reaper _RS94465c3306bb9b3c9d55b8c7178f5ed761470a11      // MT4U_FX_MENU_Prev_01.eel  
  Alt+Decrease+Rotary2	        Reaper _RSa53d4aacb8b072d7a6ab0396a9defe16ad65cdb9      // MT4U_FX_MENU_Prev_02.eel  
  Alt+Decrease+Rotary3	        Reaper _RS074637b1b554af8249c502f39f5ed701aa8f31e9      // MT4U_FX_MENU_Prev_03.eel  
  Alt+Decrease+Rotary4	        Reaper _RS6c27b24ff350d5e37917f5d04efe37a8cbddc3c8      // MT4U_FX_MENU_Prev_04.eel  
  Alt+Decrease+Rotary5	        Reaper _RSe93b961d483b93912ed350205563a80bf3d1ca4f      // MT4U_FX_MENU_Prev_05.eel  
  Alt+Decrease+Rotary6	        Reaper _RSc5afaed8eff8f9fe6fadd2aef6113d8fa8cf64e4      // MT4U_FX_MENU_Prev_06.eel  
  Alt+Decrease+Rotary7	        Reaper _RSebb16895b121c261b4738e73ad6fc42db29f0909      // MT4U_FX_MENU_Prev_07.eel  
  Alt+Decrease+Rotary8	        Reaper _RS8cdd865f8ede7ec4e95a7f433bea329f780d1362      // MT4U_FX_MENU_Prev_08.eel   

// FX Selection. These allow us to select a plug-in, so we can move it up or down whithin the chain.

  RecordArm1          	        Reaper _RS5a050d77bb0db671a322ab6afeea1c473e23922b      // MT4U_FX_MENU_Sel_01.eel
  RecordArm2          	        Reaper _RS943d149b67e3955639628ad3fcba5ecb09ef0a0e      // MT4U_FX_MENU_Sel_02.eel
  RecordArm3          	        Reaper _RS9c174a048d6852aac1146045de404f785820876b      // MT4U_FX_MENU_Sel_03.eel
  RecordArm4          	        Reaper _RSc39ebef0a88dcbbb01c9a266ca09f1086bfd06ad      // MT4U_FX_MENU_Sel_04.eel
  RecordArm5          	        Reaper _RS50b6875f1a9ec9faec87346b6116d0a98007f32f      // MT4U_FX_MENU_Sel_05.eel
  RecordArm6          	        Reaper _RS9cfda924b0efc46db8d57a8bd41e7375304c370e      // MT4U_FX_MENU_Sel_06.eel
  RecordArm7          	        Reaper _RS306c3f85913dbdd73e5ad305d2d2b68d63aebad7      // MT4U_FX_MENU_Sel_07.eel
  RecordArm8          	        Reaper _RS0088ef7ea422f2bb69a043a6065cb578405e4fa0      // MT4U_FX_MENU_Sel_08.eel

// Now the actual plug-in movers.

  Up           		      		Reaper _RS95211454bfbef97e0215b0b918446426978d0014      // Script: MT4U_FX_MENU_MoveUp.eel
  Down           	      		Reaper _RScab515c7031f31eec2ec211302e3ca346798462d      // Script: MT4U_FX_MENU_MoveDown.eel


// To delete a plug-in.

  Hold+RecordArm1             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm2             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm3             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm4             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm5             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm6             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm7             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel
  Hold+RecordArm8             	Reaper _RS6d8c8a3ec1b91ea74ddbe140f8206376b571e630      // MT4U_FX_MENU_Del.eel

  Param			      			LeaveSubZone

ZoneEnd

[MalcolmG]

Originally Posted by Geoff Waddington

Cool, that should work, since Buttons and Home have the same Navigator.

So, you will now be calling SubZones from Home instead of Buttons.

FX SubZones will remain unchanged.

I assume subzones will still be available from Radio Button Zones (like my FX Menu example in the other thread)?


Cheers
Malcolm

[Perken]

Originally Posted by Sonotor

Nobody is able to have CSI on Linux?
It would be so great if someone could do that!
And.... Also be able to install reasons on Linux!
Thanks in advance for helping.

Sorry to be bringing this message from the grave, but I just thought I'd let someone know: CSI works fine for me on linux - at least from the very little I've tested - with my midi fighter.

I just compiled it using the repo's make file, and everything works.
You'll probably need gcc and build tools. Download the github repository, and compile from your terminal:

$ make .

[Freex]

I have

    Output                      GoAssociatedZone MasterTrack

and a MasterTrack.zone

Zone "MasterTrack"
    Fader1               TrackVolume
    Rotary1              TackPan [ (0.005,0.5) ]
    Mute                 TackMute
    Solo                 Reaper 40917                   //Toggle Stereo/Mono
ZoneEnd

for the Faderport Classic, it used to all work, but just noticed that only the Fader and Solo buttons are working as expected now.

Not sure what happened, as they did work at one point.

[MalcolmG]

Originally Posted by Freex

I have

    Output                      GoAssociatedZone MasterTrack

and a MasterTrack.zone

Zone "MasterTrack"
    Fader1               TrackVolume
    Rotary1              TackPan [ (0.005,0.5) ]
    Mute                 TackMute
    Solo                 Reaper 40917                   //Toggle Stereo/Mono
ZoneEnd

for the Faderport Classic, it used to all work, but just noticed that only the Fader and Solo buttons are working as expected now.

Not sure what happened, as they did work at one point.

I noticed Track is spelled incorrectly for Mute and Rotary1. Is that the case in the actual file?


Cheers
Malcolm

[Geoff Waddington]

Originally Posted by MalcolmG

I assume subzones will still be available from Radio Button Zones (like my FX Menu example in the other thread)?


Cheers
Malcolm

Yes, they will.

[Geoff Waddington]

Originally Posted by Perken

Sorry to be bringing this message from the grave, but I just thought I'd let someone know: CSI works fine for me on linux - at least from the very little I've tested - with my midi fighter.

I just compiled it using the repo's make file, and everything works.
You'll probably need gcc and build tools. Download the github repository, and compile from your terminal:

$ make .

Thanks for compiling and testing this !!

The source code is basically non functional right now -- in the midst of some major renovations.

Once they are complete you should be good to go

[Geoff Waddington]

GoAssociatedZone will soon be removed.

Need a name for the Action that replaces it.

It has radio button / mutually exclusive behaviour.

Two candidates:

GoRadioButtonZone
GoMutexZone

Kinda leaning toward GoMutexZone, but is that too geeky ?

Got a better name ?

[Freex]

Originally Posted by MalcolmG

I noticed Track is spelled incorrectly for Mute and Rotary1. Is that the case in the actual file?


Cheers
Malcolm

And now i feel like such an idiot, I'm not even sure how that happened.
I just assumed something had gone awry, as they used to work.

Thanks for being my eyes.

Time for me to get new glasses.....

[MalcolmG]

Originally Posted by Freex

And now i feel like such an idiot

We've all done it before, so don't sweat it :-)

[MalcolmG]

Originally Posted by Geoff Waddington

GoAssociatedZone will soon be removed.

Need a name for the Action that replaces it.

It has radio button / mutually exclusive behaviour.

Two candidates:

GoRadioButtonZone
GoMutexZone

Kinda leaning toward GoMutexZone, but is that too geeky ?

Got a better name ?

Just a thought, I wonder if the mutex-ness is an important distinction to a user? I mean, one scenario could just be to bring back the name GoZone, and the default behaviour is that going to a zone means it's mutually exclusive to those other zones. GoSubZone is the exception, and it's named as such.



Cheers
Malcolm

[Geoff Waddington]

Originally Posted by MalcolmG

Just a thought, I wonder if the mutex-ness is an important distinction to a user? I mean, one scenario could just be to bring back the name GoZone, and the default behaviour is that going to a zone means it's mutually exclusive to those other zones. GoSubZone is the exception, and it's named as such.



Cheers
Malcolm

I like it !

And we could name the metadata file accordingly:

Zone GoZones
    SelectedTracks
    SelectedTrackSend
    SelectedTrackReceive
    SelectedTrackFXMenu
    MasterTrackFXMenu
    TrackSend
    TrackReceive
    TrackFXMenu
    VCA
    Folder
    SelectedTrackTCPFX
    SelectedTrackTCPFXTemplate
    CustomAux
    CustomBuses
    CustomOutputs
    CustomLayoutSmallCompressor
ZoneEnd