Eddie AI v4 Unveiled – Native Premiere and Resolve Projects, Avid Extension, and C2PA Signing

Software News

by Johnnie BehiriSeptember 9^th, 2026

Subscribe to News - Software

Eddie AI has bundled a summer of releases into a single version number and given it a launch slot at IBC 2026. Version 4 folds the pay-as-you-go pricing, chat-driven editing, and iPhone app we covered last month into one package, then adds what a post department needs before it can say yes: native NLE project files, an Avid extension, compliance certifications, signed provenance, and an option to run the whole thing on your own hardware. It is the first Eddie AI release where the handoff, not the rough cut, is the headline.

The company describes v4 as “ten times the Eddie you knew,” which is marketing shorthand rather than a measurable claim, but the scope of the release is real. Eddie AI now writes a native .prproj for Premiere Pro and a native .drp for DaVinci Resolve, ships an extension for Avid Media Composer, delivers assemblies into Premiere Pro Productions and into a Resolve project hosted on Blackmagic Cloud, and round-trips FCPXML with multicam and compound clips intact. On the compliance side it is SOC 2 Type II certified, GDPR compliant with a Data Processing Addendum ready to sign, HIPAA compliant, signs its exports with C2PA content credentials, and can be deployed on a facility’s own hardware. Underneath sits EddieEditor1-9B, the in-house editing model whose 47% win rate against Kimi K3 we reported in August, now presented as a shipping component rather than a research result. Eddie AI will show all of it at IBC 2026 in Amsterdam, September 11 to 14, at booth 7.A38 in Hall 7.

The handoff is the product now

Every earlier Eddie AI release we have covered, from Night Shift to Dirty Multicam support, ended the same way: the assistant produced a timeline and an editor opened it somewhere else. Version 4 concentrates on how clean that opening is. According to the company, the .prproj it writes lands with the multicam sequence already built, and the .drp arrives with bins, timeline, angles, and source timecode in place, so a Resolve editor is not reconstructing the project from an XML that lost half its metadata on the way in.

The Avid extension is the notable addition for broadcast rooms, which have watched most AI assistant tools skip Media Composer entirely. Eddie AI says an Avid suite now gets the same handoff as Premiere Pro and Resolve users. For Adobe shops running Productions, the assembly is delivered straight into the Production with media placed, and for Blackmagic Cloud users, Eddie AI builds bins, selects reels, markers, and organized b-roll inside the team’s existing cloud Resolve project rather than exporting a separate one.

Two smaller details will matter more in daily use than the format list. Exports reference the original camera files rather than Eddie AI’s proxies, so a project should open without offline media. And any angle switch made inside Eddie AI survives the NLE export, which was the limitation that made earlier multicam handoffs feel like a starting point rather than a first pass. For anyone who would rather skip the NLE altogether, the system still renders an MP4 up to an hour long, with audio stems, alpha graphics tracks, and footage logs as CSV, Word, or PDF.

Compliance for the rooms that could not use it before

Eddie AI has been fairly candid about who was locked out until now. SOC 2 Type II certification is the one that unblocks procurement at broadcasters and larger agencies, and the company says teams that could not approve it before now can. HIPAA compliance opens clinical and medical production, a category that could not touch a cloud editing tool at all. GDPR compliance with a signable DPA covers European clients, and the company maintains a public trust center for the security questionnaire that tends to arrive before the footage does.

C2PA is the more interesting inclusion for this audience. Eddie AI signs its output with content credentials, so a broadcaster can verify where the source footage came from and what was done to it in the assembly. Given that v4 also generates b-roll, music, voiceover, and dubbing on demand, a provenance record that distinguishes captured material from generated material is not a nice-to-have. It is the thing that lets a compliance department say yes to a tool that can manufacture shots. How granular that record is in practice, and whether downstream systems read it, is something any broadcaster evaluating the tool should establish for their own delivery chain.

The on-premises option closes the loop the 9B model opened. When Eddie AI published its research on EddieEditor1-9B, the point was that a model small enough to run on a single GPU could keep footage and editorial knowledge inside the building. Version 4 turns that into a deployment offer for facilities whose material cannot leave the premises, though the company has not published pricing or hardware requirements for it.

Multicam that knows who is on camera

The multicam workflow gets the most practical upgrade in the release. Drop in the camera files and Eddie AI groups and syncs them by audio or timecode, then cuts to the sound recorder’s dual-system audio rather than the camera scratch track. New in v4 is face-based angle labeling: the system identifies who is on which camera and names the angles accordingly, so a podcast producer can tell it to cut to “Sarah” rather than to “A002”. Combined with the angle switching that now carries through to the NLE, this is the closest the tool has come to a finished multicam podcast assembly rather than a suggested one.

Footage support has broadened to match the rooms the compliance work is courting. Eddie AI now ingests BRAW, R3D including spanned clips, MXF, Nikon N-RAW, stills, and audio-only files, and pulls from Google Drive, Dropbox, Frame.io, iconik, LucidLink, and YouTube by picker or pasted link. It can also open a Premiere Pro project directly, pick from a Resolve media pool, or take an FCPXML. If an individual file fails to import, the system reports which one and why, and lets you retry that file alone instead of restarting the batch.

Teaching the assistant your house style

The customization layer builds on the backgrounder documents introduced in May. You can attach a script, a paper edit, brand guidelines, reference faces, or a reference video, and Eddie AI edits with those in hand. Brand fonts and colors are set once and applied to every title and graphic. Word-level captions with karaoke highlighting are rendered identically in the preview, the MP4, and the NLE, and vertical reframes follow faces rather than center-cropping.

Editor agents are the new idea here. You build an editor with its own style and skills, run it, and can publish it to a marketplace, or install one built by someone else; Eddie AI has published five director agents of its own to seed it. Recipes save a repeated workflow for one-click reuse, and length control lets you specify a target duration that the assistant respects, with every version saved and recoverable.

What was already announced, and what is still missing

Much of the v4 sheet is a consolidation of the August overhaul: the credit-only pricing with no monthly fee, the MCP server that lets Claude and ChatGPT drive an edit, the iPhone app, cloud workspaces with frame-accurate comments, Slack and Microsoft Teams integration, enterprise SSO, and the generative music, voiceover, dubbing, and b-roll tools. Those are covered in that article and have not changed here beyond the version label.

What Eddie AI has not published is any pricing for the on-premises deployment, any credit cost for the new export paths, or a release date for the Avid extension and the Blackmagic Cloud integration beyond their appearance at IBC. The company’s own IBC preview also promises a launch at the show that it has not named, so v4 may not be the last word from booth 7.A38.

Would a native project file with multicam intact and C2PA on every export change how your post pipeline treats AI? Don’t hesitate to let us know in the comments below!