Step 06: from my workflow, this step says to activate the Resolve Render Setting: "Render each clip with a unique filename"
- For Output options, activate "Render each clip with a unique filename"
For clarity about my workflow invention:
in my workflow step 6 specifically says to select "render each clip with a unique filename"
Here are the Resolve Render settings from my workflow for step 6:
Terry,
In theory an AAF from Resolve can be imported into an Avid Bin making a new sequence with links to the Resolve Rendered delivered mxf media files.
In theory, in my workflow, an Avid Media Database is imported into an Avid Bin. The original Avid sequence links to the Resolve delivered mxf media files.
Currently, unless newer Resolve version test results are different, I only recommend importing the Avid created media database into the Avid Bin to link to the Rendered delivered mxf media files that Resolve created. Specifically because DaVinci Resolve v9 thru v11, I have seen issues that upon importing Resolve created Generated New AAFs into the Avid Bin, the Avid user can be locked out of the Avid modify start timecode command for master clips, and I have also seen valid start timecode metadata get masked, and source icon names got masked upon importing a resolve generated new aaf instantly without prompting the user. I have also seen video corruption from resolve generated new AAFs imported into an avid bin under certain conditions with certain bins being opened or closed and or different projects and using one of those bins and importing the resolve generated new aaf. All of this happening automatic and instantly upon importing the Resolve generated new aaf into the Avid bin.
But none of those errors so far have been from my exact workflow as tested and retested importing the Avid created media database to link to the resolve created mxf media files and relinking to the original avid sequence. My workflow inventions come from my own test and test results, so I really put a lot of love into my workflows. So far I am getting 100 percent consistent reconform results after testing codec wrapper combo and making sure both boxes auto-assigning fps and timecode are an exact match!!! Every file makes the reconform, every time!!! And this is a computer so the workflow has become a calibration tool for finding potential problems and so far bringing clarity to any relinking situation. Terry, I am not seeing from my workflow consolidation errors of frames per second conversion errors as of yet!!!!
My workflow link above specifically is to keep the frames per second of the original Avid delivered mxf media file intact for the round-trip!!!
My workflow is metadata non-destructive and just using avid native commands, the only variable that I add into the Avid Bin is the "LINK" column name metadata as far as I can recall. And that too is from tests and "LINK" metadata for master clips is non-destructive-metadata. Adding "LINK" metadata is still keeping the current condition of the Master Clips left untouched. Avid custom columns are a great testing tool for me to preserve important metadata that is valuable to the media assets to retain their place in the Avid sequence and not get corrupt if possible, and can reconform, and are back-trackable to the original master source file / camera original if planned ahead. I really try to test everything I can think of!!!! And I am open to suggestions!!!
I have tested and retested a Resolve generated new AAF and importing into an Avid Bin.
The unique relationship set-up with the AAF is very similar to my "LINK"column avid relink approach in theory. In my round-trip workflow, it is possible, with planning to have almost like graphic reels to relink to with matching timecode of the Resolve Timeline to the Avid Sequence Type of planning to have different color correction at different places supported. So to have different color for artistic purposes could take this step added to my workflow and is possible.
or
Just like how the AAF works with unique extra structure for Avid, I could use "LINK" preplanning and render out a different batch from Resolve and relink to an Avid sub sequence could also be a choice too!!! Master Clips and a Sequence selected in the Avid Bin can be defined to make the reconform. It is that simple!!!
I am just thinking...
I am trying to figure out how best use these tools from tests! And in so I have attempted to help you guys and anyone else interested with Resolve and Avid reconforms. I am just presenting choices from my personal test results. And of course I recommend people test and retest to make sure they are getting the desired results.
I would love to support generated new AAFs from resolve to import into an Avid Bin, it is just version 9 to version 11 I do not support yet. I test them out and I am still importing the Avid media database and then relink to the original sequence for the reconform and so far have not seen any errors with the reconform round-trip as specified from my steps I present in the workflow!!!
and as of yet I do not support AAFs from Resolve into an Avid Bin.
I sent blackmagic steps to create an error that I can always recreate from Resolve v9-v12beta3 generated new AAFs imported into and Avid Bin and for the first time from my TEST 01: Resolve v12 beta4 passed that test 01. I am just saying I am doing my best to figure out how to support Resolve generated new aafs and an avid bin.
My Test 01 basically is: if the source icon metadata in the avid bin viewed in text mode is not a start timecode of 00:00:00:00 then importing a Resolve generated new aaf was making the master clip start timecode change to 00:00:00:00 upon import. This was absolute when the master clip in question was from importing a quicktime movie using the avid file menu import command and round-trip, and then importing a Resolve generated new aaf. This is at least what my test results were giving me. And I can create this error with Avid 6.5 thru 8.4 with resolve v9 thru v12beta3
Source icon metadata timecode avid assigns differently depending on ingest methods. That is something I have been researching for 20 years.
Hey Terry, by the way remember that Avid v8.1 batch-import with alpha-channel bug that I solved?
My solution was to batch import the source icon if the avid user did not have the original bin that imported the clip for online. That source icon has been giving me clues for years!!!!!!!!!!!!
I need more time to test and retest.
I love dialog on this subject so thank you guys so much for your time.
I would love to know what step in the workflow you guys can't get passed?
And what version of software hardware, so I can hopefully recreate the problems you are seeing Terry?
I love problems and would love to attempt to understand the problems you guys are having and maybe I can create a solution. Or at least try!!!!
I want everyone to have the best time using my workflows, so thank you for at least trying them.
It is just a choice, and I present choices.
- scott freeman
Posted by: scott_freeman_avid@yahoo.com
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (29) |
No comments:
Post a Comment