Sunday, September 23, 2012

Re: [Avid-L2] Bin too big to save?

 

Just the sequence in the bin? Turfed unused precomputes?

DD
On 9/23/2012 2:55 AM, John Moore 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@pacbell.net <mailto:bigfish%40pacbell.net>
>
> [Non-text portions of this message have been removed]
>
>

[Non-text portions of this message have been removed]

__._,_.___
Recent Activity:
Search the official Complete Avid-L archives at:   http://archives.bengrosser.com/avid/
.

__,_._,___

No comments:

Post a Comment