Hi all,
Prime4 on 2.0.1
Symptom: When setting the CUE to somewhere in the song, the “1” - BarCounter moves there automatically and remains there for future.
This is also the fact when using the AUTOLOOP Feature (Shft+Loop), which will also automatically move the CUE (even without touching the CUE button).
Comming from Traktor the “1” BarCount is where the GRID starts so it is some “holy grail” in the Song.
Question: What is the benfit of this behaviour on my P4??
Major Downside: Next Time I load the song it is loaded at the CUE Point which is somewhere in the song (e.g. I triggered a AUTOLOOP) and not where I initially placed it. (I know: THIS is a setting I could turn off)
How to switch off this behaviour “pressing CUE → set BarCount=1” ?
In my case… in some tracks jumps to CUE point and in other ones sets CUE point. But I don’t found the logical or why happens. Really it’s like Shift was sometimes pushed by default sometimes not.
All the tracks are analyzed in EnginePrime before. And happens two/three times on last two weeks.
First time I was shocked trying to understand… now, just living with it.
Also, if you ever press the CUE button anywhere in a song, the next time you load that song it is remembered. That button is bizarrely a permanent cue button.
I put a bug report in for this once as I never realised it was intended behaviour after coming from Serato DJ. I couldn’t work out why my tracks was loading at the end it it turns out that I was tapping the CUE button by a force of habit and it was loading from this point the next time the track reloaded.