Avid has released Stream IO 2026.10 with a proof-of-concept connection that sends growing live-ingest media into Avid Content Core through the open Time-Addressable Media Store specification. As a feed arrives, Stream IO generates a proxy, writes it to TAMS and registers it in Content Core while the high-resolution recording remains on site. Editors can begin work before capture ends, and MediaCentral is no longer required in the middle of this specific ingest and registration path.

The technical significance is the separation of media access from one application stack. TAMS stores time-stamped segments behind an open API, so authorized tools can request a time range while recording continues. Avid says Content Core supplies the editorial context around those ranges, while Stream IO handles live ingest. The current connection is explicitly a first step and is available only as a proof of concept, not a generally available production feature.

The shipping 2026.10 release also broadens deployment choices. Avid lists newly certified Dell and Supermicro systems, tested AWS profiles for two, four and eight channels, DNxHR and XAVC-I UHD ingest and playout, DNx 4.0 encoding, and Functional Folders for automated file ingest. Stream IO Control Suite is in early access with centralized multi-server control beginning with multi-ISO recording.

Avid has not published production benchmarks for the TAMS path, supported third-party TAMS clients, commercial terms, availability dates or tested failure behaviour across sites. Scheduled ingest in Control Suite is also described as future work. Facilities should therefore distinguish the released Stream IO improvements from the proof-of-concept Content Core connection and validate latency, permissions, retention, failover and proxy-to-high-resolution relinking before planning an operational migration.