Updating Fusor Studio
Fusor Studio looks for a newer build on its own, downloads it quietly in the background, and installs it on a restart you chose. Between builds there is nothing to download by hand.
Fusor Studio never restarts itself
A downloaded update sits on disk until you close the app. Quit normally and it is applied as the app closes; the next launch is the new build. If you would rather not wait, Restart & Install closes and relaunches Fusor Studio immediately.
No setting changes this.
Where to look
Open Settings (the gear icon, or Ctrl+, on Windows, Cmd+, on the Mac) and choose the About & Updates tab, the last one in the list.
The version number sits at the top of the tab, next to the app name. Underneath it is one line of plain text describing where the update stands:
| Status line | What it means |
|---|---|
No update check has run yet. | Fusor Studio has just started and the first check hasn't run |
Checking for updates… | A check is in progress |
Fusor Studio is up to date. | The feed has nothing newer than the version you're running |
Version 0.9.1 is available. | A newer build exists. The download either has started or is waiting |
Downloading version 0.9.1… | Downloading, with a progress bar and a percentage |
Version 0.9.1 is ready to install. | The new build is on disk |
When a check has completed this session, the same line ends with the time it finished, for example Last checked 13:42.
Two buttons sit below the status:
- Check now. Asks the update server straight away. It's unavailable while a check or a download is in progress.
- Restart & Install. Appears once a build has finished downloading. It closes Fusor Studio and reopens it on the new version.
When it checks on its own
The first check runs about half a minute after launch, once startup has settled. After that Fusor Studio checks every six hours while it's open.
Why an update sometimes waits
The download waits for the transition to end
A download competes for the disk, so Fusor Studio doesn't start one while a transition is running. The status stays at available and a second line, in orange, gives the reason:
A transition is running — the update will download once the mix is over.
Nothing needs doing. Fusor Studio re-checks every couple of minutes and starts the download on its own once the Fusor player is idle again. A transition that is paused, still starting up, or waiting to complete counts as running for this purpose, so the download can wait a while after the transition's progress stops moving.
An armed fusor doesn't hold anything back. The download runs and Restart & Install is available with a fusor armed.
Updates need an installed build
Automatic updating only exists in an installed copy of Fusor Studio. Run it from source and About & Updates shows the version with one line:
Automatic updates are only available in an installed build.
Fusor Studio shows no update buttons in that state.
When a check or download fails
The status line turns red and shows a sentence describing what happened:
| Message | What to do |
|---|---|
Could not reach the update server. Check your internet connection and try again. | Confirm you're online, then click Check now |
The update server has no release information for this build yet. | Nothing on your side. The server reached you but has no release listed for your platform |
The update server is not responding right now. It will be retried automatically. | Nothing to do; the next scheduled check picks it up |
This update was not installed because it is not signed by Signal Spine LLC. | Keep using your current version and report it, with main.log attached. Fusor Studio installs only updates signed by its publisher |
There's no error code to quote in a bug report. Update messages do not appear on the Fusor player's status line, so the detail goes to the log.
To capture it, open Settings → Logging, turn Verbose logging on, and set the Updates category to debug. That category records every check, download, deferral and install attempt. Reproduce the problem, then click Reveal current log file and attach main.log to your report. See Logging for the full workflow.