Sovled - Engine DJ 4.1 Not Analyzing Files or Syncing Metadata on M3 Mac

I’m having issues with Engine DJ 4.1 on my new M3 computer. While I can play tracks, the software is not analyzing or reanalyzing files properly. Specifically, when I try to analyze tracks, the BPM and key fields either disappear or populate inconsistently. Additionally, no waveform previews are shown in the column view, which suggests the tracks aren’t being fully analyzed.

  • Denon has full disk access, and there are no red (missing/corrupted) files. All songs are stored locally on this computer.
  • It seems like Engine DJ is not saving or connecting the metadata correctly, even though I can play tracks without issue.
  • When syncing my library from Lexicon to Engine DJ, only playlists are transferred, but no cue points or waveforms appear, indicating that the files are not being fully processed.
  • This problem is exclusive to the new M3 computer. I have confirmed that Lexicon and Engine DJ 4.1 work correctly on my M1 computer, suggesting the issue is specific to this setup.
  • I’ve also tried syncing with beatgrids unlocked to rule out any metadata conflicts, but the issue persists.
  • It feels like there may be a permission issue or a problem with the software saving data in the correct location.

I’ve backed up everything and tried multiple troubleshooting steps, but nothing has resolved the issue. Is there something I’m missing?

Have you tried a spanking new database?

You can look at the file stamp information in ~/Music/Engine DJ/Database2/. The modified date will let you know if Engine is correctly updating the database. The same can be done for any external media you’re using.

I’m suspect that Lexicon is 4.1-schema aware. Can you confirm that it is?

What MacOS are you on?

Though I own an M2 ProMax and have not installed 4.1 yet, IIRC, the binaries are compiled in x64. This means that Rosetta 2 is used to translate the opdcode .

@CommanderKeen:MacOS$ otool -l Engine\ DJ | more
Engine DJ (architecture x86_64):
Load command 0
      cmd LC_SEGMENT_64
  cmdsize 72
  segname __PAGEZERO
   vmaddr 0x0000000000000000
   vmsize 0x0000000100000000
  fileoff 0
 filesize 0
...

IT’S WORKING!!! I renamed my music folder, deleted engine and reinstalled it, turned off auto analyze within engine, full fresh new sync (which i’ve done multiple times but never renamed my music folder) and everything is working exactly as it should!!

3 Likes

Awesome.

This tells me there was something w/ the database file itself. :frowning:

For the record, I’m not an Engine Dev and don’t work for Denon/inMusic. I’m just a community contributor who has some dev experience with random things. =)

They should probably be paying you as a consultant or just hire you outright, tbh.

1 Like

:smiling_face_with_three_hearts: :smiling_face_with_three_hearts: :smiling_face_with_three_hearts:

While I’m not looking atm, i’d definitely welcome a conversation. I rather enjoy the intersection of music & technology.