|
|
|
11-19-2020, 08:43 AM
|
#11561
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Just got around to doing a bit of OSC testing and I seem to have lost stepped parameters (including toggling of buttons) in FX zones. Mute, Solo etc are unaffected.
Pressing a button set up as:
Code:
RotaryPushB1 FXParam 2 [ 0.0 1.0 ]
...will turn the parameter on, but not off.
It all works fine on the (real) C4.
|
|
|
11-19-2020, 08:55 AM
|
#11562
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by kevrose
@MixMonkey Well it's taken a night of insomnia for me to finally realise what I was doing wrong with this - hadn't setup a ZoneFXFiles folder currently!
|
Doh! You know, I might change this to just dump the completed Zone on the Desktop! (everyone has a desktop ) The saving and loading is so convoluted because of the way VBA is implemented on the Mac. The load folder (ZoneRawFXFiles) will be there because it's where CSI outputs the RawParameter file.
Quote:
Only problem I have now is (and the insomnia probably hasn't helped this time) is with the changes I need to make to each file. I've looked at Funkybot's excellent post but I seem to have got myself completely confused and my files in a real state.
Is there any chance you could share a sample C4 .zon file for any plugin and your mst/zon for the surfaces? That way I can understand what I need to do and make the relevant changes my end.
|
Sure thing:
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOS_EQ"
SelectedTrackNavigator
/
/
DisplayUpperA1 FXParamNameDisplay 22 "VOS_EQ"
DisplayLowerA1 FXParamValueDisplay 22
RotaryA1 FXParam 22 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA1 FXParam 21 [ 0.0 1.0 ]
/
DisplayUpperA2 NoAction
DisplayLowerA2 NoAction
RotaryA2 NoAction
RotaryPushA2 NoAction
/
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
RotaryPushA3 NoAction
/
DisplayUpperA4 FXParamNameDisplay 20 "Qual"
DisplayLowerA4 FXParamValueDisplay 20
RotaryA4 FXParam 20 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA4 FXParam 20 [ 0.0 1.0 ]
/
DisplayUpperA5 FXParamNameDisplay 9 "Sat"
DisplayLowerA5 FXParamValueDisplay 9
RotaryA5 FXParam 9 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA5 FXParam 9 [ 0.0 1.0 ]
/
DisplayUpperA6 FXParamNameDisplay 15 "Mode"
DisplayLowerA6 FXParamValueDisplay 15
RotaryA6 FXParam 15 [ (4,4,3,2,1) 0.0 0.20 0.40 0.60 0.80 1.0 ]
RotaryPushA6 FXParam 15 [ 0.0 0.20 0.40 0.60 0.80 1.0 ]
/
DisplayUpperA7 NoAction
DisplayLowerA7 NoAction
RotaryA7 NoAction
RotaryPushA7 NoAction
/
DisplayUpperA8 NoAction
DisplayLowerA8 NoAction
RotaryA8 NoAction
RotaryPushA8 NoAction
/
DisplayUpperB1 FXParamNameDisplay 2 "Shape"
DisplayLowerB1 FXParamValueDisplay 2
RotaryB1 FXParam 2 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB1 FXParam 2 [ 0.0 1.0 ]
/
DisplayUpperB2 FXParamNameDisplay 8 "Model"
DisplayLowerB2 FXParamValueDisplay 8
RotaryB2 FXParam 8 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB2 FXParam 8 [ 0.0 0.34 0.67 1.0 ]
/
DisplayUpperB3 FXParamNameDisplay 7 "Shape"
DisplayLowerB3 FXParamValueDisplay 7
RotaryB3 FXParam 7 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB3 FXParam 7 [ 0.0 1.0 ]
/
DisplayUpperB4 NoAction
DisplayLowerB4 NoAction
RotaryB4 NoAction
RotaryPushB4 NoAction
/
DisplayUpperB5 NoAction
DisplayLowerB5 NoAction
RotaryB5 NoAction
RotaryPushB5 NoAction
/
DisplayUpperB6 NoAction
DisplayLowerB6 NoAction
RotaryB6 NoAction
RotaryPushB6 NoAction
/
DisplayUpperB7 NoAction
DisplayLowerB7 NoAction
RotaryB7 NoAction
RotaryPushB7 NoAction
/
DisplayUpperB8 NoAction
DisplayLowerB8 NoAction
RotaryB8 NoAction
RotaryPushB8 NoAction
/
DisplayUpperC1 FXParamNameDisplay 1 "LF"
DisplayLowerC1 FXParamValueDisplay 1
RotaryC1 FXParam 1 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC1 NoAction
/
DisplayUpperC2 FXParamNameDisplay 4 "MF"
DisplayLowerC2 FXParamValueDisplay 4
RotaryC2 FXParam 4 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC2 NoAction
/
DisplayUpperC3 FXParamNameDisplay 6 "HF"
DisplayLowerC3 FXParamValueDisplay 6
RotaryC3 FXParam 6 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC3 NoAction
/
DisplayUpperC4 NoAction
DisplayLowerC4 NoAction
RotaryC4 NoAction
RotaryPushC4 NoAction
/
DisplayUpperC5 FXParamNameDisplay 11 "Stage"
DisplayLowerC5 FXParamValueDisplay 11
RotaryC5 FXParam 11 [ 0.0 0.25 0.50 0.75 1.0 ]
RotaryPushC5 FXParam 11 [ 0.0 0.25 0.50 0.75 1.0 ]
/
DisplayUpperC6 FXParamNameDisplay 12 "Drive"
DisplayLowerC6 FXParamValueDisplay 12
RotaryC6 FXParam 12 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC6 NoAction
/
DisplayUpperC7 NoAction
DisplayLowerC7 NoAction
RotaryC7 NoAction
RotaryPushC7 NoAction
/
DisplayUpperC8 NoAction
DisplayLowerC8 NoAction
RotaryC8 NoAction
RotaryPushC8 NoAction
/
DisplayUpperD1 FXParamNameDisplay 0 "Gain"
DisplayLowerD1 FXParamValueDisplay 0
RotaryD1 FXParam 0
RotaryPushD1 FXParam 16 [ 0.0 1.0 ]
/
DisplayUpperD2 FXParamNameDisplay 3 "Gain"
DisplayLowerD2 FXParamValueDisplay 3
RotaryD2 FXParam 3 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD2 FXParam 17 [ 0.0 1.0 ]
/
DisplayUpperD3 FXParamNameDisplay 5 "Gain"
DisplayLowerD3 FXParamValueDisplay 5
RotaryD3 FXParam 5 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD3 FXParam 18 [ 0.0 1.0 ]
/
DisplayUpperD4 NoAction
DisplayLowerD4 NoAction
RotaryD4 NoAction
RotaryPushD4 NoAction
/
DisplayUpperD5 FXParamNameDisplay 10 "HPF"
DisplayLowerD5 FXParamValueDisplay 10
RotaryD5 FXParam 10 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD5 NoAction
/
DisplayUpperD6 FXParamNameDisplay 13 "Gain"
DisplayLowerD6 FXParamValueDisplay 13
RotaryD6 FXParam 13 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD6 FXParam 19 [ 0.0 1.0 ]
/
DisplayUpperD7 NoAction
DisplayLowerD7 NoAction
RotaryD7 NoAction
RotaryPushD7 NoAction
/
DisplayUpperD8 NoAction
DisplayLowerD8 NoAction
RotaryD8 NoAction
RotaryPushD8 NoAction
/
ZoneEnd
Last edited by MixMonkey; 12-13-2020 at 06:03 PM.
|
|
|
11-19-2020, 09:18 AM
|
#11563
|
Human being with feelings
Join Date: Apr 2018
Posts: 123
|
Reaper crashes after updating CSI
Hi, I hadn't done this for a while, but I've just updated to version 1.0, and Reaper crashes.
I have kept my original .zon files, and my original CSI.ini file.
As always, grateful for any suggestions
|
|
|
11-19-2020, 09:21 AM
|
#11564
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by Equitone
Hi, I hadn't done this for a while, but I've just updated to version 1.0, and Reaper crashes.
I have kept my original .zon files, and my original CSI.ini file.
As always, grateful for any suggestions
|
See this post:
https://forum.cockos.com/showpost.ph...ostcount=11490
|
|
|
11-19-2020, 09:47 AM
|
#11565
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 901
|
Just seeing the messages about sample zone files,
I'm wondering if a database of some sort would be good, to allow users to forgo the whole setup, IF they have a specific surface and Vst.
No idea how you'd do it or order it.
Just a thought out loud.
|
|
|
11-19-2020, 09:53 AM
|
#11566
|
Human being with feelings
Join Date: Apr 2018
Posts: 123
|
Quote:
Originally Posted by Freex
Just seeing the messages about sample zone files,
I'm wondering if a database of some sort would be good, to allow users to forgo the whole setup, IF they have a specific surface and Vst.
No idea how you'd do it or order it.
Just a thought out loud.
|
Good point. I have now done a bit of reading, and altering all my zon/mst files for the XTouch looks like being a big job with a deal of coffee consumption.
Geoff, looking forward to getting this up and running. These are ramblings from someone who should have read up before asking the question.
|
|
|
11-19-2020, 10:02 AM
|
#11567
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 901
|
I'm thinking in the same way as theme.
I like to "test drive" a few themes see what works what doesn't what I like, then I try to combine the best of what I like.
Rather than a cold start, blank setup from scratch.
|
|
|
11-19-2020, 10:13 AM
|
#11568
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
|
Quote:
Originally Posted by Freex
I'm thinking in the same way as theme.
I like to "test drive" a few themes see what works what doesn't what I like, then I try to combine the best of what I like.
Rather than a cold start, blank setup from scratch.
|
Yes, we were talking about starting a new thread "CSI -- Control System Integration", as soon as the wiki is in good enough shape, and there are a sufficient number of working mst/ost/zon files.
The aforementioned mst/ost/zon files/ will be in the download in the CSI folder, so you are are ready go right out of the box, if you have a currently supported surface.
__________________
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
|
|
|
11-19-2020, 10:47 AM
|
#11569
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 901
|
Quote:
Originally Posted by Geoff Waddington
Yes, we were talking about starting a new thread "CSI -- Control System Integration", as soon as the wiki is in good enough shape, and there are a sufficient number of working mst/ost/zon files.
The aforementioned mst/ost/zon files/ will be in the download in the CSI folder, so you are are ready go right out of the box, if you have a currently supported surface.
|
I was thinking more about vst FXzones.
Obviously they depend (to lesser or greater degree) on your control surface, and may or may not be cross compatible.
But thought as things settle, code wise, that a database of FXzones for specific controller would be a great asset.
|
|
|
11-19-2020, 11:26 AM
|
#11570
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by Freex
I was thinking more about vst FXzones.
Obviously they depend (to lesser or greater degree) on your control surface, and may or may not be cross compatible.
But thought as things settle, code wise, that a database of FXzones for specific controller would be a great asset.
|
If I share my MFTwister setup (and a few other users have the device too so they may have their own takes on that), then I'd share any relevant fx.zon's. A user could then re-map those as needed, or just take them as-is. But let's say cjewellstudio's MFTwister didn't line up with mine because we use different widget names and even have the hardware configured differently, then there's a chance you could run into issues. So then it becomes trickier.
For instance, MixMinkey uses "RotaryPush" on the C4 as his widget name, I use "Button" on my MFTwister, cjewellstudios uses another variation...I think cjewellstudios and I are leaning towards "let's all just adapt RotaryPush for maximum compatibility" but there's nothing in CSI that mandates that. The solution might be as simple as a find and replace across a few folders, but with flexibility comes the potential for greater incompatibility. But that's just the Reaper/CSI way. Let users figure it out.
Otherwise, the fx.zon's can actually be pretty portable, even across devices, as long as users kind of adhere to a kind of "best practice naming convention." For instance, "banks of 8, widgets called A1 up to A8, then B1, use Rotary Push for any buttons, RotaryA1 for encoders/knobs, and FaderA1 for faders, and DisplayUpperA1/DisplayLowerA1 for displays..." If people just naturally adhere to that, there's a good chance fx.zon's could be shared pretty easily. It's just not a rule that you do it that way.
In an ideal world, a programer would take up building a mapping front-end for CSI with some slick FX Lean capabilities for easy .zon generation. Until then, there's MixMonkey's spreadsheet which is probably the next best thing.
|
|
|
11-19-2020, 11:37 AM
|
#11571
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
@Funkybot Do stepped parameters work for you in OSC?
|
|
|
11-19-2020, 12:10 PM
|
#11572
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 901
|
Quote:
Originally Posted by Funkybot
If I share my MFTwister setup (and a few other users have the device too so they may have their own takes on that), then I'd share any relevant fx.zon's. A user could then re-map those as needed, or just take them as-is. But let's say cjewellstudio's MFTwister didn't line up with mine because we use different widget names and even have the hardware configured differently, then there's a chance you could run into issues. So then it becomes trickier.
For instance, MixMinkey uses "RotaryPush" on the C4 as his widget name, I use "Button" on my MFTwister, cjewellstudios uses another variation...I think cjewellstudios and I are leaning towards "let's all just adapt RotaryPush for maximum compatibility" but there's nothing in CSI that mandates that. The solution might be as simple as a find and replace across a few folders, but with flexibility comes the potential for greater incompatibility. But that's just the Reaper/CSI way. Let users figure it out.
Otherwise, the fx.zon's can actually be pretty portable, even across devices, as long as users kind of adhere to a kind of "best practice naming convention." For instance, "banks of 8, widgets called A1 up to A8, then B1, use Rotary Push for any buttons, RotaryA1 for encoders/knobs, and FaderA1 for faders, and DisplayUpperA1/DisplayLowerA1 for displays..." If people just naturally adhere to that, there's a good chance fx.zon's could be shared pretty easily. It's just not a rule that you do it that way.
In an ideal world, a programer would take up building a mapping front-end for CSI with some slick FX Lean capabilities for easy .zon generation. Until then, there's MixMonkey's spreadsheet which is probably the next best thing.
|
Yeah, Mixmonkeys configurationator is an awesome bit of work, from the first version it made life so much easier, as I own a C4 it's really a no brainer.
Naming convention would be key to portability, and even then it may not work.
That's why I thought a database of fxzones for compatibile surfaces would be useful.
|
|
|
11-19-2020, 12:13 PM
|
#11573
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,814
|
Yeah, that spreadsheet. I tried to use it, but I'm not an MS Office user. The online free version of MS Office doesn't support a lot of stuff in it. Libreoffice won't run some of the stuff, so that's that.
Certainly agree on keeping to reasonable conventions.
The major bummer is setting up fx mappings. The Avid Icon series was really good at setting up custom zones. Pick the parameter, move/touch the control, done. Custom per track in the Icon's case, not per focused fx, but that shouldn't be a huge deal.
Maybe we can recruit some folks in the scripting forum section for a setup GUI. The question is how CSI will communicate with a Lua script, and how can Lua detect midi/osc/eucon inputs. Lua has a bunch of GUI libraries already, so it's a natural choice for a scripting solution.
|
|
|
11-19-2020, 12:14 PM
|
#11574
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by MixMonkey
@Funkybot Do stepped parameters work for you in OSC?
|
On OSC "Rotaries" yes (which makes sense because they're absolute, not relative). On buttons...I'll let you know later tonight when I can check after work. I've been the FX Configurator the last few days and haven't mapped stepped params to buttons yet in any of the few zones I've created to date.
|
|
|
11-19-2020, 02:47 PM
|
#11575
|
Human being with feelings
Join Date: Apr 2018
Posts: 123
|
Rules of thum when converting mMST/ZON files
Hi,
Are there any rules for converting older zon/mst files to the new format or has the format changed completely and I need to rebuild from scratch. I will do this if I have to, but the zon files for the XTouch work really well.
|
|
|
11-19-2020, 02:52 PM
|
#11576
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by Equitone
Hi,
Are there any rules for converting older zon/mst files to the new format or has the format changed completely and I need to rebuild from scratch. I will do this if I have to, but the zon files for the XTouch work really well.
|
You don't have to rebuild from scratch (apart from CSI.ini) Just make the changes detailed in the post I directed you to and see where you are after that
|
|
|
11-19-2020, 04:32 PM
|
#11577
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by MixMonkey
Just got around to doing a bit of OSC testing and I seem to have lost stepped parameters (including toggling of buttons) in FX zones. Mute, Solo etc are unaffected.
Pressing a button set up as:
Code:
RotaryPushB1 FXParam 2 [ 0.0 1.0 ]
...will turn the parameter on, but not off.
It all works fine on the (real) C4.
|
Over here, I'm getting Toggling between minimum and maximum value, but no steps in between.
Code:
DisplayButtonA3 FXParamNameDisplay 3 "Type Up"
ButtonA3 FXParam 3 [ 0.0 0.34 0.67 1.0 ]
So that will jump from 0.0 and 1.0 but skip the two steps between. Toggling has been working here all along.
Don't know if it matters, but in the TouchOSC Editor these are setup as "Toggle Buttons" not "Push Buttons." The latter I recall just being momentary presses, which isn't what I wanted.
|
|
|
11-19-2020, 04:50 PM
|
#11578
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by MixMonkey
That all sounds right, no need for Send|1-8 line. I blank rows A and B when the FX menu activates, C and D blank (or are overwritten) when Send and FXMenu zones activate. The only recent FX zone change was the removal of Toggle+. My C4.zon looks like this:
Code:
Zone Home
OnTrackSelection MapSelectedTrackFXToMenu
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
"C4_Buttons"
IncludedZonesEnd
ZoneEnd
Zone "C4_Buttons"
Marker Shift
Track Option
ChanStrip Control
Function Alt
BankLeft TrackBank "-8"
BankRight TrackBank "8"
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
Lock MapSelectedTrackFXToMenu
Lock MapSelectedTrackSendsToWidgets
Shift+Lock Reaper "_S&M_FXBYPALL" //Toggle all FX bypass for selected track
SpotErase Reaper "_S&M_TOGLFXCHAIN" // Toggle FX chain window for selected track
Split Reaper "_S&M_WNCLS4" //Close all FX chain windows
Split Reaper "_S&M_WNCLS3" //Close all floating FX windows
Shift NoAction
Option NoAction
Control NoAction
Alt NoAction
ZoneEnd
Zone "Send"
SendNavigator
DisplayUpperC| TrackSendNameDisplay
DisplayLowerC| TrackSendVolumeDisplay
RotaryC| TrackSendVolume [ (0.001,0.02,0.04,0.06,0.1) ]
RotaryPushC| TrackSendMute
ZoneEnd
Zone "FXMenu"
FXMenuNavigator
DisplayUpperA| NoAction
DisplayLowerA| NoAction
RotaryPushA| NoAction
RotaryA| NoAction
DisplayUpperB| NoAction
DisplayLowerB| NoAction
RotaryPushB| NoAction
RotaryB| NoAction
DisplayUpperD| FXMenuNameDisplay
DisplayLowerD| NoAction
RotaryD| NoAction
RotaryPushD| Reaper "_S&M_SHOWFXCHAIN|"
Shift+RotaryPushD| Reaper "_S&M_FXBYP|" //Bypass FX Slot
Option+RotaryPushD| Reaper "_S&M_FXOFF|" //Offline FX slot
RotaryPushD| GoFXSlot
ZoneEnd
|
Thanks, took me a couple days to figure out it was "SendNavigator" that needed to be changed. Now my sends are working all as expected.
one thing is still very different, I don't use FXMenu I use MapSelectedTracktoWidgets, and I have my C4 setup like a channel strip, when I select a track previously ONLY the params/widgets that had mappings were visible, all others were blank. Now the old params remain on widgets with nothing mapped for that selected track, pretty mess.
So what changed that I now have to change here to get them blank when they should be blank? Do I now have to remap all my plugins again to add NoAction or something like that?
|
|
|
11-19-2020, 05:04 PM
|
#11579
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by Funkybot
Over here, I'm getting Toggling between minimum and maximum value, but no steps in between.
Code:
DisplayButtonA3 FXParamNameDisplay 3 "Type Up"
ButtonA3 FXParam 3 [ 0.0 0.34 0.67 1.0 ]
So that will jump from 0.0 and 1.0 but skip the two steps between. Toggling has been working here all along.
Don't know if it matters, but in the TouchOSC Editor these are setup as "Toggle Buttons" not "Push Buttons." The latter I recall just being momentary presses, which isn't what I wanted.
|
That's what I get here. It should work with the 'Press' button (it did before)
With the 'Toggle' button, the action happens when you release the button, not when you press it. I use them for Modifiers (which always latch on OSC and don't seem to work at all with Press.)
|
|
|
11-19-2020, 05:29 PM
|
#11580
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by poetnprophet
one thing is still very different, I don't use FXMenu I use MapSelectedTracktoWidgets, and I have my C4 setup like a channel strip, when I select a track previously ONLY the params/widgets that had mappings were visible, all others were blank. Now the old params remain on widgets with nothing mapped for that selected track, pretty mess.
So what changed that I now have to change here to get them blank when they should be blank? Do I now have to remap all my plugins again to add NoAction or something like that?
|
I guess they don't auto blank any more under the new architecture. The solution would be to see if you can blank the C4 when you change track.
Maybe create a zone like this:
Code:
Zone "Blank"
DisplayUpperA| NoAction
DisplayLowerA| NoAction
RotaryPushA| NoAction
RotaryA| NoAction
DisplayUpperB| NoAction
DisplayLowerB| NoAction
RotaryPushB| NoAction
RotaryB| NoAction
DisplayUpperC| NoAction
DisplayLowerC| NoAction
RotaryPushC| NoAction
RotaryC| NoAction
DisplayUpperD| NoAction
DisplayLowerD| NoAction
RotaryPushD| NoAction
RotaryD| NoAction
ZoneEnd
...and GoZone to it using the same button you use for MapSelectedTracktoWidgets ( before MapSelectedTracktoWidgets)
Let me know how you get on.
|
|
|
11-19-2020, 05:52 PM
|
#11581
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by MixMonkey
I guess they don't auto blank any more under the new architecture. The solution would be to see if you can blank the C4 when you change track.
Maybe create a zone like this:
Code:
Zone "Blank"
DisplayUpperA| NoAction
DisplayLowerA| NoAction
RotaryPushA| NoAction
RotaryA| NoAction
DisplayUpperB| NoAction
DisplayLowerB| NoAction
RotaryPushB| NoAction
RotaryB| NoAction
DisplayUpperC| NoAction
DisplayLowerC| NoAction
RotaryPushC| NoAction
RotaryC| NoAction
DisplayUpperD| NoAction
DisplayLowerD| NoAction
RotaryPushD| NoAction
RotaryD| NoAction
ZoneEnd
...and GoZone to it using the same button you use for MapSelectedTracktoWidgets ( before MapSelectedTracktoWidgets)
Let me know how you get on.
|
I'm not sure what you mean by the same button I use before mapselectwidgets, I don't press a button, I simply change tracks in the various ways to do that.
|
|
|
11-19-2020, 06:02 PM
|
#11582
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by poetnprophet
I'm not sure what you mean by the same button I use before mapselectwidgets, I don't press a button, I simply change tracks in the various ways to do that.
|
So do you use
Code:
OnTrackSelection MapSelectedTracktoWidgets
..?
|
|
|
11-19-2020, 06:20 PM
|
#11583
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Yes, here is what it looks like, I don't know how you guys do that box thing with the code text:
Code:
Zone "Home"
OnTrackSelection MapSelectedTrackSendsToWidgets
OnTrackSelection MapSelectedTrackFXToWidgets
/OnFXFocus MapFocusedFXToWidgets
SlotUp Reaper _S&M_SELFXPREV
SlotDown Reaper _S&M_SELFXNEXT
TrackL Reaper _6db7ce90e786a64d931d2e0a70c134b3
TrackR Reaper _7bd94bde9f6b394d8af68e30b1bdc1b4
BankLeft Reaper _S&M_WNONLY1
BankRight Reaper _S&M_WNONLY2
ChannelLeft Reaper _da961e76f4ab7d47be2d800d188c934f
ChannelRight Reaper _02153033d77e5145a4bf075329c64327
Split Reaper "8"
Marker Reaper "24917"
ChanStrip Reaper "24920"
Shift Shift
Alt Reaper _06625f543425f2499a143eb92ce7ee46
Control Control
Option Reaper "24901"
Lock Reaper _ed5d588478deee4fb2309fad4b01b027
Function Reaper "24914"
Track Reaper "24913"
ZoneEnd
Zone "Send"
SendNavigator
DisplayUpperA| TrackSendNameDisplay
DisplayLowerA| TrackSendVolumeDisplay
RotaryPushA| TrackSendMute
RotaryA| TrackSendVolume
ZoneEnd
edit, I realized I posted my old one, not the newly modified one. OOOOPS here is the modified zon.
Last edited by poetnprophet; 11-19-2020 at 06:28 PM.
|
|
|
11-19-2020, 06:24 PM
|
#11584
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
That’s done like this:
[bode]
Your text
[/bode]
Except replace bode with code.
|
|
|
11-19-2020, 06:27 PM
|
#11585
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
thanks!!
|
|
|
11-19-2020, 06:27 PM
|
#11586
|
Human being with feelings
Join Date: Jun 2018
Posts: 705
|
Quote:
Originally Posted by airon
Maybe we can recruit some folks in the scripting forum section for a setup GUI. The question is how CSI will communicate with a Lua script, and how can Lua detect midi/osc/eucon inputs. Lua has a bunch of GUI libraries already, so it's a natural choice for a scripting solution.
|
Quote:
Originally Posted by Funkybot
In an ideal world, a programer would take up building a mapping front-end for CSI with some slick FX Lean capabilities for easy .zon generation. Until then, there's MixMonkey's spreadsheet which is probably the next best thing.
|
I'd be very interested in something like this for obvious reasons. Unfortunately I can't program to save my life. But if you guys get someone to work on this, I would love to help. Alternatively, I may have to have someone do it for me anyway.
|
|
|
11-19-2020, 06:36 PM
|
#11587
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Try adding something like this:
Code:
OnTrackSelection GoZone Blank
OnTrackSelection MapSelectedTrackFXToWidgets
Zone "Blank"
DisplayUpperA| NoAction
DisplayLowerA| NoAction
RotaryPushA| NoAction
RotaryA| NoAction
DisplayUpperB| NoAction
DisplayLowerB| NoAction
RotaryPushB| NoAction
RotaryB| NoAction
DisplayUpperC| NoAction
DisplayLowerC| NoAction
RotaryPushC| NoAction
RotaryC| NoAction
DisplayUpperD| NoAction
DisplayLowerD| NoAction
RotaryPushD| NoAction
RotaryD| NoAction
ZoneEnd
Also, the sends zone should look like this:
Code:
Zone "Send"
SendNavigator
DisplayUpperA| TrackSendNameDisplay
DisplayLowerA| TrackSendVolumeDisplay
RotaryA| TrackSendVolume [ (0.001,0.02,0.04,0.06,0.1) ]
RotaryPushA| TrackSendMute
ZoneEnd
|
|
|
11-19-2020, 06:45 PM
|
#11588
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Ahhh, now I see what you did there. Brilliant idea, let me try it real quick.
|
|
|
11-19-2020, 06:55 PM
|
#11589
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Ok, so it sort of works. But, for folder tracks it doesn't work coming from or going to a folder track. Weird huh?
and, either way I don't have this issue with sends...if that matters.
|
|
|
11-19-2020, 07:08 PM
|
#11590
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
|
Quote:
Originally Posted by poetnprophet
Ok, so it sort of works. But, for folder tracks it doesn't work coming from or going to a folder track. Weird huh?
and, either way I don't have this issue with sends...if that matters.
|
Not sure why it would be different for folders (I'm not a big folder fan ) When you say you don't have the problem with sends, do you mean that the sends blank as they should when you move from track to track? That's what happens here too, also for the FXMenu.
I should point out that I take care of this on the FX.zon level. If a Rotary/Push/Display isn't being used in an FX.zon, I set it to NoAction.
|
|
|
11-19-2020, 08:28 PM
|
#11591
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by MixMonkey
For the plugins that don't play fair, I use BlueCat Patchwork (super handy plugin ). I put the plugin in Patchwork, assign the parameter to one of its controllers (they run from 0-100%) You can increment them 1% at a time with the up down arrows, so it's easy to see where the steps are.
|
This tip just got me through mapping out T-Racks Precision Comp/Limiter (33609). That thing has stepped parameters for everything and the two threshold knobs map very oddly. Patchwork to the rescue!
|
|
|
11-19-2020, 08:40 PM
|
#11592
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
UHHH WOW!
Honestly, I've long thought about this, but often just said to myself "no way that's going to work"
However:
RotaryC| TrackOutputMeterMaxPeakLR
Check it out!
https://drive.google.com/file/d/1ASz...ew?usp=sharing
Twister Led rings as meters
|
|
|
11-19-2020, 08:53 PM
|
#11593
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by MixMonkey
Not sure why it would be different for folders (I'm not a big folder fan ) When you say you don't have the problem with sends, do you mean that the sends blank as they should when you move from track to track? That's what happens here too, also for the FXMenu.
I should point out that I take care of this on the FX.zon level. If a Rotary/Push/Display isn't being used in an FX.zon, I set it to NoAction.
|
yea, it just means I have to go back through all my stuff again. If the new configurator works as well as the old one, it shouldn't take me too long relatively speaking. It'll be good to maybe rethink my setup anyway, etc....but now is not the time for all that...
always appreciate everyone's strategies and solutions here!
edit, yes the sends work perfectly, only taking up the space they need.
|
|
|
11-19-2020, 08:58 PM
|
#11594
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by cjewellstudios
|
That's pretty neat! Who knew!
|
|
|
11-19-2020, 08:59 PM
|
#11595
|
Human being with feelings
Join Date: Jun 2018
Posts: 705
|
Quote:
Originally Posted by cjewellstudios
|
Nice.
Hey, I have a question for you and all those using MFT. I see that rather than having single LEDs all around, that the bottom 3 spots are combined as a single large LED. And Now I can see that you are using this as an indicator of perhaps a track being muted. So a certain color on this larger LED can signify different things? Am I correct in this?
The reason I'm asking is because my unit has 18 single LEDs around the encoder and I'm wondering if it makes sense to have the bottom 3 LEDs combined into one large one that will act as an indicator of some sort? Does this make sense? Would you rather have 18 single LEDs or 3 LED Indicator at the bottom and 15 single LEDs around?
UPDATE: One more question? are all the LEDs RGB? or just the bottom one?
|
|
|
11-19-2020, 09:28 PM
|
#11596
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by siniarch
Nice.
Hey, I have a question for you and all those using MFT. I see that rather than having single LEDs all around, that the bottom 3 spots are combined as a single large LED. And Now I can see that you are using this as an indicator of perhaps a track being muted. So a certain color on this larger LED can signify different things? Am I correct in this?
The reason I'm asking is because my unit has 18 single LEDs around the encoder and I'm wondering if it makes sense to have the bottom 3 LEDs combined into one large one that will act as an indicator of some sort? Does this make sense? Would you rather have 18 single LEDs or 3 LED Indicator at the bottom and 15 single LEDs around?
UPDATE: One more question? are all the LEDs RGB? or just the bottom one?
|
I’d much rather have the bottom LEDs to be merged into a single color to potentially reflect the button state like the MFTwister. The colors are helpful for toggle states and more. They are RGB. The individual LEDs can’t be colored by end users, but the device itself can make the 12 o’clock LED a different color, meant to indicate center pan. It’s an option in the MF Utility. A nice option to have if you’re using those encoders for Pan. So while I can’t have CSI change the encoder ring colors, the hardware encoders support it.
|
|
|
11-19-2020, 09:28 PM
|
#11597
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by siniarch
Nice.
Hey, I have a question for you and all those using MFT. I see that rather than having single LEDs all around, that the bottom 3 spots are combined as a single large LED. And Now I can see that you are using this as an indicator of perhaps a track being muted. So a certain color on this larger LED can signify different things? Am I correct in this?
The reason I'm asking is because my unit has 18 single LEDs around the encoder and I'm wondering if it makes sense to have the bottom 3 LEDs combined into one large one that will act as an indicator of some sort? Does this make sense? Would you rather have 18 single LEDs or 3 LED Indicator at the bottom and 15 single LEDs around?
UPDATE: One more question? are all the LEDs RGB? or just the bottom one?
|
Yes precisely. Geoff wrote a feedback processor to send rgb values to the MFT.
You can use them to signify solo or mute toggles. You can also send rgb values in fx zones. Since the mft doesn't have any displays, the colors really help organize fx zones for me. For example an ssl style plugin you'd have a different color for each eq band.
On the MFT, it's just the bottom bar that has rgb (I think I'm right on that, but the twister is so customizable, there may actually be a setting somewhere that changes that)
As far as your controller project. I really dig how they have this set up with the bottom bar rgb led but I suppose that having the whole knob respond to rgb would be just as cool.
Actually, thinking out loud here, the indicator on the bottom is much better because if you have a value of zero, there will be no led's lit for color. I suppose that's why they did that
|
|
|
11-19-2020, 09:36 PM
|
#11598
|
Human being with feelings
Join Date: Jun 2018
Posts: 705
|
Quote:
Originally Posted by cjewellstudios
Yes precisely. Geoff wrote a feedback processor to send rgb values to the MFT.
You can use them to signify solo or mute toggles. You can also send rgb values in fx zones. Since the mft doesn't have any displays, the colors really help organize fx zones for me. For example an ssl style plugin you'd have a different color for each eq band.
On the MFT, it's just the bottom bar that has rgb (I think I'm right on that, but the twister is so customizable, there may actually be a setting somewhere that changes that)
As far as your controller project. I really dig how they have this set up with the bottom bar rgb led but I suppose that having the whole knob respond to rgb would be just as cool.
Actually, thinking out loud here, the indicator on the bottom is much better because if you have a value of zero, there will be no led's lit for color. I suppose that's why they did that
|
I'm designing the case right now, so, now it's the time to make the bottom 3 be a larger bar style indicator if that's what makes more sense.
All my Ring LEDs are RGB. So we can even make them all be one color to signify a certain track. Or even make them green at the beginning and the Yellow or Orange and then RED when they are about to clip. It's just a matter of figuring it out what's most beneficial to users. But I'll stop hijacking this thread for my project. Please feel free to respond on the other thread as I think there are plenty of things that people want to discuss regarding CSI that doesn't relate to my project.
|
|
|
11-19-2020, 11:21 PM
|
#11599
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
I'm looking at my C4 and XT minis, and ProXs, all of the encoders have a sort of "blank spot" from the 7:00-5:00 position, so it would be very useful and clever to use that blank spot for something useful like an indicator, and I think your rings are 360 so you could definitely spare those 3 for that, in my opinion.
woops, I went and commented on that anyway, my bad. just ignore what I said haha
Last edited by poetnprophet; 11-19-2020 at 11:44 PM.
|
|
|
11-20-2020, 01:22 AM
|
#11600
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
|
New build is up.
CSI v1_0.zip
Oops, sorry guys, I broke Stepped params for OSC when I was muckin' about with Hold.
Should be fixed now
__________________
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
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 06:38 PM.
|