Start here
Start here if you want to understand what MMW is, where it fits in a music-library workflow, and how to approach the first review session.
Use this page if you manage a music collection and want a careful workstation for album audit, EAC and FLAC preparation, metadata, artwork, lyrics, playlists, and delivery planning.
Prepare a focused input
Start with a library folder, album, playlist, or settings area that you are prepared to inspect carefully. MMW is most useful when the user can compare the current state with the result they actually want.
- A Windows desktop environment.
- Local access to the album folder or library area you want to inspect.
- Optional EAC and FLAC tools if you are reviewing import or encoder behavior.
- Optional Plex access if you want playlist discovery.
How it works
The workflow is built around visible evidence and a separate user decision. These models appear throughout the product surface.
- MMW reads first and explains what it finds.
- Preview and comparison are separate from write approval.
- Development status labels explain what is available now and what remains scheduled work.
- Documentation pages describe limitations as part of the workflow.
The common review path
Use the workflow as a review path rather than a promise that every destination can be changed automatically.
- Open a library area or album folder.
- Review the album and track evidence.
- Move to Import and Encoding when EAC or FLAC output matters.
- Review playlists when sequence or delivery is the real task.
- Use Safety and Recovery pages before approving any high-impact change.
Evidence boundaries
The application reads only the evidence needed to help the user understand the task.
- local file and folder evidence
- track metadata visible to the current workspace
- user-selected settings or playlist sources
- album folder structure
- available screenshots and diagnostics
Controlled-output boundary
Write-capable paths are intentionally narrower than read and preview paths.
- Nothing is changed by inspection alone.
- A controlled write path should require a clear scope, backup where relevant, and explicit approval.
First review scenario
A collector opens an album folder, notices inconsistent album-artist tags and missing artwork, then checks EAC filename rules before deciding whether the next session should be metadata repair, re-encoding, or playlist delivery.
How lifecycle labels work
Limitations are part of the public workflow because they protect the user from assuming a planned capability is already finished.
- There is no public download on the site.
- Some workflows are available as review and planning surfaces while controlled writes remain in development.
- External tools and servers remain under the user's own configuration.
Common checks
When the page does not show the expected result, start by checking the input evidence and the assumptions for that workflow.
- If no tracks appear, check that the selected folder actually contains supported music files.
- If EAC information is missing, confirm that EAC is installed and configured for the user's environment.
- If Plex is not visible, start with the Plex integration page.