Skip to content

PlexFixer 0.1.14

Choose a tag to compare

@focher focher released this 12 Nov 23:51
· 31 commits to main since this release

See where a repair has got to — and on which machine.

The problem with a percentage

ffmpeg's percentage covers one step of several. On a local disk the others go by too fast to notice; on the machine that holds the files they do not. Connecting, re-probing a finished file over the link, moving it into place across volumes — each can take minutes, and a bar sitting at 100% with no explanation is indistinguishable from a repair that has died.

What the queue shows now

Each job draws its steps as a track, with the current one marked and the percentage on it:

Connecting ✓ — Copying 55% — Verifying — Moving

The index move and subtitle sidecars appear as steps of their own when a file needs them. A job running on another machine is labelled with it (on plex@nas), and the library row's badge says the same in its tooltip.

Silence is measurable

Every job update now carries a timestamp, so a row that has reported nothing for 20 seconds says no update for 40s instead of leaving a stopped bar to speak for itself. That is the difference between a slow link and a dead one.

Honest about failure

A repair that fails is left standing at the step it failed in rather than marked finished, so nothing reads as verified or moved when it was not. A skipped job shows no track at all, because it never ran.

And ssh exit 255 is now recognised as ssh's own failure rather than ffmpeg's: a remote repair that comes back with it says the connection to the host dropped, and that nothing was promoted and the original is untouched — instead of reporting a mystifying encode failure.


macOS builds are signed with a Developer ID certificate but not notarized — right-click → Open on first launch. The Windows installer is unsigned.