Go Back   Cockos Incorporated Forums > REAPER Forums > MIDI Hardware, Control Surfaces, and OSC

Reply
 
Thread Tools Display Modes
Old 01-28-2023, 01:31 AM   #22121
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
Geoff,

These are my initial test results on the latest Exp build and support files.
Windows 10 - X-Touch(ch. 8-15) + Extender(ch. 0-7)

All 16 tracks are mapped perfectly through the Extender and the X-Touch.
Thanks for testing !

Quote:
Originally Posted by MT4U View Post
With Focused FX Mapping turned On, all surfaces must have the FX-SubZone definition, if the SubZone definition is missing for some FX, you get a C++ Runtime error in Reaper.exe.

This does not happen if I GoFXSlot from the SelectedTrackFXMenu.

If both surfaces have their SubZones, they are both loaded correctly, either through FX focusing or via GoFXSlot on the X-Touch.
Don't know what you mean by SubZones here, please clarify.

Quote:
Originally Posted by MT4U View Post
Then, GoHome takes only the X-Touch back to the track zone. Tried GlobalGoHome but it does nothing.
That's because it's called AllSurfacesGoHome, not GlobalGoHome

Quote:
Originally Posted by MT4U View Post
Something similar occurs with these actions:
Code:
GoAssociatedZone SelectedTrackSend 
GoAssociatedZone SelectedTrackFXMenu
GoAssociatedZone SelectedTrackReceive
They show the first 8 on the X-Touch displays while extender shows no change whatsoever.
Fixed, will be in next build.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 05:47 AM   #22122
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

BREAKING CHANGE BREAKING CHANGE BREAKING CHANGE BREAKING CHANGE

New build is up.

CSI Support Files.zip

CSI Exp.zip

Fix for GoAssociatedZone bug.

Renamed FXPreamble to FXPrologue.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 05:52 AM   #22123
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
Thanks for testing !



Don't know what you mean by SubZones here, please clarify.

Sorry I was not clear enough. I meant the FX Zone Definition file(s) for the focused plug-in. In any of the surfaces has no FX Zone definition for the focused plug-in, then comes the C++ runtime error in reaper.exe.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 06:07 AM   #22124
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
Sorry I was not clear enough. I meant the FX Zone Definition file(s) for the focused plug-in. In any of the surfaces has no FX Zone definition for the focused plug-in, then comes the C++ runtime error in reaper.exe.
Hmmm...

Not seeing that here.

I thought maybe it had something to do with the Template file, so I removed it.

With no Template file, no FX Zone gets auto generated, but there is no crash.

If there is a Template file, the Zone is auto generated.

Can you provide some more detail, if possible.

Is it a particular plugin ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 06:36 AM   #22125
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Just had a look at the new TouchOSC.

They have added a lot, including scripting.

I had a look, based on MM's request to add back the numbers for the FXTemplate.

I also have anticipation of some issues with Sends, Receives, etc. now that they can span Surfaces.

Way back when, CSI had the capability to set number of Channels, Sends, Receives, FX, etc. separately.

It was all very arcane and confusing, but much more flexible.

Wondering if it time to revisit the concept.

CSI could query the Surface for these values.

In the case of an MCU family device, the number would come back 8, for all queries.

However, for OSC devices this could vary, depending on how the interface was designed.

This has implications for FX auto generation, and it also has implications now that Sends, etc. can span devices.

Let's use a silly example where we have an MCU Extender, and OSC iPad, and an MCU.

Let's say we can come up with a way to query the OSC device for number of Sends, and let's say it returns 4.

CSI can now auto layout the Sends properly.

1 - 8 on the MCU Extender
9 - 12 on the iPad
13 - 20 on the MCU

Of course, with banking, this can be extended past 20, but it would keep the relative relationships working perfectly.

Any TouchOSC wizards out there know if this is possible ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 06:38 AM   #22126
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
Hmmm...

Not seeing that here.

I thought maybe it had something to do with the Template file, so I removed it.

With no Template file, no FX Zone gets auto generated, but there is no crash.

If there is a Template file, the Zone is auto generated.

Can you provide some more detail, if possible.

Is it a particular plugin ?
I tried with some plug-ins. If I delete the plug-in FxZone in any surface I get the crash.

In particular, I have an XTouch one I use as a button repository and never map FX there. If I add a dummy FX Zone for the plug-in there, everything works fine. Then I removed the XTOne from my config and got the same result with the extender if it had no FXZone for the focused plug-in.

Anyway, I’ll upgrade to the latest build, remove the template and try to isolate it a lil bit more.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 07:15 AM   #22127
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
BREAKING CHANGE BREAKING CHANGE BREAKING CHANGE BREAKING CHANGE

New build is up.

CSI Support Files.zip

CSI Exp.zip

Fix for GoAssociatedZone bug.

Renamed FXPreamble to FXPrologue.
GoAssociatedZone now maps Sends/Receives/FXMenu in the X-Touch and the Extender. Sends/Receives/etc. are shown in the X-Touch and mirrored in the Extender.

In the FXMenu, GoFXSlot works from any of them and maps everything OK on both.

I could prevent the Reaper crash adding this:
Code:
    OnInitialization ToggleAutoFXMapping
    OnInitialization ToggleAutoFocusedFXMapping
to every surface, so I believe it is related to AutoFX.
[/code]
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 07:24 AM   #22128
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
GoAssociatedZone now maps Sends/Receives/FXMenu in the X-Touch and the Extender. Sends/Receives/etc. are shown in the X-Touch and mirrored in the Extender.
When you say mirrors, you mean the same info is displayed on both ?

I think this gets to the points I was making a few posts back.

Quote:
Originally Posted by MT4U View Post
In the FXMenu, GoFXSlot works from any of them and maps everything OK on both.
Excellent !

Quote:
Originally Posted by MT4U View Post
I could prevent the Reaper crash adding this:
Code:
    OnInitialization ToggleAutoFXMapping
    OnInitialization ToggleAutoFocusedFXMapping
to every surface, so I believe it is related to AutoFX.
Do you need both ToggleAutoFXMapping and ToggleAutoFocusedFXMapping to prevent the crash ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 07:39 AM   #22129
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
When you say mirrors, you mean the same info is displayed on both ?
Exactly

Quote:
Do you need both ToggleAutoFXMapping and ToggleAutoFocusedFXMapping to prevent the crash ?
This is enough to prevent he crash:
Code:
    OnInitialization ToggleAutoFocusedFXMapping
which is logical, since the crash only occurs when focusing an FX.
Having the FXTemplates on the X-Touch or removing it makes no difference.

On a side note, regarding AutoMapping.

I've been mapping plug-ins generating FX Zones with my GUI app, but even with a lot of tools to help me, some plug-ins still take a lot of time determining the function of each parameter from their names, etc...

Then... testing CSI AutoFX Mapping and seeing where it's going, you got me to rethink the whole FX Mapping paradigm.

I'm thinking of defining FX Zones and SubZones independently from the Surfaces involved.

Let's say we have some kind of previous Plug-In base of knowledge where we catalogue those FX parameters and classify them. Think of a Synthesizer, we could have the FX Pre-Analyzed, saying something like "This is OSC 1 frequency, this is Waveform, this is Filter 1 Cut-Off, etc..."

Then, after the we are done analyzing the Plug-In, we could say "Well, let's map this plugin over this 2 or three surfaces" First give me the Oscilators, then the Filter, then the Amp, etc... in this order, creating either SubZones or modifiers, or both.

Suppose next year I'm lucky enough to get my hands on an SCE24, reconfiguring my FX Zones could be a bliss even after changing my gear.

I'm even pondering the idea of some Machine Learning to help in determining a parameter function based on the FX Type, previous FX mappings of FXs of the same type and whatever name the developers have assigned to their FX Parameters.

Well... just spilling my ideas here.

Will keep testing the latest build, this thing gets even more awesome every day.

Thanks Geoff!
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 07:45 AM   #22130
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
Exactly



This is enough to prevent he crash:
Code:
    OnInitialization ToggleAutoFocusedFXMapping
which is logical, since the crash only occurs when focusing an FX.
Having the FXTemplates on the X-Touch or removing it makes no difference.

On a side note, regarding AutoMapping.

I've been mapping plug-ins generating FX Zones with my GUI app, but even with a lot of tools to help me, some plug-ins still take a lot of time determining the function of each parameter from their names, etc...

Then... testing CSI AutoFX Mapping and seeing where it's going, you got me to rethink the whole FX Mapping paradigm.

I'm thinking of defining FX Zones and SubZones independently from the Surfaces involved.

Let's say we have some kind of previous Plug-In base of knowledge where we catalogue those FX parameters and classify them. Think of a Synthesizer, we could have the FX Pre-Analyzed, saying something like "This is OSC 1 frequency, this is Waveform, this is Filter 1 Cut-Off, etc..."

Then, after the we are done analyzing the Plug-In, we could say "Well, let's map this plugin over this 2 or three surfaces" First give me the Oscilators, then the Filter, then the Amp, etc... in this order, creating either SubZones or modifiers, or both.

Suppose next year I'm lucky enough to get my hands on an SCE24, reconfiguring my FX Zones could be a bliss even after changing my gear.

I'm even pondering the idea of some Machine Learning to help in determining a parameter function based on the FX Type, previous FX mappings of FXs of the same type and whatever name the developers have assigned to their FX Parameters.

Well... just spilling my ideas here.

Will keep testing the latest build, this thing gets even more awesome every day.

Thanks Geoff!
That's what this concept is all about, FXLayouts that span Surfaces:

Code:
Zone "FXLayout"
    "X-Touch" FXTemplate 8
    "X-Touch" FXTemplate Shift 8
    "X-Touch" FXTemplate Option 8
    "X-Touch" FXTemplate Control 8
    "X-Touch" FXTemplate Alt 8
    "MCU"     FXTemplate 8
    "MCU"     FXTemplate Shift 8
    "MCU"     FXTemplate Option 8
    "MCU"     FXTemplate Control 8
    "MCU"     FXTemplate Alt 8
ZoneEnd
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 08:02 AM   #22131
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

New build is up.

CSI Exp.zip

Possible fix for SelectedTrack, SelectedTrackSend, SelectedTrackReceive, and SelectedTrackFXMenu mirroring when spanning Surfaces.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 09:11 AM   #22132
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Miss two days of builds and all of a sudden CSI is completely different!

Quote:
Originally Posted by Geoff Waddington View Post
Just had a look at the new TouchOSC....

Way back when, CSI had the capability to set number of Channels, Sends, Receives, FX, etc. separately....

CSI could query the Surface for these values.

In the case of an MCU family device, the number would come back 8, for all queries.

However, for OSC devices this could vary, depending on how the interface was designed.
Any TouchOSC wizards out there know if this is possible ?
When you say query the device, are you saying CSI making some kind of call to TouchOSC then getting results? I'd be shocked if that was an out of the box feature. And if it depended on a user adding something to the TouchOSC templates, it wouldn't be reliable. Could you attempt to read the .ost for the relevant information and make some assumptions?

Just thinking out loud here, but perhaps a "ChannelClass" is in order for .mst/.ost files like RotaryWidgetClass. With more and more "auto stuff" happening, maybe it's worth considering better adding more details about what each widget kind of does in the .mst/.ost file then letting CSI use those definitions for guidance. I know EWidgets just went the way of the Dodo, but I liked the original concept of "just define once in the .mst and CSI will leverage that downstream". The FXTemplates and proposed FXLayout solve for that in a different way, but perhaps .mst/.ost's providing more information to CSI would help.

Still thinking out loud, maybe even just something as simple as adding this to the .mst/.ost files (might still be a mess from a CSI internals perspective)...
Code:
// X-Touch.mst

ChannelCount 8
SendCount    8
ReceiveCount 8
FXParamCount 8

StepSize
    RotaryWidgetClass 0.003
    JogWheelWidgetClass 0.003
StepSizeEnd

AccelerationValues
    RotaryWidgetClass Dec 41     42    43    44    45    46    47     48
    RotaryWidgetClass Inc 01     02    03    04    05    06    07     08
    RotaryWidgetClass Val 0.005  0.01  0.02  0.04  0.05  0.06  0.08   0.1

    JogWheelWidgetClass Dec 41     42    43    44    45    46    47    48
    JogWheelWidgetClass Inc 01     02    03    04    05    06    07    08
    JogWheelWidgetClass Val 0.005  0.01  0.02  0.04  0.05  0.06  0.08  0.1
AccelerationValuesEnd
OSC is a bit of a nightmare because it's completely free form. Someone could opt to design a surface that's meant to be assigned to 3 track channels, 19 sends, and 42 receives, with 88 FX params all on at once and custom displays that just don't exist on MIDI surfaces. Wildly unlikely that something to that extreme would exist, but my point is maybe it's not even worth catering to that.
__________________
CSI v3 Wiki
Funkybot is offline   Reply With Quote
Old 01-28-2023, 09:12 AM   #22133
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
New build is up.

CSI Exp.zip

Possible fix for SelectedTrack, SelectedTrackSend, SelectedTrackReceive, and SelectedTrackFXMenu mirroring when spanning Surfaces.
Tested Sends, Receives and SelectedTrackFXMenu.

They all map across Extender+X-Touch starting with the Extender.
I added 19 FX to a track and SelectedTrackFXMenu banking works OK.

Once inside the FX Zone, subzone navigation remains on a per-surface basis, but I think that is what's intended.

I'm taking this build to production
Thanks again!!!
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 09:29 AM   #22134
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
Tested Sends, Receives and SelectedTrackFXMenu.

They all map across Extender+X-Touch starting with the Extender.
I added 19 FX to a track and SelectedTrackFXMenu banking works OK.

Once inside the FX Zone, subzone navigation remains on a per-surface basis, but I think that is what's intended.

I'm taking this build to production
Thanks again!!!
Excellent, thanks for testing !

Check next post for one final set of improvements (I hope) before you move it to production
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 09:30 AM   #22135
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

New build is up.

CSI Exp.zip

Possible fix for Focused FX on Master Track.

Possible fix for auto Focused FX mapping crash.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 10:01 AM   #22136
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Geoff Waddington View Post
New build is up.

CSI Exp.zip

Possible fix for Focused FX on Master Track.

Possible fix for auto Focused FX mapping crash.
The crashing remains unless I add ToggleAutoFocusedFXMapping to the Home Zone for the surface that has no FX Definition for the focused plug-in.

What has changed, though, is that now the Reaper GUI doesn't auto-close when I press OK in the C++ error window. It stays unresponsive till I kill the task manually. May this give you some clue.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 10:01 AM   #22137
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Quote:
Originally Posted by Geoff Waddington View Post
Focus has always been a challenge,

As you have noticed, determining when an FX receives focus is fairly easy, find out when it loses focus is not

When you say "but then I focus/click back to tracks" do you mean using the mouse ?

If so, that's expected, since you haven't told CSI to deactivate the Zone via some Surface control.
Yes, when I click off the focused floating FX window back to a track, my display text and surface controls switch back to the main track view, but the display colors do not revert back to track colors, they remain as they were when focused on the FX. I don't think it's an issue recognising when something receives or loses focus as the controls and display text changes correctly depending on what I click with my mouse, this issues are arising due to vagueness around when a zone is activated or deactivated.

The same activate/deactivate vagueness also causes issues for setting display colors for FX with multiple subzone pages. If I have an FX with 3 pages in total (main zone + 2 subzones), and add the two lines for color functionality to each page, the display colors only work on the latter 2 pages which are subzones, not the first main page (which keeps track colors rather than the colors specified in its zone file).
themathpotato is offline   Reply With Quote
Old 01-28-2023, 10:04 AM   #22138
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
The crashing remains unless I add ToggleAutoFocusedFXMapping to the Home Zone for the surface that has no FX Definition for the focused plug-in.

What has changed, though, is that now the Reaper GUI doesn't auto-close when I press OK in the C++ error window. It stays unresponsive till I kill the task manually. May this give you some clue.
Please post your CSI.ini file contents.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 10:10 AM   #22139
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by themathpotato View Post
Yes, when I click off the focused floating FX window back to a track, my display text and surface controls switch back to the main track view, but the display colors do not revert back to track colors, they remain as they were when focused on the FX. I don't think it's an issue recognising when something receives or loses focus as the controls and display text changes correctly depending on what I click with my mouse, this issues are arising due to vagueness around when a zone is activated or deactivated.
Well when the FX loses focus, the Zone should get deactivated, that's what I'm talking about that isn't working.

Quote:
Originally Posted by themathpotato View Post
The same activate/deactivate vagueness also causes issues for setting display colors for FX with multiple subzone pages. If I have an FX with 3 pages in total (main zone + 2 subzones), and add the two lines for color functionality to each page, the display colors only work on the latter 2 pages which are subzones, not the first main page (which keeps track colors rather than the colors specified in its zone file).
Please post the contents of those Zone files and indicate how you are activating the first Zone, by FXMenu ? by Focused FX ? etc.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 10:11 AM   #22140
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by themathpotato View Post
If I have an FX with 3 pages in total (main zone + 2 subzones), and add the two lines for color functionality to each page, the display colors only work on the latter 2 pages which are subzones, not the first main page (which keeps track colors rather than the colors specified in its zone file).
You can fix this by adding the first zone's colors before calling back from the other SubZones.

Code:
Zone "VST3i: Surge XT (Surge Synth Team) (2->6ch)-1" "OSC" 
  OnZoneActivation SetXTouchDisplayColors "Blue"
  ...
  ... blah blah ...
  ...
//Navigation back to first zone
  Up SetXTouchDisplayColors "Cyan" Feedback=No
  InvertFB+Up GoSubZone "VST3i: Surge XT (Surge Synth Team) (2->6ch)" Feedback=Yes
you can the dismiss the InvertFB+ thing. I just do it to turn the LED on
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 10:14 AM   #22141
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

The first FX Zone never gets really "Activated" back as do the others, it is active the whole time.

Hence, anything you have OnZoneActivation in the first zone, has to be called again if you want it to happen again when navigating back there.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 10:16 AM   #22142
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,444
Default

Quote:
Originally Posted by MT4U View Post
The first FX Zone never gets really "Activated" back as do the others, it is active the whole time.

Hence, anything you have OnZoneActivation in the first zone, has to be called again if you want it to happen again when navigating back there.
Correct, I'm trying to figure out why it doesn't initialize properly in the first place.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 01-28-2023, 10:22 AM   #22143
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Quote:
Originally Posted by MT4U View Post
You can fix this by adding the first zone's colors before calling back from the other SubZones.
Only when navigating from a subzone back to the the first zone, not other situations like navigating from the first zone to a subzone, or from a subzone to another subzone?
themathpotato is offline   Reply With Quote
Old 01-28-2023, 10:28 AM   #22144
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by themathpotato View Post
Only when navigating from a subzone back to the the first zone, not other situations like navigating from the first zone to a subzone, or from a subzone to another subzone?
Nope, the others DO get activated every time you call them.

I personally dont’t consider it a drawback, though. It could be useful to be able to do some things only when we focus the FX, for example.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 10:31 AM   #22145
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Quote:
Originally Posted by MT4U View Post
The crashing remains unless I add ToggleAutoFocusedFXMapping to the Home Zone for the surface that has no FX Definition for the focused plug-in.

What has changed, though, is that now the Reaper GUI doesn't auto-close when I press OK in the C++ error window. It stays unresponsive till I kill the task manually. May this give you some clue.
I'm using an X-TouchOne and a SteinbergCMCQC, neither of which I've implicitly disabled AutoFXMapping on. Neither has an FXTemplates.zon. But I do have an FXTemplateZone in my MIDIFighterTwister zone folder. I'm not getting any crashes when generating an AutoFX zone when activating a new plugin for the first time.

Is that similar to what your setup looks like? Maybe the issue is the in the FXTemplates zone file you're using on the surface with FX?

Note: I'm using an FXMenu, not FocusedFX.
__________________
CSI v3 Wiki
Funkybot is offline   Reply With Quote
Old 01-28-2023, 10:39 AM   #22146
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Quote:
Originally Posted by Geoff Waddington View Post
Please post the contents of those Zone files and indicate how you are activating the first Zone, by FXMenu ? by Focused FX ? etc.
Here are my 3 zone files ignoring rotary + fader assignments
Code:
Zone "VST3: SSLChannel Mono (Waves)" "SSLMono"

OnZoneActivation	SetXTouchDisplayColors "White White White White White Green Green Green"
OnZoneDeactivation	RestoreXTouchDisplayColors

	SubZones
		"VST3: SSLChannel Mono (Waves)-1"
		"VST3: SSLChannel Mono (Waves)-2"
	SubZonesEnd
/
Left			GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
BankLeft		GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
ChannelLeft		GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
Right 			GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
BankRight		GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
ChannelRight	GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
/

...
Code:
Zone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"

OnZoneActivation	SetXTouchDisplayColors "White White Cyan Cyan Green Green Red Red"
OnZoneDeactivation	RestoreXTouchDisplayColors

/
Left			GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
BankLeft		GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
ChannelLeft		GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
Right 			GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
BankRight		GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
ChannelRight	GoSubZone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"
/

...
Code:
Zone "VST3: SSLChannel Mono (Waves)-2" "SSLSettings"

	OnZoneActivation	SetXTouchDisplayColors "Red Yellow Red Yellow White Red Yellow Red"
	OnZoneDeactivation	RestoreXTouchDisplayColors
	
/
Left			GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
BankLeft		GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
ChannelLeft		GoSubZone "VST3: SSLChannel Mono (Waves)-1" "SSLEQ"
Right 			GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
BankRight		GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
ChannelRight	GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
/
...
Behaviour is as follows:

I start on the main track view, and with my mouse open and focus the described FX in a floating window. Controls and display text change to as in the main FX zone, but colors do not change to as specified, they remain on track colors.

I press right to navigate to the second page (first FX subzone), both colors and controls now correctly change as expected, similarly when I press right again to go to the third page.

However when I press right a third time to return to the main FX page, the colors revert to track colors, not the colors specified in the zone.

Now if I once again enter the second page, (colors and controls change as expected) and click with my mouse back to a track, the controls and display text change to track view, but the colors remain as they were on the FX, they do not change to track colors.
themathpotato is offline   Reply With Quote
Old 01-28-2023, 10:49 AM   #22147
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Weirdly enough, the first FX zone still has track colors even when I access it through the SelectedTrackFXMenu. All displays go yellow when I use the FX Menu, but then change back to track colors when I select the FX, even though I specified display colors in all 3 FX zones.
themathpotato is offline   Reply With Quote
Old 01-28-2023, 10:56 AM   #22148
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Am I doing this right? This isn't working here on my X-TouchOne, which uses a SelectedTrack zone.

Code:
Zone "Buttons"
     BankLeft                  Bank SelectedTrack -8                       
     BankRight                 Bank SelectedTrack 8                        
     ChannelLeft               Bank SelectedTrack -1                       
     ChannelRight              Bank SelectedTrack 1
__________________
CSI v3 Wiki
Funkybot is offline   Reply With Quote
Old 01-28-2023, 10:57 AM   #22149
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Funkybot View Post
Is that similar to what your setup looks like? Maybe the issue is the in the FXTemplates zone file you're using on the surface with FX?

Note: I'm using an FXMenu, not FocusedFX.
If I use the FXMenu everything works fine. Have you tried with FocusedFX enabled and still no crashes?
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 11:00 AM   #22150
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Quote:
Originally Posted by MT4U View Post
If I use the FXMenu everything works fine. Have you tried with FocusedFX enabled and still no crashes?
Just checked. Still no crashes.

I'd suggest:

1. Post your CSI.ini contents
2. Post your FXTemplates.zon contents, including Prologue and Epilogue zones if any
3. Let us know if it's any specific FX or all - Edit: particularly if the FX has more params than you have widgets for in your FXTemplates.zon as that used to cause similar VC Runtime crashes in a prior build

For reference, here is mine...

Code:
Version 2.0

MidiSurface "XTouchOne" 7 9 
MidiSurface "MFTwister" 6 8 
OSCSurface "iPad Pro" 8008 9008 10.0.0.146
MidiSurface "CMC-QC" 10 12 

Page "HomePage" UseScrollLink
"MFTwister" 8 0 "MIDIFighterTwisterEncoder.mst" "FXTwisterMenu" "FXTwisterFXZones" 
"iPad Pro" 8 0 "FXTwister.ost" "FXTwisterMenu" "FXTwisterFXZones" 
"XTouchOne" 1 0 "X-Touch_One.mst" "X-Touch_One_FB" "X-Touch_One_FB" 
"CMC-QC" 0 0 "Stienberg_CMC-QC-2.mst" "Steinberg_CMC-QC-2" "Steinberg_CMC-QC-2"
Code:
Zone FXPrologue
MainDisplay2   FXMenuNameDisplay
/
ZoneEnd
Do you have the channel count numbers?
Code:
Zone "FXTemplates"
     MCUTemplate                    Rotary A 8
     MCUTemplate                    Rotary B 8
     MCUTemplate+Shift              Rotary A 8
     MCUTemplate+Shift              Rotary B 8
     MCUTemplate+Option             Rotary A 8
     MCUTemplate+Option             Rotary B 8
     MCUTemplate+Control            Rotary A 8
     MCUTemplate+Control            Rotary B 8
     MCUTemplate+Alt                Rotary A 8
     MCUTemplate+Alt                Rotary B 8
     MCUTemplate+Shift+Option       Rotary A 8
     MCUTemplate+Shift+Option       Rotary B 8
     MCUTemplate+Shift+Control      Rotary A 8
     MCUTemplate+Shift+Control      Rotary B 8
     MCUTemplate+Shift+Alt          Rotary A 8
     MCUTemplate+Shift+Alt          Rotary B 8
     MCUTemplate+Option+Control     Rotary A 8
     MCUTemplate+Option+Control     Rotary B 8
     MCUTemplate+Option+Alt         Rotary A 8
     MCUTemplate+Option+Alt         Rotary B 8
ZoneEnd
Code:
Zone FXEpilogue
/
DisplayRotaryPushA1 NoAction
RotaryPushA1        NoAction
DisplayUpperShiftA1 NoAction 
DisplayLowerShiftA1 NoAction 
ShiftRotaryA1       NoAction 
/  
DisplayRotaryPushA2 NoAction
RotaryPushA2        NoAction
DisplayUpperShiftA2 NoAction 
DisplayLowerShiftA2 NoAction 
ShiftRotaryA2       NoAction 
/
DisplayRotaryPushA3 NoAction
RotaryPushA3        NoAction
DisplayUpperShiftA3 NoAction 
DisplayLowerShiftA3 NoAction 
ShiftRotaryA3       NoAction 
/  
DisplayRotaryPushA4 NoAction
RotaryPushA4        NoAction
DisplayUpperShiftA4 NoAction 
DisplayLowerShiftA4 NoAction 
ShiftRotaryA4       NoAction 
/
DisplayRotaryPushA5 NoAction
RotaryPushA5        NoAction
DisplayUpperShiftA5 NoAction 
DisplayLowerShiftA5 NoAction 
ShiftRotaryA5       NoAction 
/  
DisplayRotaryPushA6 NoAction
RotaryPushA6        NoAction
DisplayUpperShiftA6 NoAction 
DisplayLowerShiftA6 NoAction 
ShiftRotaryA6       NoAction 
/
DisplayRotaryPushA7 NoAction
RotaryPushA7        NoAction
DisplayUpperShiftA7 NoAction 
DisplayLowerShiftA7 NoAction 
ShiftRotaryA7       NoAction 
/  
DisplayRotaryPushA8 NoAction
RotaryPushA8        NoAction
DisplayUpperShiftA8 NoAction 
DisplayLowerShiftA8 NoAction 
ShiftRotaryA8       NoAction 
/
DisplayRotaryPushB1 NoAction
RotaryPushB1        NoAction
DisplayUpperShiftB1 NoAction 
DisplayLowerShiftB1 NoAction 
ShiftRotaryB1       NoAction 
/  
DisplayRotaryPushB2 NoAction
RotaryPushB2        NoAction
DisplayUpperShiftB2 NoAction 
DisplayLowerShiftB2 NoAction 
ShiftRotaryB2       NoAction 
/
DisplayRotaryPushB3 NoAction
RotaryPushB3        NoAction
DisplayUpperShiftB3 NoAction 
DisplayLowerShiftB3 NoAction 
ShiftRotaryB3       NoAction 
/  
DisplayRotaryPushB4 NoAction
RotaryPushB4        NoAction
DisplayUpperShiftB4 NoAction 
DisplayLowerShiftB4 NoAction 
ShiftRotaryB4       NoAction 
/
DisplayRotaryPushB5 NoAction
RotaryPushB5        NoAction
DisplayUpperShiftB5 NoAction 
DisplayLowerShiftB5 NoAction 
ShiftRotaryB5       NoAction 
/  
DisplayRotaryPushB6 NoAction
RotaryPushB6        NoAction
DisplayUpperShiftB6 NoAction 
DisplayLowerShiftB6 NoAction 
ShiftRotaryB6       NoAction 
/
DisplayRotaryPushB7 NoAction
RotaryPushB7        NoAction
DisplayUpperShiftB7 NoAction 
DisplayLowerShiftB7 NoAction 
ShiftRotaryB7       NoAction 
/  
DisplayRotaryPushB8 NoAction
RotaryPushB8        NoAction
DisplayUpperShiftB8 NoAction 
DisplayLowerShiftB8 NoAction 
ShiftRotaryB8       NoAction 
/
ZoneEnd
__________________
CSI v3 Wiki

Last edited by Funkybot; 01-28-2023 at 11:07 AM.
Funkybot is offline   Reply With Quote
Old 01-28-2023, 11:02 AM   #22151
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by themathpotato View Post
However when I press right a third time to return to the main FX page, the colors revert to track colors, not the colors specified in the zone.

Now if I once again enter the second page, (colors and controls change as expected) and click with my mouse back to a track, the controls and display text change to track view, but the colors remain as they were on the FX, they do not change to track colors.
Every line where you call the first zone must be preceded by the first zone's colors:
Code:
ChannelRight	GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
should be
Code:
ChannelRight	SetXTouchDisplayColors "White White White White White Green Green Green"
ChannelRight	GoSubZone "VST3: SSLChannel Mono (Waves)" "SSLMono"
and so on.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 11:15 AM   #22152
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Quote:
Originally Posted by MT4U View Post
Every line where you call the first zone must be preceded by the first zone's colors:
I added this but it doesn't fix anything, the first FX zone is still taking display colors from the tracks.
themathpotato is offline   Reply With Quote
Old 01-28-2023, 12:06 PM   #22153
leejul
Human being with feelings
 
Join Date: Sep 2021
Location: Quebec, Canada
Posts: 123
Default

[QUOTE=Geoff Waddington;2640547]CAUTION CAUTION CAUTION CAUTION CAUTION CAUTION CAUTION
Thanks Geoff for this update.
I replaced the .ini, I deleted the CSI page in the preferences of Reaper and I created a new page.
I made the necessary changes so that everything is consistent with the EXP version
Everything works perfectly.
I checked Follow TCP Visibility.
I checked Surface and Reaper Scroll Together.
But CSI still doesn't follow TCP.
Is this normal?
Question:
Are modifier locks now stated?
If yes, how does it work?
Thanks.
__________________
LeeJul
Reaper FrenchLangPack here:
stash.reaper.fm/v/45280/REAPER_SWS_FRC.ReaperLangPac
leejul is offline   Reply With Quote
Old 01-28-2023, 12:27 PM   #22154
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by themathpotato View Post
I added this but it doesn't fix anything, the first FX zone is still taking display colors from the tracks.
What if you remove the GoSubZone and just set the colors in the button press? Do they change?
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 12:44 PM   #22155
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Funkybot View Post
Just checked. Still no crashes.

I'd suggest:

1. Post your CSI.ini contents
2. Post your FXTemplates.zon contents, including Prologue and Epilogue zones if any
3. Let us know if it's any specific FX or all - Edit: particularly if the FX has more params than you have widgets for in your FXTemplates.zon as that used to cause similar VC Runtime crashes in a prior build
Thanks and sorry, FB. It was just laziness on my part.

I decided to test drive the whole thing starting from scratch, using the support files and doing the minimal changes necessary like the csi.ini file
Code:
Version 2.0

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

Page "HomePage"
"X-TouchXT" 8 0 "X-TouchXT.mst" "X-TouchXT" "FX_Zones"
"X-Touch" 8 8 "X-Touch.mst" "X-Touch" "FX"
"X-Touch_One" 1 16 "X-Touch_One.mst" "X-Touch_One" "FX"
and the Banking channel counts.

The support files have the FX Epilogue, Prologue and Templates zones only in the X-Touch folder.

I'll do a proper configuration based on your excellent examples and get back to you once I've reached a more solid ground. If during the process the error disappears, I'll try to find exactly where, it may be of use.

Thanks again!
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 01:14 PM   #22156
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Quote:
Originally Posted by MT4U View Post
What if you remove the GoSubZone and just set the colors in the button press? Do they change?
Yes, for example I removed GoSubZone from the second page (first subzone), then pressed left in that zone, the colors correctly change as defined (but obviously the controls no longer navigate back to the first zone).

I think there's an issue with how the main FX zone is activated and deactivated, as issues occur both when first opening the FX, and when closing/unfocusing the FX.
themathpotato is offline   Reply With Quote
Old 01-28-2023, 01:17 PM   #22157
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Quote:
Originally Posted by MT4U View Post
Thanks and sorry, FB. It was just laziness on my part.

I decided to test drive the whole thing starting from scratch, using the support files and doing the minimal changes necessary like the csi.ini file
Code:
Version 2.0

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

Page "HomePage"
"X-TouchXT" 8 0 "X-TouchXT.mst" "X-TouchXT" "FX_Zones"
"X-Touch" 8 8 "X-Touch.mst" "X-Touch" "FX"
"X-Touch_One" 1 16 "X-Touch_One.mst" "X-Touch_One" "FX"
and the Banking channel counts.

The support files have the FX Epilogue, Prologue and Templates zones only in the X-Touch folder.

I'll do a proper configuration based on your excellent examples and get back to you once I've reached a more solid ground. If during the process the error disappears, I'll try to find exactly where, it may be of use.

Thanks again!
Good luck! Out of curiousity, are you using the "Bank SelectedTrack" action successfully on your X-TouchOne? Not sure if I'm doing something wrong or if that isn't working in a SelectedTrack workflow.
__________________
CSI v3 Wiki
Funkybot is offline   Reply With Quote
Old 01-28-2023, 01:44 PM   #22158
themathpotato
Human being with feelings
 
Join Date: Jan 2022
Posts: 21
Default

Now the best solution I've found so far is to define the colors on activation for the first main FX zone only, and also for both left and right navigation buttons on all three zones. By doing this, the correct colors are shown when the FX is opened both via focusing and the FX menu, and for all three pages using the navigation buttons.

However, these FX colors are still carried over back to the track view when focusing/clicking back on the tracks.

How does automatic track coloring work? I'd guess either the FX zone is not properly deactivated when focusing back on tracks (even though the controls correctly change), or the track zone is not reactivated when refocusing on it?
themathpotato is offline   Reply With Quote
Old 01-28-2023, 01:59 PM   #22159
MT4U
Human being with feelings
 
MT4U's Avatar
 
Join Date: Jan 2022
Location: Unifield
Posts: 394
Default

Quote:
Originally Posted by Funkybot View Post
Good luck! Out of curiousity, are you using the "Bank SelectedTrack" action successfully on your X-TouchOne? Not sure if I'm doing something wrong or if that isn't working in a SelectedTrack workflow.
If I select a track with the X-Touch, everything is OK.
X-Touch One displays show track info.

If I do a "Bank SelectedTrack 1" on the XT-One I get a blank display.
Track selection on the X-Touch works no more for the XT-One.
Going back "Bank SelectedTrack -1" on the XT-One fixes it.
__________________

CSI_FX
: SubZone based GUI/Automapper for CSI.(UPD:2024-01-13)
Video Demo/Tutorial
Scripts for CSI: Reaper EEL2 scripts to use with CSI
MT4U is offline   Reply With Quote
Old 01-28-2023, 02:08 PM   #22160
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 6,068
Default

Quote:
Originally Posted by MT4U View Post
If I select a track with the X-Touch, everything is OK.
X-Touch One displays show track info.

If I do a "Bank SelectedTrack 1" on the XT-One I get a blank display.
Track selection on the X-Touch works no more for the XT-One.
Going back "Bank SelectedTrack -1" on the XT-One fixes it.
Sounds like you're using one of the modes other than MC User mode on the X-Touch One. In the other modes, the Channel Bank buttons will literally change the Fader address, so you'll go to Fader2, then Fader3, etc. But that doesn't really work with the SelectedTrack workflow. For that, I always suggest using MC User mode on the X-TouchOne with the SelectedTrack zone type and everything assigned to Fader1.
__________________
CSI v3 Wiki
Funkybot is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 06:28 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.