Been trying to figure this out all week, searching on multiple sources online and I can’t seem to find a definitive answer.
In short, I’ve analyzed all my tracks in Traktor in hopes of moving them to Lexicon and then to Engine for my System One.
When the tracks are imported, there is no waveform, but oddly enough, I can use the tool to automatically generate cuepoints. When I load the file to listen to it in Lexicon, the grid it totally different from what is visible in Traktor.
Is it just not possible to migrate from Traktor to Lexicon or even Engine directly while keeping the grids that Traktor has generated?
The grid and waveform are not the same thing. Lexicon has its own waveforms that it will need to generate, it’s not imported from Traktor. The grid should be imported and doesn’t just get overwritten unless you tell it to
Totally get that. But the gridlines are completely off, even after using the beat shift fixer. Unless I’m totally misunderstanding the functionality of the software, I’m expecting the the gridlines to match up. See screenshot below.
Beatshift fixer helps when the grids in lexicon are correct and you sync back to Traktor. Then they should be correct.
In your case you could shift them in bulk (there is a recipe) but you have to be sure all/most of your tracks need the same shift. If they are all the same filetype and come from the same place, that can work.
Alternatively, there are some more beatshift improvements in the beta version so that may help. For that, just import from Traktor again (merge disabled to start fresh)
Thanks, Christiaan. One more thing to note. I also use Mixed In Key. I had some test tracks analyzed in MIK. I made sure all the settings are accurate, in Lexicon the setting for loading Mixed In Key cuepoints/beatgrid is enabled. I’ve exported cuepoints in MIK and the cue points are not populating in Lexicon. I’ve reloaded tags and still nothing.
Any thoughts as to what can be contributing to this?
I’m not sure, might be the newest MIK version. I’ve seen it happen where MIK is not actually writing those ID3 tags (you can check with kid3).
Keep in mind cues only load from MIK if the track in Lexicon has no cues yet (to prevent accidental overwrite)
Yup. Must be a compatibility with the new MIK version. I tested it out by dragging a track into Serato and it loaded with the cue points. After that imported from Serato to Lexicon and it loaded the cue points as well. Lastly moved from Lexicon to Engine and same thing, loaded the cue points. Maybe this should be notated somewhere in case others are having the same issue.
Will do. You’re using MIK 11 ?
