So you have an avid timeline that all the media is online and you export an aaf with it linked to media not embedded then when you import that aaf into Resolve 9 you have some of the sequence offline. Am I understanding this correctly so far? By "Orphaned Container Metadata" do you mean that there are clips in the media pool that don't have media linked to them. Are these clips that were generated automatically when importing the aaf or are they from populating the media pool with media before importing the aaf? Are the missing clips stills or some sort of media type that differs from the other clips that are working? I've notice things like stills a wonky including color bars. My guess for the stills is that Avid only generates one frame of media and then uses flags in Avid to let it appear to have a longer duration. When this media is imported into Resolves media pool there is only one valid frame of essence so the first frame of color bars is there but the rest of the say 30 second clip is black.
The solution of adding a suffix to the source icon name is done before exporting the aaf from Avid if I follow your proceedure. Fun stuff as always.
--- In Avid-L2@yahoogroups.com, "scott_freeman_avid" <scott_freeman_avid@...> wrote:
>
> well, I am getting closer with understanding this Resolve 9 timeline with orphan container metadata that will not link to essence (the media pool) in Resolve 9 using an AAF that was created when the metadata was not linking to essence (media offline messages in the Avid). It turns out that if you have clips that do not have a suffix in the name of the "Source" icon, then the above it true. I have discovered by adding a suffix to the "Source" icon name in the Avid before creating AAFs will avoid the Resolve 9 orphan container activity. I still need to figure out why "Source" icon names that do not contain a suffix exhibit this metadata that will not link to essence in Resolve 9 using an AAF.
>
> - scott freeman
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
No comments:
Post a Comment