In tests I did with bars a while back when prores started being supported in Avid if I brought something in prores and exported prores all was well. Same with DNX in and out. When ever I tried to cross the codec streams there would be a slight shift in the gamma area as many others have notice for years. The assumption was those codec converting exports were using the flawed QT Engine. Since my tests a while ago I've heard others say if you transcoded the media from prores to dnx in Avid or dnx to prores in Avid you could then export a same as source and the levels would not get shifted. I've never tried to confirm or deny that myself. My gut tells me anytime you don't stay with a prores import for a prores output or the same with dnx you are likely to see the slight gamma shift. I may be wrong but that's what I always seen when I tested this stuff.
--- In Avid-L2@yahoogroups.com, John Moore <bigfish@...> wrote:
>
> I have an hour show with a lot of layered nests in nests that had to be broken up in offline into 3 parts. In online I was able to make two parts in separate bins after combining the separate parts from offline. With the full sequence I got an error something like, "Too Many Items too big to save." Breaking it in two parts in separate bins I could save etc... There are also a lot of Pan and Zoom stills. Now that I have finished color correcting and have rendered each Pan and Zoom individually along the way I find I can combine the entire show and it will save in one bin although it takes approx. 20 seconds or so to save. Along the way I did do the right click remove redundant keyframes but I don't think that was really an issue. I know in the past with these kinds of layered nested sequences those sections with the heavy nesting once rendered will play down but quite often generate a dropped frame error during a digital cut. Even with
> the top Safe Color Limit rendered these sections will stall on tape output and I have to use mixdowns in those sections. I figure it's all the pointers that Avid has to process in those sections that cause the stalls even with a rendered track above. I'm really curious what others think allowed me to save the entire sequence once rendered on a safe color limit and all the pan and zooms rendered. Is it the unrendered and unlinked Pan and Zooms that caused the too many items unsavable bin? What else could it be? Just curious.
>
> John Moore
>
> Barking Trout Productions
>
> Studio City, CA
>
> bigfish@...
>
> [Non-text portions of this message have been removed]
>
No comments:
Post a Comment