Repository navigation
PlexFixer 0.1.8
Clear all
The Jobs tab has a Clear all button: it stops anything running and empties
the list. It asks first only when there is work under way — a queue of finished
jobs clears without a prompt. A job that is already running unwinds in the
background after the list is emptied, but it cannot reappear, and the file it
was working on is left exactly as it was, temporary file and all cleaned up.
Why a "simple" metadata change can take minutes
A language tag or a default flag is a fixed-width field in the MP4 header, and
PlexFixer edits those in place: 678 MB file, two bytes changed, 0.08 seconds,
nothing copied.
But if that file's index — the moov atom — sits at the end, the same repair
also has to move it to the front, and moving it rewrites every byte: the same
file, the same two bytes, 2.2 seconds on a local disk, and far longer across
a network share, where it scales with the size of the file and the speed of the
link.
The reason was being worked out and then thrown away, so the only visible
difference was the wait. The job log now names it, in plain terms, for every
repair that falls back to a full copy. It is a one-time cost per file: once the
index has been moved to the front, later metadata fixes on that file take the
fast path.
This also fixes a bug that was swallowing those explanations. The runner built
its "running" update from a snapshot of the job taken before the in-place
attempt, so anything logged while deciding was overwritten — including the
existing warning when an in-place edit fails and falls back to a full remux.
That warning has never actually reached the log in a shipped build.
Copy report, on any file
A report could only be copied for a finished job, which is no help with the
question that is actually hard: why did this file pass? Copy report now
sits beside Reveal in a row's details, for any scanned file, and emits the
whole picture — every stream ffprobe returned with its codec, tags, language and
dispositions, the findings or the absence of them, the planned actions, which
ffmpeg and ffprobe produced it, and the file's repair mode.
It also carries the settings that decided the verdict, because a report saying a
file is clean means little without them: "HEVC is compatible" and "MP4 is the
target" are settings, not facts about the file.
Fixes
- Hide passed did nothing while the Passed tile was on, and looked no
different for it — the checkbox was disabled, but the switch is drawn in CSS
that never reflected that. It now always acts, and turns the tile off, since
asking to hide passed files is the later instruction. - Choosing a new folder to scan clears the search box, the status tile and
the chips. They belong to the view you were just looking at, and leaving them
on means the files you asked for arrive into a list that is hiding them, which
reads as the scan having done nothing. Refresh all keeps them, being a
refresh of the current view rather than a new one.
macOS: the builds are signed but not notarized — right-click → Open the
first time.
FFmpeg: the bundled binaries are GPL builds, shipped as separate executables
and invoked as subprocesses, never linked. See NOTICE.md.