What can I do? Re-Import track information doesn‘t solve the problem. i Never used Lexicon.
Some Information: The files are on the internal Prime 4+ SSD.
MacBook Pro 2022 M2 8GB Ram
I already created hundreds of stems but now this message shows up every time I try to create stems on my other Tracks.
This is the message I get using Widows too. I have not yet created any Stems as allways get this message.
1 Like
Seeing this issue a lot too. Seems to pop up constantly after it’s tried to render a mp3 that is either in mono or in some way different to the majority of the other mp3’s. Restarting EngineDj seems to resolve the problem… as long as you skip the problematic (different in some way or another) mp3. Until you hit another ‘problematic’ mp3.
Restarting Engine DJ and Even restarting my Mac doesn‘t solve the problem 
Same here on a M2 Macbook Air with 8GB Ram. After approximately 200 stems processed it stops with the error message above. After restart will do another 200 and so on. It is not an issue of particular files though. After restarting the previously failing ones can be processed.
mono audio files can’t be “stemized” because stems need to be distributed in a stereo space to work.
It is also possible that you have tracks marked as stereo, but in reality inside it is mono doubled on the left and right (dual mono). This will not work either.
Often youtube rips (which are to be avoided)
I can’t confirm that. I have the track The Beatles-She loves you in mono version-Stems can be created without any problems
Check your free space on your drive - do you have a ridiculously big purgeable space, and a full drive?
It may be a mono recording but will probably still be rendered in two identical channels as stereo. I guess if you open it in Audacity or something like that you’ll be able to tell.
I can 100% confirm what Gaian is saying. When I took a look at the log files created, I pulled the problem tracks into audacity & discovered they were indeed mono (one single waveform, with centre pan). Creating a 2nd identical track & panning each, one left & one right, then exporting as mp3 - then stems for that track was created. I have no idea of what it sounds like as I don’t have a P4+… but it did create stems for it. However I do feel like Denon needs to refine this process to simply skip over the problem tracks & continue with the rest. I’m also seeing memory (virtual & ram) issues when creating stems in bulk. This is with a M1 macbook pro 8gb ram, 500gb ssd. Engine Desktop def still needs some work in this regard.
This is odd, because I do get an error warning, if mono files are in a selected bulk. But after confirming, the stems creating process starts with the rest of the files.
1 Like
Actually you’re correct. I have seen that message. Sometimes it gives a mono error message, othertimes it gives the message shown above. Perhaps that is due to something else & Im assuming incorrectly. I think its time for some input from the devs as to what could be causing this error.
You’re right- two mono channels in one track=dual mono