|
|
|
04-18-2020, 02:24 PM
|
#8481
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
Here's the MF Twister from Slow CW to Fast CW
Increase Messages:
Received Message: b0 0f 41
Received Message: b0 0f 42
Received Message: b0 0f 43
Received Message: b0 0f 44
Received Message: b0 0f 45
Received Message: b0 0f 46
Received Message: b0 0f 47
Received Message: b0 0f 48
Received Message: b0 0f 4a
Received Message: b0 0f 4d
Received Message: b0 0f 51
And slow CCW to fast CCW:
Decrease Messages:
Received Message: b0 0f 3f
Received Message: b0 0f 3e
Received Message: b0 0f 3d
Received Message: b0 0f 3c
Received Message: b0 0f 3b
Received Message: b0 0f 3a
Received Message: b0 0f 39
Received Message: b0 0f 38
Received Message: b0 0f 36
Received Message: b0 0f 33
Received Message: b0 0f 2f
Which according to your syntax would translate to...
Code:
Widget SomeEncoder
Encoder b0 0f [ 3f 3e 3d 3c 3b 3a 39 38 36 33 2f - 41 42 43 44 45 46 47 48 4a 4d 51 ]
WidgetEnd
Still very long but doable with copy/pasting.
Would something like this be possible? [This is a syntax suggestion I guess ]
Code:
Widget SomeEncoder
Encoder b0 0f [ 3f-2f , 41-51 ]
WidgetEnd
Then if I had non velocity sensitive encoders it would be simply:
Code:
Widget SomeEncoder
Encoder b0 0f [ 3f , 41 ]
WidgetEnd
|
See previous post.
__________________
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-18-2020, 02:27 PM
|
#8482
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
Great idea, that means we need the "-" for range so how about ">" for increment and "<" for decrement, so if we have a contiguous range:
Code:
Encoder b0 10 [ > 01-0f < 41-4f ]
|
I like that one.
So in MF Twister with Velocity mode it would be:
Code:
Encoder b0 0f [ > 41-51 < 3f-2f ]
And then if Velocity Sensitivity was off just simply:
Code:
Encoder b0 0f [ > 41 < 3f ]
Does it make more sense to put decrement first? Like...
Code:
Encoder b0 0f [ < 3f-2f > 41-51 ]
And then if Velocity Sensitivity was off just simply:
Code:
Encoder b0 0f [ < 3f > 41 ]
|
|
|
04-18-2020, 02:31 PM
|
#8483
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
I like that one.
So in MF Twister with Velocity mode it would be:
Code:
Encoder b0 0f [ > 41-51 < 3f-2f ]
And then if Velocity Sensitivity was off just simply:
Code:
Encoder b0 0f [ > 41 < 3f ]
Does it make more sense to put decrement first? Like...
Code:
Encoder b0 0f [ < 3f-2f > 41-51 ]
And then if Velocity Sensitivity was off just simply:
Code:
Encoder b0 0f [ < 3f > 41 ]
|
Yup, all good, and you can put inc/dec in whatever order you prefer, the parser will figure it out.
__________________
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-18-2020, 02:37 PM
|
#8484
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
Yup, all good, and you can put inc/dec in whatever order you prefer, the parser will figure it out.
|
Sounds terrific. Will be much cleaner than having a bunch of Encoder modes and should work regardless of the surface. Looking forward to it!
|
|
|
04-18-2020, 02:47 PM
|
#8485
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
Great idea, that means we need the "-" for range so how about ">" for increment and "<" for decrement, so if we have a contiguous range:
Code:
Encoder b0 10 [ > 01-0f < 41-4f ]
and if not:
Code:
Encoder b0 18 [ > 01 04 08 0c 0f < 41 44 48 4c 4f ]
|
Good stuff!
I guess a by-product of this is that Encoder can now incorporate any message, so if the surface sent 01cw and 7f ccw ( one of the BCR2000 modes ) that would be ok?
|
|
|
04-18-2020, 02:59 PM
|
#8486
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Good stuff!
I guess a by-product of this is that Encoder can now incorporate any message, so if the surface sent 01cw and 7f ccw ( one of the BCR2000 modes ) that would be ok?
|
Yup, it is completely free form now.
The value will be sent to the Action as a position/range pair -- e.g. 6/10.
If the Action incorporates acceleration, it can either use or ignore this value.
Sound sbout right ?
__________________
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-18-2020, 03:02 PM
|
#8487
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
Yup, it is completely free form now.
The value will be sent to the Action as a position/range pair -- e.g. 6/10.
If the Action incorporates acceleration, it can either use or ignore this value.
Sound sbout right ?
|
Sounds great!
|
|
|
04-18-2020, 03:20 PM
|
#8488
|
Human being with feelings
Join Date: Sep 2014
Posts: 68
|
The BCR2000 has 3 different encoder modes
Relative 2s Complement - single resolution
Sends 01 clockwise and 7F counterclockwise
B0 51 01
B0 51 01
B0 51 01
B0 51 01
B0 51 7F
B0 51 7F
B0 51 7F
B0 51 7F
B0 51 7F
Relative Binary Offset - single resolution
Sends 41 clockwise and 3F counterclockwise
B0 52 41
B0 52 41
B0 52 41
B0 52 41
B0 52 3F
B0 52 3F
B0 52 3F
B0 52 3F
Relative (sign in MS bit) - single resolution
Sends 01 clockwise and 41 counter clockwise
B0 53 01
B0 53 01
B0 53 01
B0 53 01
B0 53 41
B0 53 41
B0 53 41
B0 53 41
The values above are with one encoder resolution. Encoders can be assigned a unique resolution per velocity (rotational speed). The velocities are defined as:
Slowest
Slow
Fast
Fastest
If I assign a resolution to each of the first 3 velocities I get different values depending on the rotational speed.
Relative (sign in MS bit)
clockwise
B0 54 01
B0 54 14
B0 54 3E
counter clockwise
B0 54 41
B0 54 54
B0 54 7E
B0 54 3C
Not sure if you need an example of each. And the values from multi velocity settings are not consistent though.
|
|
|
04-18-2020, 03:29 PM
|
#8489
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by rschlierbeck
The BCR2000 has 3 different encoder modes
Relative 2s Complement - single resolution
Sends 01 clockwise and 7F counterclockwise
B0 51 01
B0 51 01
B0 51 01
B0 51 01
B0 51 7F
B0 51 7F
B0 51 7F
B0 51 7F
B0 51 7F
Relative Binary Offset - single resolution
Sends 41 clockwise and 3F counterclockwise
B0 52 41
B0 52 41
B0 52 41
B0 52 41
B0 52 3F
B0 52 3F
B0 52 3F
B0 52 3F
Relative (sign in MS bit) - single resolution
Sends 01 clockwise and 41 counter clockwise
B0 53 01
B0 53 01
B0 53 01
B0 53 01
B0 53 41
B0 53 41
B0 53 41
B0 53 41
The values above are with one encoder resolution. Encoders can be assigned a unique resolution per velocity (rotational speed). The velocities are defined as:
Slowest
Slow
Fast
Fastest
If I assign a resolution to each of the first 3 velocities I get different values depending on the rotational speed.
Relative (sign in MS bit)
clockwise
B0 54 01
B0 54 14
B0 54 3E
counter clockwise
B0 54 41
B0 54 54
B0 54 7E
B0 54 3C
Not sure if you need an example of each. And the values from multi velocity settings are not consistent though.
|
Actually, that's a perfect set of examples !
No need to provide any more Encoder values from your surface folks, we now have it sorted.
The new syntax will handle any of the above with ease, as well as anything else the encoder elves can come up with
__________________
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-18-2020, 03:40 PM
|
#8490
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Focusing back over in Actions, we will add a means of stating an inc/dec default delta amount for encoders -- maybe something like so:
Code:
Zone "SomeZone:
aWidget AnAction [ ( 0.001 ) ]
ZoneEnd
This way we can even have different instances of Actions with different inc/dec deltas.
So maybe you might want to set some FXParam deltas like so:
Code:
widget1 FXParam 0 [ ( 0.001 ) ]
widget2 FXParam 4 [ ( 0.05 ) ]
widget3 FXParam 7 [ ( 0.00001 ) ]
Scary number lists will, of course, always give the best results, but sometimes a nicely tuned delta value + acceleration is a lot better than not having either
__________________
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-18-2020, 03:48 PM
|
#8491
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
Scary number lists will, of course, always give the best results, but sometimes a nicely tuned delta value + acceleration is a lot better than not having either
|
Will the acceleration also affect the rate through which the scary number list is stepped?
|
|
|
04-18-2020, 04:05 PM
|
#8492
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Will the acceleration also affect the rate through which the scary number list is stepped?
|
Yup, that's the plan
First off, let's just say there will be a possibility of 2 forms of accelarion perhaps working in concert.
The first will be a simplistic, Action based strategy that will simply notices how fast the ticks are arriving and accelerate accordingly.
Then there is the aforementioned Encoder acceleration, were you might receive a 6/10 message.
A simple strategy might say, OK, multiply delta by 6 and apply -- assuming 1/10 was the lowest value that was expected.
Of course, things could be MUCH more complex, with the stepped value assigner taking into account the number of ticks received recently, the current state of the Encoder acceleration, and maybe even the general locale (local value bounds) within the overall scary numbers list
__________________
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-18-2020, 04:10 PM
|
#8493
|
Human being with feelings
Join Date: Sep 2014
Posts: 68
|
Will it matter which encoder mode you use? In my examples above each mode sends a different set of values for cw and ccw rotation.
Edit: I should have said the values sent are different for each mode.
Last edited by rschlierbeck; 04-18-2020 at 04:23 PM.
|
|
|
04-18-2020, 04:19 PM
|
#8494
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by rschlierbeck
Will it matter which encoder mode you use? In my examples above each mode sends a different set of values for cw and ccw rotation.
|
Totally up to you, you can use any mode, just define your widgets accordingly.
__________________
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-18-2020, 04:21 PM
|
#8495
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
Focusing back over in Actions, we will add a means of stating an inc/dec default delta amount for encoders -- maybe something like so:
Code:
Zone "SomeZone:
aWidget AnAction [ ( 0.001 ) ]
ZoneEnd
This way we can even have different instances of Actions with different inc/dec deltas.
So maybe you might want to set some FXParam deltas like so:
Code:
widget1 FXParam 0 [ ( 0.001 ) ]
widget2 FXParam 4 [ ( 0.05 ) ]
widget3 FXParam 7 [ ( 0.00001 ) ]
Scary number lists will, of course, always give the best results, but sometimes a nicely tuned delta value + acceleration is a lot better than not having either
|
I like that. So I can set everything up as an encoder, and basically set the resolution per FXParam? Or use a fixed parameter list? Sounds good.
|
|
|
04-18-2020, 05:52 PM
|
#8496
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
Yup, that's the plan
First off, let's just say there will be a possibility of 2 forms of accelarion perhaps working in concert.
The first will be a simplistic, Action based strategy that will simply notices how fast the ticks are arriving and accelerate accordingly.
Then there is the aforementioned Encoder acceleration, were you might receive a 6/10 message.
A simple strategy might say, OK, multiply delta by 6 and apply -- assuming 1/10 was the lowest value that was expected.
Of course, things could be MUCH more complex, with the stepped value assigner taking into account the number of ticks received recently, the current state of the Encoder acceleration, and maybe even the general locale (local value bounds) within the overall scary numbers list
|
Cool If we can accelerate through the scary number list that'd be great.
The SNL lets us fix any crappy parameter scaling in the plugin, by providing a finer resolution at one end of the scale than the other.
The drawback at the moment is if you want very fine control over a particular parameter all the way through its range (Samplomatic pitch, for example) you're then stuck with hundreds of turns to reach the end stops.
Current workaround is to have a different SNL attached to Shift, so you can move in bigger jumps if you need to, but it would nice if the acceleration could just 'jump' a certain number of steps when it kicks in.
That's all the Shift SNL is, the original fine list with lots of steps missed out, meaning Samplomatic pitch moves in semi-tones rather than cents.
Also, am I right in assuming that the delta value you mentioned earlier represents the minimum tick size for a parameter? Being able to set this is a must.
|
|
|
04-18-2020, 06:37 PM
|
#8497
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
I like that. So I can set everything up as an encoder, and basically set the resolution per FXParam? Or use a fixed parameter list? Sounds good.
|
Yup
__________________
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-18-2020, 06:37 PM
|
#8498
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Cool If we can accelerate through the scary number list that'd be great.
The SNL lets us fix any crappy parameter scaling in the plugin, by providing a finer resolution at one end of the scale than the other.
The drawback at the moment is if you want very fine control over a particular parameter all the way through its range (Samplomatic pitch, for example) you're then stuck with hundreds of turns to reach the end stops.
Current workaround is to have a different SNL attached to Shift, so you can move in bigger jumps if you need to, but it would nice if the acceleration could just 'jump' a certain number of steps when it kicks in.
That's all the Shift SNL is, the original fine list with lots of steps missed out, meaning Samplomatic pitch moves in semi-tones rather than cents.
Also, am I right in assuming that the delta value you mentioned earlier represents the minimum tick size for a parameter? Being able to set this is a must.
|
Yes, the delta is the minimum tick size.
__________________
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-18-2020, 09:03 PM
|
#8499
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Its sounding very comprehensive and exciting gents.
|
|
|
04-19-2020, 05:24 AM
|
#8500
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by tdc
Its sounding very comprehensive and exciting gents.
|
I agree, but when the time comes will need to be told like I'm 5 haha
......
Ok Geoff, So I found that nasty ZON file. Silly me made a template with all my encoders/buttons so I could cut and paste into other fx zones. I have some questions about all that but here's the zon for now.
File is called "FX Zone Template.zon" (realizing now it could just be a .txt and I'm sure that would be fine)
edit: Yes that works
Code:
FocusedFXNavigator
Rotary1 NoAction
Rotary2 NoAction
Rotary3 NoAction
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
Rotary9 NoAction
Rotary10 NoAction
Rotary11 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
Rotary32 NoAction
MFTButton1 NoAction
MFTButton2 NoAction
MFTButton3 NoAction
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton9 NoAction
MFTButton10 NoAction
MFTButton11 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
MFTButton32 NoAction
|
|
|
04-19-2020, 05:31 AM
|
#8501
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by cjewellstudios
I agree, but when the time comes will need to be told like I'm 5 haha
......
Ok Geoff, So I found that nasty ZON file. Silly me made a template with all my encoders/buttons so I could cut and paste into other fx zones. I have some questions about all that but here's the zon for now.
File is called "FX Zone Template.zon" (realizing now it could just be a .txt and I'm sure that would be fine)
edit: Yes that works
Code:
FocusedFXNavigator
Rotary1 NoAction
Rotary2 NoAction
Rotary3 NoAction
Rotary4 NoAction
Rotary5 NoAction
Rotary6 NoAction
Rotary7 NoAction
Rotary8 NoAction
Rotary9 NoAction
Rotary10 NoAction
Rotary11 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
Rotary32 NoAction
MFTButton1 NoAction
MFTButton2 NoAction
MFTButton3 NoAction
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton9 NoAction
MFTButton10 NoAction
MFTButton11 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
MFTButton32 NoAction
|
Well, the parser shouldn't fall over like it does now, so thanks for the file, but yeah, you should never put a .zon extension on a file that doesn't have at least this:
Code:
Zone "aZoneName"
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
Last edited by Geoff Waddington; 04-19-2020 at 05:41 AM.
|
|
|
04-19-2020, 05:40 AM
|
#8502
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
New build is up.
All Actions now have:
delta - defaults to 0.001
rangeMinimum - defaults to 0.0
rangeMaximum -- defaults to 1.0
Here's how you change things:
Code:
Zone "aZone"
widget1 Action1 [ (0.002) 0.0-0.5 ]
widget2 Action2 [ (0.002) 0.0-0.5 0.0 0.33 0.67 1.0 ]
ZoneEnd
In Action1 we change the defaults:
delta = 0.002
rangeMinimum = 0.0
rangeMaximum = 0.5
In Action2, the stepped values get used and the delta and range are ignored - in other words stepped values rule, but you already knew that
__________________
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-19-2020, 05:48 AM
|
#8503
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
2 Questions for FX Zones. Ok Well 3
Here's what I'm working with:
FX Zone looks like this:
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"
MFTButton32 FXParam 6 "Bypass"
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 NoAction { 25 255 0 }
MFTButton2 NoAction { 25 255 0 25 255 0 }
MFTButton3 NoAction { 25 255 0 25 255 0 }
MFTButton4 NoAction
MFTButton5 NoAction
MFTButton6 NoAction
MFTButton7 NoAction
MFTButton8 NoAction
MFTButton9 NoAction { 25 255 0 25 255 0 }
MFTButton10 NoAction { 25 255 0 25 255 0 }
MFTButton11 NoAction { 25 255 0 25 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
MFTButton32 NoAction
ZoneEnd
Widgets look like this:
Code:
Widget MFTButton2
Press B6 01 7F
FB_TwoState B6 01 7F B6 01 00
FB_MFT_RGB B6 01 7F
WidgetEnd
Widget Rotary2
Fader7Bit B8 01 7f
FB_Fader7Bit B8 01 00
FB_MFT_RGB B8 01 7f
WidgetEnd
1. I can bypass this but I cannot unbypass. Is the solution a stepped value? How would that look?
2. Trying to get RGB to work but failing miserably here. Tried to follow the wiki on this but I must have something wrong.
3. I missed some of the talk about the new edit window. I was able to print all the parameters from this vst to the console which was amazing. Is there more it can do? Is there a general good workflow for creating fx zones that you all have come up with?
|
|
|
04-19-2020, 06:03 AM
|
#8504
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by cjewellstudios
2 Questions for FX Zones. Ok Well 3
Here's what I'm working with:
Code:
Widget MFTButton2
Press B6 01 7F
FB_TwoState B6 01 7F B6 01 00
FB_MFT_RGB B6 01 7F
WidgetEnd
Widget Rotary2
Fader7Bit B8 01 7f
FB_Fader7Bit B8 01 00
FB_MFT_RGB B8 01 7f
WidgetEnd
1. I can bypass this but I cannot unbypass. Is the solution a stepped value? How would that look?
|
Code:
Zone "VST: AIR Compressor (AIR Music Technology)"
FocusedFXNavigator
Toggle+MFTButton32 FXParam 6 "Bypass"
ZoneEnd
Quote:
Originally Posted by cjewellstudios
2. Trying to get RGB to work but failing miserably here. Tried to follow the wiki on this but I must have something wrong.
|
You can only have one feedback processor per Widget.
This is to avoid the flicker typically caused by double mapping to a Widget.
in this case, everything is cool, because the 2 Widget feedback destinations are different.
This is a design flaw/bug -- we should allow more than 1 feedback processor if there are no display conflicts.
Will work on this.
Quote:
Originally Posted by cjewellstudios
3. I missed some of the talk about the new edit window. I was able to print all the parameters from this vst to the console which was amazing. Is there more it can do? Is there a general good workflow for creating fx zones that you all have come up with?
|
Well, the printout is a start, more goodies to come...
__________________
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-19-2020, 06:12 AM
|
#8505
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by Geoff Waddington
You can only have one feedback processor per Widget.
|
Oh ok! I actually had a hunch that was it. I did try messing with things, but couldn't crack the code. Would I want to address the rotaries or the buttons with FB_MFT_RGB? My guess is the buttons as they effect the led's. So I can try taking out FB_TwoState on those and see if I can address them without issue.
Code:
Zone "VST: AIR Compressor (AIR Music Technology)"
FocusedFXNavigator
Toggle+MFTButton32 FXParam 6 "Bypass"
ZoneEnd
OOOHHHHHHHH... WOWZERS Thanks Geoff!
Thanks for the new build!
|
|
|
04-19-2020, 08:06 AM
|
#8506
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by Geoff Waddington
You could use:
Code:
Zone "Buttons|"
someWidget GoZone "Send1"
anotherWidget GoZone "Send2"
...
ZoneEnd
or within a Channel Zone:
Code:
Zone "Channel|"
channelWidget| GoZone "Send|"
ZoneEnd
|
Geoff, thanks for that. I'll try them out and see if either achieves what I want...
(Wasn't ignoring your answer, have spent the last 36 hours frantically trying to recover from a corrupted zon file which I hadn't backed up since, ooh, just before I got it all working the way I wanted!)
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
04-19-2020, 10:46 AM
|
#8507
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by cjewellstudios
Widgets look like this:
Code:
Widget MFTButton2
Press B6 01 7F
FB_TwoState B6 01 7F B6 01 00
FB_MFT_RGB B6 01 7F
WidgetEnd
Widget Rotary2
Fader7Bit B8 01 7f
FB_Fader7Bit B8 01 00
FB_MFT_RGB B8 01 7f
WidgetEnd
|
Why are you using RGB twice? For instance, Button2 has the RGB and Rotary2 has the RGB with a different assignment, but the device only has a total of 16 RGB processors (not 16x3, one for each virtual control). So you've got two different RGB settings assigned to the same thing light. I'm pretty sure the one with the Rotary assignment isn't being seen at all.
I would try assigning the FB_MFT_RGB to the button press widget, and not assign it to the Encoder.
Here's how I basically did my MF Twister Encoder assignments for Button1, Rotary1 and ShiftRotary1:
Code:
Widget Button1
Press B1 00 7F
FB_MFT_RGB B1 00 7F
WidgetEnd
Widget Rotary1
EncoderPlainReverse b0 00 7f
FB_Fader7Bit b0 00 00
WidgetEnd
Widget ShiftRotary1
EncoderPlainReverse b4 00 7f
FB_Fader7Bit b4 00 00
WidgetEnd
See if that setup works for your needs. May be cleaner.
Then if you want to change the colors on press, you'd do something like this:
Code:
Zone "VST: AR-1 (Kush Audio)"
FocusedFXNavigator
Toggle+Button1 FXParam "0" "Bypass" { 90 255 0 255 50 0 }
ZoneEnd
However, with Encoders about to change, you may want to hold off.
Last edited by Funkybot; 04-19-2020 at 10:53 AM.
|
|
|
04-19-2020, 12:01 PM
|
#8508
|
Human being with feelings
Join Date: Oct 2007
Posts: 784
|
Evenin' all, Sunday night is stupid question night ;-)
I'm really not getting my head around the FX thing (either with selected track or focussed FX)so any further pointers would be gratefully received.
Here's my main MCU.Zon
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterChannel|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Busses Reaper 41803 //Track: Select all top level tracks
Busses Reaper 41665 //Mixer: Show/hide children of selected tracks
Busses Reaper 40297 //Track: Unselect all tracks
Send ToggleMapSelectedTrackSends
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
BankLeft TrackBank "-8"
BankRight TrackBank "8"
Rewind Rewind
FastForward FastForward
JogWheelRotary FastForward
Stop Stop
Play Play
Record Record
F1 NextPage
Solo Reaper 40340 //Toggle Off All Solos
smpteBeats CycleTimeDisplayModes
TimeDisplay TimeDisplay
Read TrackAutoMode "1"
Write TrackAutoMode "3"
Trim TrackAutoMode "0"
Touch TrackAutoMode "2"
Latch TrackAutoMode "4"
Group Reaper "_RSd8a03782dd33bd7a179c1009d9c1d1f24a2a6fdb"
Shift+Read GlobalAutoMode "1"
Shift+Write GlobalAutoMode "3"
Shift+Trim GlobalAutoMode "0"
Shift+Touch GlobalAutoMode "2"
Shift+Latch GlobalAutoMode "4"
Shift+Group Reaper "42024"
Save Reaper "40026"
Shift+Save Reaper "40022"
Undo Reaper "40029"
Shift+Undo Reaper "40030"
Shift Shift
Option Option
Control Control
Alt Alt
Marker Reaper "40157"
Alt+Marker Reaper "40613"
Option+Marker Reaper "40174"
Marker+Left Reaper "40172"
Marker+Right Reaper "40173"
Nudge Reaper "40173"
Cycle CycleTimeline
Click Reaper "40364"
Zoom+Up Reaper "40112"
Zoom+Down Reaper "40111"
F8 Reaper "41743"
ZoneEnd
Zone "Channel|"
TrackNavigator
Select| TrackUniqueSelect
Hold+Select| Reaper 41665 //Mixer: Show/hide children of selected tracks
TrackNavigator
DisplayUpper| TrackNameDisplay
DisplayLower| TrackVolumeDisplay //TrackVolumeDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
Rotary| TrackPan "0"
RecordArm| TrackRecordArm
Solo| TrackSolo
Mute| TrackMute
Shift+Select| TrackRangeSelect
Control+Select| TrackSelect
Shift+Control+Select| TogglePin
Option+Select| MapSelectedTrackFXToWidgets
Fader| TrackVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterChannel|"
MasterTrackNavigator
MasterFader TrackVolume
zoneEnd
Zone "Pan|1-8"
TrackNavigator
DisplayLower| TrackPanDisplay
Rotary| TrackPan "0"
RotaryPush| GoZone PanWidth|
ZoneEnd
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth "1"
RotaryPush| GoZone Pan|
ZoneEnd
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "FXMenu|1-4"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
RotaryPush| GoFXSlot |
ZoneEnd
And I mocked up a minimal fx.zon
Code:
Zone "VST: ReaEQ" ReaEQ
SelectedTrackNavigator
Rotary1 FXParam 0 "HPF Freq"
Fader1 FXParam 1 "HPF Gain"
Shift+Rotary1 FXParam 2 "HPF Q"
Rotary2 FXParam 3 "Freq 1"
Fader2 FXParam 4 "Gain 1"
Shift+Rotary2 FXParam 5 "Q 1"
ZoneEnd
I'd like the top row to show the item names and the bottom to show the value. At loadup (of the FX), I'd like it to show the first value of each of the paramter block,until I edit on of the others (so freq by default, but jumping to gain or q as I move the controller for them)
Other things I'd like to do, you'll see I've adjusted the display so it shows the volume in lower row, I'd like that to switch on moving the pan to showing the pan value and cycle through width (as it does now) and return back at showing the track volume. When I changed 'GoZone' in the PanWidth zone to 'Channel' instead of 'Pan it didn't work?
I've not tried the VCA Spill thing yet, but it looks like it might be an interesting detour from folders, however I like to use Sexan's 'Create VCA Master' Script for easy VCA grouping and that works down/backwards through the group numbers, I note the advice for VCA Spill is to work up, is this going to cause problems?
I've trawled this thread a bit an have some posts about getting the fx stuff working but I've not really got any closer to it, if I can get it working I'd be happy to put some time in to the wiki to try and clarify the docs because it seems something is missing if I'm not the only one struggling.
Oh yeah, I've got my toggle off all solos (Like Klinke) but with Klinke the red solo light only comes on when there is a solo active, now I've added the item in 'Buttons' the light stays on all the time (regardless of solo state), can I make it work like Klinke?
|
|
|
04-19-2020, 12:29 PM
|
#8509
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
All Actions now have:
delta - defaults to 0.001
rangeMinimum - defaults to 0.0
rangeMaximum -- defaults to 1.0
Here's how you change things:
Code:
Zone "aZone"
widget1 Action1 [ (0.002) 0.0-0.5 ]
widget2 Action2 [ (0.002) 0.0-0.5 0.0 0.33 0.67 1.0 ]
ZoneEnd
In Action1 we change the defaults:
delta = 0.002
rangeMinimum = 0.0
rangeMaximum = 0.5
In Action2, the stepped values get used and the delta and range are ignored - in other words stepped values rule, but you already knew that
|
Loving the new build!
My 10,000 step SNL has been reduced to:
Code:
DisplayUpperD8 FXParamNameDisplay 15 "Cent"
DisplayLowerD8 FXParamValueDisplay 15
RotaryD8 FXParam 15 [ (0.00006329) ]
Toggle+RotaryPushD8 FXParam 15 [ 0.5 ]
Roll on the acceleration!
|
|
|
04-19-2020, 12:47 PM
|
#8510
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by rothchild
Evenin' all, Sunday night is stupid question night ;-)
I'm really not getting my head around the FX thing (either with selected track or focussed FX)so any further pointers would be gratefully received.
Here's my main MCU.Zon
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterChannel|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Busses Reaper 41803 //Track: Select all top level tracks
Busses Reaper 41665 //Mixer: Show/hide children of selected tracks
Busses Reaper 40297 //Track: Unselect all tracks
Send ToggleMapSelectedTrackSends
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
BankLeft TrackBank "-8"
BankRight TrackBank "8"
Rewind Rewind
FastForward FastForward
JogWheelRotary FastForward
Stop Stop
Play Play
Record Record
F1 NextPage
Solo Reaper 40340 //Toggle Off All Solos
smpteBeats CycleTimeDisplayModes
TimeDisplay TimeDisplay
Read TrackAutoMode "1"
Write TrackAutoMode "3"
Trim TrackAutoMode "0"
Touch TrackAutoMode "2"
Latch TrackAutoMode "4"
Group Reaper "_RSd8a03782dd33bd7a179c1009d9c1d1f24a2a6fdb"
Shift+Read GlobalAutoMode "1"
Shift+Write GlobalAutoMode "3"
Shift+Trim GlobalAutoMode "0"
Shift+Touch GlobalAutoMode "2"
Shift+Latch GlobalAutoMode "4"
Shift+Group Reaper "42024"
Save Reaper "40026"
Shift+Save Reaper "40022"
Undo Reaper "40029"
Shift+Undo Reaper "40030"
Shift Shift
Option Option
Control Control
Alt Alt
Marker Reaper "40157"
Alt+Marker Reaper "40613"
Option+Marker Reaper "40174"
Marker+Left Reaper "40172"
Marker+Right Reaper "40173"
Nudge Reaper "40173"
Cycle CycleTimeline
Click Reaper "40364"
Zoom+Up Reaper "40112"
Zoom+Down Reaper "40111"
F8 Reaper "41743"
ZoneEnd
Zone "Channel|"
TrackNavigator
Select| TrackUniqueSelect
Hold+Select| Reaper 41665 //Mixer: Show/hide children of selected tracks
TrackNavigator
DisplayUpper| TrackNameDisplay
DisplayLower| TrackVolumeDisplay //TrackVolumeDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
Rotary| TrackPan "0"
RecordArm| TrackRecordArm
Solo| TrackSolo
Mute| TrackMute
Shift+Select| TrackRangeSelect
Control+Select| TrackSelect
Shift+Control+Select| TogglePin
Option+Select| MapSelectedTrackFXToWidgets
Fader| TrackVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterChannel|"
MasterTrackNavigator
MasterFader TrackVolume
zoneEnd
Zone "Pan|1-8"
TrackNavigator
DisplayLower| TrackPanDisplay
Rotary| TrackPan "0"
RotaryPush| GoZone PanWidth|
ZoneEnd
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth "1"
RotaryPush| GoZone Pan|
ZoneEnd
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "FXMenu|1-4"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
RotaryPush| GoFXSlot |
ZoneEnd
And I mocked up a minimal fx.zon
Code:
Zone "VST: ReaEQ" ReaEQ
SelectedTrackNavigator
Rotary1 FXParam 0 "HPF Freq"
Fader1 FXParam 1 "HPF Gain"
Shift+Rotary1 FXParam 2 "HPF Q"
Rotary2 FXParam 3 "Freq 1"
Fader2 FXParam 4 "Gain 1"
Shift+Rotary2 FXParam 5 "Q 1"
ZoneEnd
I'd like the top row to show the item names and the bottom to show the value. At loadup (of the FX), I'd like it to show the first value of each of the paramter block,until I edit on of the others (so freq by default, but jumping to gain or q as I move the controller for them)
|
So, I'm not using the MCU, but I am using a Behringer X-Touch Universal which pretty much mimic the MCU. Here's my take on the ReaEQ, which is pretty much what you're asking for (except for showing the values on the scribble strips as I look at the graph/listen):
I've got a default ReaEQ setup with an HPF, 3 frequencies and an LPF.
The zon file below sets up the following:
Rotaries 1-5 for the frequencies.
Shift+Rotaries 1-5 for the Q of each.
Faders 1-5 for the Gain of each.
Code:
Zone "VST: ReaEQ (Cockos)" ReaEQ
SelectedTrackNavigator
Mute1 Reaper "_S&M_FXBYPSEL" //Toggle Bypass Selected FX for Selected Tracks
DisplayUpper1 FXParamNameDisplay "0" "HPF"
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0 "HPF"
Fader1 FXParam 1 "Gain HP"
Shift+Rotary1 FXParam 2 "Q HP"
DisplayUpper2 FXParamNameDisplay "3" "Freq 1"
DisplayLower2 FXParamValueDisplay "3"
Rotary2 FXParam 3 "Freq 1"
Fader2 FXParam 4 "Gain 1"
Shift+Rotary2 FXParam 5 "Q 1"
DisplayUpper3 FXParamNameDisplay "6" "Freq 2"
DisplayLower3 FXParamValueDisplay "6"
Rotary3 FXParam 6 "Freq 2"
Fader3 FXParam 7 "Gain 2"
Shift+Rotary3 FXParam 8 "Q 2"
DisplayUpper4 FXParamNameDisplay "9" "Freq 3"
DisplayLower4 FXParamValueDisplay "9"
Rotary4 FXParam 9 "Freq 3"
Fader4 FXParam 10 "Gain 3"
Shift+Rotary4 FXParam 11 "Q 3"
DisplayUpper5 FXParamNameDisplay "12" "LPF"
DisplayLower5 FXParamValueDisplay "12"
Rotary5 FXParam 12 "LPF"
Fader5 FXParam 13 "Gain LP"
Shift+Rotary5 FXParam 14 "Q LP"
Plugin GoZone "Home"
ZoneEnd
It was written before the new default settings for actions were added, so it doesn't specify any of those yet. But hopefully that will point you in the right direction?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
04-19-2020, 01:08 PM
|
#8511
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
'fraid the bounds are broken in the new build.
Stepped parameters still respect 0.0 and 1.0, but [ 0.0-1.0 ] doesn't work anymore.
|
|
|
04-19-2020, 01:22 PM
|
#8512
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Funkybot
You can't double assign?
Code:
Hold+Select| TrackUniqueSelect
Hold+Select| Reaper 41665 //Mixer: Show/hide children of selected tracks
Since hold fires the first message, this might work too...
Code:
Select| TrackUniqueSelect
Hold+Select| Reaper 41665 //Mixer: Show/hide children of selected tracks
Did you try these approaches out? If not, give them a shot. If so and they don't work, well then, at least you tried.
|
I tried the first example here and it works fine! Much better than having to use two hands to open folders. Thanks
|
|
|
04-19-2020, 01:28 PM
|
#8513
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
I tried the first example here and it works fine! Much better than having to use two hands to open folders. Thanks
|
Now that I know it works, I'll have to go in and use that one myself.
|
|
|
04-19-2020, 01:31 PM
|
#8514
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Funkybot
Now that I know it works, I'll have to go in and use that one myself.
|
Try the second example first- I didn't get that far
btw the stock MCU.mst doesn't have release messages defined for the majority of it's presses, only modifiers and fader touch, I think.
|
|
|
04-19-2020, 01:31 PM
|
#8515
|
Human being with feelings
Join Date: Oct 2007
Posts: 784
|
Thanks spkr4thdd,
Between that and adding:
OnTrackSelection MapSelectedTrackFXToWidgets
To the Home section and
Plugin ToggleMapSelectedTrackFX
To the buttons I now at least have basic function working.
Real shame we can't control turning bands on and off in ReaEq, my default has the HPF and LPF disabled.
|
|
|
04-19-2020, 02:31 PM
|
#8516
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
'fraid the bounds are broken in the new build.
Stepped parameters still respect 0.0 and 1.0, but [ 0.0-1.0 ] doesn't work anymore.
|
Thanks, fixed in next build -- I think
__________________
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-19-2020, 02:37 PM
|
#8517
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
New build is up.
Fixed bug in bounds checking.
When we attacked the dreaded double mappings we overreacted.
It was right to ensure that only the first Action provided feedback.
What wasn't right was the fact that we constrained Widgets to one Feedback Processor.
No need to do that, it's fine to have different Feedback Processors, say a rotary ring value and an RGB light.
So now you can have as many Feedback Processors as you want for any Widget.
This was a substantial change, so please keep a look out for anomalies
__________________
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-19-2020, 02:55 PM
|
#8518
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
New build is up.
Fixed bug in bounds checking.
When we attacked the dreaded double mappings we overreacted.
It was right to ensure that only the first Action provided feedback.
What wasn't right was the fact that we constrained Widgets to one Feedback Processor.
No need to do that, it's fine to have different Feedback Processors, say a rotary ring value and an RGB light.
So now you can have as many Feedback Processors as you want for any Widget.
This was a substantial change, so please keep a look out for anomalies
|
Hey all. Could somebody help me and explain (in a way a dumby can understand Haha) whats going on in the new buikd ? The step and accelerate encoder stuff is it ?.and do i have to change anything in my files ? Mst or zones ? Thanks guys
|
|
|
04-19-2020, 03:31 PM
|
#8519
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Cragster
Hey all. Could somebody help me and explain (in a way a dumby can understand Haha) whats going on in the new buikd ? The step and accelerate encoder stuff is it ?.and do i have to change anything in my files ? Mst or zones ? Thanks guys
|
The new build looks to do two things: 1) allow users to easily customize the parameter step values with encoders, and 2) set custom range limits.
So let's say you've got an EQ parameter and you want the gain to be in 0.001 steps (talking VST parameter ranges not necessarily gain) but maybe that same resolution is too fine for the EQ frequency control because you'd be turning way too much. Maybe for Freq, you determine that .025 steps feel better. You can now do something like:
Code:
Rotary1 FXParam 7 'Low Gain' [ (0.001) ]
Rotary2 FXParam 8 'Low Freq' [ (0.025) ]
Now lets say you're mapping ReaComp and you want 0.001 steps, but you want them only mapped to the first third of the attack time parameter (because you're never going to use some of the really long attack times). And maybe you only want to map the first half of the Release knob. You could do something like this where you set the step size first, then define the minimum and maximum range of the parameter that you want mapped...
Code:
Rotary1 FXParam 1 'Attack' [ (0.001) 0.0-0.33 ]
Rotary2 FXParam 2 'Release' [ (0.001) 0.0-0.5 ]
Hope that helps. Geoff, correct me if I'm wrong.
|
|
|
04-19-2020, 04:31 PM
|
#8520
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Funkybot
The new build looks to do two things: 1) allow users to easily customize the parameter step values with encoders, and 2) set custom range limits.
So let's say you've got an EQ parameter and you want the gain to be in 0.001 steps (talking VST parameter ranges not necessarily gain) but maybe that same resolution is too fine for the EQ frequency control because you'd be turning way too much. Maybe for Freq, you determine that .025 steps feel better. You can now do something like:
Code:
Rotary1 FXParam 7 'Low Gain' [ (0.001) ]
Rotary2 FXParam 8 'Low Freq' [ (0.025) ]
Now lets say you're mapping ReaComp and you want 0.001 steps, but you want them only mapped to the first third of the attack time parameter (because you're never going to use some of the really long attack times). And maybe you only want to map the first half of the Release knob. You could do something like this where you set the step size first, then define the minimum and maximum range of the parameter that you want mapped...
Code:
Rotary1 FXParam 1 'Attack' [ (0.001) 0.0-0.33 ]
Rotary2 FXParam 2 'Release' [ (0.001) 0.0-0.5 ]
Hope that helps. Geoff, correct me if I'm wrong.
|
Thank you !! Yes that definitly helps. So foe example if i had a 3 step parameter it would be [ (0.5) ] ?? is That correct ?? Thanks for your help
And does the old step parameter way still work too ? do i hafta go through and change all the mappings in the old way ?
|
|
|
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:37 AM.
|