Lexicon version: 1.8.5
Operating system: Windows
Bug description: After the update to 1.8.0 the cue point generator is acting very randomly. As you can see, with a track with the Cue Points generated in version 1.7.0 it perfectly detected the points where I need the Cue Points.
But if I regenerate the cue points with the new version, they become more imprecise, detecting the initial beats of an extended version as Drop.
That’s the template I am using:
Step by step to reproduce: In my case, it’s enough to analyze any track.
I would appreciate help or knowing if there is any way to revert back to version 1.7.0, where the Cue Point generation system was slower but gave me better results.
Thanks!
With 1.8 the cue generator received a complete rework, the old code was quite inefficient, didn’t work for everyone and had no support for Apple Silicon. The new code is much much better and faster. But the results are slightly different, better in some cases and worse in other cases.
Anyway it’s much easier to make upgrades to the algorithm now too so if you send me tracks that it fails to detect the drop on, I might be able to improve it there. Looking at those screenshots, it seems like it should be able to find the first drop.
If you want to help there, you can upload tracks, more is better: You can upload with this link: http://upload.lexicondj.com
Hello Christian,
I’ve just uploaded some tracks across different genres. Someone through the official LExicon YouTube channel told me there was an option to allow the drop to be at the start but it got removed in 1.8 so now Lexicon decides if the drop (high energy section) is immediately at the start or not. If you can consider adding this option again I think the results will be better.
Thanks!
