Engine DJ export silently does nothing on Linux 2.19.0 – defineDbList() returns empty
Engine DJ export on Linux 2.19.0 silently does nothing for the internal Engine library.
I traced writeToEngineDjDB() and found that defineDbList() only adds an internal root for macOS (/Users/) and Windows (C:). On Linux it only iterates over getExternalDrives().
My Engine database is:
/home/user/Music/Engine Library/Database2/m.db
Therefore defineDbList() returns {}, this.drives is empty, and the loops that open/write the database are skipped. The function nevertheless returns "done".
strace confirms that m.db is never opened during export.
Engine DJ itself uses this exact database and PRAGMA integrity_check returns ok.
This appears to be a Linux-specific bug in defineDbList() for the internal Engine DJ library.
Serafin
• 15 days ago
I traced writeToEngineDjDB() and found that defineDbList() only adds an internal root for macOS (/Users/) and Windows (C:). On Linux it only iterates over getExternalDrives().
My Engine database is:
/home/user/Music/Engine Library/Database2/m.db
Therefore defineDbList() returns {}, this.drives is empty, and the loops that open/write the database are skipped. The function nevertheless returns "done".
strace confirms that m.db is never opened during export.
Engine DJ itself uses this exact database and PRAGMA integrity_check returns ok.
This appears to be a Linux-specific bug in defineDbList() for the internal Engine DJ library.
0
Serafin
• 15 days ago
I modified the Linux path handling so that the user’s home directory is added to the drive list used by defineDbList().
After that, MIXO immediately detected and opened
/home/user/Music/Engine Library/Database2/m.db
and the playlist export worked correctly.
So the missing internal Linux path handling seems to be the actual cause.
I only patched an extracted local test copy of MIXO; the original AppImage was left untouched.
0
Remko
• 14 days ago
I'll get the default path added for Engine and Serato so it's automatic in the next release.
0