Hi - I'm struggling to understand how CUE functions on the WeGO3 when using Djay2.
* * * To be clear, I'm refering to the CUE button next to PLAY/PAUSE, NOT the 4 Cue Point buttons * * *
What I would EXPECT to see is...
Load track
Find the point in the track where I would like to set this cue, say the first beat
Press the CUE button
Now, if I press it again it will play from that point until I let go of the button, where it will then jump back to that point. So as you see the pros doing on CDJs - CUE-CUE-CUE-CUE-CUE-PLAY.
What I ACTUALLY see is...
Load track
Find the point in the track where I would like to set this cue, say the first beat
Press the CUE button
Track jumps back to start of the the whole track, not the first beat, just the start of the track
It doesn't seem to matter whether the track is paused or playing, at the first beat, last beat, random point in the middle, as soon as I hit CUE it just jumps back to the start.
Is this right? I know Djay2 has a non 'standard' way of dealing with this where there is a 'set cue' and 'cue' button on their UI so wonder if it's to do with that, ie. set the cue with the 'set cue' button on the UI then use the CUE button on the controller - surely not though?
Just in case it's software related I've posted this on Algoriddim's forum too.
La publicación no admite más comentarios.
Hey mark! I had the same problem. The way you do it is. Load the track an hit the play button first then pause it. After that then use the jog wheel an set your cue with the cue button. Just make sure your hands on the jog when setting the cue. Not sure why algoriddim don't fix that. It's clear that it's a software issue
@Mark > I understand what you're saying - @Steven is correct; you need to play/pause first. It's a software method-of-operation, not something wrong with the hardware. After a bit of use you'll get used to it. ;)
Wow, how unobvious is that - good one Algoriddim! Matches the screwed up jog wheel pitch bend mapping, I guess.
Thanks so much for the advice.