Looks like this has been discussed, but it doesn’t seem like my questions were answered. I need to migrate my Engine Library from my internal drive to external SSD.
Want to keep
Hot cues and beatgrids.
Order of playlists.
I wish it was as simple as changing file path location and rescanning tracks. What is the best way to accomplish this without losing all the work in tagging tracks.
I don’t think I can just use sync manager because I want the new “collection” library to reside on an external drive which will be the default drive for all new music going forward…with backup clones of course.
Any help would be greatly appreciated.
I think you just can use sync manager and copy entire db on it.
After done, delete all the music from your computer and the entire collection in engine.
Finally ask engine to import the new collection from ext drive
But I do not want to import the collection from the external drive. I want my library to reside on the external Drive and save any new songs to that external. I am doing this to free up 500Gb of internal storage.
Tye EASIEST way is just to clone the internal to external then reformat internal and away it goes.
Use a freebe trial cloner like carbon copy.
That way you lnow that you are getting an exact copy as you know it everything in its place as you put it there
I have never tried this method because I’m not sure if the database references the disk/volume. But if you are saying it works…then that’s fantastic.
My experience with other DJ software with built-in relocate function is that they require a new library scan to associate the new location with the library files
The database only references the folder structure it doesnt worry about drive letters.
Because database is on drive then it ignores drive letter and gies from root.
If you clone the drive as per name it makes and exact copy. Like when you migrate your main system drive. If you make an image you need to restore the image. If you clone it its identical to the original drive.
Ok, but when I say “ import the new collection from ext drive“ means that engine will import the structure of your db, not the mp3 files which will remain on external drive
I used a backup drive, which was an SSD and added it to my prime console, the issue I had is I started with my main computer drive as my collection and when I wanted to copy over to the SSD it was a long, drawn out, messy, sounding process seeming to suggest that the main collection would be added to the Engine folders on the SSD doubling every track on the drive which… well I wouldn’t have space for.
So I ended up clearing out my collection and just adding my SSD as a ‘collection’ I just copy over to my main computer drive when I add new stuff.
So essentially my laptop is now my backup drive Bit odd, but that seems to be how Engine likes to work.
Heyo guys, I bought a new Macbook modell and want to take the chance for a “fresh start”, aka get rid of all the junk which has allocated over time e.g. in Library/ApplicationSupport, etc. so I do NOT plan to use the Migration assistant this time*. I will have both Macbooks avaiable for a few days, so in case I miss or forget something, I can still react.
*) I could also use it partially and only migrate my System & Network and Username, but not applications and “other files & folders”
All my music is in the regular music folder with subfolders for each genre, which also resemble my folders/playlist structure in EngineDJ (and SeratoDJ, though I consider ditching SeratoDJ entirely). I would simply copy my whole music folder onto the new system and let Engine (Serato) rescan my music location. That should do the job, right? Bonus question: If I also want to change my username but keep the folders paths the same, does rescanning all files still work?
E.g. MaxMueller/Music/Techno1/(tracks)… → MaxSchuster/Music/Techno1/(tracks)…
Bit odd, but that seems to be how Engine likes to work.