locoDog
Here's the explanation, the param can now be an action, e.g.
cue_pos 0 & param_multiply "`get_time total 1000"
I don't quite get it I have a feeling it's something I would approve of.
I keep looking at it and almost having a clear idea and then it just vanishes.
cue_pos 0 & param_multiply "`get_time total 1000"
I don't quite get it I have a feeling it's something I would approve of.
I keep looking at it and almost having a clear idea and then it just vanishes.
Posted Wed 28 Jan 15 @ 8:20 am
rapidfirearts
I'm sorry but i don't understand what you mean or what the script is supposed to output :(
Posted Thu 29 Jan 15 @ 5:35 am
locoDog
That's the point neither do I, I'm asking for clarity.
Posted Thu 29 Jan 15 @ 5:48 am
rapidfirearts
Looks like a try to multiply the cue position with another value from a variable, which is not possible as far as i know.
Posted Fri 30 Jan 15 @ 4:38 am
locoDog
That's why I'm asking it kind of makes sense but it doesn't.
Posted Fri 30 Jan 15 @ 5:59 am
djdad
param_ actions were expecting a value (number). They can now accept script actions, so in a way you can now multiply two values that are returned from vdj script actions.
Posted Fri 30 Jan 15 @ 4:02 pm
rapidfirearts
Okay, wow i never new that, thats awesome! May i ask what the extact syntax is then? Because i don't have a clue since it's also not in any documentation as far as i know.
Posted Fri 30 Jan 15 @ 4:46 pm
locoDog
ooo I see, kind of.
Something like this?
deck 1 filter & param_multiply "deck 2 filter" & param_cast & deck 2 filter
I have a feeling this might take a while for me to understand the application, could you give an applied example (or 2) please.
*Oh thanks for the reply*
Something like this?
deck 1 filter & param_multiply "deck 2 filter" & param_cast & deck 2 filter
I have a feeling this might take a while for me to understand the application, could you give an applied example (or 2) please.
*Oh thanks for the reply*
Posted Fri 30 Jan 15 @ 6:20 pm
synthet1c
looks like it's missing a back tick. And looks like you are calling two functions
cue_pos 0 & param_multiply "`get_time total 1000`"
// if the song was 4:00 | 240000ms
// if cue point 0 was at 1:00 | 25% | 60000ms
// and the play head was at 50% | 2:00 | 120000ms
var t = get_time( 'total', 1000 ) // get time in milliseconds | 120000ms
var c = cue_pos( 0 ) // get the position of cue 0 as a percentage | 25%
t = 120000
c = 25%
t * c = 30000
It's not a good example, but what you should take from it is that you can use the return value of a vdj script action as the modifier of different one.
It looks like you execute the script by wrapping it as a "string" and wrapping it again in `back ticks` for the executable part. eg the syntax would be:
initial_value & param_multiply "`get_some_value`"
that's how it worked with some of the old skin functions from what I remember.
All completely untested...
cue_pos 0 & param_multiply "`get_time total 1000`"
// if the song was 4:00 | 240000ms
// if cue point 0 was at 1:00 | 25% | 60000ms
// and the play head was at 50% | 2:00 | 120000ms
var t = get_time( 'total', 1000 ) // get time in milliseconds | 120000ms
var c = cue_pos( 0 ) // get the position of cue 0 as a percentage | 25%
t = 120000
c = 25%
t * c = 30000
It's not a good example, but what you should take from it is that you can use the return value of a vdj script action as the modifier of different one.
It looks like you execute the script by wrapping it as a "string" and wrapping it again in `back ticks` for the executable part. eg the syntax would be:
initial_value & param_multiply "`get_some_value`"
that's how it worked with some of the old skin functions from what I remember.
All completely untested...
Posted Fri 30 Jan 15 @ 8:23 pm
rapidfirearts
It does not work for me on VDJ8 Pro :(
I'll give it a try when i get my hands on a 7 machine.
But if they removed this feature in 8, it would be a real downgrade :/
I'll give it a try when i get my hands on a 7 machine.
But if they removed this feature in 8, it would be a real downgrade :/
Posted Mon 02 Feb 15 @ 2:15 am