What is the 26ms shift issue when converting cues/loops between softwares?

Found very interesting article related why the beatgrids and cues/loops might not match …

So, the probelm might not be that our tools are working incorrectly.
When we are using different tools we are editing mp tags resulting incorrect data into them.

=> Tools doesn’t know how to handle the incorrect data.

And the actual root cause might be the encoder sw entering incorrect data to files.

1 Like

So remember this when moving data using new OneLibrary.

The article talks of 6% of the files beeing offseted by 26 ms.
A terrible quality control :rofl:
10000 files > 600 “not correct” files. its going to be lot of work … and surprises.
And no way to detect which file is badly transfered by the OneLibrary.

i tested it before reading all this, and the first cue of the first track I played in djay was a loop and it was wroooong, hahaha.

hahaha!
I thought i was alone. For years I fought with encoder shifts - they actually worse with MP4’s - i think a much larger % of tracks have shifted cues n loops. Dealing with a shifted cue is easy because sync can take care of it, but a shifted loop can’t be used whatsoever! You have to delete and redo afresh

I handle my track prep in serato (inputting cues and loops), then djay reads those. Most of the time they’re not shifted though when you meet that one track with a shifted cue/loop, it’s so annoying.