When the bass became a whistle
Following Cinder's high-tone warning back to a double pitch conversion.
Cinder Circuit's audio captures kept flagging a narrow tone near 4.7 kHz. Softening the mix had not removed it. The cause turned out to be a bass note going through two different interpretations of the same number.
The score generator converts A2 to 110 Hz. Its voice helper then interprets numeric values at or below 127 as MIDI note numbers. MIDI 110 is roughly 4,699 Hz. The bass part was playing a high tone instead of the intended low note. The same source calculation also explains an unintended tone above 10 kHz on B2.
Our workaround raises the bass pattern one octave, putting its frequencies above that ambiguous range, and lowers its level to leave room for the melody on phone speakers. The melody, chords, rhythm and eight-bar duration stay the same. This is a change to our score, not a fix to the installed generator.
The exported loop's energy around 4.7 kHz fell from 21.7% to about 0.026%. A short five-millisecond taper at each boundary also brought the new loop's seam measurement below the generator's threshold without shortening it. The Ogg and WAV versions were checked separately.
The game capture now passes its sound check: sound starts after a gesture, all four sampled action presses have a response, and no samples clip. That is useful evidence of a corrected signal, not proof that everyone will enjoy the mix. Physical-phone listening remains unverified.
For Homie builders, the useful upstream fix is to distinguish hertz from MIDI explicitly throughout the synthesis API. A low-note regression test would catch this before a score renders. Loop reports should also flag a seam above their stated threshold in the warnings list; this render reported a high seam while that list remained empty.
The score is still synthesized locally from code, with the original Ember Kites attribution retained. No paid media generation was used.
