Skip to content

PlexFixer 0.1.10

Choose a tag to compare

@focher focher released this 12 Nov 01:45
· 40 commits to main since this release

The repaired file now shows up

Refreshing a row after a repair updated the timestamp and nothing else. The
status still said Fixable, the reason still named the same fault, and the
job badge beside them said done — which reads as a repair that quietly
failed.

The refresh was right. If output placement is set to write beside the
original (name.plexfixed.mp4) or into an output folder, a repair never
touches the source file, so re-probing it finds exactly what it found before.
The repaired file is a different file, and nothing had ever put it in the
library: the fix that had just run was nowhere on screen, and only a re-scan of
the whole folder would turn it up.

A refresh now also pulls in the output of a finished repair when that output is
a file of its own. You get both rows — the source still reporting its faults,
which is the truth about that file, and the repaired one beside it saying it
direct plays. The completion message names where it went: written to
name.plexfixed.mp4
, on the job badge and in the Jobs tab.

Nothing changes for the default in-place repair, where the output is the
source and was already being refreshed, or for a container change, where the
new .mp4 replaces the old .mkv row rather than joining it.


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.