Support

Most setup and workflow questions are covered in the illustrated user guide.

First launch

After activating access with the free 3-day trial or Full Version, open Setup and allow Automation access when macOS asks for permission to communicate with Music.app. Then build the Library Index. Keep Include playlist usage enabled on the first full build if you want playlist-usage and relationship tools ready. The trial provides full access, does not renew and creates no automatic charge.

Music.app and standalone files

Library-wide organization tools work with Music.app records and LMO's saved Library Index. Audio Inspector, local playback, Repair / Convert, and supported physical-file workflows can also work directly with physically available local audio files. Single-file Audio Inspector includes authenticity evidence for the selected file, while the batch Audio Authenticity Analyzer uses the saved Library Index or an indexed playlist. Apple Music subscription content, cloud-only/online-only files and streaming audio are outside the supported local-file workflow.

Files and output folders

Add files and choose folders through the macOS system picker. If a file-based tool needs access to another physically available local or external location, macOS may ask you to select the containing folder. LMO can save that permission for reuse by its file tools and shows the saved location in Setup. The red offline warning for a saved location can be muted without disabling its saved access; Forget removes only LMO's saved permission/bookmark and does not delete files or Music.app records. If a disk or folder moved, choose it again. Network and NAS workflows have not been validated as a supported release workflow and are outside the documented scope; use physically available local files through normal macOS paths.

Notifications

Setup contains two independent notification choices. Notify when procedures finish can report completed LMO procedures through macOS. Notify about incomplete newly added albums is off by default. When enabled, LMO uses an already complete Full Library Records index as a baseline, performs a lightweight Music.app identity check when new records are detected, and checks only the affected Artist — Album releases for missing tracks, missing discs or conflicting Track / Disc totals. This watcher does not require Automatic Library Index to be enabled, and it does not modify Music.app metadata or physical files. If tracks are removed and later imported again, that genuine new import is checked again even when the resulting album warning is textually the same as an earlier warning.

Library Index

On first use, open Library Dashboard, leave Include playlist usage enabled and click Build / Refresh Library Index. The saved Library Index is restored after relaunch and large results load in pages. After adding, replacing or removing a few tracks, use Refresh Music Changes. After changing one already indexed playlist, choose it and use Refresh Selected Playlist; use Index Selected Playlist when that playlist has not yet been indexed. A full rebuild is not required after every launch.

Normal startup does not launch Music.app. LMO restores the saved SQLite Library Index and can apply a small physical-change catch-up from the macOS FSEvents journal without opening Music.app or rescanning the whole collection. Automatic Library Index also waits while Music.app is closed and continues only after Music.app is already running. Explicit user-triggered Music-backed actions, including manual Library Index, Refresh Music Changes and Music.app Diagnostics, may launch Music.app when needed.

On an extremely large library, full Music.app records can be ready before all playlist-membership rows. LMO labels that playlist usage as partial instead of pretending the snapshot is complete. Use Index Playlist Usage or Index Selected Playlist to extend coverage. Do not clear the Saved Library Index merely because playlist usage is partial; the available full records remain useful.

Health Check

Health Check is read-only until you choose an explicit action. A Missing file means a Music.app record still exists but its saved local path is unavailable. An Orphan physical file is a readable file whose exact path is not represented by the saved Music.app library. These are different conditions: if an orphan is actually the replacement location for a Missing record, relink the existing Music.app record instead of importing a duplicate.

Repair Local Link... relinks one existing Music.app Persistent ID to a chosen file. Relink This Folder... maps the missing record's old parent folder to a replacement folder, previews exact relative-path matches and relinks the existing records; LMO does not move, copy, rename or delete the physical audio files. Remove Missing Record... removes only the exact live Music.app record after confirmation and verification, then synchronizes LMO's caches/index so stale missing state does not reappear.

For a genuine orphan import, LMO live-checks the exact physical path immediately before the Music.app action. An existing exact-path record is reused instead of creating a duplicate. The verified record can be added to several selected existing playlists and one optional new playlist.

Check Album Completeness (Track / Disc totals) is a read-only live Music.app check that reports missing numbered positions, missing discs or conflicting totals without querying the Internet or guessing titles. Find Track / Disc Numbering is a separate optional discovery scan. Its cleanup action targets only Track Number, Track Count, Disc Number and Disc Count. LMO verifies the live record before and after the write and restores exact pre-cleanup editable protected metadata if Music.app changes it during the numbering write; Persistent ID, location and artwork count remain fail-closed safety boundaries.

How to read scan results

A scan count is a review count, not an instruction to clean everything. A large hidden-tag count can be normal in a large collection. Review representative rows and the exact field names or technical evidence before applying any change.

Hidden Audio Tags and Finder Metadata

Scan Hidden Audio Tags reuses saved SQLite probe results for unchanged files and reads only new or modified files when possible. Use Full Verify Tags only when you deliberately want every file checked again; it is slower by design. Clean Selected Hidden Tags begins only after explicit selection and preserves review-only fields such as publisher, label, copyright and license while verifying the rebuilt file and artwork.

Scan Finder Metadata is separate from embedded audio tags. Cleanup is deliberately narrow: only allow-listed Finder metadata is actionable, while unknown, protected, audio, artwork and embedded music metadata remains read-only.

Naming & Tag Formatting

In File Maintenance, Scan Naming & Tag Formatting is read-only. It checks repeated spaces and spacing around round parentheses in Music.app Title / Artist / Album and local filenames. Review one row or batch-fix selected issues only when you intend to make a change. Safe physical filename renaming keeps the same folder and extension, verifies the same Music.app track and artwork, and rolls back if verification fails. After a successful tag or filename change, LMO refreshes the affected Music.app file information so Dashboard technical facts stay current.

Outdated Music.app file information

If Deep Dashboard shows Music.app info outdated, select that card to isolate the affected tracks. Refresh Music.app Info asks Music.app to reread the actual local file and verifies the result. LMO does not convert, move, delete or rewrite the audio file, and protected tag/artwork fields are checked for unexpected changes. When logging is enabled, the refresh history is written to the selected log folder.

Music.app Diagnostics

In Setup, enable Write technical errors to a local log to expose Music.app Diagnostics.... These are explicit read-only support tests: they do not edit Music.app tracks, playlists, metadata, artwork, audio files or the Saved Library Index, and they do not issue a Play command.

• Startup State: quit Music.app first. LMO verifies that it is not running, launches it without Play, and records several short player-state snapshots over roughly ten seconds. A very large library that is still loading can be reported as not ready rather than blocking the diagnostic.
• Track Flags: reads Music.app in bounded ranges and reports non-default playback-related flags plus storage-volume totals. A difficult range can be retried in smaller pieces, so the progress counter may pause and then continue. It does not traverse physical music folders and does not require Additional Folders.

Because these tests are explicit, Music.app opening during the diagnostic is expected. That alone does not mean an ordinary LMO launch opened Music.app.

When support asks for logs

1. Before reproducing the issue, enable Create Library Index Log in Library Dashboard when the test involves indexing.
2. Enable Create log files on the scan page when that option is available.
3. In Setup, enable Write technical errors to a local log.
4. Run the requested test without applying fixes unless support specifically asks for them. For Track Flags, send the final or partial log and include the last processed count; a temporarily stationary progress counter is less useful than the log.
5. When the requested tests finish, send the generated LMO text/log files from the selected log folder (commonly Desktop), plus any requested screenshots. Use Export Diagnostics only if support specifically asks for it.

Audio Inspector and Authenticity Analyzer

Audio Inspector works directly with a standalone local file and does not need the Music.app Library Index. It shows codec/container family, channels, sample rate, bit depth, bitrate, duration and file size, plus the authenticity assessment, a dB-scale spectrogram and raw afinfo technical output. The static Inspector does not show a waveform; the interactive full-track waveform belongs to Live Spectrum.

Audio Inspector > Audio Authenticity Analyzer can scan the saved library or one selected playlist; use Single File mode for an individual file. Normal files are omitted from its actionable list; Review, Likely and failed items remain visible and can be written to the local report.

Editing Music.app tags

Supported tags can be edited manually from visible result cards. Nothing changes until Save to Music is used; after saving, the supported fields are written to the exact Music.app record. Undo Last Change restores the values from the most recent supported tag edit.

Clear All Comments

Clear All Comments changes only the Music.app Comments field for the matching records. LMO verifies the live Music.app value, updates the Saved Library Index so an older cached comment cannot reappear, and records Undo data only for comments that were actually present immediately before the operation. It does not rename or rewrite the physical audio files.

Conversion

Conversion engines are built in. Do not install Homebrew or separate codecs. Batch Normalize can review 48 kHz and high-bit-depth lossless files from Library Dashboard. After successful verification, choose Keep original, Move original to Trash, or Move original to LMO Backup Folder. A CUE sheet may ask for access to the folder containing its referenced WAV, FLAC or other source audio; regular Add Files and Drag & Drop do not request extra access when the selected file is already permitted. For a problem, include the source format, chosen output profile and the Queue Report when relevant. Queue Report is informational and does not start conversion.

Include with a support request

• macOS version and Mac model.
• Application version and build number.
• Exact source format and output profile.
• The visible error and relevant application log.
• Whether the file is local, external or on a network volume.

Contact

sergeyappleservice@gmail.com