archamp 1.0.1

The update window can start what it just installed

Update left you with a new archamp on disk and the old one still on screen,
and the only way across was to quit and go and find it again.

The button that installed it now offers to start it. Update becomes
Restart, Cancel becomes Later, and archamp goes down and comes
back up on the new version — with the playlist, the track and where it had got
to all as you left them, out of the saved session. Later is still there if you
would rather pick it up next time you start archamp yourself.

Under it, this is not Electron's own app.relaunch(). That starts the new
copy as the old one is going down, and archamp holds a single-instance lock —
so the new copy found the lock still held, handed over its arguments and
exited, and the old one was quitting anyway. Nothing came back. The waiting is
done outside the process instead, by a detached shell that watches archamp go
and then starts the AppImage the update wrote, giving up rather than ever
running two players at once.

Everything else

Unchanged from 1.0.0 — see its notes
for what archamp is and what it does, including how it and
OMedia Controls were
built to go together.

Install

Download archamp-1.0.1-x86_64.AppImage below, make it executable and run it:

chmod +x archamp-1.0.1-x86_64.AppImage
./archamp-1.0.1-x86_64.AppImage

Or, from a running 1.0.0: ARCHAMP → Check for updates.