What Import and Encoding helps you decide
Use it when EAC, FLAC, filenames, or destination folders can affect the next files created by the library.
Review Import and Encoding evidence
Use the smallest evidence set that can answer the question: the relevant source, intended outcome, and any target identity or permission that would matter before a later action.
MMW reads only the Import and Encoding evidence listed here and keeps its origin visible.
Safety and availability for Import and Encoding
Controlled Import and Encoding outputs remain narrower than inspection and preview, with authorization at the point of action.
Encoding settings are high impact because they affect planned rips and encodes. MMW keeps write-capable actions behind backup, approval, and verification.
A Import and Encoding scenario
A user notices FLAC files landing in the wrong folder. The Filename and Output Rules view shows the folder rule, additional filename text, extension, and final effective path.
When Import and Encoding needs attention
Start with the Import and Encoding inputs, then verify identity, paths, permissions, and the selected destination profile.
Separate folder and filename builders
MMW separates folder structure from track filename so a user can see the final result on disk while preserving EAC's external encoder context. The current screenshot shows a proposal with write safety locked, not a completed EAC settings write.
- current rule and parsed interpretation
- proposed folder and track-filename tokens
- effective output path
- unknown or custom encoder options preserved for review
- backup, approval, verification, and rollback before controlled writes