Since version 1.2, Local Music Organizer has received several substantial updates.
The biggest addition is a built in audio player for local music files. It includes a live spectrum analyzer, waveform display, album artwork, playback queue, Previous and Next controls, Play, Pause, Stop, seeking, volume control and automatic playback of the next track.
The player can work with the current playlist context and includes direct navigation through the Music.app playlist hierarchy. There is also a compact Mini Player and a Classic interface inspired by traditional hi fi hardware.
Playlist Compare has been improved significantly. Changes made manually in Music.app are now synchronized more reliably. The app can detect when a track is replaced in a playlist even if the total number of tracks stays the same. Metadata changes are refreshed automatically, stale comparison results are removed after Refresh Music Changes, and a comparison is cleared if one of the selected playlists is deleted.
Small maker update: Local Music Organizer 1.1.19 is now out.
The biggest change is a major update to the Live Spectrum Player, but there s also a lot of work under the hood around large library performance, Library Index restore, Health Check, File Maintenance, and reliability.
I also fixed an annoying edge case where Music.app could repeatedly open Locate for a missing local file.
The user manual has been completely reworked as well it s now a much more detailed, illustrated guide covering the current workflows, controls, safety boundaries, and the intended way to work with large local/offline Music.app libraries.
Quick update since launch. I have spent most of this week improving reliability, Music.app integration and large library support. Playback with missing local files is now cleaner and should no longer trigger repeated Locate prompts. LMO can now detect moved or replaced files more reliably even when the Persistent ID has not changed, and repaired locations are updated without rebuilding the entire library. Health Check and orphan handling were tightened to reduce the risk of importing replacement files as new Music.app records. Duplicate cleanup was also improved so verified merges no longer create automatic backup playlists, while playlist membership is still protected before removing the duplicate record. I also improved saved Library Index restore behavior for very large libraries and fixed external drive diagnostics so sandbox permissions do not produce misleading unreadable volume results. A Track Flags diagnostic also completed successfully on a test library with 827,100 Music.app records and found no abnormal playback related flags. Most of this work was about making the existing tools safer and more predictable rather than adding more features.
My Music.app library is a mess of CD rips from 15 years ago mixed with newer lossless replacements, and I never had a good way to find which duplicates were actually worth keeping. The spectra/waveform view for spotting a fake-lossless upscale is the standout feature - most tools just trust the file extension and bitrate tag, which tells you nothing about whether the source was ever actually lossless.
The maker mentioned it deliberately stops at flagging a suspicious upscale rather than searching for a legitimate replacement, which I get for avoiding piracy - but a way to check your own library against other albums you already own for a better-quality copy of the same recording would close that loop without touching any download source.
I want something that works with the files I already have in Music.app rather than asking me to migrate into a new library format, and I don't want a subscription for what's basically a one-time cleanup job. A single purchase that unlocks offline analysis and repair tools fits how often I'd actually use this - a big pass now, then occasional maintenance later.
Hi everyone! 👋
Local Music Organizer started as a small personal project for my own music collection.
I've been maintaining a local music library since the early iTunes years. When CD writers and MP3 car players became common, I converted much of my CD collection to 192 kbps MP3. At the time, that seemed perfectly reasonable.
Years later, after upgrading my audio equipment, I realized how much quality I had lost. I began replacing old files with better versions lossless releases, vinyl transfers, rare editions and music collected from many different sources.
Over the years the library became increasingly difficult to maintain. Tracks were replaced, moved and reorganized. Some files disappeared while old Music.app records remained. Playlists accumulated duplicate entries. Different versions of the same recordings lived side by side, along with inconsistent tags, missing artwork and metadata left behind by converters and download sources.
But Local Music Organizer actually began for a completely different reason.
I simply wanted a better playlist shuffler. I never liked how Music.app shuffle could return to the same artists too often while other tracks seemed to disappear for a long time. So I built my own system with spacing between artists, albums and related artist projects.
While building it, I started discovering all the other problems in my library.
That small playlist tool gradually became Local Music Organizer a toolkit for inspecting, organizing, analyzing, repairing and converting large local Music.app collections.
A major principle throughout development has been safety. Most analysis is read-only, and operations that can modify files require explicit user action and additional verification.
Everything runs locally on the Mac. There are no analytics, advertising or tracking, and your music library is not uploaded anywhere.
I'm an independent developer, and I originally built this because I needed it myself.
I'd especially love to hear from people who have also maintained an iTunes or Music.app library for many years: what problems have accumulated in your collection that existing tools still don't solve?
Thanks for taking a look!
@yashekbote Thanks Yash! The orphaned Music.app metadata was definitely the messier part.
When Music.app loses or breaks the reference to a track, you may eventually have to locate the actual audio file on disk and safely reconnect it to the correct library record, so there is much more verification and post processing involved.
With duplicates, the problem is usually simpler: identify the copies correctly and decide which one should be kept.
Appreciate you checking it out!
The "started as a better playlist shuffler" origin story is very relatable - so many useful tools come from someone just wanting to fix one small annoyance and then falling down the rabbit hole of everything else wrong with the data. The read-only-by-default safety principle is the right call for anything touching a library people have spent years building.
One thing your reply to Lisa made me think about: once you've used Quality Duplicates to pick the better version between, say, a CD rip and a vinyl transfer of the same track, does the tool help reconcile the metadata gap too (missing artwork, inconsistent tags left by different converters), or does keeping the winner still mean manually re-tagging it afterward? Feels like the diagnosis half and the cleanup half could need pretty different UI.
Really respect the "diagnosis only, not a piracy shortcut" line you drew for Lisa above - that's the right call.
One thing I'm curious about on the technical side: Apple has been tightening access to the Music.app library internals over the last few macOS releases (the old readable Library.xml export isn't there by default anymore). How does LMO actually read playlist and track metadata now - are you going through the internal SQLite database directly, and if so, does a macOS/Music.app update ever silently break that and force you to reverse-engineer schema changes again?
Detecting upscales dressed up as FLAC is the feature I didn't know I needed, half my old library is probably lying to me. When it flags a suspicious transcode, does it just mark it or can it help me hunt down a proper replacement? Local music people are exactly the crowd that never wants a subscription, smart call.
@yelyzaveta_kibets Thanks! LMO deliberately stops at diagnosis. It can flag a suspicious upscale or transcode and show the technical evidence, but it will not search the web for free replacement downloads. That would cross into piracy, and I don’t want the app doing that.
If you already have multiple local copies, Quality Duplicates can help compare them and identify the better one. For an actual replacement, the idea is to use a legal source you already own or purchase separately.
And yes, I felt the same about subscriptions. A local library tool should feel like something you own.
Crates
Local Music Organizer for Mac
Thanks for taking the time to write such a detailed review. You described the kind of library LMO was made for very well: years of CD rips, newer lossless replacements, multiple versions of the same recording, and the problem of deciding which copy is actually worth keeping.
A few clarifications may help, because several different LMO tools seem to have been mixed together.
Spectrum Analyzer, Audio Inspector, and Audio Authenticity are separate parts of the app.
The Spectrum Analyzer is an interactive visual tool. It lets you inspect the frequency content of the music yourself while listening. It does not look at a spectrum and simply declare that a FLAC is "fake lossless."
Audio Inspector is the detailed inspection workspace for an individual file. It gives you the technical information about that file and lets you examine it more closely.
Audio Authenticity is the part that performs automated analysis. It works from the decoded audio itself rather than trusting the filename, FLAC extension, bitrate field, or other container metadata.
The analysis looks for combinations of characteristics that can be consistent with previous lossy encoding or artificial upscaling, such as the effective audio bandwidth, the shape and sharpness of high-frequency roll-off, how much meaningful spectral content remains above a suspected boundary, how consistently those characteristics occur throughout the recording, and whether the overall pattern resembles codec-related filtering rather than a natural recording or mastering characteristic.
Importantly, it is not based on a simplistic rule such as "there is nothing above 20 kHz, therefore this is fake FLAC." That would produce many false positives.
Old recordings, analogue sources, mastering filters, noise reduction, recording equipment, intentional low-pass filtering, restoration work and many other perfectly legitimate processes can produce similar spectral characteristics.
And there is a fundamental limitation here that applies to every audio analysis tool: you cannot reconstruct the complete history of a finished audio file with 100% certainty from the final signal alone.
If somebody converted an MP3 to FLAC fifteen years ago, the FLAC does not contain a label saying "I used to be an MP3." Analysis can find evidence that is consistent with a previous lossy source, sometimes very strong evidence, but it cannot travel back in time and prove every stage of the recording, mastering and encoding chain.
That is why LMO treats Audio Authenticity as technical evidence for investigation rather than an absolute verdict.
There is also an important correction to the "What needs improvement" part of your review: LMO does not stop after flagging a suspicious file.
It only stops at the boundary of your local library. LMO will not search external download sources or obtain replacement music for you.
But if you already have other copies or versions of that recording somewhere in your own Music.app library, Quality Duplicates is designed for exactly the next step you described.
LMO can bring the matching local tracks together so you can see the alternatives you already own, compare them, inspect the actual files, listen to them, and decide for yourself which version you want to keep.
So the workflow is closer to:
Audio Authenticity helps identify a file that deserves investigation.
Quality Duplicates helps find the matching alternatives already present in your own library.
Audio Inspector and Spectrum Analyzer give you additional tools to examine those versions yourself before making the final decision.
LMO deliberately leaves that final decision to you. A higher bitrate, larger FLAC or wider spectrum does not automatically mean that one mastering will sound better than another.
You were also right about wanting to keep your existing Music.app library rather than migrate everything into another proprietary library system. LMO is built around working with the library and local files you already have.
One correction on the pricing model as well: LMO is not a subscription.
There is a 3-day full-feature trial, and after that it is a single $29.99 one-time purchase to unlock the app permanently. There are no monthly or yearly fees.
I chose that model very deliberately. I am a music collector myself, and I do not use music subscriptions. I understand very well why another collector with a carefully built local library may also have no interest in adding yet another recurring subscription just to maintain music they already own.
A local music library utility should be something you can buy once and keep using whenever you need it, whether that means a large cleanup now or occasional maintenance later.
Thanks again for the thoughtful review. It was genuinely useful because it showed me that I need to make the distinction between Audio Authenticity, Audio Inspector and Spectrum Analyzer clearer, explain the Quality Duplicates workflow better, and make the one-time purchase model more obvious.
I wouldn't say this is a one-time product. The library is constantly growing, and tracks need to be edited regularly. I created the app primarily for myself (and only later realized it could be useful to someone else). I use the app every week after new tracks are added.