It might be a little below zero, but this is also allowed in EDJ, in fact on the console HotCue 1 is visible and functional.
Ok but if the sub-zero cue is allowed for both EDJ and Lexicon, then why does Lexicon move it forward? It could place it exactly on the ZERO position even if we do not obtain the same starting result taken from the EDJ library.
And also why with Lexicon Beta do I get the addition of all those red CUEs that don’t exist?
You have 2 options: move the cue forward to exactly zero or don’t show the cue at all.
Engine may allows cues below zero, but I question what use that is. It won’t be able to play them before zero, so activating them will effectively play them at zero.
I have some tracks that have Cue 1 set even 1 or 2 beats behind the start of the track. I use that solution when the track does not start correctly and the 4 complete bars are not respected, therefore in order to correctly align two tracks with the CUE you have to start the second track a little earlier so that when the track starts playing it is aligned with the 4 bars of the first track. I hope I have explained myself.
I used the latest beta (1.5.113). I imported the library from Engine to Lexicon from scratch.
Result: There are still some MP4 tracks with misplaced grid.
Among the various tracks with a shifted grid there are also the tracks that I sent images in previous posts, so it is useless for me to send the same images again.
The red hot cues have disappeared. But the grids are wrong, so we went back to the initial problem.
I discovered something, if it helps with this problem: the shifted grid only happens after importing MP4/M4A tracks from Engine DJ. Instead, if those traces are analyzed by Lexicon, they obtain a perfectly aligned grid.