Just thinking with the GoZone and function keys, you could get a lot out of very little realestate.
Imagine 3 knobs with push function you could have them initially set as freq, gain and q for low band, then have function keys changing type (bell, cut, notch etc) and dB grad etc. Then have the GoZone to "scroll" thru the different bandwidths.
ALL IN 3 KNOBS AND 2 BUTTONS plus function keys.
Potentially controlling up to 60 rotary and 60 push functions.

Not to mention the possibility of having more than 4 GoZone's and combofunctions (Control+Shift, etc)

Yup

Thanks, that was the number one goal, to come up with an extremely flexible architecture that could be stated in simple, human-readable, text files - as opposed to xml, etc.

Thanks, that was the number one goal, to come up with an extremely flexible architecture that could be stated in simple, human-readable, text files - as opposed to xml, etc.

Unfortunately the Configurator is a little "clunky" for these atm,

FUTURE:
Thinking ahead to expand the universe (from just the C4) what if you could decide your number or rows and columns, and have pages revealed/activated by a check box.
So you have Main, With a check box to activate Function key subzones for that main.
Another check box for Zone-pt2 again as above for subs.
and so on.

It does begin to become a fully blown program just in itself, but very very powerful.

The reason I'm think Functions should come before "Zone-pt2" is simply because the definitions will exist within that "Zone".

Just thinking with the GoZone and function keys, you could get a lot out of very little realestate.
Imagine 3 knobs with push function you could have them initially set as freq, gain and q for low band, then have function keys changing type (bell, cut, notch etc) and dB grad etc. Then have the GoZone to "scroll" thru the different bandwidths.
ALL IN 3 KNOBS AND 2 BUTTONS plus function keys.
Potentially controlling up to 60 rotary and 60 push functions.

Not to mention the possibility of having more than 4 GoZone's and combofunctions (Control+Shift, etc)

We want to do Groups, Folders, and VCA's together -- we already have busses - aka Sends.

It all has to work together, intuitively and seamlessly, so we are taking time to discuss before implementing, please share any thoughts on your "Cadillac solution" for Groups, Folders, and VCA's.

Klinke works well for me in this regard (well, folders at least). I like the press and hold select to dive in to the folder (and global to page back up) I also like that it holds the folder to the left and shows the subs to the right of that.

I could imagine a variation of this for VCAs and Busses too (possibly even groups, although I'm not a big groups user) so pressing and holding a VCA shows all the tracks under the control of that VCA and similarly with Busses (i.e. press and hold on a buss dives to the buss and all the tracks it receives from laid out L to R) Perhaps it could also be 'reverse accessible' insofar as if you hold a modifier and hold select on a track it shows you all the busses it's sending to?

New Configurator Now able to load FX.zon files it has created and save them back to the same location. It will also create the headers for four zones if needed.

It now saves the FX parameter data in the .zon file, meaning after you have created the Zone you no longer need the raw FX file to edit and re-save the FX.zon file.

I haven't tried this one yet but I read one of the comments that it won't load any zon files you have directly modified. I always have to modify them to add special characters like "-" etc in order to add separators in my c4 params, makes it easier to view everything when multiple fx are displayed at once.

So....is there any way to let us add special characters without breaking the cells? I personally like the minus sign, it's a good separator, but open to any other suggestions if it's possible. Otherwise I'm happy to continue how I'm doing now, just a thought.

Klinke works well for me in this regard (well, folders at least). I like the press and hold select to dive in to the folder (and global to page back up) I also like that it holds the folder to the left and shows the subs to the right of that.

I could imagine a variation of this for VCAs and Busses too (possibly even groups, although I'm not a big groups user) so pressing and holding a VCA shows all the tracks under the control of that VCA and similarly with Busses (i.e. press and hold on a buss dives to the buss and all the tracks it receives from laid out L to R) Perhaps it could also be 'reverse accessible' insofar as if you hold a modifier and hold select on a track it shows you all the busses it's sending to?

You could get by using a mock folder mode, there is an action for the mixer: toggle child tracks for selected tracks, something like that. Assign it to a button, select a folder track and use that toggle. it's not as elegant as the press/hold, but if you can find a good "spot" for your button it can be functional. Toggle all your folder tracks then you can go through them one by one as you need to, and free up channels on the surface.

Just thinking with the GoZone and function keys, you could get a lot out of very little realestate.
Imagine 3 knobs with push function you could have them initially set as freq, gain and q for low band, then have function keys changing type (bell, cut, notch etc) and dB grad etc. Then have the GoZone to "scroll" thru the different bandwidths.
ALL IN 3 KNOBS AND 2 BUTTONS plus function keys.
Potentially controlling up to 60 rotary and 60 push functions.

Not to mention the possibility of having more than 4 GoZone's and combofunctions (Control+Shift, etc)

this is what I love about CSI, there are so many possibilities that there's a solution for everyone. and what's better are all the great ideas coming out, thank you all for the ideas, I've been using many of them to help build a workflow for myself and it's awesome.

I haven't tried this one yet but I read one of the comments that it won't load any zon files you have directly modified. I always have to modify them to add special characters like "-" etc in order to add separators in my c4 params, makes it easier to view everything when multiple fx are displayed at once.

So....is there any way to let us add special characters without breaking the cells? I personally like the minus sign, it's a good separator, but open to any other suggestions if it's possible. Otherwise I'm happy to continue how I'm doing now, just a thought.

The minus is ok now, I changed the Configurator separator to the tilde symbol (~)

I was testing Shift/Option/Control and GoZone with the big toys, aka, Fabfilter Q3

Built for Freq 1, 2 and 3 (It was long & painful, so only did 2 freq bands)EDIT I added a 3rd just for fun with all the possible params on just 3 push/knobs
Shift/Option/Control BankL and BankR buttons.

Here's my thinking on the Zones now that The Function Buttons work,
GoZone will be great for the big picture when using, multi FX and instrument plugins,

But for the likes of EQ the function buttons seem, to me, to be a more "compact solution"
For example you could have 4x3 used on the C4, with all the little extras on the Function keys, then have zones set up to either jump to the next four or give you a "perceived scroll effect" by each subzone moving one band to the right.

Not sure if the files will attach but if they do just remove the ".txt" on the end

If anyone with a C4 and Fab-Q3 wants to see all the bells and whistles working. (albeit only on 3 bands of the possible 24 lol)

I'v been playing with the SyncZoneAcrossSurfaces this last while and find the tick box pretty handy, Would the info be stored in the .mst or where?

At the minute I have a MCU_A and C4_B that are my stable working no issues go to setup , but I have a MCU_B and C4_C that are my play around with stuff.

(Yes you'd think I'd have the same letter after them, but It's because C4 zone in CSI folder is C4_A and not just C4, so in order to simply drag and drop new versions without overwriting mine, that's what i gotta do.)(So it's all your fault Geoff)

Would the files be stored in one of those, so that setting changes would only affect one or the other?

I'v been playing with the SyncZoneAcrossSurfaces this last while and find the tick box pretty handy, Would the info be stored in the .mst or where?

At the minute I have a MCU_A and C4_B that are my stable working no issues go to setup , but I have a MCU_B and C4_C that are my play around with stuff.

(Yes you'd think I'd have the same letter after them, but It's because C4 zone in CSI folder is C4_A and not just C4, so in order to simply drag and drop new versions without overwriting mine, that's what i gotta do.)(So it's all your fault Geoff)

Yeah, don't remember why we did that, it is now renamed to C4 so it is consistent with the others.

That is a breaking change, so it will be in the OSC / ConfigZone build, a bit down the road, but be ready for it

Quote:

Originally Posted by Freex

Would the files be stored in one of those, so that setting changes would only affect one or the other?

Hmmm... maybe all the PageConfigZones could be stored in a subfolder a la:

Code:

CSI/Zones/PageConfig

Also realized Surface Configs need a Page Context, so maybe something more like:

Looking at implementing the ConfigZone thing raises a big issue -- you now have unwanted coupling between the ConfigZones and the CSI.ini files, things can get out of whack -- belay that order cap'n, we'll stick with what we've got

Looking at implementing the ConfigZone thing raises a big issue -- you now have unwanted coupling between the ConfigZones and the CSI.ini files, things can get out of whack -- belay that order cap'n, we'll stick with what we've got

Just a thought, if the intention is to keep the CSI prefs as displayed in Reaper as simple and user friendly as possible, as well as avoiding cross-platform issues, why not just leave the more esoteric settings out of the GUI and only inlude them in the .ini?

I think personally having the each function all together would be easier to read than all A1 then A2.....

In the Fabfilter Q3 I tested, I clubed them in A1, A2 rather than all the different functions together,(as it was a little faster using the configerator (then manually editing a little) and I thought it looked a little hard on the eyes and brain.
But I guess there are pros and cons with both.

I don't think they should be separate files, like the subZones are, but again that's just my feelings.
I think of the zone like it's a BOOK,
the "Main" "shift+" "option+" etc are pages of that book,
a subZone is the 2nd, 3rd, and so on, BOOK in that series, with all it's own pages.

I'm ready to test OSC (not that i think I'll have too much use for it, but you never know and after all, it's for the greater good)

Here what i did, what am I missing?
Loaded Touch OSC on tablet
settings OCS connection,
Host ( I looked for IP of PC)
out IN and name all auto

Layout as Logic Touch

Done I see a track control layout and transport on Tablet.

CSI > Added OSC

Used the setting from tablet
"remore device IP" should that be "REMOTE" i put in ip from tablet .
in and out i used from OSC (auto 8000 and 9000
Surface I used Logi as it's the only choice. lol
Zone ?????? tried MCU.

I'm ready to test OSC (not that i think I'll have too much use for it, but you never know and after all, it's for the greater good)

Here what i did, what am I missing?
Loaded Touch OSC on tablet
settings OCS connection,
Host ( I looked for IP of PC)
out IN and name all auto

Layout as Logic Touch

Done I see a track control layout and transport on Tablet.

CSI > Added OSC

Used the setting from tablet
"remore device IP" should that be "REMOTE" i put in ip from tablet .
in and out i used from OSC (auto 8000 and 9000
Surface I used Logi as it's the only choice. lol
Zone ?????? tried MCU.

Cool.

You could check your PC IP by going in to Reaper config and pretending to add an OSC surface -- Choose Local Port in the mode list == Reaper will show the IP, it's probably the same as you have.