Bob,

Thanks for the quick response!

Wusshhh!

Thats the sound of your reply rushing over my head concerning intraframe compression.

I have an idea of what you are saying, but fail to understand why a captured clip that looks so good would look so badly when rendered.

I used;

Main Concept MPEG 2
Default Setting
DVD Arcthitect NTSC widescrean video stream.
HDV 720 30-P
HDV 1080 60-I
Custom Settings

Windows Media Video V9
Default Setting
8Mbps HD 1080-30 P Video
Several Custom Settings Used with VIMEO Uploads

SONY AVC/AAC
Default Setting
Custom Settings

Main Concept AVC/AAC
Default Setting
Custom Settings

None of them looked as good as the original clip.

Tom

Long story short. Interframe compression reduces the redundant data within a frame e.g. JPEG which is similar to what's used in plain DV. Intraframe compression uses some form of interframe compression to reduce the data within a frame and then further reduces the amount of data by storing only the differences between frames. That's way, way simplified, just so you could see why motion can be a problem.

I'm not certain though I'm on the right track at all! The shot of the car shouldn't stress anything too much as most of the frame is static.
Your other Vimeo videos look fine as do most of the later shots where the camera isn't moving.
Did you shoot his at 60i or 24p?
Do all the codecs and settings that you've tried give the same jerky motion?

I hope someone else can have a look at this, I'm kind of running out of ideas.

Bob.

Horrid.

Ditto Bob, what was the original footage shot at?

Are you absolutely sure it looks ok when you view it? Are you running full frame rates?

Grazie

I don't see this in the movement of the water? Weird.

At 1:26 > 27 there is a distant car - top left - doing movement, but it is hard to pick out any doubled-inter frames there . .

Very odd . . .

Grazie

Bob and Grazie,

The footage was shot with HDV 30. The HV 30 has settings for; HDV, HDV 30, and HDV 24. I used the HDV 30 setting. According to the manual, this is a progressive frame rate of 30, but I think I read somewhere this is actually 60i.

The captured footage is so smooth and clear I can see the reverse rotation of the wheel covers.

All the codecs have similar results!

Tom

You're almost certainly right. The footage is most likely recorded with the frames split into two fields to give 60i.
Ideally your project properties should be 30fps, Field Order = None (Progressive). Next thing is Vegas probably doesn't know the video is progressive. So RClick the files on the timeline or in Project Media and Change the Field Order there to None as well. Alos probably you should also set the projects de-interlace method to Blend.
Also you should render to 30fps no matter which codec you use.

I think your biggest problem is Vimeo converts everything to 24p and 30p is a dog to convert to 24p. I suggest trying to get Vegas to convert to 24p by rendering to 24p. Make certain Resampling is On. That'll force Vegas to interpolate between the frames. Not the ideal way to convert from 30p to 24 but to do better you need expensive / hard to use tools.
I'd suggest if you want to put your footage onto Vimeo shooting 60i or 24p.

Bob.

It's seems like the field order is reversed in interlaced. Fast motion causes a jerk backward effect when you go frame to frame. Smooth motion you don't notice it as much.

Vimeo can be jerky on my slower computer, but it shouldn't jerk in the same place every time.

I am almost certain that you have screwed up the frame rate and possibly also the progressive/interlaced setting. You might have field order reversed, as others have suggested, but in my experience, that imparts a totally different feel to the video than what you are getting.

Use Gspot (free download) to find out exactly what your video is. Make sure Vegas is treating it correctly. Also, make sure you do not have any pulldown added. This can happen if you use the 24p mode in some of those Canon cameras. You say your are using 30p, but I don't know what actually comes across to Vegas in that mode.

Then, match the source video characteristics in both your project and render settings. You can change the resolution, but don't change the framerate and don't change from interlaced to progressive, or vice versa.

Also, if you can post 2-3 seconds of the original video and 2-3 seconds of what you are uploading to Vimeo -- especially the portions that show the car driving by -- I'd be willing to look at it with some tools which examine the video frame-by-frame. I can instantly tell you exactly what is going on, whether you have pulldown, reversed fields, progressive, interlaced, upper field or lower field, etc. I do this by looking at the video using special tools, rather than just examining the video header, which is what Gspot does. It is definitely possible (and I've seen it) to get video which is labeled incorrectly, and as a result, software (such as Vegas) does the wrong thing.

Thanks for all the input!

I found the problem after reading all the replies and checking the properties; project and clips.

Oops! I can't believe I did it, but I stretched the clip. Found this out when I went into the clip properties and saw the "Playback Rate" was less than 1.00. When I set the playback rate correctly the rendered video looks good.

Sorry for the inconvenience.

As far as the project properties goes, the camera is set at 30p, but when I "Match Media Settings" in Project Properties, it shows;

HDV 1080-60i (1440x1080, 29.970 fps)
Upper field first
Deinterlace Method None.

Thanks everyone!

Tom

I am showing - and I really don't care - my ignorance here but . . . . Can somebody please please please explain this to me:

This MEANS NO FIELDS - Correct? "As far as the project properties goes, the camera is set at "

This MEANS FIELDS - Correct?:
"HDV 1080-

Progressive setting on camera and Interlace on the "Match Media Settings" - why?

Grazie

Most camera record 25p and 30p progressive footage by splitting each single frame it into two fields. This makes the footage compatible with existing interlaced systems i.e. 50i and 60i
They may or may not set flags to tell anything reading it this is what they've done plus whatever is reading the footage may or may not bother to read or interpret the flags correctly.
It looks as though either the camera has not set the P flag or Vegas hasn't read them. This is easily fixed by changing the media's properties.

Normally this doesn't matter that much, most TVs still cannot display 25p or 30p so the player will split it into fields anyway. It still looks like 25p or 30p. Where it does look like it matters is when you try to resample as we've seen with Tom's problem. If this was shot at 60i he'd probably not have noticed anything wrong.

Bob.

Okkkaayyy, took me 2 readings to get it clear in my bonce . . . . So my initial "understanding" was correct and my knowledge of these things not in doubt. This is a good thing!

"Most camera record 25p and 30p progressive footage by splitting each single frame it into two fields." I didn't know that!! What do these 2 fields look like? Meaning I can understand 2-field interlace - but what does 2-field P look like? Intriguing . ..

"This makes the footage compatible with existing interlaced systems i.e. 50i and 60i" - Makes perfect sense(?).

"It looks as though either the camera has not set the P flag or Vegas hasn't read them. This is easily fixed by changing the media's properties." Sure, understood. Would G-Spot identify it as this? If G-Spot does and Vegas doesn't, would this mean there was a "bug"?

"Where it does look like it matters is when you try to resample as we've seen with Tom's problem." Ah! So only for the fact that Tom had the resampling set to something other than 1, we would not have known.

Interesting.

Thanks Bob.

Grazie

"but what does 2-field P look like?"

Pretty much the same really. Consider that film is projected with a 2 blade shutter to reduce flicker, at lower frame rates like 8mm @ 18fps the shutter has three cutouts you'll see why visually it doesn't matter. In fact every 'movie' you and I watch is being trasmitted as 25 frames split into 2 fields and that's how our SD CRTs display it.

"Would G-Spot identify it as this? If G-Spot does and Vegas doesn't, would this mean there was a "bug"?"

I can't speak for GSpot as I've rarely used it. I suspect it's the camera though as Vegas correctly recognised the flag in 25PsF material when I tested the V1P from memory.

Bob.

Pretty much the same really.

Yes I kinda realise that, no, it was WHAT does this look like in terms of a graphical representation? I can view a website that SHOWS how 50i looks - 2 fields - Upper and Lower. My "badly" framed (lol) question was physically what does progressive fields look like? Sorry .. . I can't phrase this any better!

All the other stuff I understand. It's solely, I suppose the actual digital lumps look like? Do you have a graphical re-pro of this? I can view the "fingers" of 2-field interlace. See?

Grazie

OK, gottcha.

Well no you can't really see it, I'm mean when you put the two fields together you get (drum roll) a perfect frame! If could look at each field you just see alternating lines of picture and nothingness, the next field you see the same except the alternate lines.

The way Vegas handles this can be a tad confusing. Depending on the settings for the preview monitor quality it may only display one field. At Best it merges two fields which is why you can see the mice teeth on interlaced video and none with P or PsF.

In case any non PAL people are reading this it is not so simple in NTSC with pulldown!

Bob.