Files
Alexandru CarausandClaude Opus 5.5 a02d892f83 MIDI input devices: live play-through and MIDI recording (#493)
* MIDI input devices: live play-through and MIDI recording

Keyboards and pads could not be used at all: there was no MIDI device
layer (G-02).

- crates/playback/src/midi.rs opens every MIDI input port through midir
  (ALSA sequencer, CoreMIDI, WinMM), follows devices that are plugged in or
  removed, and passes channel messages to the audio thread over a lock-free
  ring, each with the time it arrived.
- The mix engine plays them on the instruments of record-enabled and
  input-monitored MIDI and instrument tracks (crates/mix/src/live_midi.rs):
  notes at their sample offset, the sustain pedal holding note-offs back.
- While recording, the events are kept with their timeline position and
  become MIDI clips on the record-enabled tracks
  (crates/engine/src/io/midi_take.rs), with controllers, pitch bend and
  aftertouch. A pass can be MIDI only: the audio input is opened for audio
  tracks alone.
- A MIDI or instrument track chooses a device and a channel at its input
  selector (kept in the track's input route as `MIDI:<channel>:<device>`).
- Setup > Playback Engine lists the input ports with a switch each and, on
  request, what arrives from one; Setup > MIDI > MIDI Input Devices opens
  it. The switches are app preferences.

Note lifecycle:

- A strip keeps the keys and the sustain pedal of every owner (input port
  and channel) apart. A pitch held by two devices or channels sounds until
  the last one releases it, and one owner's pedal does not hold another's
  notes. A strip follows 16 owners at a time; further ones share the last
  place (documented in live_midi.rs).
- A full queue is never silent. An event that does not reach the audio
  thread (the 1,024-entry input ring or the 256 events a callback takes)
  marks its port; the audio thread then drops what it still has queued from
  that port and the engine releases the notes and pedal the port holds. A
  port that closes, a replaced feed and events skipped while nothing
  listens take the same path.
- A take records where input was dropped: the notes that port held end
  there, and the status line says the take is incomplete. Recorded events
  the UI thread did not collect in time are counted and reported too.
  Recorded notes are told apart by device as well as channel and pitch.

On Linux, live play was checked with a hardware keyboard (Akai MPK mini 3)
and recording with a virtual one (crates/playback/examples/midi_keys.rs),
before the note-lifecycle work; that part is covered by tests only. macOS
and Windows are type-checked only; there is no MIDI input on FreeBSD or
the web.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* midi real device tests

* midi device drop test

* midi device fix pr review comments

* MIDI input: review fixes for note ownership, lost input and takes

Live notes (crates/mix/src/live_midi.rs):

- An owner without a place of its own joins the shared place while it is
  in use, even when another place has come free. It could get a second
  place before, and the release of its key in the shared place was then
  not found: the note stayed on. The same held for the pedal.
- A change of the track's input releases the shared place when the input
  no longer takes any one of the owners in it, not only the first.
- The strip remembers which port and channel last set each controller.
  When that source loses its input or the track stops listening to it,
  the instrument's controllers are set again from the clips and from the
  sources that are left, so a bend from an unplugged device does not stay.
- When playback runs out under monitoring, the clips' sustain pedal goes
  up with their notes.

Capture (crates/playback):

- A loss carries its time. What a port sends after it is played and comes
  after the mark in the take; before, it was dropped and recorded ahead
  of the mark.
- The age of an event is counted at the transport speed.
- Loop recording writes a mark where the loop goes round, and a key played
  with the playhead at the end of the loop stays inside the loop.
- The end of a record pass is acknowledged by its number, so the late
  answer to an earlier pass does not end the wait for a later one.
- A connection the backend closes marks its port, also when a device with
  the same name is opened in its place.

Takes (crates/engine/src/io/midi_take.rs, crates/ui-egui):

- A note held into the next round of a loop is split there, also when its
  release is later on the timeline than its press.
- A track taken out of record during a pass keeps what it recorded.
- A pass whose end the audio engine did not confirm is reported as
  incomplete in the status line.
- An inactive record-enabled audio track no longer turns a MIDI pass into
  an audio one that is then refused.

docs/midi-input.md: Windows drivers that allow one program per device, and
the new status text.

* MIDI input: review follow-ups on loss order, controllers and loop takes

- Each port has its own time of loss. One port's later loss no longer
  takes along what another port sent after its own: that is played, and
  comes after that port's mark in the take.
- A retired connection is closed before its port is marked as lost. Marked
  first, a note-on delivered while it closed carried a later time than the
  loss and could be played after the release.
- The strip keeps the last controller value of every source, not only the
  newest. When one of two sources that set the same controller goes away,
  the controller goes back to the value of the one that stays. 64 values
  are kept; past that the oldest is forgotten.
- A take can say where the pass stopped (MidiTakeEvent::END), and the UI
  says so for loop passes. A key still down then ends at the stop in the
  round it is in: held over a round or more it covers the loop, where it
  used to end at the loop end of its first round.
- A pass that records MIDI does not start while the audio engine has not
  confirmed the end of the previous one. It takes the MIDI since its last
  callback with the state of the pass it knows, so a pass started and
  stopped meanwhile had its notes written at the old position.

* MIDI input: loss marks in the queue, connection gate, stop position

- A loss from a full queue is also written into the queue, ahead of the
  first event that fits again. The audio thread deals with it at that
  place. Before, a loss flagged after the callback had read the flags was
  seen one callback late and ended a note played after it. The flag for a
  loss already met in the queue is not a second loss.
- A connection is shut off under the feed's lock when it is closed
  (MidiFeed::close_port), and what its device thread still delivers is
  discarded. Dropping a connection joins that thread on ALSA; CoreMIDI
  (MIDIPortDispose) and WinMM (midiInStop, midiInReset, midiInClose) do not
  promise to, so the order of drop and mark is no longer relied on.
- When the controller table is full and forgets a value, the strip keeps
  the port and channel it came from. The controllers are still reset when
  that source goes away, where a bend pushed out of the table used to stay.
- A loop pass ends where the audio engine is. The larger of the engine's
  and the UI's position was used, and just after the loop went round the
  UI's is still near the loop end: a short held note covered the loop.
- The end of a pass waits for the audio engine by what the pass set out to
  record, not by the devices connected at Stop. A pass whose last device
  was unplugged before Stop left nothing pending, and a new pass could
  start before the engine was done with it.

* MIDI input: stop at the loop end, and passes owed by the audio engine

- A key played while the playhead stands at the end of the loop is the
  last thing of that round. It was written as the first of the next round,
  with a mark that the loop had gone round; a pass stopped right there
  never went round, and a note held to the stop grew a second part.
- The feed knows whether an ended pass is still owed by the audio engine
  (MidiFeed::pass_owed), and the UI asks it before a pass that records
  MIDI starts. The UI kept that itself, where no test could stall the
  audio callback against it.

* MIDI input: stop boundary, loop rounds, loss marks and shared owners

- A pass ends at a time on the feed's clock (MidiFeed::end_pass). Only
  what arrived up to it is written to the take, however late the audio
  thread hears of the Stop, and the callback takes the queue in once more
  after the command before it confirms: a note that arrived between its
  reading the queue and the Stop was missing from a confirmed take.
- The confirmation carries where the playhead stood (MidiFeed::stopped_at).
  A loop pass ends there; the player's position read afterwards could be
  a round further on, which the take knows nothing about. Without a
  confirmation no stop position is used.
- The take builder is told whether the pass looped (MidiPass). In a pass
  that did not, a release stamped before its key press (a late callback)
  is one short note, where it was split around the ends of the clip. The
  stop position is a parameter, not an entry that the event cap could cut.
- A pass records the tracks that were in record when it started, and only
  those: the same list the end of the pass waits by. A track put in record
  during the pass got what was played before that, without a wait.
- A short loop goes round several times in a callback: each entry is put
  in the round it arrived in, so two entries a round apart have one mark
  between them.
- A mark in the queue is stamped with the time of its loss. A port that
  overflowed, played on and was then closed keeps a mark for the close
  (the new note was held to the end of the take), and a loss told by the
  port's flag is not written again when its mark arrives.
- Live events stay in order of arrival when they are played: a release
  taken by a shorter callback was due before its note-on.
- A callback reads the transport speed once, for rendering and for the
  ages of the next callback's events.
- The shared owner place is left alone by a source that never joined it:
  its note-off no longer ends another owner's note there, and its loss no
  longer releases the place.
- When a live source goes away, the instrument's controllers are restored
  before the block's clip events are sent, so a clip controller at the
  start of that block keeps its new value.
- Tests that assert MIDI positions use a clock the test sets.

* MIDI input: pass boundaries, loop punch-in and review follow-ups

- A pass begun while the transport runs has a start time on the feed
  (MidiFeed::begin_pass): what is played after Record is written down
  also when the audio thread takes it in before it reads the command.
- A pass goes on through a transport stop until the command that ends it.
  The UI sends the two one after the other; when they reached two
  callbacks, a note played just before the stop was left out of a
  confirmed take.
- The end of a pass is asked for every entry, so a Stop that comes while
  the queue is being read still cuts off what follows it.
- A mark in the queue carries the time its events were dropped, kept apart
  from a later close of the port. An overflow before Stop is in the take
  when the port closes after it.
- A pass punched in while a loop plays is a loop take over that loop. In a
  line from the punch-in to a stop in the next round nothing fell inside
  the range.
- In a loop take with marks, only the marks say that the loop went round:
  a release stamped before its press within one round is one short note.
- A key pressed in the last samples of the range starts at the last tick
  the clip plays, not at the tick of its end.
- When the clips' controllers are sent again while stopped, their sustain
  pedal goes up again: no pedal-up of theirs would follow.
- The render step is taken after the commands, so a session at another
  sample rate is rendered at that rate from the callback that installs it.
- The stop position and the incomplete-take warning go by one answer from
  the audio engine.

* MIDI input: test that a callback renders at the speed it keeps

A speed change that arrives while a callback runs takes effect from the
next one: the callback renders at the speed it read, and the next callback
counts the ages of its events at that same speed.

* MIDI input: volume and pan go back to MIDI's defaults with their device

The reset sent when a live source goes away is Reset All Controllers,
which leaves the channel volume (CC 7) and the pan (CC 10) alone. A
device that turned the volume down to nothing and was unplugged left the
track silent. When the source that went away had set one of the two, and
neither the clips nor a source that is still there gives it a value, the
instrument is sent the value MIDI names as the default (100, and 64).
The same when the track stops playing live input.

* MIDI input: third round of review follow-ups

- The stop cutoff is one value on the feed, in force from the store that
  ends the pass and gone when the audio thread confirms it.
- The start of a pass holds for the whole pass: what was played before
  Record stays out also when it is taken in after the start command.
- What is played just before a Stop is put inside the range that ends at
  the stop, not on its end.
- A port closed while the queue is read is met through the mark of its
  overflow; the flag of that close, a callback later, is not a second
  loss (it ended a key the new connection played).
- An overflow and the loss it is have one time. Read apart, they could
  differ by a microsecond and count as two losses.
- A volume or pan the full controller table forgot goes back to its
  default when its own device goes, not when another does.
- The chase of the clips' controllers uses the track's MIDI delay, as
  playing them does.
- Recorded controllers in the last samples of the range stay where the
  clip plays; in a take without marks the press as played, not the note's
  start, says whether the loop went round; a take cut at the event cap
  does not use the stop position.
- The loop the MIDI of a punched-in pass goes to is the loop the audio
  engine plays: not a range too short to loop, nor one that Play From
  dropped.
- The audio input stops taking in before the wait for the MIDI.

* MIDI input: fourth round of review follow-ups

- A record pass goes on through the natural end of playback until the UI
  ends it, up to the time playback ran out: what was played as it reached
  the end is in the take, what follows is not.
- Before the end of a pass is confirmed, the device threads are kept out
  of the queue while it is read once more, so a message stamped before
  the Stop is not put in after the answer. The audio thread does not wait
  for a device thread that is in there.
- A later loss of a port is noted as dealt with only at the end of the
  callback: with two overflow marks of one port in the queue, the second
  was skipped and the key played between them had no end.
- Whether a pass was begun is read before when: a pass seen as begun has
  its own start time.
- The volume and the pan go back to their defaults when the source that
  set them last goes, also when the controller table forgot its value,
  and not when an earlier setter goes.
- A clip's note-off that is held back because a live key holds the pitch
  is remembered for the block: the key going up earlier in the block no
  longer ends the note before the clip would have.
- In a take without marks, whether the loop went round between a press
  and its release is judged by their samples, not their ticks.
- The stop position of a loop pass is not used when recorded entries did
  not reach the take: one may be the mark of a round.
- Loop recording over a selection too short to loop is recorded as a
  punch, as the transport plays it.

* MIDI input: fifth round of review follow-ups

- Whether a pass was begun is asked for every event: a pass begun while
  the callback is reading the queue records from when it began.
- The ages of a pass's last events are counted up to when the transport
  stopped. Counted up to the callback that takes them in, the time the
  playhead stood still moved them back.
- An overflow the port's flag told of keeps its time when an older mark
  in the queue shows a later close: its own mark may never come.
- What becomes of the clips' held back note-offs is settled after the
  block's live events. A key that goes down again before the clip's note
  would have ended is not ended by it, and with two clip notes of a pitch
  in a block the one that sounds when the key goes up lasts to its end.
- When the source that set the volume or the pan last goes and another
  one's value is sent again, that one is the last setter from then on.

* MIDI input: sixth round of review follow-ups

- A loss is followed whenever the transport runs, and written to the take
  by when it happened, like an event: a port lost in a pass that began
  while the queue was being read ends its notes in the take.
- A pass started and ended by the commands of one callback is still that
  pass in the last read of the queue: what was played in it is kept.
- When a live key takes a pitch again, the clips' held back note-offs
  from since the last key went up are sent where they were, so the
  instrument lets go of the clip's note before the new press.

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-19 08:37:06 +07:00

30 KiB
Raw Permalink Blame History

SoundCraft roadmap

Stage: pre-alpha · next: alpha, ~5% and ~110–180 h away (the alpha gate's three failing workflows)

Last reviewed: 2026-10-24 · Last updated: 2026-11-18 · Change: minor (MIDI input in the progress log; previously trivial: Frequency Shifter plugin, Command-click target priority and cursor, Command-click automation points, plugin editors on Linux/X11, Cancel Zoom Toggle, side panels in dock columns, Auto Pan stereo balance, Alt-click returns a plugin parameter to its default, Clip List Auto Rename, Strip Silence rectangles, Strip Silence Rename, Strip Silence Extract and Separate, Clip Looping dialog, AudioSuite Vari-Fi speed ramps, Auto Pan plugin, Subharmonic plugin, Ring Modulator plugin, Float32 file headroom) · Target: Avid Pro Tools Ultimate 2026.4.1

SoundCraft is a clean-room, pure-Rust digital audio workstation that aims at full parity with Avid Pro Tools, and then beyond it: faster, open, scriptable and agent-controllable. This page is the one-page summary; the detail is in docs/target-app-parity.md (assessment), docs/gaps.md (ranked work list), docs/roadmap.md (milestones and beta plan) and docs/parity-checklist.md (generated menu checklist).

Headline numbers

Number Value Kind
Menu breadth 482 / 512 Pro Tools menu leaves (94.1 %); engine alone 397 / 512 measured (cargo xtask parity + UI-layer aliases)
Feature breadth ~70 % estimated (menus plus plugins, hardware, formats, immersive, cloud)
Ready for real work ~40 % estimated, weighted by dimension
Mainstream practitioner (tracking/mixing engineer) ~36 % estimated: 50.6 % weekly-area depth × 0.90 interaction × 0.92 stability × 0.85 file exchange (how)
Essentials user (song or podcast, defaults) ~57 % estimated: 72.4 % core-feature depth × 0.90 launch/stability × 0.90 discoverability × 0.97 files (how)
Remaining to alpha ~110–180 Opus 5.5 agent-hours (the failing gate rows) estimated, calibrated on PR history
Remaining to beta ~350–570 Opus 5.5 agent-hours (includes the alpha work; ~60–70 % parallelizable) estimated
Remaining to full parity ~950–1,450 Opus 5.5 agent-hours estimated
Audience Ready % Agent-hours to ~95 % Work that dominates
Full target (ready for real work) ~40 % ~950–1,450 h Hardware, the stock plugin catalogue, AAF/OMF and immersive, localization, fidelity
Mainstream practitioner ~36 % ~380–600 h Interface and MIDI recording, AAF/OMF, stock-plugin depth, core-path bugs
Essentials user ~57 % ~110–200 h Launch and platform fixes, onboarding, effect panels and presets, MP3/AAC export

Hours are Opus 5.5 agent wall-clock hours, calibrated on this repo's PRs; 60–70 % parallelizes. Detail: target-app-parity.md.

Why pre-alpha: the core-workflow gate in docs/roadmap.md fails. Editing, mixing, bouncing, and saving and reopening work end to end. But a Pro Tools user can't record from a chosen audio interface at a chosen buffer size (only the default devices, a fixed 512-sample block, and takes held in RAM). Recording MIDI from a keyboard is built but checked on Linux only: macOS and Windows are type-checked and have not been tried with a device, and there is no MIDI input on FreeBSD or the web. And they can't bring a session in or hand one back (no AAF/OMF/.ptx). Readiness (~40 %) sits right at the alpha bar, but a gate failure keeps the app pre-alpha. The 2026-10-07 estimate ("~65 % overall, 110–150 h to 100 %") counted feature presence. This one measures readiness and adds hardware, localization and field bug reports.

By dimension

Dimension Ready Remaining (h) Doc
Features ~45 % 520–810 target-app-parity.md
UI/UX fidelity ~55 % 60–100 ui-parity.md
File formats ~40 % 70–120 file-format-parity.md
Hardware (interfaces, MIDI, surfaces, sync) ~12 % 110–180 hardware-parity.md
Localization ~12 % (1 of Pro Tools' 8 languages; English and pt-BR fixed UI strings, no CJK/RTL font fallback or native review) 70–110 localization-parity.md
Performance ~35 % (unmeasured) 40–70 hardware-parity.md
Stability ~45 % 50–80 gaps.md
Platforms ~65 % (5 platforms built, macOS exercised) 20–40 gaps.md
Ecosystem / plugins ~30 % in Features + Hardware plugin-parity.md
AI features ~5 % 30–50 gaps.md
Agent control ahead of Pro Tools 3 control-protocol.md, mcp.md

Features

Area Breadth Ready Remaining (h)
Recording and monitoring 75 % 40 % 40–60
Editing 92 % 65 % 40–60
Mixing and routing 85 % 60 % 35–50
Automation 80 % 55 % 20–30
Built-in plugins and AudioSuite 40 % 35 % 80–120
Third-party plugin hosting 70 % 45 % 40–60
MIDI and instruments 70 % 30 % 50–80
Score and notation 60 % 35 % 20–30
Elastic Audio, TCE, Beat Detective 70 % 35 % 40–60
Surround and immersive 55 % 35 % 50–80
Video and post 60 % 40 % 40–60
Session, file management, interchange 55 % 35 % 60–100
Collaboration and cloud (Avid services) 0 % 0 % owner decision
Agent control 100 % 100 % 3

Weights and evidence per row: target-app-parity.md.

Languages

Language Code Status Translated
English en full 100 %
Simplified Chinese zh-Hans none 0 %
Spanish es none (PR #143 open) 0 %
Hindi hi none 0 %
Arabic ar none 0 %
French fr none (PR #143 open) 0 %
Portuguese (Brazil) pt-BR full — 100 % of fixed UI strings; tests pass 100 % (native-speaker review pending)
Indonesian id none 0 %
Japanese ja none 0 %
German de none 0 %
Korean ko none 0 %
Vietnamese vi none 0 %

Other languages shipped: 0 complete. Brazilian Portuguese covers the fixed UI strings (100 %), with native-speaker review, CJK/RTL font fallbacks and script shaping still pending. Detail: localization-parity.md.

Upcoming

Ranked; the alpha gate, the alpha checklist and the beta plan are in docs/roadmap.md.

  1. Alpha blocker: audio interfaces: device and buffer-size choice, duplex stream, ASIO; record to disk (G-01, G-06). 35–55 h.
  2. Alpha blocker: MIDI devices: keyboard input, live play and recording are in (checked on Linux only; macOS and Windows type-checked, none on FreeBSD or the web); output, clock and loop/merge recording remain (G-02). 12–22 h.
  3. Alpha blocker: AAF/OMF import and export (G-03). 50–90 h.
  4. macOS plugin entitlement (#153), then AU editors and embedded CLAP editors on macOS (G-05). 1 h for the entitlement (needed for the mix row), then 10–15 h.
  5. Land the open bug-fix PRs and clear the correctness backlog (G-04). 15–25 h.
  6. PR CI running cargo xtask ci on three OSes (G-14). 5–10 h.
  7. Fidelity harness against Pro Tools (G-07). 20–30 h.

Robustness

Property tests drive random edit sequences (with full undo), mutated session files and hostile command parameters through the engine and mixer; they have caught fade, overflow and unbounded-allocation bugs. Every command also runs with empty parameters on empty and demo sessions. Hosted plugins live in isolated unsafe crates (clap-host, vst3-host, au-host) and are created, loaded and destroyed off the audio thread. The video decoders survive hundreds of mutated and truncated movies. Field reports from the first public week are tracked in gaps.md (G-04).

Progress log

  • 2026-11-18 (MIDI input): MIDI input devices: keyboards play record-enabled and input-monitored MIDI and instrument tracks live and are recorded into MIDI clips, with a device and channel choice per track. The device switches are in the MIDI inputs section of Setup › Playback Engine (Setup › MIDI › MIDI Input Devices opens the same window) and are kept in the app preferences, per computer, not in the session. Controllers, pitch bend and aftertouch reach the instrument live; a pitch held on two devices or channels sounds until both release it; a full input queue releases the notes of its device and marks the take incomplete. On Linux, live play was checked with a hardware keyboard (Akai MPK mini 3) and recording with a virtual one; macOS and Windows are type-checked only, and there is no MIDI input on FreeBSD or the web. Guide: docs/midi-input.md. No readiness percentage change until that is measured.
  • 2026-11-09: A built-in Frequency Shifter (freq_shifter) moves every frequency in the signal by the same number of hertz, from 0.01 Hz to 5 kHz: up, down, both ways at once, or down on the left and up on the right of a stereo track. The unwanted sideband stays at least 100 dB down from 20 Hz to 20 Hz below Nyquist at 44.1 to 96 kHz. Feedback sends the output round again for a trail of further shifts, Mix blends in the dry signal, and every change glides without a click. No readiness percentage change.
  • 2026-11-08: Command-click near an existing automation breakpoint keeps that point as the click target with every active tool, and existing fade and clip-gain controls retain their normal priority. Empty automation space shows a crosshair and an insertion hint while Command is held. The active tool's drag gestures stay unchanged. No readiness percentage change.
  • 2026-11-05: Command-click in an automation lane adds a point at the clicked time and value with the current editing tool (#1394), using the existing Pencil mapping. Command-click preserves the existing selection and also works on the fallback volume lanes of Master, Aux and VCA tracks. Plain clicks and clip contents stay unchanged, and one Undo removes the new point. No readiness percentage change.
  • 2026-10-27 (plugin editors on Linux): VST3 editors and embedded CLAP editors open in a SoundCraft X11 host window on Linux and the BSDs (XWayland on Wayland desktops), resized on request and closed from its title bar; the host run loop (VST3 Linux::IRunLoop, CLAP timer-support and posix-fd-support) lets X11 editors read their display connection and repaint. Verified with Graillon 3 and Surge XT Effects (JUCE) in both formats (#527). No readiness percentage change.
  • 2026-10-25: Alt+Shift+E (view.zoom_toggle_cancel) and an Alt-click on the Zoom Toggle button cancel Zoom Toggle and keep the current view: the zoom, the scroll and the track heights stay as they are, and the button is no longer lit. The next Zoom Toggle zooms in from that view and goes back to it. No readiness percentage change.
  • 2026-10-25: Tracks and Groups and the Clip List sit in dock columns that run the Edit window's full height at its left and right edges, with the MIDI Editor under the session view between them; Mix docks Tracks and Groups at its left edge. A panel dragged onto a dock group joins it as a tab, stacks above or below it, or makes a new column; one dragged to an empty window edge makes a dock there. A list with no saved place reopens in its dock, and makes the dock again when it is gone. Preferences and window configurations saved with the earlier split-frame layouts load with the new default layouts and keep their other settings. No readiness percentage change.
  • 2026-10-25: Auto Pan moves the balance of a stereo track: the left channel's level falls as the position moves right and the right channel's as it moves left, at constant power, and each channel stays on its own side. At the center the track passes unchanged, so a wide or out-of-phase stereo image keeps its width, and the envelope follower follows the louder channel. No readiness percentage change.
  • 2026-10-24: An Alt-click (Option-click on a Mac) on a parameter in the plugin window, the Clip Effects window or an AudioSuite plugin's window returns it to its default value, on a slider or a slider's value box, and in the plugin window on a choice list too, as an Alt-click returns a fader to 0 dB. In the plugin window and the Clip Effects window the reset is one undo step. While Alt is held, a drag on a slider leaves the value where it is. No readiness percentage change.
  • 2026-10-24: The parameter sliders of the plugin window, the Clip Effects window and AudioSuite plugins move a tenth as far for the same drag while Ctrl (Command on a Mac) is held, as the Strip Silence sliders do. Logarithmic sliders move a tenth as far along the slider, and whole-number sliders stay on whole numbers. No readiness percentage change.
  • 2026-10-24: The Strip Silence window's four sliders move a tenth as far for the same drag while Ctrl (Command on a Mac) is held, on the slider and on its value box. Pressing or releasing the key during a drag leaves the value where it is. The Threshold and Clip Start Pad boxes show one decimal place. No readiness percentage change.
  • 2026-10-24: Clip List › Auto Rename (clip.auto_rename) sets the names that editing gives the clips it separates from the selected clips: a name, a starting number, a number of places (zeros before the number) and a suffix. The piece after each cut takes the next name, the piece before it keeps its name, and all the pieces count up one number sequence. Pieces that Strip Silence names with its own Rename fields, or removes, take no Auto Rename name. Copied clips keep their scheme when they are pasted, saved sessions hold the schemes, and Import Session Data brings them along. No readiness percentage change.
  • 2026-10-24: While the Strip Silence window is open, the Edit window draws a rectangle around each range that Strip would keep on the selected tracks, padded by Clip Start Pad and Clip End Pad, and the rectangles follow the sliders as they move. They are removed when the window closes. edit.strip_silence_preview returns the same ranges without changing the session. No readiness percentage change.
  • 2026-10-24: The Strip Silence window has a Rename button. It opens Rename Selected Clips, where a name, a starting number, a count of zeros and a suffix set the names of the clips that Strip, Extract and Separate leave in the selection (for example SFX023.Reel1, SFX024.Reel1). The app keeps the scheme for later uses of Strip Silence until the app quits, or until Clear and then OK empty it. No readiness percentage change.
  • 2026-10-24: The Strip Silence window has Extract and Separate buttons. Extract removes the audio and keeps the silent parts of the selection, and Separate separates the clips at the edges of the silence without removing anything. Minimum Strip Duration goes up to 4,000 ms. No readiness percentage change.
  • 2026-10-24: Clip › Loop… (Cmd+Alt+L) opens the Clip Looping dialog: Number of Loops, Loop Length in the main counter's time format, or Loop Until End of Session or Next Clip. A loop length that is not a whole number of loops cuts the last loop short, and Unloop removes that short loop too. No readiness percentage change.
  • 2026-10-24: AudioSuite ▸ Pitch Shift ▸ Vari-Fi slows the selected clips down to a complete stop or speeds them up from one, and the pitch follows the speed. Fit To keeps each clip's length and plays two-thirds of it; Extend plays all of it and makes the clip 150 % long. Fades On fades the audio out with the slowdown or in with the speedup. Before, the menu item resampled the clip at a constant speed. No readiness percentage change.
  • 2026-10-24: A built-in Auto Pan plugin pans the mono sum of a stereo track between left and right. An LFO with seven waveforms moves it at a rate in BPM or at the session tempo, running free, once, in step with the transport, or when the level crosses a threshold or a manual trigger changes; an envelope follower can move it by level instead. Width, Manual and Path set the field, and Output sets the level. No readiness percentage change.
  • 2026-10-24: A built-in Subharmonic (subharmonic) adds the octave below a lower and an upper band of the input, chosen from four frequency ranges, with a direct bass band, a gain and a solo for each band, Drive with six characters, HP and LP filters, and a Mix that keeps one path at full level. No readiness percentage change.
  • 2026-10-23: A built-in Ring Modulator (ring_mod) applies ring modulation, frequency modulation or a positive or negative resonator, and an LFO, an envelope follower or sample and hold moves its frequency. AudioSuite › Modulation › Sci-Fi now runs it instead of the Flanger. No readiness percentage change.
  • 2026-10-19: Float32 WAV and AIFF-C encoding preserve finite samples above full scale. Integer PCM still clips at full scale. Tests cover whole-file and streaming encoders, non-finite samples, and bounce output with normalization on and off. No readiness percentage change.
  • 2026-10-18: Mono audio devices receive the average of the stereo channels before output clipping, retaining right-only audio. Surround mixes use the same average after their ITU stereo fold-down. Regression tests cover channel balance, polarity cancellation, clipping, centered mono tracks, each 5.1 channel and several callback sizes. No readiness percentage change.
  • 2026-10-16: Master fader volume automation uses each render block's actual last sample, matching track faders. Breakpoints in the next block no longer pull the preceding block's level toward them, and ramps reach their last-sample value. Regression tests cover nonzero starts, one-sample callbacks and several block sizes. No readiness percentage change.
  • 2026-10-16: Aux, folder and master latency calculations exclude inserts already taken out for producing NaN or infinity, matching audio tracks. Subsequent blocks no longer compensate for an insert that is bypassed after failure. Regression tests check impulse timing, healthy insert latency and reset/retry at 64- and 512-sample blocks. No readiness percentage change.
  • 2026-10-16: Split into Mono extracts the correct source channel for each mono track instead of playing channel zero on every track. Clip offsets, gain, fades and stretch, source timestamps, Undo/Redo and saved audio are preserved; repeated clips share each extracted mono source. Unavailable media returns an error without partial edits. No readiness percentage change.
  • 2026-10-14: MCP batch rejects more than 1000 calls before executing any command, instead of silently running only the first 1000 (#460). No readiness percentage change.
  • 2026-10-14: soundcraft-cli convert dithers only when the output loses resolution (fewer bits than the source, a float or lossy source, or resampled/normalized samples); a same-depth, wider or 32-bit float conversion copies the samples exactly and digital silence stays silent. --dither and --no-dither override the choice (#548)
  • 2026-10-13: WAV: an empty data chunk followed by metadata (LIST, bext) reads as no audio; a recording that was never finalised (sizes left at 0) still gives what was written (#466)
  • 2026-10-13: Sampler: a ping-pong loop keeps its phase and direction when a step is wider than the loop (a narrow loop with high transposition), instead of reflecting once and dropping the rest of the travel (#463)
  • 2026-10-13 (VST3 host messages): The VST3 host creates IMessage and IAttributeList objects for plugins (IHostApplication::createInstance), so plugins whose controller and processor talk through IConnectionPoint::notify work: Line 6 Helix Stadium Native now loads its content database (it reported "Failed to get content database recovery info (Out of memory condition)") and exposes its parameters. No readiness percentage change.
  • 2026-10-13: mix.instrument takes the built-in instrument's parameters in params (validated, clamped) and refuses any other field, so a synth setting written beside plugin is an error instead of being accepted and ignored (#265)
  • 2026-10-13: A bounce of a bus that an aux returns onto lines up with the timeline: the aux insert's lookahead is compensated like the main mix's (it left the bus late and cut the end off), and tracks routed to that bus wait for it too (#246)
  • 2026-10-13: Delay compensation covers the inserts of the master faders: a bounce of the main mix with a Maximizer on the master lines up with the same mix without it (it came out 71 samples late) (#351)
  • 2026-10-12 (audio device settings): Setup › Playback Engine chooses the audio system, output and input device, sample rate and buffer size, kept per machine with the preferences; 16/32-bit integer devices are converted; ASIO is available behind the opt-in asio build feature (verified with an SSL 2+ at 128 samples). Channel routing, one duplex clock and latency compensation remain (G-01). No readiness percentage change.
  • 2026-10-12 (Mix in a separate window): Window › Mix in Separate Window shows the Mix window in its own native window, so Edit and Mix can be on screen at once (e.g. one per monitor), as in Pro Tools. No readiness percentage change.
  • 2026-10-12 (plugin editors on Windows): VST3 editors and embedded CLAP editors open in a SoundCraft host window on Windows (owned by the app window, resized on request, closed from its title bar); verified with a JUCE VST3 compressor and a CLAP effect. No readiness percentage change.
  • 2026-10-12: soundcraft-cli convert rejects an unparsable or zero --rate and an unknown --bit-depth (exit 1, nothing written) instead of converting with a default (#256)
  • 2026-10-12: Timecode labels with huge fields no longer overflow: frame counts are computed in 128 bits and clamp, so setup.current_timecode and session.format_time saturate instead of failing (#248)
  • 2026-10-12: session.format_time with the smallest bar number no longer fails with an internal error: the bar offset saturates (#249)
  • 2026-10-12 (plugin editors on Windows): VST3 editors and embedded CLAP editors open in a SoundCraft host window on Windows (owned by the app window, resized on request, closed from its title bar); verified with a JUCE VST3 compressor and a CLAP effect. No readiness percentage change.
  • 2026-10-12 (Mix in a separate window): Window › Mix in Separate Window shows the Mix window in its own native window, so Edit and Mix can be on screen at once (e.g. one per monitor), as in Pro Tools. No readiness percentage change.
  • 2026-10-12 (audio device settings): Setup › Playback Engine chooses the audio system, output and input device, sample rate and buffer size, kept per machine with the preferences; 16/32-bit integer devices are converted; ASIO is available behind the opt-in asio build feature (verified with an SSL 2+ at 128 samples). Channel routing, one duplex clock and latency compensation remain (G-01). No readiness percentage change.
  • 2026-10-10 (UI docking): Tracks and Groups, Clips, MIDI Editor, Memory Locations, and Undo History use movable panels. Edit and Mix retain separate arrangements; Clips and MIDI Editor belong to Edit. Transport, plug-in, and specialist utility windows retain their existing hosts. Panel moves and reset are available as UI commands, and saved UI preferences retain arrangements. Common toolbar and track record-enable buttons share interaction, accessible labels and keyboard focus through craft-ui, retaining blue tool selection and red record-arm states. No readiness percentage change.
  • 2026-10-10 — Stage re-normalized to pre-alpha by the core-workflow gate (interface recording, MIDI recording and session interchange fail). Full re-measure against Pro Tools Ultimate 2026.4.1 and the progress docs set (this page, target-app parity, gaps, roadmap, UI/format/hardware/plugin/ localization parity). v0.4.0 released. Community fixes: Cut All Automation, snap to neighbours, tempo stretch, I/O Setup, clip export names, menu-only dialogs, playback stop on new session.
  • 2026-10-09 — Light theme and live system appearance, clip-gain fader and nudge, missing-media warnings, session audio health, malformed-JSON and encoder-extension checks in the CLI, macOS system menu bar, Windows DX12 default, Linux fontconfig, metronome click in playback.
  • 2026-10-08 — v0.2.x–v0.3.0 released (Flatpak, AppImage zsync); VST3 quit crash fixed; Ctrl-as-Cmd shortcuts on Windows/Linux; plugin menus by vendor, AU inserts, instrument picker; rotating log file; branded DMG.
  • 2026-10-07 — Repository published; About window credits; release CI on macOS runners.
  • 2026-10-06 — Video track, Audio Unit hosting, plugin state and editors, Renderer; Mix window views; score export and print; surround mixing; VST3 hosting; property tests.
  • 2026-10-05 — Foundation crates, Edit and Mix windows, playback, CLI/MCP, parity report, recording and punch, CLAP hosting, Elastic Audio, Beat Detective, release pipeline.

Revision history

Date Change Summary
2026-11-09 trivial Progress log: Frequency Shifter plugin; readiness estimates unchanged
2026-11-08 trivial Command-click breakpoint/control priority and insertion affordance; active-tool drags retained; readiness estimates unchanged
2026-11-05 trivial Progress log: Command-click adds an undoable automation point (#1394); readiness estimates unchanged
2026-11-05 trivial Languages table: Brazilian Portuguese (pt-BR) near complete for fixed UI strings via PR #1346; needs native review. Estimates unchanged
2026-10-27 trivial VST3 and embedded CLAP editors on Linux/X11 (#527); G-05 estimate down to 10–15 h; readiness estimates unchanged
2026-10-25 trivial Progress log: Cancel Zoom Toggle; readiness estimates unchanged
2026-10-25 trivial Progress log: side panels in dock columns; readiness estimates unchanged
2026-10-25 trivial Progress log: Auto Pan stereo balance; readiness estimates unchanged
2026-10-24 trivial Progress log: Alt-click returns a plugin parameter to its default; readiness estimates unchanged
2026-10-24 trivial Progress log: fine adjustment on plugin parameter sliders; readiness estimates unchanged
2026-10-24 trivial Progress log: Strip Silence fine adjustment; readiness estimates unchanged
2026-10-24 trivial Progress log: Clip List Auto Rename; readiness estimates unchanged
2026-10-24 trivial Progress log: Strip Silence rectangles; readiness estimates unchanged
2026-10-24 trivial Progress log: Strip Silence Rename; readiness estimates unchanged
2026-10-24 trivial Progress log: Strip Silence Extract and Separate; readiness estimates unchanged
2026-10-24 trivial Progress log: Clip Looping dialog; readiness estimates unchanged
2026-10-24 trivial Progress log: AudioSuite Vari-Fi speed ramps; readiness estimates unchanged
2026-10-24 trivial Progress log: Auto Pan plugin; readiness estimates unchanged
2026-10-24 trivial Progress log: Subharmonic plugin; readiness estimates unchanged
2026-10-23 trivial Progress log: Ring Modulator plugin; readiness estimates unchanged
2026-10-19 trivial Float32 file encoding preserves finite headroom (#791); readiness estimates unchanged
2026-10-18 trivial Mono device playback retains both stereo sides and surround fold-down channels; readiness estimates unchanged
2026-10-16 trivial Master volume automation block boundaries corrected; readiness estimates unchanged
2026-10-16 trivial Failed inserts no longer contribute aux, folder or master latency after containment; readiness estimates unchanged
2026-10-16 trivial Split into Mono preserves each source channel, clip edits and saved audio; readiness estimates unchanged
2026-10-14 trivial Progress log: oversized MCP batches rejected before execution (#460)
2026-10-13 trivial Progress log: empty WAV data chunk followed by metadata (#466)
2026-10-13 trivial Progress log: sampler ping-pong phase for wide steps (#463)
2026-10-13 trivial Progress log: Delete key clears the selection (#404)
2026-10-13 The Delete and Backspace keys clear the edit selection in the Edit window, as Pro Tools' Delete does (Edit › Clear is Cmd+B); the MIDI editor keeps them for its selected notes (#404)
2026-10-13 trivial Progress log: mix.instrument params, unknown fields refused (#265)
2026-10-13 trivial Progress log: bus bounce compensates aux returns (#246)
2026-10-13 trivial Progress log: master insert latency compensated (#351)
2026-10-12 trivial Progress log: convert option validation (#256)
2026-10-12 trivial Progress log: timecode overflow (#248)
2026-10-12 trivial Progress log: bar offset saturates (#249)
2026-10-10 minor Readiness-by-audience table with hours: full 950–1,450 h, mainstream 380–600 h, essentials 110–200 h
2026-10-10 minor Added mainstream practitioner ~36 % and essentials user ~57 % to the headline numbers
2026-10-10 minor Stage alpha → pre-alpha: the core-workflow gate fails on interface recording, MIDI recording and session interchange; alpha distance added
2026-10-10 major Progress docs restructured: stage alpha (re-normalized the same day), two numbers (breadth ~70 %, ready ~40 %), dimension/feature/language tables, hours re-calibrated; area table moved to docs/target-app-parity.md, milestones to docs/roadmap.md
2026-10-07 major Menu parity 94 %, ~65 % estimated feature parity, alpha list
2026-10-06 minor Alpha and parity estimates