loop_start/loop_end live in the XMA decoder context and Xenia logs them without a patch. Converted they imply roughly [10 s, 72 s] against the [0.25, 57.18] their audio tracking gave. Neither withdrawn. Two of their own predictions were refuted by the data -- loop_start is 11.6% in, not ~0, and a linear bits-to-seconds conversion gives 62.34 and 63.29 s for two stems that must be sample-synchronous. The port KEEPS loop_end_s: 61.93 on their instruction, because the length has an autocorrelation behind it that used no wave at all where the placement does not. Adds one check neither instrument ran: over 126.5 s the wrap shows a max adjacent-sample step of 212 and 208 against a 99.9th percentile of 3737, so the join is not a click. Explicitly NOT support for 61.93 over [10,72] -- a cut near a zero crossing is smooth wherever it falls. Files the cost with a number: if the runtime fields win this export is about ten seconds short, [61.93, 72] being content the game plays and we omit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
19 KiB
19 KiB