Several releases have landed since I last posted here, and one of them explains something a few of you have run into.
Updating has not been finishing
Pulling an update replaces the code on disk. It does not replace the code the running panel already loaded - that needs a restart. Phosphene has shipped a "Restart to finish update" prompt for exactly this since 4.0.5, and it has never once been able to appear.
It compared the version on disk against a value that a background check kept refreshing, so the answer to "has the code changed under this process?" was always no. The update succeeded, the panel kept serving the old build, and nothing said so. Found on an install running a seven-hour-old process against a current checkout while reporting itself perfectly up to date.
Fixed in 4.4.0. If Phosphene has ever looked unchanged after an update, Stop and Start it once after installing this - that should be the last time you need to think about it.
Also since 4.0.7
- Updates announce themselves in a banner instead of hiding behind a click, and updating is one click, not two.
- The engine picker is a dropdown, so a third engine costs no header room. The six status pills are now one chip with the detail one click away.
- The live preview loops instead of standing still - same decode, same cost.
- Fixed a SIGABRT crash that killed every render on some Apple silicon: the automatic Metal-watchdog retry only recognised one of the two names macOS uses for that kill. Root-caused by @ybekocak.
- On 48 GB Macs, forcing a high or pro tier now actually lifts the resolution cap instead of only changing the info modal. Reported and measured by a user on a Mac Studio M4 Max.
- Model files now load on the fast path - a data section at the wrong offset was making every tensor take a slow copy instead of a zero-copy view.
If your install hung on a white window
That was Pinokio wedging on an over-long shell line during install. There is now a build gate that fails if any launcher line gets too long, so it cannot come back. Re-run the install and it should complete.
Thanks to everyone who filed something with real detail - most of the fixes above came from those reports rather than from me.
AboutPhosphenemrbizarro/phosphene
Several releases have landed since I last posted here, and one of them explains something a few of you have run into.
Updating has not been finishing
Pulling an update replaces the code on disk. It does not replace the code the running panel already loaded - that needs a restart. Phosphene has shipped a "Restart to finish update" prompt for exactly this since 4.0.5, and it has never once been able to appear.
It compared the version on disk against a value that a background check kept refreshing, so the answer to "has the code changed under this process?" was always no. The update succeeded, the panel kept serving the old build, and nothing said so. Found on an install running a seven-hour-old process against a current checkout while reporting itself perfectly up to date.
Fixed in 4.4.0. If Phosphene has ever looked unchanged after an update, Stop and Start it once after installing this - that should be the last time you need to think about it.
Also since 4.0.7
If your install hung on a white window
That was Pinokio wedging on an over-long shell line during install. There is now a build gate that fails if any launcher line gets too long, so it cannot come back. Re-run the install and it should complete.
Thanks to everyone who filed something with real detail - most of the fixes above came from those reports rather than from me.