Saturday, August 17, 2013

[Avid-L2] Re: "Source" icon missing suffix, AAF metadata wont linked to essence in Resolve 9

 

I'm confused if I have an avid sequence that has media offline in it I wouldn't expect an aaf exported from Avid to Resolve to suddenly find media that was offline in the first place in Avid. I do know that when I've got a sequence in Avid and I've linked all the Red Raw files through ama and linked the sequence to them by adding a tape name the resulting aaf from Avid to Resolve will link to the Red Raw files in Resolve without using Reel Names to assist. But if I haven't linked to ama the Red Raw and relinked the sequence in Avid the aaf won't work. This is a dicey pain in the arse because on the project I've been banging on the ama linked Red Epic Files would not automatically relink ama the next time the project was launched so each time I started the Avid Project I would have to manually relink by ama volume each of the Red Epic Raw volumes and go through all the Avid relinking steps to export an aaf to Resolve that would know to link to the Red Raw files.

Also when you add a suffix what kind of suffix do you add? Is it like a .new01 thing or something completely different?

--- In Avid-L2@yahoogroups.com, "scott_freeman_avid" <scott_freeman_avid@...> wrote:
>
> The DaVinci Resolve 9 exhibits a non-working linking situation.
>
> If you have an Avid with "Media Offline" messages and you then export an AAF with "Source" icons that do not have a suffix in their name. The AAF is useless. This AAF will never link to the media pool.
>
>
> I am so happy to discover this so I can have complete control over my AAF export and Resolve 9. I suspect this is a Resolve 9 issue only.
>
> - scott freeman
> (818) 657-9490
> I love this stuff
>
> --- In Avid-L2@yahoogroups.com, "johnrobmoore" <bigfish@> wrote:
> >
> > 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 (4)
Recent Activity:
Search the official Complete Avid-L archives at:   http://archives.bengrosser.com/avid/
.

__,_._,___

No comments:

Post a Comment