This content has been marked as final. Show 15 replies
Did you try rendering? Sometimes that smooths things out.
I did render. I also deleted the previous renders to be safe but to no avail. I also exported the timeline to be sure it wasn't the preview. It is not. It is definitely the footage because I have also exported the timeline to Encore, encoded it, put it on DVD and watched it on the standalone DVD player- same jumpiness. I am re-rendering the test clips on a different machine right now, hoping it is a CS3 problem only on this machine.
I will try 2.0 next.
Previewing with "draft" or "best" yields the same results- jumpy.
2.0 does the same thing with a nested timeline... Is it just my system? And how could I not have noticed this before?
Hardware, disk configuration, source, codec, project settings, etc.?
Laptop with Intel Pentium 1.6GHz, 2GB RAM, footage is on external USB drive (7200RPM (I think)). Source is NTSC widescreen DV. Microsoft DV AVI.
I tried making a flash video to show the effect but the compression hides the jumpiness. It appears to be some kind of field order/interlacing problem.
CPU is borderline, the external disk is about the slowest you can get so I would suggest more capable hardware, better CPU and faster disk using eSATA.
While those are good ideas, Harm, I'm not sure they would cause this problem. Especially since it happens before and after export.
What I can say is that this is not normal behavior for 2.0. I know things changed in the slow motion department for CS3, though.
I agree this system's hardware is low for video editing, but wouldn't the hardware just affect the rendering time (or encoding time) and not necessarily the quality of a simple timeline within a timeline?
I'm not challenging you but just want to understand this. Rendering the 10 second clip is exactly the same speed whether it is the actual video or a nested timeline and either methods result in a rendered clip. Shouldn't any boarderline system result in the same output file especially when it is something so simple at slow-motion (even with frame-blending)?
could you clarify whether you're using time remapping (ie the new CS3 feature that allows keyframing of time changes), or are you simply using 'speed change' on the nested sequence clip?
I have tried using both. Time remapping on the clip (not nested) works fine, so does 'speed change.' But both time remapping and speed change result in jumpy frames when applied to a nested sequenced clip.
I tried this on another (much lower system) and have found the same results. I am begining to think it is the footage but it seems odd that it is perfect when applied to a clip in the timeline but NOT to a timeline in the timeline (nested).
I am on vacation and do not have access to a faster machine until next late next week but for now I will try the export again to be sure Encore sees the same thing.
I am dumbfounded because I had been using 1.5, then 2.0 and now CS3 for weddings for years and have never noticed this. I have noticed it on the both the last project and now this current one.
I thought it could have been the original footage (or a camera problem except that the problems are not there until a nested sequence comes along. I will try moving the footage to my internal drive now and see what happens...
Thank you so far for giving me ideas.
Ok, I have an example clip online at www.thewaterspick.com/testclip.avi . In the process of making this test video I made titles to describe both clips in it. I discovered that if I have a title over the nested timeline it will render correctly as can be seen in the uploaded video...
As you can see in the video on the second clip (the nested timeline) it looks fine until the title disappears at which point the jumping starts.
Sure enough, I just needed to make a transparent title, although, now that I think about it I may be able to use a transparent video instead. At least with a transparent title the affected clips in the ceremony are rendering just fine.
Hi Stephen -
I see the stuttering in the second example just after the guy stands (just making sure that we're talking about the same thing). I suspect that it's a subtle bug in the frame blending algorithm, probably only exposed by the nested sequence case.
If you don't mind, I'd love to get a sample project with just that particular clip in the nested sequence case. If you could duplicate just that portion into a new project, and upload it on an ftp server somewhere, I'd be much obliged.
In the meantime, I suspect that you might find that if you were to alter the length of the nested sequence by +/- a frame or two, it might be enough to bump the math so that it won't create the judder you're seeing.
I'd be glad to upload the condensed project. I'd love to here other's opinions on this as it has been most troubling for me on these last two weddings, one of which the client actually pointed out. I will try to get the project online tomorrow. I am also going to grab some old footage and see if it has anything to do with this particular footage or not. I think you're right that it is something to do with the blending.
I appreciate everyone's help with this!