You can tweak the times of the script, but remember, the wait time (2000ms) must always be smaller than the scroll time (3000ms) you'll never be sure that will work and will mostly loose time if you really want be sure it will run and not loose time, slow computer, overload, analyzing, read errors, slow network, big files, skip missing. You can tweak the times of the script, but remember, the wait time (2000ms) must always be smaller than the scroll time (3000ms) We will delay the execution for 2 seconds, which should be plenty of time for most cases: repeat_start_instant 'RunThruBrowser' ? repeat_stop 'RunThruBrowser' : repeat_start_instant 'RunThruBrowser' 3000ms & browser_scroll bottom ? repeat_stop 'RunThruBrowser' : browser_scroll +1 & load & repeat_start 'DoActions' 2000ms 1 & set_firstbeat & set_cue 1 What's vital on the above additions to the script besides the wait time, is the number of repeats (1) So, since we use a repeat_start and not a repeat_start_instant action and we execute it only once, we effectively are delaying the execution of it's actions.
Virtualdj script debugger code#
"Load" is not instant and you need to let some time pass by before you perform any other action So repeat_start_instant 'RunThruBrowser' ? repeat_stop 'RunThruBrowser' : repeat_start_instant 'RunThruBrowser' 3000ms & browser_scroll bottom ? repeat_stop 'RunThruBrowser' : browser_scroll +1 & load This is the code that will advance the current folder every 3 seconds and will load the track Now we will add the rest actions (that you'll need to edit) with a second repeat just to "delay" the execution after loading the track.
Actually, you need two repeats: One repeat to scroll the browser and one repeat to do the rest actions.
0 kommentar(er)
