* 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>
19 KiB
Where SoundCraft falls short of Pro Tools
Last reviewed: 2026-10-25 · Last updated: 2026-11-18 · Change: minor (G-02 shrunk: MIDI input devices work; previously minor: G-05: plugin editors on Linux/X11; previously trivial: G-09: the pt-BR catalog now covers helper-passed tooltips, the status bar, the remove-session prompt and engine error text; G-08: Frequency Shifter, 28 processors; G-04: volume automation read at every sample, #1354; G-01:
setup.playback_engineapplies the device buffer in the desktop app; G-04: Clip Looping crossfade and loop count) · Target: Avid Pro Tools Ultimate 2026.4.1
Every known shortfall, one entry each, ranked by how much it stops a Pro Tools user from doing
real work in SoundCraft. This is the work list: pick from the top. Rows marked alpha blocker
fail the core-workflow gate in roadmap.md and keep SoundCraft pre-alpha. Numbers and weights live in
target-app-parity.md; the plan that orders these into milestones is
roadmap.md. Hours are Opus 5.5 agent-hours (calibration in target-app-parity.md).
Estimates marked "≈" are judgements; issue numbers are storytold/soundcraft GitHub issues.
When you close a gap, delete its entry (or shrink it) in the same PR, and bump the timestamp.
Ranked gaps
| # | Gap | Dimension | Doc | Est. (h) |
|---|---|---|---|---|
| G-01 | Alpha blocker. No channel routing or duplex low-latency path (device, rate and buffer choice done; ASIO opt-in) | Hardware | hardware-parity.md | 15–25 |
| G-02 | Alpha blocker. MIDI devices: input works (checked on Linux only); no output, clock or loop/merge recording | Hardware / MIDI | hardware-parity.md | 12–22 |
| G-03 | Alpha blocker. Cannot exchange sessions with Pro Tools (no AAF/OMF, no .ptx) |
File formats | file-format-parity.md | 50–90 |
| G-04 | Open correctness bugs in features counted as done (~25 issues) | Stability | this file | 25–40 |
| G-05 | (Entitlement part: alpha blocker for the mix row) Third-party VST3s blocked in the signed macOS build; AU editors missing | Ecosystem | plugin-parity.md | 10–15 |
| G-06 | (Record-to-disk part: alpha blocker for the tracking row) Sources decoded whole into RAM; recording into RAM | Performance | hardware-parity.md | 15–25 |
| G-07 | Nothing is compared against Pro Tools' output (no fidelity harness) | Features | this file | 20–30 |
| G-08 | Built-in plugin catalogue thin and unverified | Features | plugin-parity.md | 80–120 |
| G-09 | English-first UI with a pt-BR catalog (not native-reviewed); all fixed UI strings covered, no CJK/RTL rendering | Localization | localization-parity.md | 20–40 |
| G-10 | No control surfaces (HUI/MCU, EUCON) | Hardware | hardware-parity.md | 40–70 |
| G-11 | No external sync (MTC, LTC, MIDI clock, video reference) | Hardware | hardware-parity.md | 15–25 |
| G-12 | Immersive delivery: no Dolby Atmos/ADM BWF, MPEG-H, binaural | Features | file-format-parity.md | 50–80 |
| G-13 | Sidechain inputs, ARA, out-of-process plugin sandboxing | Ecosystem | plugin-parity.md | 30–50 |
| G-14 | Windows/Linux/Web exercised only lightly at runtime; no PR CI running the tests | Platforms / Stability | this file | 20–40 |
| G-15 | Elastic Audio depth: one algorithm, no Elastic Pitch | Features | target-app-parity.md | 30–45 |
| G-16 | Session templates, track presets, workspace browser, batch rename | Features | target-app-parity.md | 25–40 |
| G-17 | Video: HEVC/DNx decode, video export, external timecode | Features / Formats | file-format-parity.md | 30–50 |
| G-18 | Speech-to-text transcription | AI | this file | 30–50 |
| G-19 | UI feel: generic plugin windows, shortcut collisions, pro-grade meters and scaling | UI/UX | ui-parity.md | 60–100 |
| G-20 | MIDI/instrument depth: MIDI learn, notation editing | Features | target-app-parity.md | 40–60 |
| G-21 | Compressed export (MP3, AAC/M4A, Ogg/Opus) | File formats | file-format-parity.md | 10–20 |
| G-22 | Avid cloud services (collaboration, Sketch, Splice, sign-in) | Ecosystem | — | not estimated (owner decision) |
Details
G-01. Audio interface support
- Done (2026-10-12): Setup › Playback Engine chooses the audio system, output and input
device, sample rate and device buffer size (kept with the preferences, per machine;
ui.audio_devicefor agents); f32 and 16/32-bit integer devices; ASIO behind the opt-inasiobuild feature (verified on Windows with an SSL 2+ at 128 samples). - Done (2026-10-25):
setup.playback_engineandsetup.hardwareapplydevice(the output name) andbuffer_sizein the desktop app on the same path as the Playback Engine window (ui.audio_device) and return the open device.buffer_sizeis any integer 16..=8192 and is not rounded onto the window's power-of-two list. Headless (CLI, no app) still stores the request and returnsapplied: false, withbuffer_sizenull when unset; playback does not read those session values. - Missing: routing to physical channels (I/O Setup), one duplex stream on one clock (input and output are still separate cpal streams), latency reporting and record-offset compensation, ASIO in official builds (owner decision: Steinberg's SDK is proprietary or GPLv3), JACK, and verification on macOS and Linux. The mix still runs in fixed 512-sample blocks.
- Evidence: code above; Playback Engine window says "Mix block size: 512 samples"; issue #42 (no input device selection, forced monitoring feedback with virtual routing).
- Impact: blocks tracking with any multichannel interface; latency makes overdubs hard.
- Estimate: ≈ 25–40 h (device enumeration and selection, buffer size, duplex stream with one clock, ASIO feature build, per-channel I/O mapping into I/O Setup, latency reporting and record-offset compensation). Needs hands-on hardware testing.
G-02. MIDI devices
- Done (2026-10-12): MIDI input devices (
crates/playback/src/midi.rs,midir): 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. Controllers, pitch bend, aftertouch and program changes reach the instrument live. Notes are kept per device and channel, and a full input queue releases the notes of its device and marks the take incomplete. The device switches (Setup › Playback Engine, also opened by Setup › MIDI › MIDI Input Devices) are app preferences. User guide: midi-input.md. On Linux, live play was checked with a hardware keyboard (Akai MPK mini 3) and recording with a virtual one; not yet on macOS or Windows (type-checked only). - Missing: MIDI output (external synths, MIDI tracks without an instrument), MIDI clock/MTC
out, loop and merge recording (a MIDI take replaces what it covers; a loop pass piles every
pass into one clip), audition from the MIDI editor (
midi_editor.rs:288), MIDI input on FreeBSD and the web.setup.midi_input_devicesandsetup.midi_studiostill only store names in the session; the real device switches are app preferences. - Impact: you can play and record a keyboard, not drive hardware synths or sync other gear.
- Estimate: ≈ 12–22 h (output tracks and thru, clock out, merge/loop takes, controller path).
G-03. Session interchange with Pro Tools
- Missing: opening or saving
.ptx/.ptf, AAF and OMF import and export (#40), Media Composer–compatible sessions. Our session format is.scraftJSON. - Impact: a main-format requirement for beta. A Pro Tools user cannot bring a project in or hand one back; post-production (picture editors deliver AAF) is blocked.
- Estimate: AAF/OMF import + export ≈ 50–90 h (FilmCraft already writes AAF/OMF; we can learn
from it but not share code).
.ptxis proprietary and undocumented: owner decision on whether black-box format study is in the clean-room rules; not included in the estimate.
G-04. Correctness bugs in "done" features
Fixed (2026-10-19, #791): Float32 WAV and AIFF-C encoding retain finite samples above full scale. Whole-file and streaming tests cover both formats, integer clipping, and the existing NaN/infinity behavior. A bounce regression checks preserved headroom and file/report agreement with normalization off, then checks normalized output.
Fixed (2026-10-18): Mono device playback averages the stereo channels before output clipping, Fixed (2026-10-16): Master fader volume automation uses the first and last samples of each Fixed (2026-10-16): Aux, folder and master latency calculations now skip inserts already render block, matching track faders. A breakpoint at the next block no longer ramps the preceding block, and ramps reach their last-sample value. Regression tests cover nonzero render starts, one-sample callbacks and several block sizes. Since #1354, track and master volume automation is read at every sample, so its interior breakpoints no longer depend on the block; send levels and plugin parameters are still read once per block.
disabled for producing NaN or infinity. Subsequent blocks compensate only for healthy inserts; regression tests verify rendered impulse timing, retained healthy latency and reset/retry at 64- and 512-sample blocks, with audio tracks as the control.
instead of discarding the right side. Surround mixes average both sides of the ITU stereo fold-down. Regression tests cover right-only and left-only audio, equal and opposite-polarity channels, clipping order, centered mono tracks, each 5.1 channel and 1-, 37- and 512-frame callbacks. Fixed (2026-10-16): Split into Mono now gives each output track its own source channel, including surround channels, instead of repeating channel zero. Clip edits, source timestamps, Undo/Redo and save/reopen are covered by regression tests; missing or empty media fails atomically.
Open (2026-10-25): the Clip Looping dialog (#1030) has no option to crossfade the loops into each other, and its Number of Loops field stops at 512, while Loop Length and Loop Until End of Session or Next Clip make up to 1000 loops.
Open on 2026-10-10 (several have PRs open): editing #3, #5, #140, #144; clip/session #86 (PR #123), #88 (PR #130), #91 (PR #124), #92 (PR #132); automation #104 (PR #134); mix/bounce #59 (PR #131), #103 (PR #133), #152; playback #101 (PR #129); MIDI #87, #98 (PR #125); import #89 (PR #128); CLI #95, #96 (PR #126, #127); MCP #145 (PR #146); web #63, #64, #136; Clip List #4 (PR #75); plugin view #6; shortcuts #7, #41; launch #142; Linux #45, #107.
- Impact: each one is small, but together they say "presence is not parity": an outside contributor found seven in one sitting (#116–#122).
- Estimate: ≈ 25–40 h at 0.5–1.5 h each, plus review of the open PRs.
G-05. Plugin hosting on macOS
- Missing: the
com.apple.security.cs.disable-library-validationentitlement in the signed build, so hardened runtime refuses third-party VST3 bundles (#153, #149). AU editor views (crates/au-host/src/lib.rsheader: "Not hosted yet: Audio Unit editor views"). Embedded CLAP GUIs on macOS (#485). VST3 and embedded CLAP editors are hosted on Windows and Linux/X11. - Estimate: ≈ 10–15 h (entitlement ≈ 1 h; AU Cocoa views and embedded CLAP on macOS most of it).
G-06. Memory-bound media
- Missing: streaming sources from disk; recording to disk. Every source is decoded whole into
the
SourcePool; takes accumulate in RAM until stop (PR #84 open). - Impact: hour-long multitrack sessions and long takes exhaust memory; a crash during a long take loses it.
- Estimate: ≈ 15–25 h.
G-07. Fidelity harness against Pro Tools
- Missing: any measured comparison: null tests of bounces of the same material, fade curve
and pan-law checks, plugin frequency/dynamics responses, elastic-audio quality, automation
timing. Pro Tools is installed; it can be driven black-box with synthetic sessions (outputs kept
under
plan/, never committed). - Estimate: ≈ 20–30 h for the harness and the first 20 scored cases; turns many "≈" in target-app-parity.md into measurements.
G-08. Built-in plugins
See plugin-parity.md: 28 processors + 3 instruments against Pro Tools'
roughly 80 bundled processors and instruments; no fidelity checks; generic parameter UIs; EQ
parametric request #139. ≈ 80–120 h.
G-09. Localization
See localization-parity.md: a pt-BR catalog covers the menu labels and
every fixed UI string passed to text / localized_format! or localized inside a button, toggle or
close button (test-checked), including the Edit-window status bar, the remove-session question and
the send help text; engine errors are matched against catalog templates at display time by
error_text. What remains is independent native-speaker review plus egui's lack of complex-script
shaping and RTL, and the missing other Pro Tools languages; values built at run time (file, track
and device names) and engine command parameter documentation stay untranslated. egui has no
complex-script shaping or RTL; no CJK font fallback (PR #141 open). ≈ 70–110 h plus
native-speaker review.
G-10. Control surfaces
None: no HUI or Mackie Control, no EUCON (Avid-proprietary, needs Avid's SDK: owner decision), no generic MIDI controller mapping. Pro Tools users on S1/S3/S4/S6/Dock or HUI devices can't switch. ≈ 40–70 h for HUI/MCU plus a mapping layer; hardware needed to verify.
G-11. Sync
No MTC/LTC chase or generation, no MIDI Beat Clock (setup.midi_beat_clock stores a flag only),
no video reference or word clock awareness, no Satellite-style linking. ≈ 15–25 h after G-01/G-02.
G-12. Immersive delivery
No Dolby Atmos renderer integration, ADM BWF import/export, re-renders, binaural monitoring, MPEG-H (new in Pro Tools 2026.4), surround/object automation. ≈ 50–80 h; Dolby's renderer and SDKs are licensed, so we'd write our own ADM and object renderer.
G-13. Plugin ecosystem depth
No sidechain (key input) buses for any host; no ARA (Melodyne-style editing is a menu in Pro Tools); plugins run in-process, so a crashing plugin can take the session down. ≈ 30–50 h. AAX cannot be hosted (#109): Avid's AAX SDK licence and PACE signing; owner decision, likely never.
G-14. Platforms and CI
Only freebsd.yml and windows-arm64.yml run on pull requests, and only for manifest paths;
nothing runs cargo xtask ci on PRs. Windows and Linux have startup and rendering reports
(#41, #45, #107, #142). ≈ 20–40 h (a PR CI matrix plus runtime smoke tests on three OSes).
G-15. Elastic Audio depth
One warp algorithm; Pro Tools offers several per track (polyphonic, rhythmic, monophonic, varispeed, high-quality offline) plus Elastic Pitch and warp-marker editing depth. ≈ 30–45 h.
G-16. Session management
Session templates, track-preset recall UI and browser, workspace/sound browser with previews, batch rename (new in 2026.4), disk-usage and relink depth remain. Track-preset saves capture the current hosted-plugin state before writing (#661); recall UI, partial recall and preset browsing remain tracked in #639. ≈ 25–40 h.
G-17. Video and post
No HEVC, DNxHD/HR or AV1 decode; no bounce with video; no external timecode/9-pin; no iXML field-recorder conform. ≈ 30–50 h.
G-18. Speech-to-text
Pro Tools transcribes dialogue to a searchable transcript (upgraded in 2026.4). We have a settings command only. Needs an openly licensed local speech model. ≈ 30–50 h.
G-19. UI feel
See ui-parity.md. ≈ 60–100 h.
G-20. MIDI and instrument depth
MIDI learn, drum machine depth, notation editing (tuplets, lyrics, articulations, parts). ≈ 40–60 h.
G-21. Compressed export
Bounce writes WAV/BWF/RF64, AIFF and FLAC; Pro Tools also writes MP3 and AAC/M4A in Bounce Mix. ≈ 10–20 h (pure-Rust encoders).
G-22. Avid cloud services
Collaboration, cloud projects, Sketch, Splice, Learn, sign-in: 11 of the 30 menu leaves still missing. Out of scope unless the owner decides otherwise.
Revision history
| Date | Change | Summary |
|---|---|---|
| 2026-11-13 | trivial | G-09: the pt-BR catalog now covers tooltips localized inside buttons and toggles, the Edit-window status bar, the remove-session question, the send help text and engine errors shown in the status line; estimates unchanged |
| 2026-11-09 | trivial | G-08: 28 processors + 3 instruments with the Frequency Shifter |
| 2026-11-04 | trivial | G-04: track and master volume automation read at every sample, so breakpoints act on their own sample in any block size (#1354); estimates unchanged |
| 2026-10-30 | minor | G-05: VST3 and embedded CLAP editors on Linux/X11 (#527) |
| 2026-10-25 | trivial | G-04: Clip Looping (#1030) lacks the loop crossfade option, and Number of Loops stops at 512 while length and fill make up to 1000 loops |
| 2026-10-25 | trivial | G-01: setup.playback_engine and setup.hardware apply the device and buffer in the desktop app; headless returns applied: false |
| 2026-10-24 | trivial | G-08: 27 processors + 3 instruments, as the plugin registry holds; G-20: the sampler shipped (#108), so it is no longer listed as missing |
| 2026-10-19 | trivial | G-04: Float32 encoding retains finite headroom (#791); integer clipping and non-finite handling retained |
| 2026-10-18 | trivial | G-04: mono device stereo/surround fold-down fixed and regression-tested; estimates unchanged |
| 2026-10-16 | trivial | G-04: master volume automation block boundaries fixed and regression-tested; estimates unchanged |
| 2026-10-16 | trivial | G-04: failed aux/folder/master inserts excluded from latency compensation after containment; estimates unchanged |
| 2026-10-16 | trivial | G-04: Split into Mono channel preservation fixed and regression-tested; estimates unchanged |
| 2026-10-16 | minor | G-16: capture current hosted-plugin state before saving a track preset (#661); broader preset work remains (#639) |
| 2026-10-12 | minor | G-01 shrunk: audio device, rate and buffer choice; opt-in ASIO |
| 2026-10-12 | minor | G-02 shrunk: MIDI input devices, live play-through and MIDI recording landed; output, clock and loop/merge recording remain |
| 2026-10-10 | minor | Marked the alpha blockers (G-01, G-02, G-03; parts of G-05 and G-06) from the core-workflow gate |
| 2026-10-10 | major | Created from the full re-measure against Pro Tools Ultimate 2026.4.1: 22 ranked gaps with evidence and estimates |