Idk if anyone else has encountered this, but many of my tracks are playing completely different songs when I try to activate stems. I have 1 track loaded - Marcia Aitken’s ‘I’m Still in Love’. And when I activate stems its playing Miley Cyrus. This is not ok lol
I tried to share a clip but I just registered and it says I cant upload attachments bc Im new 
You can use we-transfer and provide a link here.
I listened to this advice and went through all of the trouble to post the link here, receiving an error message saying “Sorry, new users cant put links in posts” 
Lame AF.
Basically, when I hit the hot cue on my prime4+ to access the 4 pads that control stems, and then hit any one of those pads, it immediately plays a different song, as if as its been playing another song secretly underneath the song I actually chose to play. I only had one song loaded on one deck at the time. I tried to see if it was just happening to that one song, and its happening with like 70% of the songs in my library.
I just got granted access to post a link. Here it is:
Hi
You have wrong stems code in the database. Stems are selected from Track ID from m.db database, in table “Track”. Stem file name begin with that code. The first numbers of stem file name must match with the Track ID.
Ej. 988 877cec43-d48f-4ec6-8743-3fe6ec4b10f5.stems file match with track ID 988 in Track table.
You can delete stem files with errors and recreate stem files,
Did you copy stems folder from another system with other database?
I’ve been using lexicon to update my library and I figured that’s what caused it, but didnt know how to fix it now. Im not sure where the “track table” is? How do I find it?
This was also reported by @crazycraig here: Stems allocated to incorrect tracks In that case there was an error while creating stems. Once they were recreated things were correct.
Still, this should be transparent to the user and not happen. Albeit, maybe it’s a bug particular to @SXRGWRLD’s configuration.
I’m still on 4.1. If I remember correctly, you can’t preview the stems on Engine DJ desktop, only listen to / use them in Engine OS. If true, then it would be helpful to have a preview to check at the point of creation. I could not find a feature request for that. Since, I’m not on 4.2, it’s not my place to create it. Maybe it’s not even an issue to those using stems.
Ahh, the more cooks in the kitchen the more can go wrong. @SXRGWRLD, you should delete the stems and recreate them. You don’t want to be messing around in the m.db “track” table.
Tracks table IS inside m.db database, in database2 fólder. Its a sqlite3 database.
There are a lot of free programas to open It but i do not recomend to modfy It if you are not sure what you are doing.
Yea I started to look at it then came back here and its probably best I dont mess with anything lol. Took me 3 whole days - 72 whole hours - leaving my laptop on to convert my entire library to stems the first time and looks like I have to do it again 
Small price to pay for having standalone stems but damnit.
I just deleted all my stems, and redid one of the tracks that I was having issues with to test before I redo my library, and that track is operating as it should now. Thanks yall. Will update if I continue to have the same issue.
I suggest you do smaller lots. Check them before moving on. Keep a backup of the Engine Library on each iteration.
Hey @SXRGWRLD have you run into this problem again since re-rendering your tracks? Did you only notice this issue after using lexicon? Did you ever have any issues with rendering tracks in Engine? i.e. Did you see a ‘Stems failed to render’ dialog on screen?
Hey all of my tracks finally finished rendering last night, didnt have a chance to check it today but can let you know when I do.
I started using Engine DJ and Lexicon around the same time so I cant really answer that 2nd question. I know when stems came out, Lexicon users (myself included) were having trouble creating stems, bc Engine DJ read Lexicon’s synced library as a remote library, and then they did an update that resolved that issue, but I believe that update is what caused this new issue. It sounds like maybe they didnt account for keeping track IDs consistent when updating the new library (I’m talking out of my ass here bc I rarely ever use terminal, I’m just a lowly DJ/Producer over here 
). These are the only issues I’ve had, and I only saw a ‘Stems failed to render’ dialog for a small chunk of songs that I believe all were low quality, (and need to eventually be replaced anyway) but dont think that related to this issue at all as 98% of my library was seemingly successfully rendered at some point pre-Lexicon update
i’m glad to hear this. Hope all go well.
I think than Stems identification based on file name is not the best way to do it. SoundSwitch uses a IDtag to refer the correct program for the track. So this way, It doesn’t matter the file name.
What do you think about it?
Honestly just knowing that that can even happen means if i wanna use the stems featiure, when cueing the track beforehand in headphones I now have to check to make sure its not just going to play a completely different song. I view this as Lexicon’s fault more than Engine DJ, but also it straight up should not even be possible for something like this to happen. This basically introduces a new problem that didnt exist before, where i now have cant trust that the song im bringing in is what people will hear (if i use stems)
So yea, maybe track ID isn’t the way if it introduces a new problem, but also, maybe now that Lexicon has adjusted, it could have just been a one time thing that won’t be an issue again? 