From what i experience is that Denon Engine finds a way to mess it up once again.
Lexicon exports to rekordbox / traktor / serato seemed to work ok enough (some minor details but from what i read on the forum @Christiaan is on the case) and Engine too untill a couple of upgrades ago…
'm going to let it rest for a week now & set up a nice & steady list so i can quickly get back on track
Just had this problem (or very similar) happen. Every track jumped to SPEED -100 causing the BPM to be on 0 and the waveform way way stretched.
Then I tried to recreate it but I couldn’t… Super weird. Still on it though!
I fixed the bug I mentioned before. I’m not 100% sure it is the same bug as the 120 BPM bug but it is very similar. Next update has the fix, let’s hope it’s gone then.
@Christiaan "Then after that, you can run the quantize cues recipe to put all your cues exactly on the beatgrid. Not a perfect fix since these are auto generated beatgrids and the ones you maybe added by hand, but still much better than broken beatgrids everywhere.
The problem is more that the grid is off now… but the made cue markers are still on point… (this is actually a big positive!)
The fact that the made markers are still on the right places… can’t it be a guideline for a function in lexicon?
the function to align the beatgrid on made cue points…
For example:
cue1 is mostly my start point
cue2 is mostly my DROP1
I don’t know how much it is possible… but if there could be a recipe that sets the grid correct based on a cue the user can fill in …
The user selects a bunch of tracks
goes to edit
recipe
set grid accordingly to cue marker (the user can now choose on which marker lexicon is going to base itself to set up the grid)
=> priority is off course that the track 1st need to be analysed & have the right bpm set up…
@Christiaan - Sorry it took so long but sadly reporting the problem still exists with the latest update. Here are screenshots that illustrate the tracks’ original BPM, the alteration to 120 BPM, and the speed at 0. Hope this helps! I’ll keep an eye our for updates
Nice! When you export from lexicon, are you exporting the whole database or “only new tracks and playlists”
Well earlier when that 120bpm issue occured … i did a whole check up with:
deleting the Lexicon database
Importing the full Engine database to lexicon
Re-analyse the database in lexicon
4a) Recipe “Round BPM”
4b) Check up if all the new bpm’s were correct (some tracks needed to be corrected manually as they had bpm shift… (admitted… this took a while to perfect again… my advice is NOT to skipp this step!)
Select all tracks => edit => Use the recipe “quantise beatgrid” (since all my earlier made cue-markers were still on point, i use this feature to be almost 100% sure the beatgrid will be on point again (based on the cuemarkers))
Recipe “Replace Cue Text” (so the whole cue-marker system i use is in order over the whole lot)
Finally: 7) Sync from Lexicon to Engine again (full session)
=> Besides finding out every track has the correct bpm, it’s pretty do-able to correctly fix your database again (especially because of step 5 you’re pretty sure it will be perfectly on point!)
PS: admitted Cue’s totally on the beginning of the track (read: just before the timeline) tend to fall off… but with the simple CUE button on the gear you’ll assign it in no time when playing live. (later on you can refresh those edits again it to Engine when you connect your external device you use in your Prime gear to your computer again…) (=> I mostly refresh from my stick to Engine database (as those newly made edits are the way to go on the spot) after that i redo the whole process again and it works perfectly)
PS2: This is on a windows based system, i really do not know if the mac procedure works or not…
Ok cool, thank you. I tried deleting the Lesicon database with no results. It might be a mac issue. I am not importing from Engine though. I am importing from Serato, which might be a contributing factor. Serato beat grids nicely and I don’t want to risk losing any Serato data. I simply want this tool to shit out my serato library into the Engine format. Hopefully it works in the future. I understand this is beta and am looking forward to it working on release.
Nice. Yeah not sure. I’m still having issues on my second sync and there after. I have a large library of 500 gigs. Not sure if that makes a difference.