apster07
Hoping I can get some help here as I've been relentlessly been googling this issue without luck. Previously I used to run Virtual DJ 7/8 and would run my old controller with that. Now that I've turned to 2021 with my new DDJSB3 im having some issues figuring Cue points out.
My entire VDJ career, whether it was on my previous hardware controller OR on the software itself, pressing the standard CUE button would save a CUE 1 position in the song and store it forever. So if I ever unloaded and reloaded the track again even immediately after it would start right back up at that cue point.
Now with VDJ 2021, pressing CUE on my hardware controller OR on the software it only sets a temporary GREY cue point that goes away if I reload the song. My question is, is there any way to go back to the old way of setting a hard cue point by only pressing CUE and not having to click on HOT CUE's?
Thanks again.
My entire VDJ career, whether it was on my previous hardware controller OR on the software itself, pressing the standard CUE button would save a CUE 1 position in the song and store it forever. So if I ever unloaded and reloaded the track again even immediately after it would start right back up at that cue point.
Now with VDJ 2021, pressing CUE on my hardware controller OR on the software it only sets a temporary GREY cue point that goes away if I reload the song. My question is, is there any way to go back to the old way of setting a hard cue point by only pressing CUE and not having to click on HOT CUE's?
Thanks again.
Inviato Mon 12 Sep 22 @ 4:06 am
PhantomDeejay
It IS possible by remaping
Remap your controller cue button to this:
This code will give you a VirtualDJ 7 alike behavior.
The CUE button will set/update the last used hotcue (or hotcue 1 if no hotcue exists)
If you want just to set hotcue 1 if it doesn't exist but not mess with the rest hotcues (like on VirtualDJ 7 where you could mess up hotcues by mistake via the CUE button) then use this code instead:
Remap your controller cue button to this:
play ? cue_stop : cue ? cue_stop : (param_equal get_cue 0 ? set_cue 1 : get_cue & param_cast & set_cue) & goto_cue
This code will give you a VirtualDJ 7 alike behavior.
The CUE button will set/update the last used hotcue (or hotcue 1 if no hotcue exists)
If you want just to set hotcue 1 if it doesn't exist but not mess with the rest hotcues (like on VirtualDJ 7 where you could mess up hotcues by mistake via the CUE button) then use this code instead:
play ? cue_stop : cue ? cue_stop : param_equal get_cue 0 ? set_cue 1 & goto_cue 1 : cue_stop
Inviato Mon 12 Sep 22 @ 11:37 am
I noticed that if you use the Cue button it creates a Cue 0.
Is this cue saved? I think he is saying above that it is not.
I am curious if there is anyway to replicate the DJuced behavior.
Cue is an altogether different cue than your hotcues. Kind of like Cue 0.
In DJUCED, no matter where you are in the song if playing it will go back to cue 0 and play until you release.
If you are not playing it will change the current spot to the Cue 0.
Is there any way to replicate this?
I came close but it looks like if there is even hotcue assigned than the cue verb goes to the latest cue, not directly to Cue 0.
Is this cue saved? I think he is saying above that it is not.
I am curious if there is anyway to replicate the DJuced behavior.
Cue is an altogether different cue than your hotcues. Kind of like Cue 0.
In DJUCED, no matter where you are in the song if playing it will go back to cue 0 and play until you release.
If you are not playing it will change the current spot to the Cue 0.
Is there any way to replicate this?
I came close but it looks like if there is even hotcue assigned than the cue verb goes to the latest cue, not directly to Cue 0.
Inviato Wed 16 Oct 24 @ 7:17 pm
user29376933 wrote :
I noticed that if you use the Cue button it creates a Cue 0.
Is this cue saved? I think he is saying above that it is not.
I am curious if there is anyway to replicate the DJuced behavior.
Cue is an altogether different cue than your hotcues. Kind of like Cue 0.
In DJUCED, no matter where you are in the song if playing it will go back to cue 0 and play until you release.
If you are not playing it will change the current spot to the Cue 0.
Is there any way to replicate this?
I came close but it looks like if there is even hotcue assigned than the cue verb goes to the latest cue, not directly to Cue 0.
Is this cue saved? I think he is saying above that it is not.
I am curious if there is anyway to replicate the DJuced behavior.
Cue is an altogether different cue than your hotcues. Kind of like Cue 0.
In DJUCED, no matter where you are in the song if playing it will go back to cue 0 and play until you release.
If you are not playing it will change the current spot to the Cue 0.
Is there any way to replicate this?
I came close but it looks like if there is even hotcue assigned than the cue verb goes to the latest cue, not directly to Cue 0.
I took the 2nd block of code you created and after the first cue_stop I put a 1 to go back to hot_cue 1.
This seems to work, but is there any way to set this up without using one of the hotcue buttons?
Thanks,
Hernando
Inviato Wed 16 Oct 24 @ 7:29 pm
PhantomDeejay
No.
In VirtualDJ temporary cue (Cue 0) does not get saved between program restarts.
In VirtualDJ if you want a cue to get saved, then it MUST be a hotcue.
Now, I'm not familiar with DJUCED but from your description you can try this:
play ? down ? goto_cue : cue_stop : cue_stop
This script will use the "last used" cue.
If you don't use any hotcue after loading the track, that will be cue 0
If you use a hotcue, then it will be that hotcue.
In VirtualDJ temporary cue (Cue 0) does not get saved between program restarts.
In VirtualDJ if you want a cue to get saved, then it MUST be a hotcue.
Now, I'm not familiar with DJUCED but from your description you can try this:
play ? down ? goto_cue : cue_stop : cue_stop
This script will use the "last used" cue.
If you don't use any hotcue after loading the track, that will be cue 0
If you use a hotcue, then it will be that hotcue.
Inviato Thu 17 Oct 24 @ 6:32 am