migrating to a new computer with beaTunes 5.1

mr.m.kaufman's Avatar

mr.m.kaufman

14 Nov, 2018 04:50 AM

So I found the Knowledge Base article written for earlier versions, but it only goes up to version 4. The comment there was that if you are using iTunes-based beaTunes, and use Migration Assistant to move, you'll be fine.

For beaTunes 5, does this still hold true? My media server is an old Mac Mini with a hard drive, plenty fast enough to serve out music via AirPlay, but way too slow to use beaTunes to scan through my 100,000+ songs iTunes library! So I am using my 2017 MacBook Pro with SSD and USB 3 to do the heavy processing (over a week to scan the entire library!), and then want to just copy the results to the Mini.

Can I just copy over my ~/Music/iTunes folder to the Mini, install beaTunes, and copy ~/Library/Application Support/beaTunes to the Mini? Reading between the lines, "use the Migration Assistant, things should be fine" tells me it's just a matter of copying all the right files... I am a UNIX hacker from way back in the day, and totally comfortable with a bash prompt, so if there is more involved I'd appreciate knowing the details. Almost any trouble is worth it to avoid re-analyzing my entire library in place on the Mac Mini :-(.

Thanks for your help. I found beaTunes as a way to get much better results than iTunes "Genius" recommendations - I am already hearing music entirely in my chosen range that I've never heard from my library before!

-Mark

  1. 1 Posted by mr.m.kaufman on 14 Nov, 2018 04:52 AM

    mr.m.kaufman's Avatar

    And yes, I will ensure identical volume names and file paths :-).

  2. Support Staff 2 Posted by hendrik on 14 Nov, 2018 10:41 AM

    hendrik's Avatar

    Hey Mark,

    you mention an iTunes-based library, so that's what I assume you're are using.

    "Transporting" analysis results can happen in two forms:

    1. In the internal beaTunes database
    2. As embedded values in your audio files

    In the first case, it's necessary that all persistent ids for library and tracks are identical on both machines. This only happens when you have identical volume names/paths and also copied all the correct iTunes library files (I guess the .itl files).

    The reason for this is that beaTunes refers to tracks and libraries by those iTunes given ids. While the ids are persistent (i.e. they do not change between application starts), they are assigned randomly. Re-creating the same library on a different machine leads to different ids and then the mapping is broken.

    When analyzing tracks in beaTunes you can ask beaTunes to embed all values into the audio files as well (option in the general preferences). If you do that, you can simply analyze on your MBP, and copy the analyzed files to your Mini. Make sure they are found by iTunes on your Mini. Then, on the Mini, create a new iTunes-based beaTunes collection. When creating a new iTunes-based collection beaTunes imports as many values as possible from the files (this is only done during the initial synchronization, which is why this takes long).

    In any case, when manipulating large amounts of files and having beaTunes write results to them, make sure you have a backup, in case something goes wrong.

    Hope this helps,

    -hendrik

  3. 3 Posted by mr.m.kaufman on 14 Nov, 2018 06:47 PM

    mr.m.kaufman's Avatar

    Well, you don't have to school this guy on backups - I have several, in rotation, and stored in several physical locations :-). I'm not risking a music library it's taken me 50 years to compile.

    Despite your recommendation to embed beaTunes metadata in the actual music files, you also mentioned that ensuring exact copies of the iTunes library, volume and path names, the beaTunes database, and the music files would also work. That's what Migration Assistant basically does. I have all my music on an external drive that I maintain exact copies of via Carbon Copy Cloner, and the destination Mac Mini will have the same hard drive name and user name.

    I just need an answer from you as to whether cloning ~/Library/Application Support/beaTunes to the Mini will take care of the beaTunes side of this operation? Do you use any other locations?

    I'm just loathe to write to all of my 1.5TB of music files if merely exactly copying what I already have/created will do the trick :-).

    Thanks again for this marvelous support.

  4. Support Staff 4 Posted by hendrik on 14 Nov, 2018 07:04 PM

    hendrik's Avatar

    Well, you don't have to school this guy on backups - I have several, in rotation, and stored in several physical locations :-). I'm not risking a music library it's taken me 50 years to compile.

    I just wish everybody took backups that seriously!

    I just need an answer from you as to whether cloning ~/Library/Application Support/beaTunes to the Mini will take care of the beaTunes side of this operation? Do you use any other locations?

    That's the only relevant location beaTunes uses.

    Thanks again for this marvelous support.

    You're very welcome. Let me know, if you run into any trouble.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac