|
|
|
04-20-2020, 05:45 PM
|
#8561
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Also, now that we now this works conceptually, I think it may be a good idea to bake in some presets. Here's what I'm thinking...
Custom Values
Code:
Rotary16 FXParam "3" "Blend" [ (0.001,0.002,0.003,0.005,0.0075,0.015,0.025,0.040,0.05,0.06,0.07) ]
No Acceleration
Code:
Rotary16 FXParam "3" "Blend" [ ]
Linear Acceleration
Code:
Rotary16 FXParam "3" "Blend" [ (lin) ]
Exponential Taper
Code:
Rotary16 FXParam "3" "Blend" [ (exp) ]
Logarithmic Taper
Code:
Rotary16 FXParam "3" "Blend" [ (log) ]
No need for lookup tables (well Geoff can build those behind the scenes - at least in my head) or files in folders. But this would allow for some built in options + customization + completely disabling acceleration if you hate it.
Just a friendly suggestion.
I'd probably just park everything on exponential and never worry about acceleration again. If you do that though Geoff, I think a max speed around .075 for the fastest acceleration settings would be good.
|
|
|
04-20-2020, 05:45 PM
|
#8562
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Funkybot
Not sure if this is a bug or me just not getting the finer points of the new syntax, but I have an encoder widget mapped to a 3 step parameter as such...
Code:
Rotary11 FXParam "11" "Tone Shift" [ 0.0 0.5 1.0 ]
Code:
Widget Rotary11
Encoder b0 0a 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]
FB_Fader7Bit b0 0a 00
WidgetEnd
Turning the encoder counter clockwise repeatedly cycles through the three steps at way too fast a setting to be useful. Also, after it gets to the top, it goes back to the bottom and starts over (endless looping!).
Geoff, is there a way to slow this down to get a more useful range out of stepped parameters+encoders? Also, is there a way to set upper/lower bounds so stepped parameters don't spin endlessly?
|
Yeah, not sure how to handle all that, keep playing around, I'm sure we will need some tuning
__________________
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
|
|
|
04-20-2020, 05:46 PM
|
#8563
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Funkybot
Also, now that we now this works conceptually, I think it may be a good idea to bake in some presets. Here's what I'm thinking...
Custom Values
Code:
Rotary16 FXParam "3" "Blend" [ (0.001,0.002,0.003,0.005,0.0075,0.015,0.025,0.040,0.05,0.06,0.07) ]
No Acceleration
Code:
Rotary16 FXParam "3" "Blend" [ ]
Linear Acceleration
Code:
Rotary16 FXParam "3" "Blend" [ (linear) ]
Exponential Taper
Code:
Rotary16 FXParam "3" "Blend" [ (exponential) ]
Logarithmic Taper
Code:
Rotary16 FXParam "3" "Blend" [ (logarathmic) ]
No need for lookup tables, files in folders, and allows for some built in options + customization + completely disabling acceleration if you hate it.
Just a friendly suggestion.
|
Yes, opens up a lot of possibilities...
__________________
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
|
|
|
04-20-2020, 05:49 PM
|
#8564
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
New build is up.
If things went well you should be able to do this now with contiguous values:
Code:
Widget Rotary1
Encoder b0 00 7f [ < 3f-2f > 41-51 ]
FB_Fader7Bit b0 00 00
WidgetEnd
__________________
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
|
|
|
04-20-2020, 05:49 PM
|
#8565
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
Nice one Geoff!
Working here with:
Code:
Widget RotaryD1
Encoder b0 18 7f [ > 01 04 08 0C 0f < 41 44 48 4c 4f ]
FB_Encoder b0 18 7f
WidgetEnd
and
Code:
DisplayUpperD1 FXParamNameDisplay 0 "Thresh"
DisplayLowerD1 FXParamValueDisplay 0
RotaryD1 FXParam 0 [ (0.001,0.005,0.01,0.05,0.1) 0.0-1.0 ]
Toggle+RotaryPushD1 NoAction
Hours of fun to be had playing with the acceleration factors!
|
Is this a standard mapping for all rotarys or will it be different for different surfaces and parameters ? This a little over my head so far. And if i remember correctly mixmonkey you use an MCU? My surface is the Prox which is basically an MCU copy and was hoping if i just copy what u have here it will work with mine ??
|
|
|
04-20-2020, 05:58 PM
|
#8566
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
If things went well you should be able to do this now with contiguous values:
Code:
Widget Rotary1
Encoder b0 00 7f [ < 3f-2f > 41-51 ]
FB_Fader7Bit b0 00 00
WidgetEnd
|
So even if i update to this new build i will be able to keep the old way ?? Ive been going through the posts . This is wayyyyy over my head but i still want to update cause i will catch on eventually...i hope ...but i can still stay the old way after updating ??
|
|
|
04-20-2020, 06:00 PM
|
#8567
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
Not sure if this is a bug or me just not getting the finer points of the new syntax, but I have an encoder widget mapped to a 3 step parameter as such...
Code:
Rotary11 FXParam "11" "Tone Shift" [ 0.0 0.5 1.0 ]
Code:
Widget Rotary11
Encoder b0 0a 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]
FB_Fader7Bit b0 0a 00
WidgetEnd
Turning the encoder counter clockwise repeatedly cycles through the three steps at way too fast a setting to be useful. Also, after it gets to the top, it goes back to the bottom and starts over (endless looping!).
Geoff, is there a way to slow this down to get a more useful range out of stepped parameters+encoders? Also, is there a way to set upper/lower bounds so stepped parameters don't spin endlessly?
|
Not just you, I'm getting this too. Stepped parameters wrap round at max instead of stopping and only work in a CW direction.
Would be good to be able to set the acceleration values for them in the same way as continuous parameters.
|
|
|
04-20-2020, 06:00 PM
|
#8568
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
So even if i update to this new build i will be able to keep the old way ?? Ive been going through the posts . This is wayyyyy over my head but i still want to update cause i will catch on eventually...i hope ...but i can still stay the old way after updating ??
|
Yes, the new way is totally optional, all the old .mst files will still work just fine.
__________________
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
|
|
|
04-20-2020, 06:03 PM
|
#8569
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
If things went well you should be able to do this now with contiguous values:
Code:
Widget Rotary1
Encoder b0 00 7f [ < 3f-2f > 41-51 ]
FB_Fader7Bit b0 00 00
WidgetEnd
|
Works like a charm!
|
|
|
04-20-2020, 06:05 PM
|
#8570
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Cragster
Is this a standard mapping for all rotarys or will it be different for different surfaces and parameters ? This a little over my head so far. And if i remember correctly mixmonkey you use an MCU? My surface is the Prox which is basically an MCU copy and was hoping if i just copy what u have here it will work with mine ??
|
This is for the C4, not the MCU. The MCU .mst encoder values would be:
Code:
Widget Rotary1
Encoder b0 00 7f [ < 01-0f > 41-4f ]
FB_Encoder b0 00 7f
WidgetEnd
I haven't tried this, so you'll have to go boldly..
|
|
|
04-20-2020, 06:09 PM
|
#8571
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Funkybot
Works like a charm!
|
Cool !!
__________________
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
|
|
|
04-20-2020, 06:11 PM
|
#8572
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
Not just you, I'm getting this too. Stepped parameters wrap round at max instead of stopping and only work in a CW direction.
Would be good to be able to set the acceleration values for them in the same way as continuous parameters.
|
Here's what I'm thinking: for stepped parameters CSI does NOT ignore acceleration on encoders. What we* do instead is behind the scenes convert the parameter into 1,000 slices from 0.000, 0.001...1.0. Then, CSI only stops at the defined steps, but encoder acceleration still works.
So for example:
Rotary4 FXParam "8" "Release" [ (0.001,0.0025,0.005,0.0075,0.033,0.05) 0.0 0.5 1.0 ]
Anything in the parenthesis will dictate the acceleration scale. Then CSI interpolates between the parameter steps, in going from the user defined step 1 to step 2 or vice versa, but it only actually "snaps into place" when the noted step value has been reached. The idea is users could still set random step sizes this way. CSI would just need to assume the first step is always the "bottom" and last step always the "top."
Does that make any sense?
*By "we" I mean Geoff.
Last edited by Funkybot; 04-20-2020 at 06:17 PM.
|
|
|
04-20-2020, 06:12 PM
|
#8573
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
Not just you, I'm getting this too. Stepped parameters wrap round at max
|
Stepped parameters have always wrapped around at max, remember our discussions on this ?
What's different is that now we are using rotaries instead of buttons to adjust them
Will have to ponder this a bit...
__________________
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
|
|
|
04-20-2020, 06:16 PM
|
#8574
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Stepped parameters have always wrapped around at max, remember our discussions on this ?
What's different is that now we are using rotaries instead of buttons to adjust them
Will have to ponder this a bit...
|
Ahem, Rotaries have always stopped at the endpoints, min and max. Presses wrap round, but only in a positive going direction- remember?
|
|
|
04-20-2020, 06:23 PM
|
#8575
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
Ahem, Rotaries have always stopped at the endpoints, min and max. Presses wrap round, but only in a positive going direction- remember?
|
Yes all true, except for one thing.
We have not used rotaries with stepped values before today that I know of, we've always used buttons with stepped values thus far.
Did I miss something here ?
Have we done this somewhere before that I don't recall ?
The reason I ask is I don't see anything in the code to stop stepped values at the top.
I think this all means we need improvement when using a rotary with stepped values.
That's the pondering I was talking about.
But hey, I'm really old and maybe I'm not remembering something really important
__________________
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
Last edited by Geoff Waddington; 04-20-2020 at 06:33 PM.
|
|
|
04-20-2020, 06:33 PM
|
#8576
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
Yes all true, except for one thing.
We have not used rotaries with stepped values before today that I know of, we've always used buttons with stepped values thus far.
Did I miss something here ?
Have we done this somewhere before that I don't recall ?
The reason I ask is I don't see anything in the code to stop stepped values at the top.
I think this all means we need improvement when using a rotary with stepped values.
That's the pondering I was talking about.
But hey, I'm really old and maybe I'm not remembering something important
|
Dont know if this is what u mean but i use the rotaries with step parameter. Like if a parameter has 3 values or choices in it ill use
Rotary1 fxparam whatever [ 0.0 0.5 1.0 ]
Works great
And it also could mean i dont know what im talking about. That your probly referring to something totally different
|
|
|
04-20-2020, 06:34 PM
|
#8577
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Geoff, maybe you didn't intend it, but I believe Mix Monkey and I were both pretty extensively using rotaries with stepped values.
Code:
Zone "VST: Sonsig Rev-A (Relab Development)"
FocusedFXNavigator
Rotary1 FXParam "5" "Pre Delay"
Rotary2 FXParam "0" "Time"
Rotary3 FXParam "2" "Size" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary4 FXParam "9" "Diffusion" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary5 FXParam "3" "Character" [ 0.0 0.5 1.0 ]
Rotary6 FXParam "4" "Ensemble" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary7 FXParam "7" "Brightness" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary8 FXParam "8" "Hi Decay" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary9 FXParam "10" "Tilt" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary10 FXParam "11" "Low Tilt" [ 0.0 0.167 0.333 0.5 0.667 0.833 1.0 ]
Rotary11 NoAction
Rotary12 FXParam "12" "Width"
Rotary13 FXParam "14" "In"
Rotary14 FXParam "15" "Out"
Rotary15 FXParam "16" "Mode" [ 0.0 0.5 1.0 ]
Rotary16 FXParam "13" "Blend"
ZoneEnd
Works fine with Fader7bit widgets, but way too fast with encoders (that plus spinning).
|
|
|
04-20-2020, 06:34 PM
|
#8578
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
Dont know if this is what u mean but i use the rotaries with step parameter. Like if a parameter has 3 values or choices in it ill use
Rotary1 fxparam whatever [ 0.0 0.5 1.0 ]
Works great
|
Does it wrap around at the top ?
__________________
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
|
|
|
04-20-2020, 06:35 PM
|
#8579
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Funkybot
Geoff, maybe you didn't intend it, but I believe Mix Monkey and I were both pretty extensively using rotaries with stepped values.
Code:
Zone "VST: Sonsig Rev-A (Relab Development)"
FocusedFXNavigator
Rotary1 FXParam "5" "Pre Delay"
Rotary2 FXParam "0" "Time"
Rotary3 FXParam "2" "Size" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary4 FXParam "9" "Diffusion" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary5 FXParam "3" "Character" [ 0.0 0.5 1.0 ]
Rotary6 FXParam "4" "Ensemble" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary7 FXParam "7" "Brightness" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary8 FXParam "8" "Hi Decay" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary9 FXParam "10" "Tilt" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary10 FXParam "11" "Low Tilt" [ 0.0 0.167 0.333 0.5 0.667 0.833 1.0 ]
Rotary11 NoAction
Rotary12 FXParam "12" "Width"
Rotary13 FXParam "14" "In"
Rotary14 FXParam "15" "Out"
Rotary15 FXParam "16" "Mode" [ 0.0 0.5 1.0 ]
Rotary16 FXParam "13" "Blend"
ZoneEnd
|
And they weren't wrapping?
__________________
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
|
|
|
04-20-2020, 06:37 PM
|
#8580
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
Does it wrap around at the top ?
|
No it stops
|
|
|
04-20-2020, 06:38 PM
|
#8581
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
No it stops
|
OK, looks like a bug.
I had never used rotaries that way, you guys are just too ingenious for me
__________________
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
|
|
|
04-20-2020, 06:40 PM
|
#8582
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
And they weren't wrapping?
|
No they weren't wrapping. Did EncoderPlainReverse change at all? I could always go back to those widgets and confirm.
Wish I had an old CSI build laying around but I lost some files recently and my CSI builds going back the last few months were among them.
|
|
|
04-20-2020, 06:40 PM
|
#8583
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Funkybot
Geoff, maybe you didn't intend it, but I believe Mix Monkey and I were both pretty extensively using rotaries with stepped values.
Code:
Zone "VST: Sonsig Rev-A (Relab Development)"
FocusedFXNavigator
Rotary1 FXParam "5" "Pre Delay"
Rotary2 FXParam "0" "Time"
Rotary3 FXParam "2" "Size" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary4 FXParam "9" "Diffusion" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary5 FXParam "3" "Character" [ 0.0 0.5 1.0 ]
Rotary6 FXParam "4" "Ensemble" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary7 FXParam "7" "Brightness" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary8 FXParam "8" "Hi Decay" [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
Rotary9 FXParam "10" "Tilt" [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
Rotary10 FXParam "11" "Low Tilt" [ 0.0 0.167 0.333 0.5 0.667 0.833 1.0 ]
Rotary11 NoAction
Rotary12 FXParam "12" "Width"
Rotary13 FXParam "14" "In"
Rotary14 FXParam "15" "Out"
Rotary15 FXParam "16" "Mode" [ 0.0 0.5 1.0 ]
Rotary16 FXParam "13" "Blend"
ZoneEnd
Works fine with Fader7bit widgets, but way too fast with encoders (that plus spinning).
|
Ahhh, with Fader7Bit widgets, they are self limiting, they never go beyond 1.0.
By spinning, do you mean wrapping ?
__________________
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
|
|
|
04-20-2020, 06:42 PM
|
#8584
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
OK, looks like a bug.
I had never used rotaries that way, you guys are just too ingenious for me
|
Yes i use rotarys for all the step params using that mapping [....] it works really good
|
|
|
04-20-2020, 06:44 PM
|
#8585
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
OK, looks like a bug.
I had never used rotaries that way, you guys are just too ingenious for me
|
Here you go, this'll jog your memory
https://forum.cockos.com/showpost.ph...postcount=6742
EDIT: About halfway down page 169
|
|
|
04-20-2020, 06:50 PM
|
#8586
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by MixMonkey
|
Right, forgot about the old +/- encoders, eons away in my mind.
OK, so the older encoders should work properly with stepped values, and they shouldn't wrap.
Things should only fall apart when you add the new "[...]" syntax.
Will work on the new Accelerated Encoder, thanks for the memory jog
__________________
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
|
|
|
04-20-2020, 06:56 PM
|
#8587
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Sorry for the break in discussion. Love what's going on with encoders now. I'll wait to dig into that until you guys suss that out before I jump in. You guys do really really well figuring things out.
For now, I got the RGB working in the example that funkybot provided (thanks again, dude)
But haven't got RGB working anywhere else I wanted to yet.
Unless I'm mistaken, you have to address the buttons to address the LED's. If you try to address the Rotaries it won't work. This to me, makes sense because the buttons seem to be tied pretty tightly to the RGB lights (i.e. when you press a button, the LED changes in normal operation)
I'm mapping AIR Compressor to start for simplicity
I tried:
Code:
MFTButton1 { 90 255 0 255 50 0 }
Code:
MFTButton1 NoAction { 90 255 0 255 50 0 }
Code:
MFTButton1 FXParam 9 "Dummy" { 90 255 0 255 50 0 }
Where 9 is greater than the actual number of FXParam's
and finally:
Code:
MFTButton1 FXParam 3 "Attack" { 90 255 0 255 50 0 }
Where " 'FXParam 3 "Attack' " is an actual FXParam and the correct name, but it was already mapped to the corresponding Rotary like this above:
Code:
Rotary1 FXParam 3 "Attack"
The problem is, in FX Zones, most of the time the buttons won't actually have an "FXParam" that I need mapped. So is there a way to address the LED's here without having a parameter attached? Or a correct way to use "dummy" param?
EDIT: I don't need it to have a 2nd color in this instance, I just have that there because that worked for "bypass"
I did try it with just the one rgb value but I vaguely remember seeing if you want one color it's just the same rgb value twice in a row
|
|
|
04-20-2020, 07:07 PM
|
#8588
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Right, forgot about the old +/- encoders, eons away in my mind.
OK, so the older encoders should work properly with stepped values, and they shouldn't wrap.
Things should only fall apart when you add the new "[...]" syntax.
Will work on the new Accelerated Encoder, thanks for the memory jog
|
Terrific! Sorry to spring it on you.
Priority is probably stopping at the ends and being able to go CCW (back down the step list).
Acceleration through stepped parameters can wait, the old encoder stepped through the list at a rate of 1 step = 1 encoder tick and the new encoder still does this if you turn the encoder r e a l l y carefully
EDIT: Not sure if we even need to accelerate through stepped parameters now we have such fine control over the step size and acceleration without using SNL.
Last edited by MixMonkey; 04-20-2020 at 07:22 PM.
|
|
|
04-20-2020, 07:29 PM
|
#8589
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by cjewellstudios
Sorry for the break in discussion. Love what's going on with encoders now. I'll wait to dig into that until you guys suss that out before I jump in. You guys do really really well figuring things out.
For now, I got the RGB working in the example that funkybot provided (thanks again, dude)
But haven't got RGB working anywhere else I wanted to yet....
|
This worked over here:
Code:
Toggle+MFTButton1 FXParam 9 "Dummy" { 90 255 0 255 50 0 }
It will only be the first color, but that's all you wanted anyway.
Last edited by Funkybot; 04-20-2020 at 07:38 PM.
|
|
|
04-20-2020, 07:37 PM
|
#8590
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by Funkybot
Can you go into more detail about what you're trying to accomplish with the lights. Why do you want colored lights on parameters that have no action?
There might be a way to workaround the issue, but I'm still not grasping what you're ultimately trying to accomplish. Can you post the entire fx.zon for Air Compressor and then describe exactly which buttons you want colored lights under?
|
Code:
Zone "VST: AIR Compressor (AIR Music Technology)"
FocusedFXNavigator
Rotary3 FXParam 0 "Threshold"
Rotary9 FXParam 1 "Ratio"
Rotary10 FXParam 2 "Smooth"
Rotary1 FXParam 3 "Attack"
Rotary2 FXParam 4 "Release"
Rotary11 FXParam 5 "Output"
Toggle+MFTButton32 FXParam 6 "Bypass" { 90 255 0 255 50 0 }
Rotary32 FXParam 7 "Wet"
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
Rotary12 NoAction
Rotary13 NoAction
Rotary14 NoAction
Rotary15 NoAction
Rotary16 NoAction
Rotary17 NoAction
Rotary18 NoAction
Rotary19 NoAction
Rotary20 NoAction
Rotary21 NoAction
Rotary22 NoAction
Rotary23 NoAction
Rotary24 NoAction
Rotary25 NoAction
Rotary26 NoAction
Rotary27 NoAction
Rotary28 NoAction
Rotary29 NoAction
Rotary30 NoAction
Rotary31 NoAction
MFTButton1 FXParam 8 "" { 90 255 0 }
MFTButton2 { 90 255 0 }
MFTButton3 { 90 255 0 }
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton9 { 90 255 0 }
MFTButton10 { 90 255 0 }
MFTButton11 { 90 255 0 }
MFTButton12 NoAction
MFTButton13 NoAction
MFTButton14 NoAction
MFTButton15 NoAction
MFTButton16 NoAction
MFTButton17 NoAction
MFTButton18 NoAction
MFTButton19 NoAction
MFTButton20 NoAction
MFTButton21 NoAction
MFTButton22 NoAction
MFTButton23 NoAction
MFTButton24 NoAction
MFTButton25 NoAction
MFTButton26 NoAction
MFTButton27 NoAction
MFTButton28 NoAction
MFTButton29 NoAction
MFTButton30 NoAction
MFTButton31 NoAction
ZoneEnd
That's just at it's current state because I gave up trying different things. I tried all the things in a previous post in a fully sussed out sort of way.
I can't address the Rotaries, as I was saying, otherwise I would just do that. I just couldn't get it to work, even taking the FB_Fader7bit line out of the .mst (which I obviously need) and just trying the FB RGB.
I want to color everything that I'm using in that Zone and leave everything else blank.
|
|
|
04-20-2020, 07:47 PM
|
#8591
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by cjewellstudios
Code:
Zone "VST: AIR Compressor (AIR Music Technology)"
FocusedFXNavigator
Rotary3 FXParam 0 "Threshold"
Rotary9 FXParam 1 "Ratio"
Rotary10 FXParam 2 "Smooth"
Rotary1 FXParam 3 "Attack"
Rotary2 FXParam 4 "Release"
Rotary11 FXParam 5 "Output"
Toggle+MFTButton32 FXParam 6 "Bypass" { 90 255 0 255 50 0 }
Rotary32 FXParam 7 "Wet"
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
Rotary12 NoAction
Rotary13 NoAction
Rotary14 NoAction
Rotary15 NoAction
Rotary16 NoAction
Rotary17 NoAction
Rotary18 NoAction
Rotary19 NoAction
Rotary20 NoAction
Rotary21 NoAction
Rotary22 NoAction
Rotary23 NoAction
Rotary24 NoAction
Rotary25 NoAction
Rotary26 NoAction
Rotary27 NoAction
Rotary28 NoAction
Rotary29 NoAction
Rotary30 NoAction
Rotary31 NoAction
MFTButton1 FXParam 8 "" { 90 255 0 }
MFTButton2 { 90 255 0 }
MFTButton3 { 90 255 0 }
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton9 { 90 255 0 }
MFTButton10 { 90 255 0 }
MFTButton11 { 90 255 0 }
MFTButton12 NoAction
MFTButton13 NoAction
MFTButton14 NoAction
MFTButton15 NoAction
MFTButton16 NoAction
MFTButton17 NoAction
MFTButton18 NoAction
MFTButton19 NoAction
MFTButton20 NoAction
MFTButton21 NoAction
MFTButton22 NoAction
MFTButton23 NoAction
MFTButton24 NoAction
MFTButton25 NoAction
MFTButton26 NoAction
MFTButton27 NoAction
MFTButton28 NoAction
MFTButton29 NoAction
MFTButton30 NoAction
MFTButton31 NoAction
ZoneEnd
That's just at it's current state because I gave up trying different things. I tried all the things in a previous post in a fully sussed out sort of way.
I can't address the Rotaries, as I was saying, otherwise I would just do that. I just couldn't get it to work, even taking the FB_Fader7bit line out of the .mst (which I obviously need) and just trying the FB RGB.
I want to color everything that I'm using in that Zone and leave everything else blank.
|
I edited my reply hoping you hadn’t read it yet. Reread it now for a working solution.
|
|
|
04-20-2020, 09:50 PM
|
#8592
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by Funkybot
I edited my reply hoping you hadn’t read it yet. Reread it now for a working solution.
|
Oh ok Thanks for that. Unfortunately still no dice here. Here's what I have now getting me the same results.
Code:
Zone "VST: AIR Compressor (AIR Music Technology)"
FocusedFXNavigator
Rotary9 FXParam 1 "Ratio"
Rotary10 FXParam 2 "Smooth"
Rotary1 FXParam 3 "Attack"
Rotary2 FXParam 4 "Release"
Rotary11 FXParam 5 "Output"
Rotary32 FXParam 7 "Wet"
Toggle+MFTButton32 FXParam 6 "Bypass" { 90 255 0 255 50 0 }
MFTButton1 FXParam 8 "Dummy1" { 90 255 0 255 50 0 }
MFTButton2 FXParam 9 "Dummy2" { 90 255 0 255 50 0 }
MFTButton3 FXParam 10 "Dummy3" { 90 255 0 255 50 0 }
MFTButton9 FXParam 11 "Dummy4" { 90 255 0 255 50 0 }
MFTButton10 FXParam 12 "Dummy5" { 90 255 0 255 50 0 }
MFTButton11 FXParam 13 "Dummy6" { 90 255 0 255 50 0 }
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
Rotary12 NoAction
Rotary13 NoAction
Rotary14 NoAction
Rotary15 NoAction
Rotary16 NoAction
Rotary17 NoAction
Rotary18 NoAction
Rotary19 NoAction
Rotary20 NoAction
Rotary21 NoAction
Rotary22 NoAction
Rotary23 NoAction
Rotary24 NoAction
Rotary25 NoAction
Rotary26 NoAction
Rotary27 NoAction
Rotary28 NoAction
Rotary29 NoAction
Rotary30 NoAction
Rotary31 NoAction
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton12 NoAction
MFTButton13 NoAction
MFTButton14 NoAction
MFTButton15 NoAction
MFTButton16 NoAction
MFTButton17 NoAction
MFTButton18 NoAction
MFTButton19 NoAction
MFTButton20 NoAction
MFTButton21 NoAction
MFTButton22 NoAction
MFTButton23 NoAction
MFTButton24 NoAction
MFTButton25 NoAction
MFTButton26 NoAction
MFTButton27 NoAction
MFTButton28 NoAction
MFTButton29 NoAction
MFTButton30 NoAction
MFTButton31 NoAction
ZoneEnd
I also tried the "Toggle+" before each one in case that was the key. I've taken alot of guesses here but I'm coming up short.
edit: I forgot to say that is is actually doing *something*
On Rotaries that are not mapped, pushing those buttons allows the MF Twister to use whatever On and Off color are set in the MF Utility for the device. However pushing any one of those buttons that I'm trying to address the LED's, it actually doesn't change, just stays at the color it's at (which is not the color I'm trying to change it to )
EDIT 2:
SHEESH.... I figured it out finally. For those other params... The colors need to be switched. I still have to look at which one is actually the important one lol but switching them did the trick.
Last edited by cjewellstudios; 04-20-2020 at 10:01 PM.
|
|
|
04-20-2020, 11:48 PM
|
#8593
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Quote:
Originally Posted by Geoff Waddington
I don't even know if these new acceleration methods will work worth a sh^t
|
I think that's a new phrase to learn,
"S H to the Power of T"
:-)
|
|
|
04-21-2020, 01:12 AM
|
#8594
|
Human being with feelings
Join Date: Jul 2009
Posts: 429
|
New to this thread. First off, great idea!
However, I feel can be little out of reach due to complexity issues to a great number of potential users. An interesting solution would be to go towards a more graphical, intuitive way to set up a surface. Is that possible?
Also, a database of already mapped controllers would be useful.
Excuse me if these subjects were already discussed. It is quite a long/dense thread.
Thanks.
|
|
|
04-21-2020, 02:51 AM
|
#8595
|
Human being with feelings
Join Date: Jul 2009
Posts: 1,231
|
Sorry, I've been out of the loop for a couple of weeks (months?). Does any of the new encoder options (steps, accelleration) affect the Softube C1 mapping/structure as of yet? It uses encoders, but they are mapped as 7bit faders for now I believe. Any info on this, perhaps some other C1 users that can chime in?
|
|
|
04-21-2020, 03:08 AM
|
#8596
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by ramses
Sorry, I've been out of the loop for a couple of weeks (months?). Does any of the new encoder options (steps, accelleration) affect the Softube C1 mapping/structure as of yet? It uses encoders, but they are mapped as 7bit faders for now I believe. Any info on this, perhaps some other C1 users that can chime in?
|
Exactly right -- the C1 uses 7 bit faders, nothing to do with encoders -- C1 sitting right in front of me as we speak -- works great.
__________________
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
|
|
|
04-21-2020, 03:10 AM
|
#8597
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
New build is up.
Hopefully this fixes at least some of the accelerated encoder issues.
__________________
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
|
|
|
04-21-2020, 04:52 AM
|
#8598
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,688
|
Quote:
Originally Posted by barbaroja
Also, a database of already mapped controllers would be useful.
|
I suppose this is growing. And some day hopefully supported in ReaPack.
But you not only need to specify the hardware but also the intended workflow.
-Michael
|
|
|
04-21-2020, 06:06 AM
|
#8599
|
Human being with feelings
Join Date: Jul 2009
Posts: 1,231
|
Quote:
Originally Posted by Geoff Waddington
Exactly right -- the C1 uses 7 bit faders, nothing to do with encoders -- C1 sitting right in front of me as we speak -- works great.
|
Ok, so the C1 is not affected by these new improvements, if I understand you correctly? So, no way of using stepped values and being able to go from low-high and then back high-low? I need both in order to be able to lay out some plugins properly on the C1, if I remember correctly. Also, no way to determine what amount of "turning" will return the next step? Sorry if I'm being unclear.
Last edited by ramses; 04-21-2020 at 06:14 AM.
|
|
|
04-21-2020, 06:10 AM
|
#8600
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
Hopefully this fixes at least some of the accelerated encoder issues.
|
Hi Geoff, was this fix meant to include stepped values? They're not working at all here. The values just aren't moving at all. So I twist the encoder on the "3-position Mode" knob and nothing's happening. The knob is not moving at all. One time I made it jump to minimum, but then it wouldn't move from there.
Things I've tried include:
Acceleration+Steps:
Code:
Rotary15 FXParam "10" "Mode" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) 0.0 0.5 1.0 ]
Steps Only:
Code:
Rotary15 FXParam "10" "Mode" [ 0.0 0.5 1.0 ]
Acceleration Only:
Code:
Rotary15 FXParam "10" "Mode" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]
Nothing Extra:
Code:
Rotary15 FXParam "10" "Mode"
|
|
|
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 03:33 PM.
|