Anton Robsahm
Forum Replies Created
-
Thank you Jon.
Yes, OpenEXR files are supported in CC.
I will send in a bug report (or request maybe?). Hopefully if we are many enough they will consider it sooner rather than later.
I might try your workflow, right now i’m going through After Effects with DNxHD clips with the proper metadata for reference and replacing there and send it to Premiere. Goes quite fast, but much slower than if Premiere had a proper Conform for image sequences.
Best
Anton
-
Hello.
Great thread, i am currently working out a workflow on the same issue (with OPENExr files not DPX).
The AAF/XML (from Resolve) give out both timecode, frame count, file path, file name metadata but Premiere Pro does not read this properly and therefore won’t conform all clips.
When I link one sequence and check it out its no problem.So did you ever find a sollution to this? If so i’m very interested in hearing about it.
Anton
-
Update:
So i took my old EDL (from Baselight to the EXR files) into Resolve. It linked up great so I started exporting XML’s and AAF’s to use in Premiere Pro. The File Path now works, but Resolve changes the name on the source file in the XML EX: A101C002_151002_R6XY_[986975-987062].exr wich i understand is framecode of some sort.
I don’t know if it’s because of the framecount or whatever else but Premiere just dont want to link to the Filepath. Source material is on NAS server.
Is there a workaround for this in Resolve? Or maybe in Premiere?
-
Hello Jorn.
Thank you again.
The problem with Avid MC is that it don’t support OpenEXR, only DPX. I can transcode in Metafuze but it is gonna work against us.
I noticed after i linked up 5 EXR files from an EDL in Premiere manually and exported and XML – Import in a new project it linked with NO issue (wheras AAF didnt.) so yeah, XML is definately the way to go.I talked to the guy running the Baselight and he told me the list options are bad and an XML export is an update to send graded info back to Avid/Premiere etc. Are we missing a plugin or have just overshadowed an XML export in Baselight?
Anton
-
Update:
Tried to export a new AAF from Avid to Baselight. Then did a conform of a small amount of clips, made new EXR files and tried to update the AAF, wich Baselight didnt allow us to do.
We then tried a new EDL with the Source path definately in the EDL, still like you said Premiere wont even locate these files.A AAF right from avid gave us the path files.
-
Great explanation on Premiere’s media handling.
I just tried to link up two – three clips – put them on a timeline – export a new EDL – import EDL and the same issue persist. It wont link. And since you explained why I understand now. Thank you.My idea from here is to export an AAF/XML from Avid Media Composer to Blacklight, and from there make a updated AAF/XML to test in Premiere Pro. Would really love for this workflow to actually work! As i said we are in the experimental stage for this workflow still.
Thank you for your time.
-
Yes it is.
When I manually linked the files it worked just fine.
The only thing i stumbled on when i took a look at the EDL is that on earlier projects ive been on the folder path for alexa footage was in the EDL and in Avid under the “Tape” colomn. Ex: A003RIFT or similar (dont have acces right now unfortunatly.) On this project the folder name does not show up under Tape, instead its the filename EX: A001C001_000000_RIFT