So I’m wanting to move my music files off my local MacBook drive to iCloud. I have multiple back ups and I have SSD’s installed in each of my SC6000’s so redundancy is there in case of failure. After searching here and finding many of the same issues I’m having, I thought I’d post again. So to test … I moved about 10 files from my local drive to iCloud (which is synced to the Mac). The files went red and I highlighted them, clicked Auto relocate all and nothing. Manual relocate works fine but Auto does not. I’m petty sure I’m not missing anything unless the Auto Relocate only checks locally connected drives.
Autorelocate is lacking in its ability to find music outside of the home directory.
Lmk if you want some offline help with this. I can offer you a few steps to gather some data and I can write a script to update your DB(s?) for you if you wish.
1 Like
Hit me up on Discord. How about this solution? I took a brief look at Lexicon. It has rave reviews for library management and can export to almost anything. The $40US a month subscription is too pricey however. But… if I imported EngineDJ to Lexicon (get the 1st month discount), moved the files, relocated the files in Lexicon, then exported back to EngineDJ. Perhaps that would work? I haven’t dug too deeply into it yet but just thinking out loud.
I’m also trying to relocate my library from my computer’s drive to an external SSD and am grappling with how to do that without manually relocating every song. I don’t want to have to get additional software like Lexicon! Engine, what can I do!
Without experience in some programming SQL and something like PowerShell or Bash, manual is the only option. It’s such a shame that this feature is not even close to half baked.
Complete novice here, who’s never actually tried this (probably talking nonsense), but can you open the DB file up in notepad ++ then use a simple replace function to change the first part of the file path so it points to the new place?
Won’t work. It’s a Binary file.
One could dump the DB into a text file, then edit it, use search and replace tool, and recreate the binary DB. This will be hard on many text editors b/c the file would be massive. So, use of cli tools would help make it easier.
1 Like
Simple SQL example that I recently needed for adjusting some file paths:
UPDATE Track SET path=replace(path, '../../Favorites/Music1/', '../Music/1/' ) WHERE path LIKE '../../Favorites/Music1/%';
Replaces the path prefix '../../Favorites/Music1/' with '../Music/1/'. Well, not only the prefix. But it is very unlikely that the replaced term appears elsewhere in the file path. Be careful and make backups.
In contrast to Pioneer/AlphaTheta products the Engine SQLite database is not encrypted and easily accessible.
1 Like
Ultimately, it’s just pathetic that something this basic is still an issue.
4 Likes
There is this open feature request with 3 votes–
Oddly, there was no discussion.
Yes, we are lucky. And, yes, as @uklotzde says, “Be careful and make backups.”
There are multiple databases in the …/Engine Library/Database2/ folder. I presume @uklotzde is referencing the path field of the track table in the m.db database. Some of the other databases handle integration from other programs (e.g., rbm.db = Rekordbox).
Edit- see my comments in another posting below. The track data is stored in a separate m.db on each drive. Therefore, only edit data in m.db, if you move tracks on the same drive.
1 Like
As a developer I can assure you that auto-relocating files is not an easy or trivial task. Far from “basic”.
There are myriads of different situations and you cannot foresee and handle all of them. Everyone thinks their particular use case is the most common and obvious.
Be humble with the AIR/inMusic devs.
Pretty much every other music database program has it so…
Actually, doing some testing today, I noticed that Engine DJ creates a separate set of databases on each connected drive. All the tracks I add from MacintoshHD (or C) are in /Engine Library/Database2/m.db, While tracks added from a connected drive are in /Engine Library/Database2/m.db on that drive. What you see in the Engine program is a conglomeration of all the m.db on the drives you have connected.
Path field entries (or Directory as displayed in the Engine interface) are relative paths to the root of /Engine Library/. Therefore, I’m wondering if the relative path to the music on your SSD is the same as on your original hard drive, if you copy the the /Engine Library/ folder over to your SSD, it might work? Be sure to back up the SSD first.
1 Like