Repository navigation
PlexFixer no longer runs on Electron. It renders in macOS's own webview and its
native side is Rust, which takes the download from 145 MB to 61 MB.
Why
The old build shipped 252 MB of Electron to run 2 MB of PlexFixer's own code —
three quarters of every download was the runtime. Nothing about the app needed
its own browser engine.
What did not change
Almost nothing moved to Rust. Rust does what only a native process can — spawn
ffmpeg, walk a filesystem, write the settings file, open a dialog — and
TypeScript keeps every decision. The analysis engine, the compatibility rules,
the H.264 SPS parser, the repair planner, the command builder and the job
runner are the same code, running in the webview, with the same tests.
Three things genuinely changed. The settings store, the library walk and the
environment probe are Rust now, with their own tests. The commands that start a
binary will only run the ones PlexFixer resolved — the bundled ffmpeg and
ffprobe, a path set in Settings, and your own ssh — so the page cannot ask
for anything else. And known_hosts is reached by name rather than by a path
from the caller, keeping the one file outside the app's own directory that it
writes to from becoming a general append.
Dolby Vision profile 5 can be converted
Profile 5 has no HDR10 base layer and keeps its picture in IPT-PQ-C2, so a file
relabelled 8.1 still shows the wrong colours — the familiar green/purple cast.
The only correct fix rebuilds the picture.
Settings → Compatibility → Dolby Vision profile 5 → Convert to HDR10 does
that: a full re-encode through ffmpeg's libplacebo, applying the Dolby Vision
RPU and writing plain BT.2020 PQ HDR10. The Dolby Vision layer is deliberately
dropped — that is the point, since an HDR10 file looks right on every client
where profile 5 only looks right on a Dolby Vision one. It is off by default,
forces 10-bit HEVC whatever your transcode codec says, and refuses outright
where libplacebo is unusable rather than quietly doing a plain re-encode.
The bundled macOS arm64 ffmpeg changed to one that has libplacebo, with Vulkan
and MoltenVK linked in. Intel Macs keep the old build and report the conversion
as unavailable rather than doing it wrong.
A default folder for the remote host
The remote browser opens where your library is instead of in the account's home
folder. Set it in Settings → Remote host → Default folder, or from the
browser itself with Start here next time — standing in the folder beats
typing a remote path from memory.
Smaller things
- Settings is a list of sections with one on screen at a time, rather than one
long scroll whose height changed under you when the remote host was toggled. - The library's tiles, search box and filter chips stay on screen; only the
file list scrolls, and the table's column header sticks to the top of it. - The About panel reports the Tauri and webview versions in place of Electron,
Chromium and Node.
Windows
This release is macOS Apple Silicon only. Tauri compiles a native binary
and does not cross-compile, so the Wine arrangement that produced a Windows
installer from a Mac no longer applies; that build now needs a Windows machine
or CI runner. An Intel Mac build needs an Intel Mac or a cross-build target set
up for it.
Opening it on macOS
PlexFixer is signed with a Developer ID certificate but is not notarized, so
macOS will refuse to open it on first launch. The DMG ships Allow PlexFixer
to open.command next to the app: drag PlexFixer to Applications, then run
that script — it clears the download flag, checks the signature is intact, and
opens the app. By hand, the equivalent is:
xattr -dr com.apple.quarantine /Applications/PlexFixer.app
or System Settings → Privacy & Security → Open Anyway. macOS quarantines
the .command too, so if a Mac blocks the script as well, use one of those.