Sat Dec 07, 2019 12:59 am
Shot BRAW for a client that only edits in Premiere Pro. I told them to just edit it Resolve, they said no, so I told them to make proxy files and use those in Premiere, and they said no. Instead, they are stubbornly editing BRAW in latest Premiere 2020 with the v1.6 BRAW plugin. Ugh.
I expected problems and sure enough it's a complete trainwreck.
Playback and editing works, but the sequence will not render and will not export. Premiere Pro just hangs and throws up errors at every attempt to render or export. Their Mac has a decent 4-core i7 CPU, 16GB RAM and a 2GB discrete GPU. The timeline is just HD, so the computer should be able to handle it fine. I've tried exporting an XML and pulling it into a fresh project, but none of that worked. There's not a single effect on the timeline, this is just the first assembly cut and I can't get it to kick out a simple export. I cannot figure out what the problem is with it.
Deadline is approaching first the for assembly and client is not happy. I may have to take on the edit myself in Resolve, but I really don't have the time. It's a damn headache.
Anyone else had this issue in Premiere Pro with BRAW?
EDIT #1: In an effort to at least get an assembly edit out, I had the client export an XML and pulled that into Resolve. All of the clips are way out of sync relative to the original sequence. WTF?!?!
From what I'm seeing here, the entire workflow for BRAW outside of Resolve is completely broken. Granted, I don't expect anything but a mess from Premiere Pro, but I've read of people having success working with BRAW in Premiere Pro so I assume it must be possible. I can't imagine BMD would release a plugin that did not work at all. Any advice that anyone can provide would be much appreciated.
EDIT #2: New attempt to fix the issue, we rendered all the BRAW to ProResLT in Resolve. The in Premiere Pro offline the BRAW clips to relink them to the ProRes and all the clips in the sequence have shifted sync (not audio-video sync, they are literally as if they were all slipped in the timeline. This makes no sense as the ProResLT proxies have exactly the same timecode as the original BRAW files. We're going to have to start over completely and recut the assembly from scratch using the ProResLT Proxy files. How is anyone using BRAW in Premiere Pro at all for any normal workflow? It's a complete mess.
EDIT #3: I had the client uninstall v1.6 of the BRAW plugin and install the earlier version 1.5.2
At first that made the Premiere Pro project crash upon trying to do anything to a BRAW clip in the project. But, we were able to export an XML of the sequence and pull that into a fresh project and that, finally, would function and render and export. What a pain in the ass.
BMD really needs to look into fixing these issues with v1.6 of the BRAW plugin for Premiere Pro.
Last edited by
Jamie LeJeune on Mon Dec 09, 2019 6:29 am, edited 2 times in total.
www.cinedocs.com
http://www.imdb.com/name/nm4601572/