Yes, this helps. The waveform is still not exported (I have to play the track in Engine OS to see it), but the beatgrid now is OK. Unfortunately there is a slight offset in Engine OS:
The above is Lexicon, below is Engine. You can see that the beginning of the beat is correct in Lexicon but not in Engine. The difference is noticeable. Note that the magnification in both waveforms is nearly equal.
I tried the beatshift-function but it did not have any effect. And BTW: does the re-encoding decrease quality ?
I remember that putting on the beat lock did not solve the problem when I earlier tried Lexicon on my 20.000 files performance library. I will have another look on the problem with more than 1 file, and come back to you.
Please comment on the slight shift in the beatgrid.
Waveforms do not export to Engine, analysis is always required the first time a track appears in Engine. If the waveform in Engine disappears after a sync, then that may be a bug.
Re-encoding does not decrease quality, it re-encodes at 320kbps. The beatshift fixer should help there, although Engine is not really affected by beatshift in the first place, it’s pretty rare.
Try to remove the track from Lexicon completely, drag it in again and set a grid. Then sync it to Engine again. If that works then there was some old beatshift offset info that didn’t get removed for some reason.
analysis is always required the first time a track appears in Engine
Do I get this right – I import a track into Lexicon from my file system, analyze it, correct the beat grid and so on – and then export it to Engine. You are saying that Engine will analyze it because it is first time it sees it? This renders Lexicon unusable. I want the work I have done in Lexicon to be available in Engine.
If the waveform in Engine disappears after a sync, then that may be a bug.
No, it does not disappear. If the track has been analysed in Engine, a round trip to Lexicon and back keeps the waveform intact. But it does not transport changes in beatgrid I have done in Lexicon back to Engine. Same problem as above – this is not acceptable.
Try to remove the track from Lexicon completely, drag it in again and set a grid
That may be possible, but is not feasible. I cannot remove thousands of tracks from my database, reimport them into Lexicon, export them again to Engine and re-work everything on the beatgrids.
If that works then there was some old beatshift offset info
I deleted the whole Engine databases on all drives. What do you mean with “old beatshift offset info” ?
I come to the impression that your workflow with Engine is that we have to do all work in Engine. Adjust beatgrids etc. in Engine, then import to Lexicon to do some other work there not possible in Engine, and then export to Engine again. If this is so, we Denon-Users will have no advantage from Lexicon.
Please find a way to make changes (in beatgrid) we make in Lexicon available on Engine when we export.
Waveform is just not possible to generate in Lexicon so that will always be like this.
Denon devices generate on demand so totally possible to use Lexicon with them.
I think you don’t understand what Engine analyzes, it just adds a waveform (not beatgrid, if beatgrid is locked) so I don’t know why you are saying that it makes Lexicon unusable.
analysis is always required the first time a track appears in Engine
That means that things we do in Lexicon are lost when exporting to Engine the first time. Switch the beatlock on helps, but I showed you picture that beatgrids are still shifted. A small amount, but noticeable when mixing. You suggested to remove the track and reimport it again from file system. I definitely will not do this for thousands of tracks. I lose all beatgrid, cuepoint, loop etc. and must work on the tracks again. You cannot be honest with this suggestion.
I will look at larger amounts of tracks and see whether the shift is systematic or punctual.
