Just updated Engine DJ to latest version (4.2), downloaded the Stems software as requested, activated Stems in the preferences but… nothing! I drag a track into stems playlist but nothing happens. I’d tried reinstalling Engine DJ and starting a fresh installation and download but still nothing. Im running a Macbook Pro 64Gb, M1 Max, OS Version: 14.6.1
I don’t have any clue what is going on here, but when I move anything to the stems folder myself, a log file is created in C:\Users(username)\AppData\Local\AIR Music Technology\EnginePrime\Logs.
Can you check whether you also see a logfile there, and upload it if so?
Right click and click create stem on the tracks.
Tried that… still nothing
I’m running on a Mac so the log files will be stored at a different location to where you describe - but I’ll try and find a log file
Still nothing as in it’s not there, or nothing is running?
Stems playlist there but nothing runs
One thing you can try is what others have found that works for them.
Right-click a track and re-import the track info. Then try again. Does it work after this step? Many have had success after this.
If it works, highlight all your tracks and re-import the data. You can make stems then.
Thanks for the advice but it didn’t work. Still no stems and no reply from Denon support either. Just a bit of background too - I’ve worked in IT and am very computer literate so have tried all the obvious things. this is definitely a bug. I don’t think this latest version of Engine DJ has been fully tested. I’d be interested to hear from anyone else with the same problem. I also use Lexicon and was wondering if this could be causing a conflict?
Would be nice if you stated 3rd party database tool Lexicon in your first post.
1 Like
Just some background info on the issue, regarding Engine stems in combination wtih Lexicon:
There is a database ID for each track in the Engine database. If that refers to the ID of the main database, then Engine can generate stems for it and places the stems files on the same drive as your tracks.
What Lexicon used to do is make that database ID refer to the Lexicon database. That’s why stems can’t be generated because Engine thinks the tracks are external tracks. At the time this seemed like the logical approach because it made more sense when importing tracks from an external database back into Engine or Lexicon.
In the beta I’ve changed it so tracks synced from Lexicon to Engine are using the same Engine database ID again, so Engine should be able to generate stems again for those tracks.
As for reports that the beta does not work, I still have to investigate that. It might be related to some existing databases which is why I recommend deleting the Engine database so a clean database is recreated. If all your tracks are in Lexicon, only a full sync is required (and a re-analyze in Engine on all tracks) and you should be good again. Going to work on that after the weekend so hopefully I can make it so an Engine database wipe is definitely not needed.
5 Likes
Thanks for all your hard work, Christian
1 Like