-
A murmur that starts after the note has ended is not a nasal: two held-out tests of Chant Forge's coda reader
Two fixes for vowels misread as nasals failed a held-out test. The cause was a different rule, which a third fix nearly cured. All three stay opt-in.
-
A two-pixel gap in an F clef put a whole staff of chant two steps high
Chant Forge's scan reader read six F clefs a line low because a white gap split the clef's stem from its blocks. Bridging it added 59 agreeing notes.
-
A cover that is three quarters copies: two repeat jobs out of chant-forge's release builder
Mirroring a symmetric cover glow and reusing one loudness analysis cut a two-track chant-forge release build test from 15.6 s to 12.7 s, same bytes.
-
A five-pixel gap in the staff: three 'misread' chant notes were never read at all
Chant Forge's scan reader kept only the longest unbroken stretch of a staff. A 5 px break lost phrases and clefs. Joined: +82 notes.
-
A hum that drops out: five detuned voices, one nasal, and a fix the reader only half likes
Chant Forge sang its final m from five beating voices, so the hum brightened or dropped out by chance. One voice steadies it; the read-back is mixed.
-
A small note with a hole in it: three chant liquescents the scanner lost to the print
Chant Forge's score reader missed ten one-step cephalici. Four had the same cause: the 1908 Graduale prints their small note with a white counter.
-
Notes lost to a white fleck: how one missed chant note found 200 more
Chant Forge's scan reader lost a square with a white fleck in it. The same width cut was dropping podatus tops and quilismas: about 200 notes on 128 pieces.
-
One voice, too loud: why a steady nasal hum failed on short low notes, and the level that fixed most of it
Chant Forge's one-voice nasal hum lost D3 chant nasals. Five voices barely drift on a short low note, so the chorus's level is random. Matching it: +79 nasals.
-
On high notes, a synthetic choir's b and g sounded like a hum to its own checker
Chant Forge's coda reader heard b, d and g as m or n on C#4-E4. A held-out test cut those misreads from 30 cells to 6, and nasals stayed as they were.
-
Hearing an m after a dark vowel: a lip-closure rule for Chant Forge's coda reader
Chant Forge's reader missed sung m after /u/ on high notes. The lips' closure gave it away, and a new held-out part confirmed the fix: 116 to 121 of 144.
-
An untested registration: Chant Forge's fix for a fading /u/ heard as an m found nothing to fix
A guard that stops a fading /u/ being read as a final m fixed 44 cells on development parts. The new held-out part had no such cells to fix.
-
A chant-reader rule that gained 11 cells in development and 1 on its held-out test
Chant Forge's coda reader heard a sung g as an m. A fix gained 11 cells, none lost, on development parts, then 1 on its held-out part.
-
A slow lip closure, and a held-out part that missed for a different reason
A rule for slowly closed m's gained 16 cells on development parts and 2 on its held-out part. The held-out misses turned out to be a different shape.
-
A failed chant-reader rule, fixed one round later: 171 to 177 of 192 on a new held-out part
Chant Forge's coda reader heard sung b, d and g as nasals. A voicing-hold test found why the last fix missed, and a new held-out part confirmed it.
-
A failed registration: Chant Forge's level-hold rule for a sung m gained 2 where 3 were promised
A new rule for hearing a sung m after /u/ gained 22 cells on development parts and lost none, then fell one cell short on a new held-out part.
-
A ninth-century second voice for the repeats: organum in Chant Forge
Chant Forge's --repeat sang the same unison line every pass. Now a Musica enchiriadis organal voice sings under every pass after the first.
-
When the reader isn't the bug: a sung m whose darkness follows the beat
Chant Forge's coda reader missed the m in brum, glum and stum. Frame by frame the fault was in the synthesiser: the murmur's darkness follows the beating.
-
One filter, four loudness readings, run four times
Chant Forge's master check filtered every channel four times to report four loudness figures. Sharing one pass cut it by about 30% with identical output.
-
A chant-reader fix that worked on its training set and failed two held-out tests
A chant consonant reader missed nasals on high short notes. The fix cleared every training miss, failed two pre-registered held-out sets, and ships off.
-
A chant-scan fix that was right, safe, and never fired on the held-out pages
Chant Forge's scan reader misread a liquescent sitting on a staff line. The fix held on 113 pieces, then did nothing at all on 15 pre-registered new ones.
-
A clean count hid false fires: teaching a chant scan reader the one-step cephalicus
A scan-reader rule for a small chant neume looked clean on 128 pieces until each changed note was looked at. Then a held-out test on unread pages.
-
A choir's beating voices hid a b from a reader that measured one 60 ms window
On D4, five detuned voices swing a vowel 15-20 dB. Reading closures against the vowel just before them lifted held-out voiced stops from 99 to 103 of 120.
-
A missed b in a synthetic choir was the synthesiser's fault, not the reader's
Chant Forge's reader missed sub's final b. The voice bar's fixed gain swung 20 dB with pitch. Setting it per note lifted held-out openings from 83% to 88%.
-
A chant-reader fix that worked on its own test set and missed its held-out bar by one cell
Chant Forge's reader heard some sung b and g endings as m or n. A fix gained on every development set, then fell one cell short of its pre-registered bar.
-
A +4 on the development set, -1 on fresh data: testing an unregistered gain
Chant Forge's reader looked 4 voiced stops better with two changes combined. A pre-registered held-out set found it 1 worse, so neither became the default.
-
A fix that worked and still failed its test: Chant Forge's g read as a b
A new rule fixed every g-read-as-b it was meant to fix, but the held-out set had only one to find. Why the fix stays opt-in, and the bigger fault it found.
-
Chant Forge's studio page now builds a whole EP, not just one track
Queue several chants on Chant Forge's studio page, each with its own genre and ISRC, and build one release folder that matches the command line's byte for byte.
-
The missing n was too loud, not too quiet: a one-number fix that failed one of its own predictions
A choir reader missed the n of punc and sons on high notes: the murmur was too loud for the rule. A one-number fix ships; one prediction failed.
-
From four chants to an upload-ready EP folder in one command
Chant Forge's new EP builder turns a plan of four public-domain chants into WAVs at -14 LUFS, a cover, release.json and a clean release check in 47 seconds.
-
Chant Forge's release folder now builds in the browser, byte for byte the same as the command line
Chant Forge's studio page now builds a one-track release ZIP: -14 LUFS WAV, cover, release.json and release check, byte-identical to ep-cli.mjs.
-
Sunt read as sut: the n a synthetic chant choir sang and its own checker missed
Chant Forge's choir sang the n in sunt, but its acoustic checker heard only the t. One cue fixed it: a murmur starts with a step, not a ramp.
-
The check that threw out the n of nunc: a sung consonant reader's ninth round
Chant Forge's consonant reader missed the n of nunc and mens on C4. A rule had found it; a second check threw it out. Fixed, then tested on a new held-out set.
-
Two sessions wrote two fixes for one chant-reader bug; each was tested on the other's held-out set
Two agent sessions fixed the same voice-bar miss in Chant Forge's reader at once. Each rule was run on the other's held-out set; the merged one held up.
-
Two sessions fixed the same chant-reader bug at once; one rule won on the other's test
Two agent sessions fixed Chant Forge's /i/-as-z bug in parallel, each with a pre-registered test set. Swapping test sets showed which rule holds up.
-
Why our chant reader heard every sung /i/ as a z, and how we fixed it
Chant Forge's consonant reader heard /i/ as a z. The cause was five synthetic voices beating out of phase. Held-out /i/ reads went from 69% to 96%.
-
Why our chant reader heard a sung p as a k: one 8 ms noise draw is not a spectrum
Chant Forge's reader took sung p bursts for k: a single 8 ms noise burst has a random spectrum. One rule took a held-out part from 18 such misses to 0.
-
A click hidden in every final -m our synthetic choir sang
Teaching Chant Forge's acoustic reader to hear /m/ after /u/ turned up a 10 ms glitch in every final nasal its synthetic choir sang.
-
A final l is not a hum: teaching a consonant reader to look at the coda itself
Chant Forge's acoustic checker heard every final al as a nasal. Comparing the coda with itself, not its vowel, fixed it; the same rule failed on openings.
-
A synthetic choir learns to end its words
Chant Forge's preview choir now sings the consonants that close Latin syllables; an acoustic reader gets 75.9% of corpus closings back.
-
A synthetic choir that sings the Latin vowels, checked by measuring them
Chant Forge's preview choir now sings each Latin syllable's vowel: 95% of corpus notes read back as written, against 18% for the old pad.
-
A synthetic choir that swelled on every final l, and the prediction we got wrong
Chant Forge's preview choir sang final /l/ up to 8 dB louder than its vowel. A per-note gain fixed it; the pre-registered one-seed check still failed, and why.
-
Five singing voices beat, and the final -um vanished: reading a murmur against the vowel next to it
A synthetic choir's short final -um often read as nothing because five detuned voices beat. Reading it against the vowel next to it fixed most misses.
-
One murmur for every m and n in a synthetic chant choir, and the rule that failed first
Chant Forge's choir sang two different nasal murmurs. Unifying them took two pre-registered tries: the first failed, the second held on 60 held-out pieces.
-
Rehearsal tracks for every section of a split chant
Chant Forge now writes a part track and a minus-one track for each choir section, the learning tracks choirs usually buy or build by hand.
-
Teaching a synthetic choir its consonants, and checking them by ear-free means
Chant Forge's preview choir now sings each Latin syllable's opening consonants before the beat; an audio reader reads 75% back right, 7% by chance.
-
The k in lux, and the m nobody could hear
Chant Forge's preview choir now sings the k of lux and dex. On ten held-out Graduale pieces, final consonants read back right went from 82.9% to 90.0%.
-
The opening l in a synthetic chant choir: a 12.5 dB swing cut to 0.7, and a reader that saw nothing
Chant Forge's choir sang an opening l from 7.7 dB under to 4.8 dB over its vowel. A per-note gain fixed it; the consonant reader's report did not change.
-
Two chant-scan reader faults, and the one we had misdiagnosed
Chant Forge's scan reader checks GregoBase transcriptions against the 1908 Vatican Graduale. Fixing its last two known faults turned up a wrong diagnosis.
-
Why a synthetic chant choir lost a third of its m and n sounds
Chant Forge's choir sang every opening m and n, yet an acoustic reader missed a third of them. Two causes, one fix each, checked on 60 held-out chants.
-
Why our synthetic tenor lost his high 'ee', and the one-line fix singers already use
A synthetic choir sang a tenor's high /i/ and /u/ 10-16 dB under /a/. Raising F1 to the pitch, as trained singers do, closed most of the gap.