Sign In:     

Forum: General Discussion
Topic: Script School - Page: 4.00

This part of topic is old and might contain outdated or incorrect information

A small unsexy addition that came with v8.4 [2020] that actual could be a big thing
variables can now hold strings

Set [capture] like this
set 'test1' `get_text 'hello'`
set 'test2' `get_browsed_song "artist"`

And you can compare just like any other variable

prove it with custom_button led logic
param_equal `get_var test1` 'hello' ? on : off

check what the var actually is with this as a custom_button name
`get_var test1`

or inspect with the var list viewer
var_list
I'll post more as I figure any nuances
 
Hi, a quick, question -
I want to be able to turn on a specific shader (eg: "geometry") and then control transparency in the poi editor.
I tried effect_string "shader" 1 "geometry" & effect_slider "shader" 1 +0% but they do not work for me.
can anyone advise?

Tks
 
As locodog said previous page:

Button 1 : show position & size selection tool
Button 2 : AutoChange
Button 3 : BeatMove

Slider 1 : Shader selection
Slider 2 : Transparency

String 1 : Indexed name ... the one on Shadertoy
String 2 : Prety name ... the one we understand

Only shader selection (slider 1) reflect in the GUI, all other actions are not reported
however transparency, BeatMove and AutoChange are effective even not updated in the gui

NOT working anymore ?
When a shader or folder is specified by any of its name , the string is affected, querying them gives the changed value, but nothing apply
maybe some extra action is needed or syntax change ?

for transparency use :
deck master effect_slider 'shader' 2 50%

for a shader...
deck master effect_slider 'shader' 1 12%
it is working but have to know the relative position in the list "All"


Don't play too much with it actually.. it crashed some of my PC just using it ... VDJ still up but WindowManager totally broken.. and another one got BSOD
was working fine before last summer
 


I've reported effect string not working but the "nudge" of slider 1 [shader select]workaround works here
 
Just a little thing I've been playing with for NYE, for your 1 hour/ 30minutes /10 minutes etc to go, you'll have something planned yourself
but just as general countdown for your video out you could do this

firstly set some variables, say you start showing your countdown at 9:30pm, 2 & a half hours to go, also turn text fx on

set 'hour' 2 & set 'min' 30 & set 'sec' 0 & effect_active 'text' 1

Second start these variables counting down [really you could do script 1 & 2 together]
repeat_start 'tCounter' 1000ms & cycle 'sec' -60 & var 'sec' 59 ? cycle 'min' -60 & var 'min' 59 ? cycle 'hour' -24 : : :

Third put these variables into a text string & send it to the text fx
repeat_start 'clock2text' 1000ms & get_text "`get_var 'hour' & param_cast '00'`:`get_var 'min' & param_cast '00'`:`get_var 'sec' & param_cast '00'`" & param_cast 'text' & effect_string 'text' 2

realistically you'd ditch this at 1 minute to go and you could kill it via event schedule at 23:58:59 with something like this

repeat_stop 'tcounter' & repeat_stop 'clock2text' & effect_active 'text' 0

And honestly you could put the countdown together with 1 script [I broke it up to make it easier to understand]

set 'hour' 2 & set 'min' 30 & set 'sec' 00 & effect_active 'text' 1 & repeat_start 'clock2text' 1000ms & get_text "`get_var 'hour' & param_cast '00'`:`get_var 'min' & param_cast '00'`:`get_var 'sec' & param_cast '00'`" & param_cast 'text' & effect_string 'text' 2 & cycle 'sec' -60 & var 'sec' 59 ? cycle 'min' -60 & var 'min' 59 ? cycle 'hour' -24 : : :
 
A couple of things added as of BUILD 5451 (2019-11-24)

goto "loopsize+" and goto "loopsize-" to jump in steps based on default loop size
goto "loopsize" works on endless rotary knobs

simple enough, goto action will treat the "loopsize+" or "loopsize-" as a number.


effect_bank_save "BANKNAME"
effect_bank_load "BANKNAME"
effect_bank_load "BANKNAME" "multi"

Your fx banks are saved in settings.xml
effect_bank_load "BANKNAME" stops previous effect unless "multi" is added as second parameter
 
Is it just me or has the drop down explanatory text that used to appear in the Controller Settings Scripting window in 2018, which explained which conditions were active at any point in the script when you pointed to it with the mouse.... disappeared in 2020 (and been replaced by some sort of colour coding)?

If so, is there any way to turn it back on?
 
Not just you, I think it vanished during the time they were sorting some text spacing bugs of the editor before 8.4 release.
It was a handy pointer for shorter scripts but anything longer than the textbox size you couldn't scroll down to see the conditioning.

For longer stuff I write in a text editor in a logic tree format, with np++ you can easily change from tree layout to wall of text with shift+tab to remove indents & ctrl+j to turn several lines into one line.
 
Thanks as ever - I'll check out np++. Looks like a nifty little utility.....

While I'm here I would like to ask about chaining commands in queries and using "&&" ......

According to the VDJ Script page "If && is used instead of &, to chain commands in queries, the query returns true only if both chained commands return true."

However testing out the example that you gave earlier in the Script school (and other ones I've played around with myself):
effect_active "echo" && effect_active "flanger" ? effect_active "brakeStart" : effect_active "echo" on & effect_active "flanger" on
it doesn't seem to behave at all as I would expect....

Both Effects off -----> Press 1: Turns both effects on -----> Press 2: Brakestart Activated -----> Press 3: Echo starts toggling on and off & Brakestart with it.....

So it is looking to me like it is taking the first script effect_active "echo" as a command rather than as part of a single query as to whether both echo and flanger are active.

Could you say a bit more about how chained commands are used in queries using either "&" or "&&"

Cheers
 
I see what you mean, strange I see && used lots in skins for conditioning also a pad with something like this
effect_active 'echo' && effect_active 'cut'

will only light up with both conditions true,

but like you said in straight script [query to a command] it's only taking the last as a query and a first as a command.
perhaps something the devs could elucidate.
 
action1 && action2 ? action3 : action 4

if action1 is false, script stops and action2 is ignored maybe because global query will fail, but the test is ignored too
action2 only execute when action1 is true, making test appearing to only apply to action2

Test:
set a pad and name it " `get_var myvar`" - without quotes, keeping the leading space
as action:
set myvar ` var var1 1 && var var2 2 ? get_constant 55 : get_constant 42`

_ var1 _ var2 _ resulting name:
__ 0 ____ 0 ____ ?
__ 0 ____ 2 ____ ?
__ 1 ____ 0 ____ 42
__ 1 ____ 2 ____ 55
 
Yes this does seem strange Locodog. Especially as the official script page definitely says:

Quote :
"When chained commands are used in queries, the result depends on the state of the 1st action. E.g. play & loop will return true if the deck is playing (regardless if the deck is looped or not).
If && is used instead of &, to chain commands in queries, the query returns true only if both chained commands return true.
E.g. play && loop query will return true only if both commands return true (deck is playing and is looped) and false in all other cases.


Which doesn't seem to be what is happening in practice.
 
The difference between & and && is only when used in queries, so for LED's etc, not when the action is executed when a button is pressed for example.
In that case & and && have the same effect, namely that both are executed.
So "a & b ? c : d" and "a && b ? c : d" both mean the same thing, namely, first do "a", then do "b ? c : d"
If you need "(a && b) ? c : d" you'll have to write it as "a ? b ? c : d : d"
 
Thanks Adion, that clears that one up then! And I don't need to spend any more time trying to get it to work!

It might be worth editing the script page on the website to make it clear that it only applies to "queries" rather than 'scripting questions' creating "conditional branching".
 
hello vdj user,
I am working on a live show. One of my deck are several loop. Each on a cue (8 hotcues) and edit it "type" "saved loop". for some reasons, i can not be "precise" for triggering at the good time an another loop, then I need to command to vdj "when the 4 bars are completed, go to "loop 1" (or two or three depending on the button i trigger). It s a bit like the smart cue, but I do not like it because it trigger at the same moment of bar and not wait for the end of bars. I don't know if I am clear, my english is bad...for some Ableton users it is like launch a scene with the quantize on 1 bar.
thanks for futur help
bye
 
a rsi monitoring get_beat_bar X, looking for a high value <1.0 when true call whatever and stop the rsi.
 
thanks locodog for this respons. beginning of a new era for me :)
here is the code i put on custom pad

"repeat_start_instant 'bars' 10ms & get_beat_bar 4 & param_bigger 99% ? repeat_stop 'bars' & deck 1 hot_cue 1 : nothing "

working with my mouse (sometimes missed the first beat and do it at the second)
BUT I Copy Paste this code working good with my mouse on a button of my midi controller (traktor s4) button on cc gate
When i use this code on button encoder , it don't work...If I code my button with "pad1" it work but not ideal for me...does it have an explain for this ?
may be an holding condition?
 
OK For the comment just below : when button is on cc..not working, when button is on note it is working :)
 
fastest a rsi can run is 30ms [any thing lower defaults to 30ms], to query beat_bar >99% leaves too little margin to catch it every time [as you've seen], try >97.625% that should be good upto about 190bpm.

If you want it tighter, the maths is
[1/bpm] * 60000 == ms/beat
30 / ms per beat == smallest fraction of a beat that can be caught with a 30ms poll rate
1 - [0.25*fraction] == value to query against
but rsi's have a bit of swing to the timing of the repeats so best to add 10-20 to the initial bpm to give a bit of wriggle room.
 
thanks for those precious math info. Sure I find a way to use it !
 
8%