When attempting to import my EngineDJ library Mixo stalls out at “Parsing Data”, Start Import button greyed out. I’ve let it stay on the screen for over 30m a couple times now. Just started happening today, I’ve restarted the computer and verified the m.db file is present and folder location correct.

I’ve been adding and updating tracks in the EngineDJ app, but haven’t touched any of the database files.

Any help appreciated, thanks!

Using Mixo 12.15.0, on macOS Tahoe 26.5.2

Please can you send me your m.db? I'll try to replicate and fix it for you :)

You can upload your file here:
https://www.mixo.dj/uploads

Uploaded, thank you for your assistance.

Thanks, I think I've fixed it.

I downloaded the new m.db version you uploaded and replaced the old one. I also ran the v2.16 Mixo update before attempting to import EngineDJ library again. It still seems to be stalling out at Parsing Data, not sure the fix worked. I’m going to leave Mixo open and let that process keep running, just in case. Is there anything else we should try? Maybe we delete the Mixo library and have it start fresh?

I just use Mixo to transfer/update my EngineDJ library (I have a Denon SC Live 4) to Rekordbox (when I’ll be using Pioneer decks). So I’m okay with wiping the Mixo library if necessary.

Hi there, sorry was going to message you to say this fix is live.

I didn’t upload anything, I just tested with your m.db, noticed an error, fixed it and parsed your whole library. Parsing took about 2 seconds FYI.

Not sure why it doesn’t work for you!

It’s all handled, but as a test you could remove the hm.db file from that folder first.

If that fixes it, please upload the hm.db and I should be able to solve it.

You can upload your file here:
https://www.mixo.dj/uploads

Ah, I see. So I removed the hm.db file, Mixo import was successful and parsing only took a couple seconds as you said. hm.db file uploaded. Everything seem back to normal thank you!

Thanks for that! It was related to History lists that had no tracks, a weird anomaly that I hadn't accounted for.

That will be handled in the next release.

Meanwhile, I've attached a fixed version of your hm.db for you to use, that won't cause the error.