Skip to content

PlexFixer 0.1.13

Choose a tag to compare

@focher focher released this 12 Nov 22:01
· 33 commits to main since this release

Run the work on the machine that holds the files — and get logged in to it.

(0.1.12 was tagged but never published; everything in it is here.)

Why run it there

A remux copies every byte of the file. Across a mounted share that is two network trips per byte — in to your Mac and straight back out to the server — which is most of the reason a repair that should take seconds takes minutes. Settings → Remote host moves the work to where the disk is: ffprobe and ffmpeg run there, and only the probe output and the progress come back.

Logging in

PlexFixer shells out to your own ssh, so your keys, your ~/.ssh/config, your agent and your known_hosts all apply, and the app never sees a credential. It never asks for a password — a prompt on a pipe would simply hang — so key-based login has to work on its own.

  • Private key: name one key, with a file picker that opens in ~/.ssh. Naming one sets IdentitiesOnly, so a host that refuses it says so at once instead of after ssh has offered every other identity it has.
  • First connection: the question ssh normally asks at a prompt gets asked in the connection test instead. On a host nobody has connected to before, the test fetches the key, prints every fingerprint with its type, and writes them to ~/.ssh/known_hosts only when you press Trust this host — then tests again in the same step.
  • A changed key is never offered as something to accept. If there is already an entry and the key no longer matches, the test stops and gives you the ssh-keygen -R line to run once you know whether that machine was rebuilt or something else is answering at that address. Keys are compared by their material, so a hashed known_hosts entry still matches, and trusting an already-trusted host is a no-op that simply re-tests.

The connection test

One scripted round trip reports what answered: the platform, ffmpeg and ffprobe with their versions and paths, and every POSIX utility the repair flow shells out to — ls, find, stat, df, mkdir, mv, rm, tail, head, base64, pkill. A missing one is named now rather than discovered half way through a repair on a machine you are not watching.

Browsing and scanning

With remote mode on, Scan… opens a browser for the remote filesystem — the native dialog can only see this machine — showing folders, media files and their sizes, with a path box for jumping to a known library root. A dropped local file now says it is on the wrong machine instead of failing file by file.

Everything downstream is unchanged: the same analysis, the same plans, the same write-to-temporary, re-probe, back-up and promote sequence, all happening on the far end. Encoder detection runs its test encodes there too, so a force transcode uses the server's NVENC rather than this laptop's idea of it.

Limits, stated plainly

  • The remote host must be POSIX — Linux, macOS or BSD, not Windows.
  • The in-place header edit (a few bytes rewritten instead of the whole file) stays local; a remote repair always rewrites the file.
  • Cancelling a remote repair stops the remote ffmpeg by matching the job's own temporary path, since closing an SSH connection does not reliably take the process with it.

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