locoDog
Another user brought up a problem that after applying a script of mine the skin hotcues just rewrote themselves,
after some messing about I was able to recreate it
Have this script on a custom
pause ? has_cue 2 ? cue_play 2 & play while_pressed : hot_cue 2 : hot_cue 2
Pause the track, press the button, keep pressing the button
Now all on skin cues will rewrite themselves until V8 is restarted
after some messing about I was able to recreate it
Have this script on a custom
pause ? has_cue 2 ? cue_play 2 & play while_pressed : hot_cue 2 : hot_cue 2
Pause the track, press the button, keep pressing the button
Now all on skin cues will rewrite themselves until V8 is restarted
Mensajes Tue 24 Feb 15 @ 5:18 pm
PhantomDeejay
That script is WRONG and therefore it's normal to misbehave.
cue_play as an action will preview the deck as long as you keep the button pressed and if you keep it pressed for more than 2 secs it will start the deck (in other words the track won't return to the cuepoint when you release the button)
So basically on cue_play 2 & play while_pressed part you use contradicting functions. You should either use "cue_play 2" or "goto_cue 2 & play while_pressed"
I already posted on another thread that you should avoid the "while_pressed" expression when you use actions that by default act in a temporary way.
For instance "cue 2" will preview the cuepoint 2 while you keep the button pressed. There's no need to use "cue 2 while_pressed"
cue_play as an action will preview the deck as long as you keep the button pressed and if you keep it pressed for more than 2 secs it will start the deck (in other words the track won't return to the cuepoint when you release the button)
So basically on cue_play 2 & play while_pressed part you use contradicting functions. You should either use "cue_play 2" or "goto_cue 2 & play while_pressed"
I already posted on another thread that you should avoid the "while_pressed" expression when you use actions that by default act in a temporary way.
For instance "cue 2" will preview the cuepoint 2 while you keep the button pressed. There's no need to use "cue 2 while_pressed"
Mensajes Tue 24 Feb 15 @ 6:26 pm
locoDog
Spotted that reply, replied there (I hadn't seen this reply then) I don't want to cross post so kill this thread.
Mensajes Tue 24 Feb 15 @ 6:54 pm