Addressed this problem before,
when using a hotloop And jump from this loop to a hotque, its just plays the loop
from beginning.
Not all fixes are detailed in the release notes, best bet is to try it and if it doesn't work now, wait to see about the next version as they may not have had time to address it yet.
Post is closed for comments.
Wasn't able to reproduced the problem on 4.3.0. Watched your videos three times but wasn't sure of the issue, there's a lot going on, three cue points all sound too similar to me.
From your video, it looks like you're just not pressing the 2nd button hard enough to get it to change -- but playing the loop from the beginning; is that not where you had the hotcue set?
Im pressing the button hard enough, believe me!
No the quepoint i press is a que AFTER the loop, the loop is at 4bar and the other que
is just before the 8th bar. This ONLY happens in DVS mode, so without turntables and only the controller its fine.
Ive made a other youtube clip, please watch:
https://www.youtube.com/watch?v=1HsEkdGu3qE&feature=em-upload_owner
You even see when pressing the hotque B (thats is a few bars before the loop)
the track still goos in loop.
You see me pressing C, that should be further in the track, but it just goos to play the loop again, and even the loop is not a visible yellow bar???
here is a picture, you see the loop is on H, B is a first bar C is the intro of the song
and please Pulse, im struggling so long with this now, maybe you can recreate this
with your gear for a faster solution?
I got a new video:
https://youtu.be/NCvlxMkmdDM
@michel > Thanks, that last video shows the issue much more clearly! I'll see if I can replicate it here and pass it up to the product team. If I need any other info I'll let you know.
@Pulse> Thats great! Thanks!!
@Pulse> did you manage to replicate the issue?
@michel > Yes, the same thing happened, even with 4.3.1 (although in 4.3.1 the background doesn't appear blue after pressing C the same way it does with 4.3.0).
I'll pass this up to our product team.
okay cool
Our engineers were able to replicate the issue and are working to determine the cause and integrate a fix. Thanks for your patience.
Perfect thanks!!
I read in the release note of 4.4.0 that this problem is not addressed?
whats the status on this?
