Dear Apple Logic Pro Support,
I'm seeking assistance with a persistent Sound Library problem affecting the one-time-purchase version of Logic Pro 13 on my Mac mini M4.
I've spent considerable time troubleshooting this issue, including testing Logic in a separate macOS administrator account. The results strongly suggest a fault associated with my main macOS user profile rather than the Logic application itself.
System details
- Computer: Mac mini M4, 16 GB RAM, 256 GB internal SSD
- macOS: Version 27.2 (build 26B123)
- Application: Logic Pro 13, one-time-purchase version
- Application bundle identifier: com.apple.logic10
- Sound Library: Previously stored on an external 2 TB SSD
Description of the problem
Logic's Sound Library is effectively unusable in my main macOS account.
- Sound Library → Manage Packs reports Zero KB for both available and installed packs.
- Loops and One-Shots are completely empty in the Unified Browser.
- The three essential starter sound packs are listed but each reports Zero KB.
- Logic fails to recognise an existing 3.12 GB Logic Pro Library.bundle containing samples, patches and approximately 462 MB of Apple Loops.
- The problem was already present in Logic Pro 12 and persists following the upgrade to Logic Pro 13.
Important diagnostic finding
I created a completely new macOS administrator account on the same computer.
In that account, Logic Pro 13 worked correctly: the Sound Library catalogue populated normally and sound packs could be downloaded.
Returning to my original user account, the problem persisted.
This demonstrates that the application and network are capable of retrieving the Sound Library catalogue, but something specific to my existing macOS user profile is preventing it.
Troubleshooting already performed
- Reset com.apple.logic10.plist and restarted the computer.
- Removed Logic's user-specific cache folders temporarily, allowing them to regenerate.
- Reset Logic Pro Library.bookmark.
- Temporarily removed the com.apple.musicapps.content application-support folder, including its SQLite databases, to allow Logic to regenerate its content-management data.
- Tested with iCloud Private Relay disabled.
- Verified that HTTP and HTTPS proxies are disabled.
- Inspected /etc/hosts and found no suspicious redirects.
- Inspected user LaunchAgents without identifying an obvious blocker.
- Checked home-directory ownership, permissions and access-control lists, which appeared normal.
- Booted macOS into Safe Mode and reproduced the problem.
- Checked the registration of Apple StoreKit and App Store services.
- Captured macOS diagnostic logs while reproducing the problem.
None of these steps resolved the issue.
Additional background
I previously had a trial of the Apple Creator Studio version of Logic before purchasing the perpetual licence. My account still contains com.apple.mobilelogic.plist and associated Creator Studio application-service records.
There was also an earlier non-licensed Logic Pro X installation. I mention this because I wonder whether either earlier installation could have left behind conflicting user-specific configuration or authorisation data.
However, I have found no direct evidence of such a conflict.
Diagnostic observations
The macOS logs show several successful HTTPS requests returning HTTP status 200. They also contain activity involving CFURLResolveBookmarkData, but no conclusive error explaining the missing sound-pack catalogue.
The content-management folder contains databases including UserContentV02.sqlite and AutoTaggingV01.sqlite. Resetting these did not resolve the problem.
Assistance requested
Could this case please be referred to a Logic Pro specialist or senior technical adviser?
In particular, I would appreciate assistance with:
- Identifying which account-specific service, database or authorisation state manages Logic Pro 13's downloadable sound-pack catalogue.
- Determining whether remnants of earlier Logic installations or the Creator Studio trial might interfere with the purchased version.
- Repairing or resetting the affected component without deleting my macOS user account or reinstalling the operating system.
- Collecting any additional diagnostic information necessary to identify the failure.
I can supply screenshots, Terminal output and the Logic diagnostic log.
I would particularly like to avoid migrating to a completely new macOS user account, as my existing account contains an extensive professional audio and video production environment.
Thank you for your assistance.
