Se Connecter:     

Forum: General Discussion
Sujet: Script School - Page: 52.6
Like I said repeat_start_instant, but if it only "catches" on the 5th attempt that would be ~130ms too late.

Even if you stick with OS2L, my skin saves all the pain of typing out os2 poi.
 
 
Yes it does.
There's 2 things on show there,
First is sending midi out of vdj which goes to light show software
Second thing is writing action poi with one button press, they can send midi or they can send os2l instead, you can choose at run time.

To get midi out you will need the skin, and a mapping & definition file.
To just write os2l poi quickly, you just need the skin.
 
locoDog wrote :
param_cast is what you use to put a variable on the end of a verb

get_var $toto & param_cast & deck 2 filter


to set a variable to a script action value, the set verb allows script actions as a parameter when the action is wrapped in ` `

set $toto `deck 1 filter`


I thought I was in control but now, what if I want to replace the 3 below by $toto in order to select the slot?

deck right effect_select 3 +1
 
Then casting the slot number is where that verbs params end,
you use browser_scroll +1 & browser_enter to get the same result after, casting an fx slot is pretty weird need.
 
I want to implement a "selection mode" on my FLX4. The Beat FX are in slot 1 while the Release FX is on slot 3. Depending on the mode, the same button will select the FX of slot 1 or 3. It can be done with a condition, but I thought it would be cleaner with a variable. As I stumbled with the problem, I saw it as a learning opportunity. Unfortunately, I don't understand your answer.
 
sometimes there isn't a clean way to do it, sometimes you do what you can even if it feels like a long way round, it might be the only way round.

Your case, why cast? it's a binary choice, you don't need to make it dynamic. Why make work for yourself,
but if you do want to learn, pay attention to what I said,

set a 3 & get_var a & param_cast int & effect_select & wait 33ms & browser_scroll +1 & browser_enter
 
Now I understand. I couldn't see the link between the browser and fx selection!

Thanks!
 
A few things added in BUILD 8663 that I think need some notes.

-settings script can update more settings
-setting script accepts script as second parameter
-browsed_song_hashtag and loaded_song_hashtag scripts to add/remove hash tags from user 1, user 2 and comment field
-effect_arm_* scripts support fx units as first parameter (1 or 2, with 3 slots per unit)

-settings script can update more settings
well that's a bit vague, but I did some testing here's what I've found

setting browserShortcuts
setting browserShortcutsIcons
setting colorRules
setting quickFilters
setting rootfolderslocation
setting skinsplitstate
setting browserColumns

are now all scriptable, example case
setting colorRules 'red=Exists = 1,...'

This change means most* of settings are now scriptable.

I'll show you something I've used this for that I think is pretty handy [in a browser administration kind of way]
First I get my browser exactly how I like it, the dividing lines between folders/songs/sideview where I like them [the proper name is "split(s)"]
I then also get my browser columns exactly how I like them; in order and spaced the column splits how I like them
I made a custom_button called SAVE, I gave it this script
get_text `setting browserColumns` & param_cast & set_var '@$browserColumns' & get_text `setting skinsplitstate` & param_cast & set_var '@$browserSplits'

I press the button to save these settings.
I then made a second custom button called "RESET" with this script
get_var '@$browserColumns' & param_cast & setting browserColumns & get_var '@$browserSplits' & param_cast & setting skinsplitstate


I can now totally change my browser, move the splits, remove columns, add columns, make a real mess [like all guests on my rig seem to need to do]. And then all I have to do it press my RESET button and my browser is restored to how I like it. Ah zen :)

the layout is just saved and recalled from a variable so you could have as many save states as you need with a different variable name [just always start with @$ to make it a persistent global variable]

This leads me to the second thing
-setting script accepts script as second parameter
remember our RESET button earlier? We can do this now instead of the param_cast :)

setting browserColumns `get_var '@$browserColumns'` & setting skinsplitstate `get_var '@$browserSplits'`


Video demo



The third thing
-browsed_song_hashtag and loaded_song_hashtag scripts to add/remove hash tags from user 1, user 2 and comment field

example
browsed_song_hashtag 'user 1' '#bouncy'

param 1 is the tag, param 2 is the hashtag string to add/remove.


More; There's almost certainly things you could do with
setting browserShortcuts
setting colorRules
setting quickFilters
that could be useful in some cases, I haven't fully studied.

Lastly
-effect_arm_* scripts support fx units as first parameter (1 or 2, with 3 slots per unit)
I haven't studied this at all yet, so I'll make another post when I have.
 
Since set_var also accepts a script parameter, you could further tidy up the storing of settings as well
set_var '@$browserColumns' `setting browserColumns`
 
oh of course yeah, I think of set_var as only strings, but without " or ' a `script action` will parse as a string.
 
Thank you so much to add the tagging verb (browsed_song_hashtag ) and to follow my suggestion.
This makes tagging using a pad so much easier.

You guys simply rock!