|
← 判断力与美学 ← Judgment & Aesthetics
SAE 判断力与美学 · 余项之美
SAE Judgment & Aesthetics · Beauty of the Remainder
2026-07-20

Void LinkAudio:去掉中心之后,剩下来的是什么

Void LinkAudio: What Remains When the Hub Is Gone

Han Qin (秦汉)

Julien Bayle(Structure Void),认证Ableton讲师,电子音乐人,开发者。2026年5月3日,他在CDM上发布VOID LinkAudio v0.2.0,比Ableton官方Live 12.4早两天。这个开源套件的核心是一件在技术上很小但在结构上很大的事:让Max/MSP、Pure Data、VCV Rack、TouchDesigner、openFrameworks和VST/AU/CLAP插件在局域网上直接交换音频——无需驱动程序,无需BlackHole,无需JACK,采样精确,节拍锁定,自动重连。Ableton Link Audio是底层协议:把节拍/速度同步(已在移动应用和硬件中广泛实现)扩展为可以在P2P节点之间传输音频流。Bayle建立的,是这个协议在几乎所有主流创意工具中的首批实现。

宿主制(host paradigm)是数字音频三十年的沉积层。一切音频经过一个中心——DAW——插件和乐器作为节点挂载其上。即便艺术家同时运行多个工具——Live、Max、TouchDesigner、VCV Rack——工具之间的音频路由仍须经过操作系统的虚拟音频驱动(BlackHole、Loopback、Soundflower)这个代理层。代理层本身是宿主制的延续:用一个OS级中心替代了DAW级中心,结构未变。这是已构(已构 = 被凿-构循环充分沉积、不再作为余项存在的结构)。Link Audio在协议层切断了这条代理链:工具与工具直接建立音频对等关系,不再经过任何中心。余项浮出:工具边界本身——当VCV Rack的模块信号越过边界进入TouchDesigner的视觉处理环境,再越过边界进入Max的算法空间——每一次跨越都是一次创作事件。这片"工具之间"的地带,因宿主制从未允许它作为材料存在,从未被命名。

需要区分已构中的两个命名对象,以看清余项的轮廓。Dante和AVB是专业广播网络音频:有专用网络基础设施,以关闭实验性为代价换取稳定性;是已构,命名完整。JACK over network(NetJack)更接近创意使用,但依赖驱动架构和专业OS配置;也是已构,在技术社区中已被充分理解。Link Audio既不是Dante也不是NetJack。它运行在Ableton Link的P2P会话协议之上——一个为"在同一房间的工具之间实时同步"设计的协议——在其上添加音频流。代价是范围约束(局域网、特定拓扑);这个约束恰好界定了它的领地:创意工具组成的即兴网络,以创作决策而非专业广播惯例为路由逻辑。Kirn写道Link Audio"填补了JACK与Dante之间的某片领地"——这个表述是命名缺口的精确形状:两个负片夹出一个轮廓,轮廓本身还没有名字。

为什么现在看比以后看更重要?Ableton Live 12.4已于2026年5月5日正式发布,Link Audio在官方生态中确立。从这个时刻起,最自然的使用模式变得显而易见:所有工具向Live发送音频,或从Live接收。宿主制以新的形式归来——不是DAW作为插件宿主,而是DAW作为网络音频的引力中心。Bayle的工作比Live 12.4早两天发布,恰在这个归来之前揭示了工具边界地带:当没有任何中心时,路由图本身——哪个工具发送给哪个,以何种拓扑——成为创作参数,类似于模块合成器中patch cables图谱的地位。拓扑是乐器。一旦Live成为网络引力中心,路由图便失去这个自由度,退回到已构:工具围绕Live,余项再次消失于基础设施。

v0.3.0已添加Linux支持——VCV Rack for Linux、Pure Data for Linux均已可运行(x86_64和ARM64)。Cycling '74论坛、Pure Data论坛、KVR Audio上的帖子在问如何实际使用这个设置。没有人用同一个词称呼它。Bayle说:"架构、音频路径、线程模型、DSP决策都是我的。"他凿的不是代码,他凿的是一个习惯了宿主制的社区对工具边界的想象力。代码库是MIT协议,Gumroad页面是pay-what-you-want。这片领地是开放的,实践在增长,名字还没有。工具边界区、创意对等网络、作为乐谱的路由图——这些仍然未被命名,而未被命名,是它们作为余项存在的条件。

structure-void.com ↗

Julien Bayle (Structure Void) — Ableton Certified Trainer, electronic musician, developer — released VOID LinkAudio v0.2.0 on May 3, 2026, two days before Ableton shipped Live 12.4. The project is an open-source multi-host implementation of Ableton Link Audio: a lightweight peer-to-peer audio routing protocol over local networks. No drivers. No BlackHole. No JACK. Audio streams sample-accurately between Max/MSP, Pure Data, VCV Rack, TouchDesigner, openFrameworks, and VST/AU/CLAP plugins — any tools on the same local network can publish and subscribe to audio channels, beat-synced, auto-reconnecting. The underlying protocol is Ableton Link Audio, which extends the existing Link tempo-sync layer (already embedded in iOS apps and hardware) to carry audio buffers between peers. Bayle built the first public implementations of this protocol across nearly every major creative tool.

The host paradigm is thirty years of sediment. All audio flows through a central DAW; instruments and effects hang as nodes on its star topology. Even when artists run multiple tools simultaneously — Live alongside Max alongside TouchDesigner alongside VCV Rack — the audio routing between those tools still passes through the OS's virtual audio driver layer (BlackHole, Loopback, Soundflower) as a proxy. That proxy is structurally identical to the hub: a system-level center replacing the DAW-level center, the topology unchanged. This is already-construct (already-construct: a structure so sedimented by the chisel-construct cycle that it no longer exists as a remainder — it is simply given). Link Audio severs the proxy at the protocol layer. Tools become audio peers, no center required. And what surfaces? The boundary between applications itself — the zone where VCV Rack's modular signal crosses into TouchDesigner's visual processing environment and then into Max's algorithmic space. Each crossing is a compositional event. This between-tools territory has always existed (artists have always run multiple tools simultaneously) but it has never been material, because the hub always made the boundary invisible infrastructure rather than creative content.

Two named constructs in the same space help define the remainder's outline. Dante and AVB are professional broadcast network audio: dedicated infrastructure, stability at the cost of experimental closure — fully named, fully construct. JACK over network (NetJack) is closer to creative use but requires driver architecture and professional OS configuration — also named, fully digested in technical communities. Link Audio is neither. It runs on Ableton Link's existing P2P session protocol — designed for "tools in the same room, syncing in real time" — and adds audio streams on top. The constraint (local network only, specific topology) is precisely what defines the territory: a creative tool ensemble routing audio by compositional decision, not broadcast convention. Kirn writes that Link Audio "fits some territory in between" JACK and Dante. That phrasing is the exact shape of the naming gap: the silhouette between two negations, the silhouette itself still without a name.

Why does seeing it now matter more than later? Ableton Live 12.4 shipped May 5, 2026, officially establishing Link Audio inside the Live ecosystem. From that moment, the most natural usage pattern became obvious: all tools send audio to Live, or receive from Live. The hub returns — not as plugin host, but as the gravitational center of the audio network. Bayle's work, released two days before Live 12.4, made the peer topology visible at the exact moment before Live recaptured the center. Without any gravitational center, the routing graph itself — which tool sends to which, in what configuration — briefly became a compositional parameter, analogous to the patch-cable diagram in modular synthesis. The graph was the instrument. Once Live becomes the network's center, that freedom collapses: tools orbit Live, the routing graph reverts to administrative decision, the remainder disappears back into infrastructure.

v0.3.0 landed Linux support — VCV Rack and Pure Data on Linux, both x86_64 and ARM64, with the same Link Audio integration. Threads at Cycling '74, the Pure Data forum, and KVR Audio are working out how to use this setup in practice. No one calls it by the same name twice. Bayle says: "The architecture, audio path, threading model, and DSP decisions are mine." He built an implementation, not just a wrapper. The repository is MIT-licensed; the Gumroad listing is pay-what-you-want. The territory is open, practice is accumulating, a name has not arrived. The tool-boundary zone, the creative peer network, the routing topology as musical score — these remain unnamed. And remaining unnamed is the condition of their being alive as remainder.

structure-void.com ↗