Ok. So you’re a Windows and Lexicon user, and chances are since Engine 4.2 came out, some stuff is glitching. You can’t make stems being the big one.
There is a fix, and it’s relative ease is going to depend on how often do you make your USBs?
You see, your USB library doesn’t point to your library(s) and thus the lexicon glitch isn’t going to be present.
What worked for me:
Close Engine DJ
Take your existing engine library folder on your local computer, and rename it to “ZZZ Engine Library”. A backup of sorts.
Make a new Folder called “Engine Library” in the same directory as the old folder.
Grab your trusty (and hopefully recently made) USB. Stick it in your computer
Grab the USB’s Database2 folder & version file, and copy it to your new Engine Library Folder. No need to copy the music as it should be on your computer already.
Safely remove the USB.
Launch Engine. It is going to flag all your files as missing.
Select all and right click, and select “relocate tracks”
Point it at your computers music directory (where you keep your bangers, yo) and let it go to work. It won’t find all of them, even though they may be there.
Do the onesies and twosies and search those out. Call it housekeeping. Drink a coldie.
You should now be able to create the stems since the lexicon library pointing is gone.
Note: Do not launch lexicon until they get a fix in place. I know there is a beta lurking in their discord - but I work on guarantees. I am waiting for the release version.
Edit to add: It appears using lexicon’s current release build also messes up soundswitch’s ability to find music files via the Engine DJ collection. This fix above also resolves that. (I just tested it)
Interesting you mention that “more information is available on the lexicon homepage”.
I just went there. There is no mention about this bug their software causes on the home page. I even search the blog for “stem engine dj” and it returned zero results.
Care to provide a hyperlink to where you read this on their website?
I tried this and it didn’t work. It just couldn’t find the tracks. I even tried relocating specific tracks and it just didn’t work, showing that the track could not be found.
Sometimes you have to manually select each file, one by one, as opposed to doing a batch. I found out that of the 700 or so tracks in my active engine library, I had to manually find about 50 or so.
Normal Lexicon has the same fix for Engine 4.2 now as well.
Because the problem happens around database IDs, Lexicon tries to auto correct it but if for some reason it can’t, you may need to delete your Engine database. If your entire library is in Lexicon it’s no problem, a full sync will get you back to where you were. Only a re-analysis is needed then.
Unfortunately I can’t play experiment with lexicon right now. I’ve a gig coming up and I need to program lights and video and such and lexicon isn’t trustworthy (for me) just yet. I’ve got some rekordbox drives off to the side in case I hit some cdjs between them and now, so lexicon can wait. Engine is my primary database for now. Lexicon can wait.
4.2.1 Update for engine dj on windows didn’t change anything. I can’t use lexicon, as it didn’t meet my expectations and I canceled my subscription, so I’m just stuck here with a broken database. Hopefully engine dj devs fix the issue, as it seems like it has an impact on lots of users.
I have the usb I have exported my current playlist. I tried getting the db from it but it didn’t seem to work. I tried pointing to the files but nothing changed…