Is background rendering working

[ScorpioProd]

Do the rest of you find background rendering working correctly or not?

For instance, I am currently editing a DV project made of HDV clips. Based on my computer, I have it render anything with more than 1 HD clip at a time.

So OK, I put a transition between two HDV clips, it renders as it should. Good.

But then the problem... I'm keyframing motion on that clip downstream of the transition. And EVERY time I keyframe anything on that clip, even though it has NOTHING to do with the transition area at the beginning of the clip, the freakin' background render starts OVER again.

Now on a slow system that needs background rendering to begin with, this is a big hit and slows down my editing.

What are the rest of you finding?

Thanks.

[ted]

Yup, I haven't found why, but quite often I'll change something up or down from everything else. Then I'll see a bunch of areas background rendering.
I'm talking 5-15 clips and overlays away. No common dissolves are even close.
I'm pretty sure I have the Default render option on, but I've played with a couple others as well.

Seems like this had been discussed here and I can't remember what Andrew said???

[SBowie]

I was thinking it was fixed in 1.51, but not in the current SE-VT ... could be wrong about that.

[ScorpioProd]

It's not fixed in SE 1.5.1. :thumbsdow

[ScorpioProd]

Well, I turned background rendering off.

And now as I continue in my project, I'm getting some crashes when I copy CG instances within the project! :thumbsdow

[SCS]

I've found it a lot easier to render out areas as temp files manually - Background re-re-re-rendering wastes too much time!

[John Perkins]

Changing any part of the clip will trigger the "rerender" function. The editor receives a clip change message, so it believes that it must need it.

You can cut the clip at a point beyond the BG rendered section or do as SCS mentioned and render out "patches" to cover the effected areas.

[John Perkins]

BTW, we've been working extensively on the CG, but please report any problems you see. We'd like to have them all ironed out before the next release.

Thanks,

[ScorpioProd]

Changing any part of the clip will trigger the "rerender" function. The editor receives a clip change message, so it believes that it must need it.

You can cut the clip at a point beyond the BG rendered section or do as SCS mentioned and render out "patches" to cover the effected areas.
But John, you do understand that this isn't a good way for it to be working, right?

I mean, changing the clip, the SAME clip downstream should NOT be triggering a rerender.

[John Perkins]

That depends, we may be speaking of two different things.

Are you saying two different instances of the same clip, disconnected/cut-in-two

or

The head and tail of a single instance of a video clip?

It makes a big difference.

If it is re-rendering the head of an instance of a clip when you keyframe the tail end, then it is working as expected. Changes were made to the instance, so it re-renders.

Thanks,

[ScorpioProd]

Well... Actually, I mean a single clip. Not an instance, though honestly I always thought once one cut a clip, it wouldn't affect the previous parts of that same original clip.

But anyway, I mean just a normal clip, as I add nodes for movement, my transition into the clip re-BG renders each time, even though nothing in that part of the clip has changed.

Maybe I just need to ignore it, if you assure me it won't slow down my editing.

[Adam_LightPlay]

I think this applies to the situation you describe.
I'll drag in several Force-render croutons. Leave one under what doesn't change, and another in the little section I'm tweaking. Then it only has to re-render, the new area each time.

[ted]

Nice trick Adam. Thanks!

[KiloWatkins]

I think this applies to the situation you describe.
I'll drag in several Force-render croutons. Leave one under what doesn't change, and another in the little section I'm tweaking. Then it only has to re-render, the new area each time.

Yeppers, it has been posted by me and others to use a ForceRender, quess I could have pointed out what you did better.

BestWishes