Resolve a finding
Correct project inputs deliberately, then run a fresh inventory to verify the change.
On this page
MediaTether reports observations; it does not edit media assets or delivery files. Use the finding code and evidence to decide what your project should change, make that change yourself, and then run a fresh inventory.
- For
MEDIATETHER-FILE-MISSING, check the File Media Source path and restore the expected file if it belongs in the delivery. - For
MEDIATETHER-FRAME-MISSING, verify the sequence pattern and inclusive range. Restore a genuinely expected frame, or correct the rule if the range was wrong. - For
MEDIATETHER-PATH-EXTERNAL, decide whether the file should be part of the delivery. Update the asset or delivery root yourself; the plugin does not copy it in. - For
MEDIATETHER-FILE-UNREADABLEorMEDIATETHER-SEQUENCE-UNAVAILABLE, check permissions and direct local paths. Do not treat access failure as proof of absence. - For
MEDIATETHER-PATH-UNSAFE, use a direct local path without a network, device, alternate-stream, junction, or symbolic-link ancestor.
Review the full finding-code reference for unsupported sources, proxies, path types, and changed inputs. After editing a source or its files, the prior report is a snapshot and may be stale; rerun the inventory before exporting. Completed means traversal finished, not that the media plays.