v0.3.97 — Lighter instruments, quiet tails, and a speed test for your computer

Most instruments now take less of your computer to play — the TEO-5 about an eighth less, the Phosphor Synth, Juno-60, Little Phatty and hall reverb about a tenth, the rest a little — and not one sound changes: all 7,418 factory sounds and control moves were checked bit for bit before and after. Long fading tails on the Prophet-6 and TEO-5 delays no longer drift into the tiny numbers that slow many processors down as a sound dies away; the only difference is in values far below anything a speaker could play. And phosphor --benchmark tells you whether a computer can keep up: it plays a busy song through the real engine for about half a minute, on one core and then on all of them, and says in a sentence whether there is plenty of room, just enough, or not enough — the thing to run on a Raspberry Pi before building on one.

cargo install phosphor-studio --locked

v0.3.96 — Your own drum kits, and a deck that lights up

A sampler's pads can now be saved as a drum kit of your own (Space+W on a sampler track, "save pads as a drum kit"), which keeps its own copy of every sound and is picked on any Drum Rack by turning the kit knob past the eighteen built-in kits; Enter on a kit opens it on a sampler to edit and saving it under the same name updates every Drum Rack playing it, d deletes it after asking, and songs keep their own copy so changing a kit never changes a finished song. Since 0.3.94: clips in the track lanes are tinted capsules with a small picture of their notes, the lanes scroll and zoom (z/Z, [ ]) and follow the clip you are on, the loop brace and the playhead, and the loop editor copies sections of any size quickly — type a number to repeat a key (8L, 4p), c braces a clip, a the whole song, z zooms to fit, with a grid down to a thirty-second; the Phosphor Deck's buttons light to match the screen; the deck's circuit board gains JLCPCB's assembly files and a step-by-step ordering guide; and a terminal shrunk to nothing no longer crashes Phosphor.

cargo install phosphor-studio --locked

v0.3.94 — Sounds stop when you play the next key, and waveforms you can read

A sound brought onto a sampler pad — loaded, chopped or recorded — is now mono by default, so a long sample stops the moment you play any other key instead of having to be waited out; set a pad to one-shot when it should ring on under the next. A chop's break slices are mono too, while its melodic feel still lets held keys ring together, and in keys mode a zone made from a fresh pad stops when you let go of the key so chords still work. Sessions you already saved keep exactly the trigger modes they had. Every waveform — under the pad panel, in the trim strip and on the chop screen — is now drawn upward with each moment's loudness solid inside its peaks, so a loud finished mix shows its hits and gaps instead of one solid block, and a long note's swell and fade are plain to see. A panel row with a long heading, such as a keys-mode zone's, no longer runs one cell past the edge of the screen.

cargo install phosphor-studio --locked

v0.3.93 — 0.3.92, building on current Rust

0.3.92 would not build with the newest Rust compilers, which treat one pattern in the new multi-core engine as an error; installing it with an up-to-date toolchain failed. This release is the same engine with that pattern written out the way current Rust requires — nothing about how Phosphor sounds or behaves changes.

cargo install phosphor-studio --locked

v0.3.92 — Every core, and the sound stays exactly the same

Phosphor now spreads its tracks over all of your computer's cores instead of doing everything on one, so a song with many instruments and effects has far more room before the audio drops out — a busy eleven-instrument song that used a fifth of one core now uses under a tenth, and its worst moments are three times calmer. Nothing about the sound changes: every sample is identical however many cores play it, and a test holds it to that. On Linux, Phosphor also asks for real-time scheduling so other programs cannot delay the audio, if your account is allowed it. PHOSPHOR_AUDIO_THREADS=1 runs everything on one core, as before.

cargo install phosphor-studio --locked

v0.3.91 — Every MIDI device at once, plugged in whenever

Phosphor now listens to every MIDI keyboard and controller you have plugged in, all at once, instead of only the first one it found when it started. Devices can come and go while it runs: plug one in and within a couple of seconds the bottom bar says it is connected and it plays; pull it out and the bar says so, with nothing to restart. A keyboard set to MIDI channel 16 also plays normally now — before, its notes could be mistaken for presses on the Phosphor Deck controller, which is now recognised by its own port name rather than its channel.

cargo install phosphor-studio --locked

v0.3.90 — Copy a pad to another key

On the sampler, y copies the pad under the caret — every sound on it and every setting — and p on another key makes that key an exact copy, replacing what was there. Y copies just the one sound under the layer cursor, and p adds it to the key's own sounds instead. The copy works across keys and across sampler tracks, costs no extra memory because the copies share their audio, and every paste is one step of undo and redo; in keys mode the same keys copy a zone's sound.

cargo install phosphor-studio --locked

v0.3.89 — The chop plays itself back, and every key has one name

The chop screen gains a clip row: set it to yes and landing a chop also writes a clip that plays the slices back in the recording's own timing, loud hits loud and quiet ones quiet, on the next free bar — play it and you hear the recording, move its notes and you have rearranged the break. One undo takes back the slices and the clip together, and if the break is not at the song's tempo the message says how many bars it runs. Every screen now names notes the same way, with middle C as C4: the sampler used to call it C3 while the piano roll, chord device and sequencer said C4, so the same key had two names. Sampler pads and zones read one octave higher than before, a chop starts on C2, and new recorded takes are named to match; older sessions open unchanged.

cargo install phosphor-studio --locked

v0.3.88 — Chop a recording across the keys

On the sampler, c chops the sound on a pad across the keyboard, one slice per key from C1 up, and C does the same for any recording in your samples folder. Cut where the hits are — listening to everything, or only the kicks, the snares or the hats, so a break can be cut from kick to kick — or on a beat grid, or into even slices; turn the sensitivity, keep only the strongest few to fill one octave, grab any cut and move it by ear. The keyboard shows in amber where the slices will land and in red any key already holding a sound, which a chop never overwrites; c lands it as one undo step, and every slice shares one copy of the recording, saved as one file.

cargo install phosphor-studio --locked

v0.3.86 — The app tells you what changed, and when there's more

Phosphor now keeps you current on its own, two ways. The first time you run a version you haven't seen, a small card sums up what changed — read from a changelog that ships inside the binary, so it works offline and is always exactly right for the version in front of you. Dismiss it with Esc and it remembers, greeting you once per upgrade and no more. And once every six hours, on a background thread, it checks crates.io for a newer build and shows a single dismissible line telling you to run the install command to get it. It checks crates.io rather than git tags deliberately — a tag exists before the crate is published, so the notice only fires when the version you'd actually get is installable. The TLS is pure Rust (rustls, no system OpenSSL), so the one-command install is untouched; the check times out in three seconds, is silent whenever you're offline, never runs in a headless build, and PHOSPHOR_NO_UPDATE_CHECK=1 turns it off. Install: cargo install phosphor-studio --locked