Repository navigation
Showcase #3: Für Elise, sampled instruments and the music library's additions - #86
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
…no's sympathetic strings
A `.samples` file is a sampled instrument among a script's files: recordings and the zones that say
which keys and strengths each plays (SFZ's regions: trigger on attack, release or the pedal, volume,
amp_veltrack, ampeg_release, rt_decay, tune, keytrack, round robin, lorand/hirand). The recordings are
16-bit, coded without loss (four fixed predictors and Rice codes, a block of 4096 at a time): the
Salamander Grand Piano's 483 recordings, 16 layers, keys 28-91, cut to 10 s, are 125 MB of text where
plain 16-bit in base64 would be 787. A recording is decoded when a build first needs it; a check names
every clip made from one by its key (`storedClip`) without decoding.
scripts/make-samples.mts makes one from an SFZ instrument or a folder of recordings named by note
(--keys, --layers, --seconds, --octave, --detect, --pitch). `samples(zones)` makes one in a script from
clips it has. The hover and a small viewer say what one holds; the editor does not make them yet.
Clip gains `lufs` (ITU-R BS.1770-4, as libebur128 designs the K-weighting for any rate), `loudness(lufs)`
and `resonance({ pedal, amount, decay })`: a comb filter a string from A0 to E6, fed while the pedal is
down, damped in 0.1 s when it comes up. Nothing an existing clip does changes, so ENGINE stays "sound 3".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
`music.sampled(set, options)`: each note from the recording nearest its key (moved the few semitones to it, cut to what is heard before it is moved), and among those the one made at its strength; let go, it dies 60 dB over its release and the instrument's release zones play (a piano's damper and its strings settling, quieter the longer the key was held). Instruments may now `strike` a note at a velocity (a pattern's "@" chooses the recording, not only the gain) and play a performance's notes `together`: the sustain pedal holds what is let go and makes its own sound, a key struck again stops the sound before, and `resonance` rings the strings while the pedal is down. `music.perform(options, parts)` reads a score's notation a part at a time: lengths after "/" (dots, triplets), ties, rests, "@" velocities, ' staccato, ! accents, pp … ff and hairpins, "ped" and "*", and bar lines that are checked. A tempo map ([bar, bpm] points, changing evenly between them), holds and a seeded unevenness place every note in seconds. What comes back is the timeline a picture can follow: each note's time, end, key, velocity, part, chord voice, bar, beat and frame; bar starts; the pedal. `music.render` mixes a performance as it mixes a song (parts on one instrument played by it together) and takes `loudness`: LUFS the mix is brought to before the limiter. Songs whose instruments have no `strike` make the same clips as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
probes/lib/note-timeline.ts turns a performance's notes into what a map shows frame by frame, all when the script is built: notes on the game's clock (nearest frame, chords marked), the keyboard they need, a piano roll's cells at a frame (falling or rising, a row standing for some frames), and pictures turned into the changes from frame to frame. probes/lib/fur-elise-score.ts is our own transcription of Für Elise's A section from the public-domain score (bars 12-14 still to be checked against an edition) and a stormy D-minor passage of our own in the manner of the C section, played on a tempo that moves: downbeats a little long, bars marked to slow down. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
A 128 x 128 Space Platform map: a piano roll of Overlords on the minimap's Space (D2-E6, 40 rows, a row every two frames), and a stage on Platform the camera looks at, a keyboard of Flag-looking Spider Mines with notes falling onto it and a sync lamp (a start-location ring, white on every frame a note starts). probes/lib/fur-elise-run.ts lays the parts end to end (clicks, the A section, the storm, the theme as one clip and as a clip a bar, other looks), draws every frame's picture and flattens the changes into the tables the program reads. A Spider Mine is never asked for where it would overlap one of its frame or the frame before: the game would put it beside its place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
…f its frames probes/fur-elise-visual.ts plays the run back: a stand-in piano (an FM electric piano) rendered as one clip a part and, for S2, a clip a bar, each started on the frame its first note is drawn; per frame the clips, the text, the pixel changes (made, taken away, or handed to another player with Give Units, which recolours a unit where it stands) and the storm's effects. Parts: clicks with the lamp, the A section (falling a row a frame, then every other frame), the storm (red flashes and Disruption Webs, then explosions), the theme as one clip and as a clip a bar, then rising notes and the keys alone. About 100 seconds. In the lifted game every frame holds exactly the picture worked out (2,470 frames); at most 0.55 ms a frame by Remastered's weights; game-check finds nothing Remastered refuses or ignores. probes/lib/fur-elise-frames.mts draws chosen frames as PNGs from the same run, to look at before a play. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
What the probe draws and how, what the lifted game showed (a Spider Mine is never made overlapping another, and one taken away stands until its frame ends; Give Units recolours in place; 1.16.1 refuses a Disruption Web), its cost, what to measure from the recording, and the choices left for after the play. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
… before it `Clip.lufs` measured a clip of one channel as BS.1770 does, on one side: 3 dB under what the game plays (it plays one channel from both sides), so a mono render brought to −16 came out at −12.9. Measured from both sides now. A sampled note let go (no pedal) died over its release — a second on a piano — and a fast repeated note (Für Elise's E–D#) struck again 0.23 s later still had the one before 7 dB down under it. The release now ends a tenth of a second after the key is struck again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Five rendered items in a map, each announced: the old single-sample sampler on the grid, the Salamander grand on the grid, the A section played (tempo map, dynamics, Beethoven's pedal marks, sympathetic strings, a hall), the D minor storm with strings, horns, trombones, tuba and timpani, and the theme's last bars into the storm. The transcription (probes/lib/fur-elise-score.ts) is ours, from the Breitkopf & Härtel complete edition (1888, public domain); the orchestra's parts are our arrangement. The instruments are made from the sample libraries outside the repository by probes/lib/fur-elise-sound-gen.mts. Map 3.5 MB (five Oggs, 3.36 MB, quality 6), 3:46 a run; −17 LUFS for the piano items, −15 for the storm, true peaks under −1.4 dBTP decoded; the lifted game clean over 5,800 frames. The plan's S7 has what was built and what is open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
…section at a time
`music.excerpt(performance, from, to)` is the bars asked for as a performance of its own from 0, with
`at` where it begins: the notes struck in it, and the pedal — a pedal put down before it is down
already (a negative down), holding what it holds but making no sound of its own there, since the
excerpt before has it. Rendered apart, each section can have its room, its tail ringing under the next
when they are added up at their `at`s.
`together(parts, { lufs })` turns sections made apart up or down by one gain, so what they add up to
has that loudness and they stay as loud against one another as they were played. Without `lufs` it
makes the same clips (and names) as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The whole of WoO 59 from the 1888 Breitkopf scan, every repeat taken: the A section with both repeats, the F major episode (grace notes, the thirty-second passage twice), the theme again, the bar of drumming A and the storm, the arpeggios and the chromatic run (the 8va bar an octave up), the last theme and the held A. Bars 12 … 14 read again against the scan: the left hand's E4 → E5 over the bar line is a slur, not a tie (the probe had it tied). probes/fur-elise.ts plays it as the probe's item 3 was played, extended, and renders it a section at a time: A, the episode and the theme again in the smaller room, the storm and the closing in the hall, added up with their tails so the room changes where the storm comes in. One clip for the whole piece (3:33.4, −16.7 LUFS, −1.3 dBTP decoded, 4.2 MB), each section's clip with its tail as the fallback. probes/lib/fur-elise-timeline.ts is the timeline for the picture (1,340 notes with hand or part, the sections with their frames, bars, pedal), written by fur-elise-timeline-gen.mts from the build itself. The piano's samples now reach key 101: the arpeggios climb to E7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The sound probe's score (probes/lib/fur-elise-score.ts) is the score now; the visualizer probe keeps the notes it was played with, as probes/lib/fur-elise-probe-score.ts. The plan keeps both subsections. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
probes/lib/fur-elise-soundtrack.ts holds the whole piece's sound (take, sections, whole and the section clips) so that the showcase can import it without the soundtrack probe's own program; probes/fur-elise.ts imports and plays it as before. The same six clips by name, and the timeline made again from it is the same to the byte. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
A script whose files include a .samples, .sound or other media file could not run beside the game for its tests: the game host ran its modules again without the media, so the import failed. GameTestPayload.media carries them now and scripts/test-game.mts passes them. Found with the Für Elise showcase, whose soundtrack imports the piano's samples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The window of keys (or white keys) holding the most notes, white key to white key, and the rest moved in by octaves: a map has only so many columns for a keyboard. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Salamander's C4 regions name no pitch_keycenter; taken as their lowest key (B3) they played a semitone sharp on B3, C4 and C#4 — heard in the Für Elise soundtrack (C4 is struck 46 times). Measured on the render: B3/C4 +95/+96 cents before, -5/-5 after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
probes/fur-elise-showcase.ts (lobby "Für Elise") plays the whole soundtrack as one clip, started two frames before the picture's frame 0 (the probe measured the picture ~95 ms ahead), and plays back the picture worked out at build: notes falling onto a keyboard on both screens (the main screen a row every other frame), right hand gold, left cyan, the loud section's chords red with the white keys flashing red, explosions on its strongest downbeats; the other parts in violet on the minimap only. No sync lamp; a title line, an end line, then the game waits. probes/lib/fur-elise-showcase-run.ts takes everything from the timeline so that a new arrangement drops in: the hands (or the two busiest parts), drums kept off the rolls, both keyboards fitted with fitKeys, the loud sections by velocity, the explosions by the weight of each downbeat (for Für Elise: C1, C9 and C16, the bars the score accents). In the lifted game every one of the 5,180 frames holds the worked-out picture; 0.55 ms a frame at most; game-check finds nothing Remastered refuses or ignores. fur-elise-frames.mts --showcase draws its stills. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
How the showcase is built and why it is generic over the timeline, the choices for Für Elise as it is now (the key range, the orchestra on the minimap), what was checked and what turned up on the way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
scripts/tuning-check.mts measures a render against its timeline: for each pitch, the median cents of
its fundamental and second harmonic just after each onset (FFT, parabola), flagging a pitch more than
25 cents off (above C6 the piano's stretch allowed; under 200 Hz judged by the second harmonic, which
0.2 s can place). From the coordinator's script that found B3/C4/C#4 a semitone sharp. The straight
soundtrack, re-rendered: 60 pitches, none off.
scripts/samples-tuning.mts measures each pitched zone's recording of a .samples file against its key and
tune, flagging a zone whose fundamental and second harmonic are both off. The probe's instruments: none
off in the piano (with the stretch above C6), the string sections or the trombone; the horn's G2 zones
(+34 and −79 cents), the tuba's F1 (−39), the fifth timpani's ff (+40) and some timpani rolls are —
none of them in the notes the arrangements play.
make-samples --kit: percussion, a key a drum, from a JSON of name patterns; strengths read from "v3" or
ppp … fff in the names, the rest played in turn. `music.hits({ C2: clip, … })`: one-shots as a part of
a performance, each whole and unpitched at its velocity. Presets braam (a trailer's low blast), pulse
(a sixteenth ostinato) and sub.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
A clip from a .samples file was named by its own recording's bytes, so a change elsewhere in the instrument (another recording, a zone's root or strengths) left it the same name — and in the editor withSounds keeps a file whose name the map already has. Now each recording's key carries the instrument's identity too: a hash of its rate, its zones and every recording's hash, worked out once when the file is read from the coded bytes (nothing decoded). Change anything in an instrument and every clip made from it gets a new name. ENGINE stays "sound 3": only clips made from instruments are renamed, by their keys; nothing else is made differently. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
A trailer-score arrangement, 2:36.5 with the hall's tail: the theme's first phrase on the piano alone, free in time, a drone and a riser; the band in at 0:12.7 at 144 eighths a minute, felt in 6/8 (the theme, its repeat, the middle part); the F major episode as a lift and a build; the storm with everything as the climax; a breakdown over a pumping pad; the theme big; the band gone and the last bars on the piano alone. The piano is the lead throughout; around it VSCO strings, brass and timpani, a new VSCO percussion kit as taiko patterns, and synths made in the script (braam, sub, pads, pulses, supersaw, kick, impacts, risers). Rendered a section at a time in the hall, section faders, one gain to −14 LUFS, limited once: −14.0 LUFS, −1.4 dBTP decoded, the storm the loudest. probes/lib/fur-elise-cinematic-timeline.ts carries every part with its role, the sections with their frames and the big hits, for the picture; the straight timeline gained roles and hits too. The timeline generator takes --cinematic. tuning-check now calls a pitch off only when both readings agree (a chord neighbour moves one) and leaves pitches under 80 Hz unjudged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The plan keeps every subsection, the showcase's and the soundtrack's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
probes/lib/fur-elise-showcase-choice.ts picks the soundtrack: the cinematic arrangement by default, the straight piece with FUR_ELISE=straight under Node; the showcase plays that one clip and draws that timeline. The run reads ROLES: the piano's lead (gold) and accompaniment (cyan) on the keyboards, drums, cymbals, impacts and risers on no roll. The storm keeps the user's red chords and red flashes; in the big sections (the storm and the final) the rest of the band falls on the minimap in violet and the strongest low-drum hits pulse the minimap keyboard red; the intro and the ending show the piano alone, the main screen only the piano throughout. Explosions come from HITS: the impacts of strength 0.9 or more, 4 s apart (seven, Battlecruisers on the strongest); the straight piece, with none, keeps its accented downbeats. The run's tests cover both soundtracks. In the lifted game every frame holds the worked-out picture on both; at most 0.71 ms a frame. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The switch, the roles, what is bigger where the music is and what was left calm, the explosions' moments and why, the maps, the tuning and lifted-game checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
….sweep
`Clip.duck(key, { depth, threshold, attack, release })` turns a clip down by up to `depth` dB while
another sounds, in proportion to the key's level (followed, its louder side): the pads and chords under
a melody ducked by the melody itself, not only by the kick. `render(performance, { parts })` mixes only
the parts named — stems: the lead apart from what plays under it, to key the ducking and to measure it.
Presets trance (seven saws, a short glide into each note), arp (a pluck whose filter snaps shut) and
stab (supersaw chord hits); `music.sweep(seconds, { down })`, white noise through a sweeping lowpass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The melody and everything else rendered apart, the same mix at the same places, and for each bar where the melody plays (parts whose role is lead or lead-synth, from the timeline), how much louder it is than the rest in its own range: from 0.85 of its median note's fundamental to 5 kHz, energy over the bar in Hann-windowed FFT frames. Prints each section's lowest and median and the bars under --want (6 dB); exits 1 when a bar is under it. Made to hold the trance remix to "the melody first". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
…elody first The piano alone in 3/8 (bars 1 … 8, free), a sweep and a crash reversed, then a remix in 4/4 at 128: the theme reshaped as dance covers do (each 3/8 bar half a bar of 4/4, the turn as running sixteenths) on a trance lead over the piano; the F major episode as a breakdown; a build; the storm as the biggest drop (the drumming A as the bass, the diminished chords as stabs); the arpeggios and the run; the theme in full; then the last bars and the held A on the piano alone. 2:34.8. The melody first, measured: each section mixed as melody, harmony (dipped where the melody sits, ducked 6 dB by its envelope), effects (dipped, ducked) and rhythm, the ducking keyed from the whole melody so tails go down too. lead-check: all 75 bars with the melody at 6.9 dB or more over the rest in its range, medians 14 … 18 dB. −11.8 LUFS integrated, drops −10.8 … −11.1, the piano's ends −20; −1.3 dBTP decoded; the limiter at most 3.8 dB. Tuning: 41 pitches, none off. probes/lib/fur-elise-remix-timeline.ts puts the three performances together with roles, sections with a kind, DROPS and HITS; the timeline generator takes --remix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The plan keeps every subsection, the showcase's and the soundtrack's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
The switch has a third soundtrack, the remix, now the default (FUR_ELISE=cinematic or straight builds the others). A small LOOK per soundtrack says what the timeline does not: the storm section (the remix's drop 2), the big sections (its drops and builds) and the roles the main screen shows besides the piano (its stabs). Every "lead" part (the piano's right hand and the trance lead) is gold and drawn on top on both screens, the left hand cyan; in the drops and builds the stabs fall on the main screen in violet and the band on the minimap; the intro, breakdowns and ending show the piano alone. The storm's stab chords are red with the white keys flashing on each; the drops' downbeats and big impacts flash too and get the explosions, five Battlecruisers on the storm's. The cinematic and straight runs are unchanged. In the lifted game every frame of the remix holds the worked-out picture; 0.79 ms a frame at most. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Showcase #3: Für Elise, a piano that turns into a trance remix, drawn as falling notes on the minimap and the main screen. Video: https://www.youtube.com/watch?v=CFVdWwmngyw
The music library (
stdlib/music.ts,compiler/sound.ts,compiler/samples.ts):.samplesfiles. These are SFZ-like zones with velocity layers, release and pedal sounds, and sympathetic resonance, decoded lazily.scripts/make-samples.mtsmakes them from an SFZ or a percussion kit.music.sampledandmusic.perform: score-like note text with a tempo map, pedal and humanizing.music.excerpt,music.hits,music.sweep,together(parts, { lufs }), and the presets trance, arp, stab, pulse, sub and braam.Clip.lufs,Clip.loudness,Clip.resonance,Clip.duck.render(…, { parts }).scripts/tuning-check.mts(cents for each pitch),scripts/samples-tuning.mts, andscripts/lead-check.mts. The lead check requires the melody to stand ≥ 6 dB over the rest in its range in every bar.GameTestPayload.media, so the lifted game tests carry a map's sounds.The probes:
probes/fur-elise-showcase.ts, the showcase. It plays three soundtracks: the trance remix (the default), the cinematic arrangement, and the straight piece.probes/lib/fur-elise-score.ts)..samplesfiles are not committed.probes/lib/fur-elise-sound-gen.mtsmakes them from the Salamander Grand Piano V3 (CC BY 3.0) and VSCO 2 Community Edition (CC0).Checks:
tscis clean, and all 83 files and 1,468 tests pass.game-checkis clean.The plan's S7 section covers the measurements and the decisions behind them. The library additions reach the editor with the next TrigScript release. The editor can't import a
.samplesfile yet.🤖 Generated with Claude Code
https://claude.ai/code/session_01VEdp4UsAHvBRUfa1qAdsTV