Importing ATEM Mini Pro ISO Resolve-Compatible XML files into Vegas

RedRob-CandlelightProdctns wrote on 10/16/2021, 5:50 PM

The ATEM Mini Pro ISO units create resolve XML files during a live stream, containing all media, all cuts and cross-fades.

The idea is that post-switch, a producer may want to fix a few "bad cuts", add titles or overlays that didn't make it into the live show, etc. The individual camera recordings (ISO 70mbps .MP4), cuts and cross-fades can instantly load up on the Davinci Resolve timeline by loading that XML... make a few tweaks and changes and re-render. Super-efficient workflow!

Has anyone here come up with or seen a way to import that resolve XML file into Vegas so that ATEM set of recordings could be efficiently edited in Vegas instead of Resolve?

In my perfect world, the resulting .VEG project would look like a multi-cam Vegas project after the multi-cam track was created

The single multi-cam track would be up top
The event would contain multiple takes, each take one being one camera
The track have cuts and cross-fades matching what was in the XML file, with the appropriate take selected in each event to match the live switch
The PGM recording's audio would be on the audio track beneath the MC track
Individual audio tracks would remain underneath that master MC track, so they could be re-edited easily if desired

OR.... :

Individual ISO recordings would be loaded on the timeline
Markers would be created to correspond to the cuts and cross-fades in the XML file. They would use @jetdv-Excaliber-compatible syntax, so after adjustments are made to the edit, Excaliber could be run to build the new master track

Comments

jetdv wrote on 10/17/2021, 7:24 AM

@RedRob-CandlelightProdctns, Have you also looked at VEGAS Stream? That basically does the same thing you are referencing here. You capture a stream and all camera switches are saved (as well as all titles and many other things that can also be modified afterwards). You can then use the "Import from VEGAS Stream" script to do exactly what you are saying.

I would think the best option would be to write a script that reads through the ATEM XML file and imports the project creating the tracks as needed.

RedRob-CandlelightProdctns wrote on 10/17/2021, 8:30 AM

I've looked briefly at Vegas Stream hoping I could use it for overlays and titles. Unfortunately that won't work if we want to use the hardware ATEM Mini Extreme for our switches. Using Vegas Stream to switch 5-8 cameras would need a capture card with 8 HDMI inputs, or 8 generic USB capture devices (with 8 ports).. not what I have right now, but I would consider if I knew it was portable and rock solid. The point of this post wasn't to argue hardware vs software switches and streamers. 🙄

For now, me and the thousands (10's of thousands?) of ATEM users could benefit from a Vegas resolve import that could ingest these ATEM Mini ISO files.

Does none presently exist?

RedRob-CandlelightProdctns wrote on 11/4/2021, 4:55 PM

UPDATE: I'm coding this script :-) Feels soooo good to be coding again! So far the script is creating individual tracks for each ISO recording, and a MC track with takes.

Next up -- I'm planning to

create track envelopes on the individual tracks corresponding to the cuts and cross-fades in the ATEM file. (it seems to be a JSON formatted file.. I've got the objects classes all setup.. yay!).
create similar cuts/cross-fades on the MC track to match what was done
add support for media-player content
After that's all done, I'm going to look at partial cross-fade support -- that is, when someone begins a transition on the ATEM but stops it part-way through (think event opacity is not at 0 or 100%).

For MY workflow -- 99% of the time we will take the recorded program-mix on the top track, and simply apply a few fixes where a bad switch occurred (or we missed an entrance, etc). For that workflow, just having the PGM track and MC track (to quickly see other options for a fix) will work. Trying to think of a good way to record "markers" during the live switch to note the spots which we need to go back and look at. Currently it looks like the ATEM only writes to its XML/JSON file when a change occurs (or the beginning setup line).

fr0sty wrote on 11/4/2021, 6:48 PM

So you're writing a VEGAS Script to import the ISOs? Could be a profitable thing to offer to the ATEM community for a small fee if so.

RedRob-CandlelightProdctns wrote on 11/4/2021, 7:17 PM

Perhaps.. the ISO import/setup part is done.. the rest which imports all the edits is still being worked on. I'm definitely offering it up to the ATEM community.. not sure about how I might charge a fee... perhaps the ol' "if you like this, we happily accept donations" thang

Alex-Pitel wrote on 11/6/2021, 4:58 AM

Many of us will hope that you'll make it! Wish you good luck in this hard job and waiting for a script 😀👍