[dave_bass5]

I thought i was getting on ok with Vegas but tonight i noticed this ghosting.
The original .mts file seems ok so its just the output form Vegas thats looking wrong.
Can someone please have a look at this video to see if you have any idea?
Is i t to do with pulldown maybe?
Look at the guy at the front in the blue. Any idea how to correct this?

Marching band on Vimeo

Cheers.

[dave_bass5]

Answering my own post i found out that Vegas was re sampling the footage.

After right clicking on the properties for the clip in the time line you can turn smart (?) re sampling off.

Right, so thats fixed but can anyone shed more light as to why it was affecting my footage in the first place? It seems ot be well hidden and not explained very well yet had a huge impact on the output.

[nikonuser11]

trying to help but your link wants registration before viewing

[dave_bass5]

Sorry about that. I set it to be hidden and forgot to turn it off.
Should be working now.
As i said, it was the fact that Vegas was re sampling it. What i cant understand is why or how to stop it (other than to turn it off).

My project is (based on clip properties) 1280x720 50P and im wondering if its because i was rendering at 1280x720 25P.
Im just bothered that ill always have to do this adjustment.
If you have a look at the Scouts pledge clip it starts with the same footage but without the re sampling and you can see its fine.

Cheers.

[A n d r e w]

Hi Dave.

Can you clarify what settings you used when shooting the video, i.e. I'm assuming it was recorded at 50i but was it? You mention pulldown, but there shouldn't be any pulldown required unless you were shooting at 24p, and I assume your camcorder doesn't shoot 24p.

Although you didn't have this problem with the "Scouts pledge" clip, I'm wondering whether the problem here is partly to do with the conversion to Flash format by Vimeo. I'm reasonably sure that Flash video is 15 frames per second, but I'm not sure whether this means that the original frames are blended (which might well produce the ghosting we're seeing) or simply dropped. I haven't downloaded the original file to check for myself, but when you play the clip as exported from Vegas (before uploading), do you see the ghosting?

Just trying to establish at which stage the ghosting enters the picture (no pun intended) i.e., on export or after uploading and conversion to Flash.

[dave_bass5]

Hi Anderw, thanks for replying.
First off its not Vimeo, this file looks the same on my PC but by turning smart render off it then plays fine. I can even see the ghosting in the preview window so its definitely Vegas causing this.
The only reason i mention pull down (and have no real idea what it is) was there was a mention of 24 pulldown on the page, thought it might have something to do with it

According to Vegas the .mts files are 50P and this is what the project is set to.
Im rendering at 1280x720 25P. Having now checked my other files it does seem to be down to my settings in Vegas but i would rather not have to keep changing the resampling if i can just change the project or rendering instead.

Does this make sense?

[mmace]

my guess is from your last post, the original is 50fps but you're outputting at 25fps so it's merging 2 frames to make it half the fps

[dave_bass5]

Originally Posted by mmace

my guess is from your last post, the original is 50fps but you're outputting at 25fps so it's merging 2 frames to make it half the fps

Ok thanks. Is there anything i can do about that other than what im already doing?
There doesn't seem to be an option to output at 50fps, or if there is i cant figure it out.

what i cant figure out is that until this file all my other renders seem to be ok, at least i think they do.

EDIT: Seems like all the clips do suffer with this, just not as bad.

[A n d r e w]

Sticking my oar in again here:

Your timeline settings in Vegas are 50p? This seems weird, since I don't think the HF100 (or any camcorder I've heard of) records at 50p. Are you sure the original .mts clips on the HF100 aren't 50i (two interlaced fields per frame)? 50i is still 25 frames per second, which you could convert to 25p (usually by selecting an interlacing option, which would either blend fields to make progressive frames, or drop odd or even fields, depending on the options given by Vegas which I'm not familiar with so can't be of any more precise help on interlacing options ).

I'm thinking that the .mts files created by the HF100, regardless of the mode you've recorded in, should be 1920x1080 50i, and should be recognised by Vegas as such.

Anyway, none of this solves your problem. Just out of interest, what does Smart Render in Vegas do?

[dave_bass5]

Originally Posted by A n d r e w

I'm thinking that the .mts files created by the HF100, regardless of the mode you've recorded in, should be 1920x1080 50i, and should be recognised by Vegas as such.

Anyway, none of this solves your problem. Just out of interest, what does Smart Render in Vegas do?

Im not talking about my HF10, its my Lumix TZ7 in having the trouble with ;-)
And yes, the files are 1280 x 720 50P (or so im told).
Having just looked at some of my other renders form this camera i can now see that the issue is there, just not as bad as this clip. Im going to re render them all today.

This is what the help file says about smart rendering.

"Select a radio button to determine how video frames will be resampled when the frame rate of a media file is lower than the project’s frame rate. This can occur either when the event has a velocity envelope or when the frame rate of the original media is different than the Frame rate setting on the Video tab of the Project Properties dialog.

With resampling, the intervening frames are interpolated from the source frames, much like a crossfade effect between the original frames. This may solve some interlacing problems and other jittery output problems.

Smart resample


Resampling occurs only when an event's calculated frame rate does not match the project frame rate and the project frame rate is 24 fps or greater.

The calculated frame rate takes into account any changes made to event speed with velocity envelope, playback rate, and undersample rate."

Thanks again.