Control Surface Integration (CSI) Technical Feature Discussion

[fourdogslong]

Originally Posted by Geoff Waddington

Please post a Zone that does this.

Here's one that was made with the non experimental csi version using learn.
There's no parameter mapped to it but in the old csi all display looked blank which is what I wanted, now they don't.

Zone "VST3: A-Console (Sonimus)" "A-Console" "Generated by Learn"

#Begin auto generated section
	Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




#End auto generated section
ZoneEnd

[fourdogslong]

Originally Posted by Geoff Waddington

How would you tell CSI to Learn if you don't use a button ?

Maybe it could be a reaper action associated to a key command. Thing is my controller is already pretty maxed out button wise. It's no big deal I'll find a way.

[Geoff Waddington]

Originally Posted by jacksoonbrowne

Geoff,

"class SendOSCMessage : public Action" method "void Do(ActionContext *context, double value)

Is broken.

original code:

    void Do(ActionContext *context, double value) override
    {
        if (value == 0.0) return; // ignore button releases
        
        string_list tokens;
        GetTokens(tokens, context->GetStringParam());

        if (tokens.size() != 2)
            return;
        
        const char *t1 = tokens.get(1), *t1e = NULL;
        if (strstr(t1,"."))
        {
            const double dv = strtod(t1, (char **)&t1e);
            if (t1e && t1e != t1 && !*t1e)
            {
                context->GetSurface()->SendOSCMessage(tokens[0].c_str(), dv);
                return;
            }
        }
        else if (*t1)
        {
            const int v = (int)strtol(t1, (char **)&t1e, 10);
            if (t1e && *t1e)
            {
                context->GetSurface()->SendOSCMessage(tokens[0].c_str(), v);
                return;
            }
        }

        context->GetSurface()->SendOSCMessage(tokens[0].c_str(), tokens[1].c_str());
    }

I have tested the code below and suggest it makes into the new build

    void Do(ActionContext *context, double value) override
    {
        if (value == 0.0) return; // ignore button releases
        
        string_list tokens;
        GetTokens(tokens, context->GetStringParam());

        if (tokens.size() != 2)
            return;
        
        const char *t0  = tokens.get(0);
        const char *t1  = tokens.get(1);
        const char *t1e = NULL;


        // ---- WHEN A STRING -----
        if (isalpha(t1[0]))
        {
            context->GetSurface()->SendOSCMessage(tokens[0].c_str(), tokens[1].c_str());
                return;
        }

        // ---- WHEN A FLOAT
        if (isdigit(t1[0]) && strstr(t1,"."))
        {
            const double dv = strtod(t1, (char **)&t1e);
            if (t1e && t1e!=t1)
            {
                context->GetSurface()->SendOSCMessage(tokens[0].c_str(), dv);
                return;
            }
        }

        // ---- WHEN AN INTEGER -----
        if (isdigit(t1[0])  &&  !strstr(t1,"."))
        {
            const int iv = (int)strtol(t1, (char **)&t1e, 10);
            if (t1e && t1e!=t1)
            {
                context->GetSurface()->SendOSCMessage(tokens[0].c_str(), iv);
                return;
            }
        }
    }

Looks like that wouldn't work with negative numbers or a string that starts with '-'.

Does the original work for any type, or are they all broken ?

[Geoff Waddington]

Originally Posted by fourdogslong

Here's one that was made with the non experimental csi version using learn.
There's no parameter mapped to it but in the old csi all display looked blank which is what I wanted, now they don't.

Zone "VST3: A-Console (Sonimus)" "A-Console" "Generated by Learn"

#Begin auto generated section
	Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Shift+Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Shift+RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush1	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush2	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush3	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush4	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush5	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush6	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush7	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




	Option+Rotary8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction

	Option+RotaryPush8	NoAction
	NullDisplay	NoAction
	NullDisplay	NoAction




#End auto generated section
ZoneEnd

Ah, looks like you've exposed a bug in Learn in the non experimental version.

What happens if you use the latest Exp and Learn ?

Please post the results here.

[Geoff Waddington]

Originally Posted by fourdogslong

Maybe it could be a reaper action associated to a key command. Thing is my controller is already pretty maxed out button wise. It's no big deal I'll find a way.

Which control surface do you have ?

[Geoff Waddington]

Can someone who uses Focused FX frequently verify that CSI now properly loses focus when you still have the FX open but click on another Window, thereby causing the FX Window to lose focus ?

Thanks.

[fourdogslong]

Originally Posted by Geoff Waddington

Can someone who uses Focused FX frequently verify that CSI now properly loses focus when you still have the FX open but click on another Window, thereby causing the FX Window to lose focus ?

Thanks.

I'll test this in a bit.

[fourdogslong]

Originally Posted by Geoff Waddington

Which control surface do you have ?

SSL Nucleus 2

[Geoff Waddington]

Originally Posted by fourdogslong

SSL Nucleus 2

Does it have modifier keys (Shift, Alt, etc.) ?

[Edit] I see it does have modifiers. You can use combinations like Shift+Alt+Option, etc., for less used functions like Learn. Do the modifiers have lights ? If so you can latch the modifiers and tell at a glance which mode you are in.

[fourdogslong]

Originally Posted by Geoff Waddington

Does it have modifier keys (Shift, Alt, etc.) ?

[Edit] I see it does have modifiers. You can use combinations like Shift+Alt+Option, etc., for less used functions like Learn. Do the modifiers have lights ? If so you can latch the modifiers and tell at a glance which mode you are in.

Yes it has modifiers with lights but they do not latch, the ssl cpu doesn't allow it.
I'll figure something out.

[fourdogslong]

Originally Posted by Geoff Waddington

Can someone who uses Focused FX frequently verify that CSI now properly loses focus when you still have the FX open but click on another Window, thereby causing the FX Window to lose focus ?

Thanks.

I just tested this and it seems to work! I can focus from one fx to another with no issue and if I click somewhere else in Reaper the FX focus clears properly. That's great!

[fourdogslong]

Originally Posted by Geoff Waddington

No, instead there are 2 Actions:

LearnFocusedFXParams
SaveLearnedFXParams

Just assign a button to each.

Is there a use for the LearnFXParams zone file now with these new actions?
EDIT: nevermind, I guess I can put the new actions in that zone.

[Geoff Waddington]

Originally Posted by fourdogslong

Yes it has modifiers with lights but they do not latch, the ssl cpu doesn't allow it.
I'll figure something out.

Not quite sure what you mean.

As long as the modifiers send both press and release messages, CSI should be able to make them latch.

[Geoff Waddington]

Originally Posted by fourdogslong

Is there a use for the LearnFXParams zone file now with these new actions?
EDIT: nevermind, I guess I can put the new actions in that zone.

You need a button for LearnFocusedFXParams which will activate the LearnFXParams Zone, and yes, SaveLearnedFXParams and EraseLastTouchedControl belong in the LearnFXParams Zone.

[Geoff Waddington]

Originally Posted by fourdogslong

I just tested this and it seems to work! I can focus from one fx to another with no issue and if I click somewhere else in Reaper the FX focus clears properly. That's great!

Excellent, thanks for testing !

[fourdogslong]

Originally Posted by Geoff Waddington

Not quite sure what you mean.

As long as the modifiers send both press and release messages, CSI should be able to make them latch.

I know it should, but after many exchanges with SSL tech support I got confirmation that these and some other buttons too, are not allowed to latch, that's how it is.

[fourdogslong]

Originally Posted by Geoff Waddington

You need a button for LearnFocusedFXParams which will activate the LearnFXParams Zone, and yes, SaveLearnedFXParams and EraseLastTouchedControl belong in the LearnFXParams Zone.

Got it, but I'm running into some issues.

First, when I go in learn zone, the plugin window closes, I have to open it again manually, but this isn't new to this release, it was like that in the official release too.

Then, after I reopened the FX gui, all my display are still showing whatever was there before, they should all be empty.

In Learn mode, my Rotary push still send what I assigned to them in my track zone. So if I try to assign a Rotary Push to an FX param, it also triggers the action assigned to it in my track zone.

Once I'm done Learning and test the result, I see that anything I didn't assign to an FX param, still triggers whatever is assigned in my track zone and any display not assigned still shows track name and so on.

I don't know if it's a bug or by design, but imo when in Learn and then in an FX zone, all controls and display should by default have NoAction assigned to them unless told otherwise.
If I have a plugin with only 4 parameters, I want my other 12 display to be blank and other rotaries to be inactive, otherwise it's very confusing.

[Geoff Waddington]

Originally Posted by fourdogslong

I know it should, but after many exchanges with SSL tech support I got confirmation that these and some other buttons too, are not allowed to latch, that's how it is.

I think there is a miscommunication here.

The SSL buttons do not need to latch.

The CSI software takes care of that.

If you tap a modifier button quickly it should latch.

Press and hold, then release, to unlatch.

The SSL internals are not involved at all, other than press and release messages.

Unless I'm missing something they are doing internally in the SSL.

[MixMonkey]

Originally Posted by fourdogslong

Then, after I reopened the FX gui, all my display are still showing whatever was there before, they should all be empty.

Does your LearnFXParameters Zone "NoAction" all the unused Widgets?

[Geoff Waddington]

Originally Posted by fourdogslong

Then, after I reopened the FX gui, all my display are still showing whatever was there before, they should all be empty.

I don't know if it's a bug or by design, but imo when in Learn and then in an FX zone, all controls and display should by default have NoAction assigned to them unless told otherwise.
If I have a plugin with only 4 parameters, I want my other 12 display to be blank and other rotaries to be inactive, otherwise it's very confusing.

Ok, let's tackle this one firsrt.

You need to upgrade your LearnFXParams Zone to look similar to this (it will vary based on your control surface):

Zone "LearnFXParams"
    OnZoneActivation	SetXTouchDisplayColors Cyan 
    OnZoneDeactivation  RestoreXTouchDisplayColors
    Instrument		SaveLearnedFXParams
    User                EraseLastTouchedControl

    Rotary1		NoAction
    Fader1   		NoAction
    RotaryPush1		NoAction
    DisplayUpper1       NoAction
    DisplayLower1	NoAction

    Rotary2		NoAction
    Fader2   		NoAction
    RotaryPush2		NoAction
    DisplayUpper2       NoAction
    DisplayLower2	NoAction

    Rotary3		NoAction
    Fader3   		NoAction
    RotaryPush3		NoAction
    DisplayUpper3       NoAction
    DisplayLower3	NoAction

    Rotary4		NoAction
    Fader4   		NoAction
    RotaryPush4		NoAction
    DisplayUpper4       NoAction
    DisplayLower4	NoAction

    Rotary5		NoAction
    Fader5   		NoAction
    RotaryPush5		NoAction
    DisplayUpper5       NoAction
    DisplayLower5	NoAction

    Rotary6		NoAction
    Fader6   		NoAction
    RotaryPush6		NoAction
    DisplayUpper6       NoAction
    DisplayLower6	NoAction

    Rotary7		NoAction
    Fader7   		NoAction
    RotaryPush7		NoAction
    DisplayUpper7       NoAction
    DisplayLower7	NoAction

    Rotary8		NoAction
    Fader8   		NoAction
    RotaryPush8		NoAction
    DisplayUpper8       NoAction
    DisplayLower8	NoAction
ZoneEnd

[Edit] crosspost, thanks MM, yup, that's the ticket.

[fourdogslong]

Originally Posted by Geoff Waddington

I think there is a miscommunication here.

The SSL buttons do not need to latch.

The CSI software takes care of that.

If you tap a modifier button quickly it should latch.

Press and hold, then release, to unlatch.

The SSL internals are not involved at all, other than press and release messages.

Unless I'm missing something they are doing internally in the SSL.

I know it sounds like it should but it does not.
The latch feature works, but the led does not stay lit. Modifiers and F keys do not, SSL confirmed it and I tried really hard to make them stay lit but they don't, all other buttons allow for it but not these unfortunately.

EDIT: For the Learn zone, I used the assignment display to show "Ln" so I know I'm in that mode, works fine.

[fourdogslong]

Originally Posted by Geoff Waddington

Ok, let's tackle this one firsrt.

You need to upgrade your LearnFXParams Zone to look similar to this (it will vary based on your control surface):

Zone "LearnFXParams"
    OnZoneActivation	SetXTouchDisplayColors Cyan 
    OnZoneDeactivation  RestoreXTouchDisplayColors
    Instrument		SaveLearnedFXParams
    User                EraseLastTouchedControl

    Rotary1		NoAction
    Fader1   		NoAction
    RotaryPush1		NoAction
    DisplayUpper1       NoAction
    DisplayLower1	NoAction

    Rotary2		NoAction
    Fader2   		NoAction
    RotaryPush2		NoAction
    DisplayUpper2       NoAction
    DisplayLower2	NoAction

    Rotary3		NoAction
    Fader3   		NoAction
    RotaryPush3		NoAction
    DisplayUpper3       NoAction
    DisplayLower3	NoAction

    Rotary4		NoAction
    Fader4   		NoAction
    RotaryPush4		NoAction
    DisplayUpper4       NoAction
    DisplayLower4	NoAction

    Rotary5		NoAction
    Fader5   		NoAction
    RotaryPush5		NoAction
    DisplayUpper5       NoAction
    DisplayLower5	NoAction

    Rotary6		NoAction
    Fader6   		NoAction
    RotaryPush6		NoAction
    DisplayUpper6       NoAction
    DisplayLower6	NoAction

    Rotary7		NoAction
    Fader7   		NoAction
    RotaryPush7		NoAction
    DisplayUpper7       NoAction
    DisplayLower7	NoAction

    Rotary8		NoAction
    Fader8   		NoAction
    RotaryPush8		NoAction
    DisplayUpper8       NoAction
    DisplayLower8	NoAction
ZoneEnd

[Edit] crosspost, thanks MM, yup, that's the ticket.

Yes, after I posted my message that's what I ended up doing for the Rotary Push, I'll do the same for the Display and all that, thanks.
With the old version it worked without these lines.

[Geoff Waddington]

Originally Posted by fourdogslong

I know it sounds like it should but it does not.
The latch feature works, but the led does not stay lit. Modifiers and F keys do not, SSL confirmed it and I tried really hard to make them stay lit but they don't, all other buttons allow for it but not these unfortunately.

Unfortunate, Console1 has some issues like this, where they tried to make the surface too "smart"

Originally Posted by fourdogslong

EDIT: For the Learn zone, I used the assignment display to show "Ln" so I know I'm in that mode, works fine.

Excellent workaround !

[Geoff Waddington]

Originally Posted by fourdogslong

With the old version it worked without these lines.

That's because the old version used FXLayouts.zon and SurfaceFXLayout.zon.

The new Learn is much simpler and more direct, take a look at the Zones it generates.

[Geoff Waddington]

New Exp build is up.

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

All internal code now uses the new Focused FX approach.

[fourdogslong]

Originally Posted by Geoff Waddington

Excellent workaround !

Thanks to you for making it accessible!

Originally Posted by Geoff Waddington

The new Learn is much simpler and more direct, take a look at the Zones it generates.

I see, is there a way to make "Learn" automatically write no action on everything in the resulting FX zone unless told otherwise?

Or is there a suggested workflow to accomplish something similar?

[Geoff Waddington]

Originally Posted by fourdogslong

I see, is there a way to make "Learn" automatically write no action on everything in the resulting FX zone unless told otherwise?

Not right now, but that is a great feature request !

[Funkybot]

I'll try to play around with the FocusedFX in the next few days. I could see myself using them again if the unfocus piece of the puzzle is solved. That sounds like awesome news!

[jakeman19]

Originally Posted by Geoff Waddington

What is Plugin by itself mapped to ?

Plugin GoAssociatedZone TrackFXMenu

Jd

[Geoff Waddington]

Originally Posted by jakeman19

Plugin GoAssociatedZone TrackFXMenu

Jd

Ok, in case you didn't know, that will always execute before the Hold Action.

That may be unrelated to your issue though.

What if you GoHome before pressing Plugin, does it work then ?

[Geoff Waddington]

Originally Posted by Funkybot

I'll try to play around with the FocusedFX in the next few days. I could see myself using them again if the unfocus piece of the puzzle is solved. That sounds like awesome news!

Please do put it through its paces.

[jakeman19]

Originally Posted by Geoff Waddington

New Exp build is up.

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

All internal code now uses the new Focused FX approach.

Geoff,

The Focus FX seems to work as expected. When switching to other Reaper Windows, MCU doesn't layout FX until you Focus on that plugin window, it then lays out on the MCU again. I believe this was the intent.

Although the "Plugin GoAssociatedZone TrackFXMenu" stays on the same FX(feedback light is lit now), pushing it a second time makes the MCU "GoHome", and pushing again then goes to TrackFXMenu" and "Hold+Plugin GoAssociatedZone SelectedTrackFXMenu" just stays on the same FX when pushed & held of course.

Jd

Edit: Cross Post while typing this out. Will test what you posted.

[jakeman19]

Originally Posted by Geoff Waddington

Ok, in case you didn't know, that will always execute before the Hold Action.

That may be unrelated to your issue though.

What if you GoHome before pressing Plugin, does it work then ?

So if I was to go like this just for testing

Hold+Plugin            GoAssociatedZone TrackFXMenu
Plugin			GoAssociatedZone SelectedTrackFXMenu

you'd think it would work, but it doesn't. It stays on the mapped out FX and no menu is displayed.

Could this be an issue with being in Selected Track Mode other than Global Mode? I'm in Selected Track mode during all this testing by the way.

Jd

[Geoff Waddington]

Originally Posted by jakeman19

So if I was to go like this just for testing

Hold+Plugin            GoAssociatedZone TrackFXMenu
Plugin			GoAssociatedZone SelectedTrackFXMenu

you'd think it would work, but it doesn't. It stays on the mapped out FX and no menu is displayed.

Could this be an issue with being in Selected Track Mode other than Global Mode? I'm in Selected Track mode during all this testing by the way.

Jd

Ok, just to be clear, when you Press Plugin you will go to SelectedTrackMenu no matter what order the statements appear in the Zone definition.

To be as responsive as possible CSI always executes on press.

So, if you hold the Plugin button, CSI will first go to SelectedTrackMenu and then it will go to TrackFXMenu.

Don't know why you would want to set it up like that.

Please explain the rationale.

[jakeman19]

Originally Posted by Geoff Waddington

Ok, just to be clear, when you Press Plugin you will go to SelectedTrackMenu no matter what order the statements appear in the Zone definition.

To be as responsive as possible CSI always executes on press.

So, if you hold the Plugin button, CSI will first go to SelectedTrackMenu and then it will go to TrackFXMenu.

Don't know why you would want to set it up like that.

Please explain the rationale.

Geoff, with my Buttons setup as per the code listed and a plugin window open and focused, it DOESN'T go first to SelectTrackMenu.
I had this setup this way before we had Select Track Mode and Global Mode and it's become muscle memory. If I have to change that, so be it.


EDIT: Ideally I'd like to not have to use the mouse all that often durning mixing and use the MCU & now my Rocksolid Audio Micro4k. So getting to the next plugin to control is ideal of course.

Jd

[MT4U]

Originally Posted by Geoff Waddington

New Exp build is up.

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

All internal code now uses the new Focused FX approach.

Focused FX is working OK now with plug-ins within FX Containers, gotta do some more testing on the unfocusing behaviour, but looks promising.

In the Extender+X-Touch config the Extender's encoders don't work. They get feedback alright if I move a parameter on the FX GUI, but spinning the encoders does nothing.

Faders and buttons (including RotaryPress) work as expected. Extender is first in config, same FX-SubZones work OK with non-EXP version.

Version 3.0

MidiSurface "X-TouchXT" 11 12 15 
MidiSurface "X-Touch" 9 8 15 
MidiSurface "X-Touch_One" 7 11 15 

Page "HomePage" UseScrollLink UseScrollSynch
	"X-TouchXT" 8 0 "X-TouchXT.mst" "X-TouchXT" "X-TouchXT"
	"X-Touch" 8 8 "X-Touch.mst" "X-Touch" "X-Touch"
	"X-Touch_One" 8 16 "X-Touch_One.mst" "X-Touch_One" "X-Touch_One"

	Broadcaster "X-Touch"
		Listener "X-Touch" "GoHome Sends Receives FocusedFX FocusedFXParam FXMenu SelectedTrackFX Custom "
		Listener "X-TouchXT" "GoHome Sends Receives FocusedFX FocusedFXParam FXMenu SelectedTrackFX Custom "

	Broadcaster "X-TouchXT"
		Listener "X-TouchXT" "GoHome Sends Receives FocusedFX FocusedFXParam FXMenu SelectedTrackFX Custom "
		Listener "X-Touch" "GoHome Sends Receives FocusedFX FocusedFXParam FXMenu SelectedTrackFX Custom "

[Geoff Waddington]

Originally Posted by jakeman19

Geoff, with my Buttons setup as per the code listed and a plugin window open and focused, it DOESN'T go first to SelectTrackMenu.
I had this setup this way before we had Select Track Mode and Global Mode and it's become muscle memory. If I have to change that, so be it.

Well, I believe it actually does, you just don't see it, because SelectedTrackFXMenu then deactivates when the Hold Action occurs, at least that's what the code says

Originally Posted by jakeman19

EDIT: Ideally I'd like to not have to use the mouse all that often durning mixing and use the MCU & now my Rocksolid Audio Micro4k. So getting to the next plugin to control is ideal of course.

Jd

Do you use the Focused approach at all ?

It might be tricky to get both approaches to coexist.

If you place this in your Home Zone, Focused FX mapping will be disabled, until you toggle it again, that's how it's set up here:

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

[Geoff Waddington]

Originally Posted by MT4U

Focused FX is working OK now with plug-ins within FX Containers, gotta do some more testing on the unfocusing behaviour, but looks promising.

Great news, thanks for testing !

Originally Posted by MT4U

In the Extender+X-Touch config the Extender's encoders don't work. They get feedback alright if I move a parameter on the FX GUI, but spinning the encoders does nothing.

Faders and buttons (including RotaryPress) work as expected. Extender is first in config, same FX-SubZones work OK with non-EXP version.

Are you saying the Encoders don't work in unmapped FX Zones on the Extender in Learn mode ?

[MT4U]

Originally Posted by Geoff Waddington

Great news, thanks for testing !



Are you saying the Encoders don't work in unmapped FX Zones on the Extender in Learn mode ?

Nope. Just a standard Zone that’s working in the non-EXP, same thing in the Track Zone, actually, Pan does not work.

[Geoff Waddington]

Originally Posted by MT4U

Nope. Just a standard Zone that’s working in the non-EXP, same thing in the Track Zone, actually, Pan does not work.

What happens if you remove the Broadcasters/Listeners, can you at least get back to normal ?

Anyone else having extender problems ?