the SOUND INSURGENT
Trying a new pad page but every time I click on it, VDJ just crashes and then reopens.
Can someone look this up please??
Can someone look this up please??
Mensajes Tue 22 Oct 24 @ 9:16 pm
Adion
What's in the pad page? Looks like there's a pad calling itself or something like that
Mensajes Wed 23 Oct 24 @ 4:00 am
Adion
Looks like it's just too many &
It might work if you break it up like (a & b & c) & (d & e & f)
It might work if you break it up like (a & b & c) & (d & e & f)
Mensajes Wed 23 Oct 24 @ 1:59 pm
locoDog
@tsi What is that padpage doing? I can read the script but I can't figure out how that works for a real world use.
Mensajes Thu 24 Oct 24 @ 5:49 am
the SOUND INSURGENT
Its supposed to add cue points every 32, 16, or 8 bars depending on the button you push and then automatically run through a folder, basically a set it and forget it.
The other half is supposed to delete your cue points, again a set it and forget type thing.
Here's where I got it from, https://www.youtube.com/watch?v=2VteNFY7ESg
I have a script already kinda like this so I was curious as to how his works.
The other half is supposed to delete your cue points, again a set it and forget type thing.
Here's where I got it from, https://www.youtube.com/watch?v=2VteNFY7ESg
I have a script already kinda like this so I was curious as to how his works.
Mensajes Thu 24 Oct 24 @ 1:55 pm
locoDog
Try these instead, the "100" can be changed to -1 if you just want to run until it hits bottom, I also added in; 2nd press stops the thing, also if browser points to folders it stops the thing.
This should be easier all round [shorter, easier to adapt/human read, faster to run, safer]
I could go a little further with a song_pos check before every cue placement [no point adding more cues if we're at the end already] , but kept it readable for you.
add every 64
delete upto cue 4
This should be easier all round [shorter, easier to adapt/human read, faster to run, safer]
I could go a little further with a song_pos check before every cue placement [no point adding more cues if we're at the end already] , but kept it readable for you.
add every 64
repeat_start_instant every64 ? on & repeat_stop every64 : off & repeat_start_instant every64 50ms 100 & ( browser_window folders ? repeat_stop every64 : browser_window sampler ? repeat_stop every64 : ) & load & set_cue 1 & goto +64 & set_cue 2 & goto +64 & set_cue 3 & goto +64 & set_cue 4 & browser_scroll bottom ? repeat_stop every64 : browser_scroll +1
delete upto cue 4
repeat_start_instant deleteCues ? on & repeat_stop deleteCues : off & repeat_start_instant deleteCues 50ms 100 & ( browser_window folders ? repeat_stop deleteCues : browser_window sampler ? repeat_stop deleteCues : ) & load & delete_cue 1 & delete_cue 2 & delete_cue 3 & delete_cue 4 & browser_scroll bottom ? repeat_stop deleteCues : browser_scroll +1
Mensajes Thu 24 Oct 24 @ 3:16 pm
the SOUND INSURGENT
Yeah it was a nice time saver but it's only if your tracks don't have any lead in time. I just wanted to see if it was any good and yes it'll work but the cues would never be in the right place.
Thanks for the scripts tho 👍🏾
Thanks for the scripts tho 👍🏾
Mensajes Thu 24 Oct 24 @ 8:27 pm
locoDog
set cue 1 manually and remove the set_cue 1 bit from the script.
Mensajes Thu 24 Oct 24 @ 8:33 pm
PhantomDeejay
Assuming that CBG is set correctly (or you fixed it) you can use goto 0 to go on the downbeat.
repeat_start_instant every64 ? on & repeat_stop every64 : off & repeat_start_instant every64 50ms 100 & ( browser_window folders ? repeat_stop every64 : browser_window sampler ? repeat_stop every64 : ) & load & goto 0 & set_cue 1 & goto +64 & set_cue 2 & goto +64 & set_cue 3 & goto +64 & set_cue 4 & browser_scroll bottom ? repeat_stop every64 : browser_scroll +1
Another similar script I made for a friend is this:
goto 0 & set_cue 17 & set 'CueCounter' 17 & repeat_start_instant 'setcues' 100ms 300 & (goto +32 & param_bigger `get_time elapsed 1` `get_time total 1` ? cycle 'CueCounter' 360 & get_var 'CueCounter' & param_cast integer & set_cue : repeat_stop 'setcues')
This is not meant to traverse the browser. Instead it adds cuepoints (starting from cue 17) every 32 beats until it reaches the end of the track.
I think it can be modified to also traverse the browser, but I'm not keen to do the script at the moment if it's not needed by any
repeat_start_instant every64 ? on & repeat_stop every64 : off & repeat_start_instant every64 50ms 100 & ( browser_window folders ? repeat_stop every64 : browser_window sampler ? repeat_stop every64 : ) & load & goto 0 & set_cue 1 & goto +64 & set_cue 2 & goto +64 & set_cue 3 & goto +64 & set_cue 4 & browser_scroll bottom ? repeat_stop every64 : browser_scroll +1
Another similar script I made for a friend is this:
goto 0 & set_cue 17 & set 'CueCounter' 17 & repeat_start_instant 'setcues' 100ms 300 & (goto +32 & param_bigger `get_time elapsed 1` `get_time total 1` ? cycle 'CueCounter' 360 & get_var 'CueCounter' & param_cast integer & set_cue : repeat_stop 'setcues')
This is not meant to traverse the browser. Instead it adds cuepoints (starting from cue 17) every 32 beats until it reaches the end of the track.
I think it can be modified to also traverse the browser, but I'm not keen to do the script at the moment if it's not needed by any
Mensajes Fri 25 Oct 24 @ 10:22 am