What Diagnostics and Support helps you decide
Use it when a workflow does not behave as expected and evidence is needed for support.
Review Diagnostics and Support 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 Diagnostics and Support evidence listed here and keeps its origin visible.
Safety and availability for Diagnostics and Support
Controlled Diagnostics and Support outputs remain narrower than inspection and preview, with authorization at the point of action.
Support evidence should be user-inspected. Credentials, tokens, and private library paths should not be shared casually.
A Diagnostics and Support scenario
A Plex playlist appears incomplete. The user collects a playlist report, reviews the playlist name and track evidence, then shares only the report needed to explain the issue.
When Diagnostics and Support needs attention
Start with the Diagnostics and Support inputs, then verify identity, paths, permissions, and the selected destination profile.
Repair and conversion capability boundaries
Current evidence supports format-aware inspection across the application’s recognized audio families and active FLAC external-command interpretation. External validation execution, repair writes, remuxing, broad conversion, quarantine, and post-operation verification remain planned workflows.
A repair plan must separate container, stream, tag, picture-block, and decode findings; distinguish remux from re-encode; preserve source masters; and retain checksums, prior-state evidence, approval, and verification. No process can reconstruct missing samples or restore original lossless quality from a lossy source.
- FLAC structure, Vorbis comments, and picture blocks are distinct evidence
- tool discovery is not tool execution
- non-FLAC encoder families remain planned
- successful process exit is not proof of media integrity