Scripted dial alpha

jordikt wrote:Regarding {minmax} action:
If I write this line, the editor alerts me with an error message due the "0-127"

jordikt wrote:It seems that if I select "Horizontal bar" for the display of the Dial rotate, the {iconleft} and {iconright} actions are ignored the most part of the time.

jordikt wrote:It seems that {iconleft} and {iconright} are ignored when "V-pot" is selected as display of Dial rotate. I can't display any icon for vpots.

jordikt wrote:It seems there is a bug when "V-pot" is selected as display of Dial rotate, minmax is set to 0-16383, and endless is checked. In this case, the v-pot doesn't change to endless. If minmax is set to 0-127, endless works as expected.

jordikt wrote:I would say that the maximum values for turning fast the dial for doing some agressive automations in music can go between +14 and -14.

This information can be useful to update the documentation if you consider it interesting.

jordikt wrote:I think there is a wrong behaviour here:

[(press) {title:TITLE} {text:TEXT}]
[(rotate:np) {pb:1,#@e_value#}]
[(pb:1,*) {value:#@e_pbvalue#} {value:p,#@e_pbvalue#}]

Just press the dial for setting the title and the text in the dial. Then you will see that everytime the dial is rotated, the text "TEXT" substitutes the title "TITLE".

As there is no {text} action after the (rotate) event, I suppose the title should not be hidden by any previous text.

• vpotendless
  
• vpotsize
  
• vpotspan
  
• display
  

jordikt wrote:It seems that e_cc is not working.

This works:
[(cc:12,1,*) {value:#@e_ccvalue#} {text:#@e_ccvalue#}]

This doesn't:
[(cc:12,1,*) {value:#@e_cc#} {text:#@e_cc#}]

thx538 wrote:Now, I have observed that the following instruction :
[(rotate:r,1-23)(@g_trsc:0){cc:16,0,#MIN(@e_value+@e_tics-1,24)#}]
does not send anything when in position 23, but the handle is moved to position 24.

• If min/max is set to 1/23 it will not move to 24.
  
• If the min/max values are set to something else, the fader will be moved to 24, and you must add a script command that returns the fader to 23 if you don't want that to happen.
  

thx538 wrote:I did set {minmax:1,24}
In this case I want the fader to move to 24 and the CC to be sent. But no CC is sent.

thx538 wrote:I apologize for the confusion.
I would have expected the range in the rotate command to filter the current state (initial position) and the @e_value to represent the target position (after rotating) but it does not work this way.

If I set a step size of 0 then the following command works well, it will send a cc,0,24 when in (initial) position 23 :
[(rotate:r,1-23)(@g_trsc:0){cc:16,0,#MIN(@e_value+@e_tics,24)#}]

...while with a stepsize of 1 nothing is sent when the current position (before rotating) is 23.

Not a big deal, I have a workaround with the step size = 0, but  I just wanted to report this little inconsistency (Handle being moved while the rotate command is not executed).

• You have a fader with the range 1-24.
  
• You have a command that triggers on values 1-23.
  
• Your initial report was that it "does not send anything when in position 23, but the handle is moved to position 24.".
  
• Now you say I" dont want to send anything when the current value is 24."
  
• Then you say "If I set a step size of 0 then the following command works well, it will send a cc,0,24 when in (initial) position 23".
  

jordikt wrote:1) It seems that {vpotspan:_name_} doesn't work. I can't select any option with this action.

jordikt wrote:2) {display} action have a cosmetic issue, it doesn't refresh the editor after a change. Steps to reproduce it:

jordikt wrote:Some ideas:

1) "Horizontal bar (volume)" and "Horizontal bar (pan)" are long names. What do you think of changing them to "Volume bar" and "Pan bar"?

2) "Title value/position" is the only faulty property to script, it could be added to faders and vpots.

3) I think it could be useful to reference the labels of {valuedisplay} {vpotspan} {display} and {titlevalueposition}.