u/Nicolas-CrossFlow

I built a Premiere <-> Resolve converter and I need beta testers to try and break it

I built a Premiere <-> Resolve converter and I need beta testers to try and break it

XML/AAF/EDL lose a lot on the way to Resolve, so I wrote something that writes straight into Resolve: multicam, nests, merged clips, speed changes/time remapping, Warp Stabilizer, Clip Colors, markers and bin structure come across. Anything Resolve genuinely can't reproduce gets auto-transcoded via AME rather than silently dropped (AE comps, unsupported effects), and there's a "Return to Premiere" mode that brings the graded clips back.

Limitations: it needs Resolve Studio (the free version doesn't expose what's needed), it's beta, and there are rough edges I'd rather you find than a future user does.

MacOS and Windows, Free during beta: https://nablast.com

Note: I'm a post-production developer. I co-created BRAW Studio and PlumePack with Autokroma, and I'm launching now my own solo "CrossFlow" app.

u/Nicolas-CrossFlow — 8 days ago

Premiere <-> Resolve: what do you always end up rebuilding by hand?

I'm a post-production developer (one of the devs behind BRAW Studio/PlumePack; went solo this year with CrossFlow) and I'm digging into the Premiere <-> Resolve round-trip.

For those of you who send sequences to Resolve for grading (or receive them / work with both softwares) I'd like to know what actually breaks in practice. Not the theory, the "every damn time I have to redo X" stuff.

Specifically curious about:

  • What do you always have to rebuild manually after an XML/AAF/EDL? (speed ramps? multicam? adjustment layers? nests?)
  • How do you get graded footage back into Premiere, and how painful is it?
  • Roughly how long does a round-trip cost you on a typical project?
  • Have you just given up on some of it and started conforming a different way?

Happy to share back what I learn from the thread.

reddit.com
u/Nicolas-CrossFlow — 8 days ago