v0.8.2

Download

	Installer
Windows	FSVR-Windows-Installer.exe	Run it; it asks for admin rights to install into Program Files
macOS	FSVR-MacOS-Installer.zip	Unzip and open FSVR-MacOS-Installer; it is not signed, so right-click it and choose Open the first time
Linux	FSVR-Linux-Installer	chmod +x FSVR-Linux-Installer, then run it

The installer puts every format in place (VST3, CLAP, VST2, the 32-bit VST2 with its DXi, AU and the standalone) and can keep FSVR up to date. To install one format by hand instead, take its own zip from the list below, FSVR-<OS>-<format>.zip. FSVR-MacOS-Update is for the updater, not for downloading.

---

FSVR v0.8.2: the LCD's POLY, performance name and MIDI mark.

This round answers jameshansen's reports of the POLY readout sticking at 32, the LCD showing no name on a new instance and the note mark going dark, and takes digitalboy1's suggestion (from Discord) of a longer performance name on the LCD.

POLY counts what you hear. Since v0.5.2 the readout counted every channel the allocator still owned, and a channel stays owned until its last envelope is done: a release that ends on a floor never is (Nightmare's carriers park at -91 dB), and one crawling through -70 dB takes half a minute (Zap !). Thirty-two staccato notes pinned it at 32. It now counts a key down or sustained, or a released note still above -60 dB; voice allocation is unchanged. Forty staccato notes, then 1, 5 and 10 s of silence: Zap ! reads 32, 27, 0 (was 32, 32, 32) and Nightmare 16, 0, 0 (was 32 for good).

The LCD names the performance on a new instance. The name was published only when it changed, but a restored session clears it, so a new instance or a reloaded project showed a blank top row until another performance was picked. A restore now publishes it again.

The performance name uses the whole top row (digitalboy1, Discord). 25 characters up to the edit mark, where it stopped at 19.

The note mark lights for the editor's own keyboard. MIDI from the host always lit it; notes played on the on-screen keys now do too.

Checks. Locally on Linux: the engine selftest (with a new case for a release parked on an inaudible floor), dsp_check, check_plugin and check_gui (with new checks for the LCD after a restore and for the editor's notes counting as MIDI in) all pass, and the LCD was looked at in headless renders at 1x and 2x. regress.py was not run (its reference is a Windows build's); the engine change touches only the readout, not the render. CI builds every leg and the installers on the tag.