Measured on 240 s parked on the real menu: no seam at all (zero runs >=0.3 s
below median-18 dB in 232 s), and the loop is at 61.93 s, not the summed wave's
87.744 s length. Two instruments agree -- top correlation lag 61.909 s with
r=-0.009 at 87.750, and slice location showing playback wrap at 61.93 three
times. The final ~25.8 s, the fade-out and trailing silence, is never played.
This port had authored loop: restart, measured the resulting 3.4 s of
near-silence off its own Master bus, and reported it as the price of the missing
loop point -- in BLOCKED and in a message to the Decoder. The measurement was
correct and the attribution was wrong. Second time this fortnight I have measured
something real and assigned it to the wrong side.
Godot loops whole files, so the loop region has to BE the file: BgmSpec gains
loop_end_s and the bed is trimmed to 61.930 s. Verified over 131 s on the port's
own bus -- 5 near-silent windows, no run >=0.2 s, against 36 windows and 3.4 s.
Also records their withdrawal of '8 of 10 three-chunk regions': that audit file
was truncated mid-list with no summary line, so the multichannel-specificity
claim is unsupported and my 25 stands.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
93b823eedf