hendrik on 27 Apr, 2021 07:42 AM
Let’s clarify a couple of basic questions!
Which version of beaTunes are you using, how many tracks are on your external drive, how is it connected to your computer and what kind of beaTunes library are you using: folder-based or Music.app-based.
I have no idea how many tracks are on my external drive; the total size of my Music library is 1.4 TB. I'm using whatever type of library the Mac Music app uses.
I have attached screen shots that may give you all the information you need.
This is a very frustrating program for me; I want to open it, choose the tasks I want performed, and have them done without a loss of overall functionality of my iMac.
hendrik on 29 Apr, 2021 11:03 AM
Sorry that you're having such a bad experience with beaTunes. I'll try to give some pointers that hopefully make using beaTunes more pleasant.
I have no idea how many tracks are on my external drive; the total size of my Music library is 1.4 TB
Since the file size per track varies a lot between audio formats, the total file size does not tell me anything about the number of tracks, which is the number that affects beaTunes performance. Music.app should tell you how many tracks are in its collection.
That said, it sounds like you have a quite large library. One of the most important performance-related things for large libraries is to turn off synchronization on windows activation in the beaTunes general preferences.
The second thing you probably want to do, is to never ask beaTunes to analyze anything you don't really really need. Doing anything for 100,000 tracks will always take substantial time and resources.
Regarding the question about how your external drive is connected. The worst case scenario for beaTunes is a slow disk connected via a slow network. The optimal scenario is a fast, builtin SSD. Somewhere in between are fast disks connected via USB3. One needs to realize that for certain analysis tasks, like ReplayGain, beaTunes needs to read the entire track. That mean in your case, if you wanted to determine ReplayGain for all tracks, beaTunes would need to read 1.4 TB of data, which then also needs to be decoded and then analyzed. The bottleneck here is usually disk read speed.
I'm using whatever type of library the Mac Music app uses.
beaTunes supports two kinds of collections:
Folder-based collections, i.e. it does not cooperate with Music.app very well, but only operates on your files
Music.app/iTunes-based collections, i.e. beaTunes closely coordinates everything it does with Music.app/iTunes.
The difference is explained in greater detail here.
I'm guessing you are using a Music.app-based library, since you are using Music.app. If not, I would recommend a Music-based library. You can confirm this in the beaTunes general preferences.
Here's my recommendation:
let beaTunes repair its database
(it is possible that repair fails, then a rebuilt is necessary)
ensure that synchronization on window activation is off (beaTunes general preferences)
when analyzing tracks with beaTunes, ensure that only the desired tasks are turned on
if your iMac becomes too slow during analysis, reduce the number of parallel tasks (in the beaTunes analysis preferences) to reduce the load on your system