I see nothing whatsoever wrong with the clip. You might want to either enable downloading of that clip (it's a Vimeo preference that you have to set for each clip) or else upload the original file to Dropbox or Mediafire so we can take a look at it.

I paused the video several times and saw no ghosting on the ball or the racquets. While playing it, I did see the usual "judder" from using a relatively low frame rate (24p?).

The oddest thing I saw was around 4 seconds in, you can see through the player in the foreground and see the white ground line bleed through. Are there two tracks on your timeline and is the top track opacity not 100%? If they are offset a bit, I can see where some ghosting may occur.

fldave - the problem is that there is only one track, this is how it looks after rendering...

You're right johnmeyer, what I'm writing about can't be seen while playing on vimeo... I added download original file option. I will also try switching on deinterlace method to interpolate fiields (earilier I had "blend fields" switched on).

do you have resample dissabled (right click on the clip -> properties -> dissable resample)?

that might cause 'ghosting' if for example you have clips shot at 50/60fps and the project in 25/30fps

OK, after downloading your clip, it is completely and totally screwed up. It is interesting that Vimeo makes it look OK (more on that in a moment).

The odd fields of your video are completely fine, but the even fields are an almost random sampling of fields from various parts of the video. Apparently Vimeo only uses half of the fields, and managed to choose the odd fields, which is why it looks OK on Vimeo. (Warning to Vimeo users: they seem to be throwing away half of the video you upload!)

Based on all the problems I've had and that I've seen reported for five years in this forum, this is probably yet another GPU screw up. It is most definitely NOT a deinterlacing or field order issue. I'm 100% certain about that.

So, the solution is to turn off GPU everywhere within Vegas. Forget it exists, and don't EVER use it again. Ever. It is the only way to have any hope of consistently and reliably getting a good result every time you render. Yes, some people seem to be able to get it to work if they buy just the right GPU, and download just the right version of video card driver, but even then I suspect that they are sitting on a loaded keg of dynamite.

My experience is that GPU problems can range from the horrible and obvious (i.e., the problem you have), to the very subtle and difficult to detect, which is what I've experienced. The more typical problem is having one or two blank frames in a thirty minute video. I actually wrote software to detect these, and after I kept finding them, I gave up on all modern versions of Vegas, until I was able to prove that it is caused by Vegas' horrible GPU feature, and if you turn it off, everything will be OK.

So, turn GPU off in the Preferences--> Options dialog, and then when you render, click on the Custom button and make sure that GPU rendering is completely and totally disabled (i.e., do NOT choose Auto).

Remember to do this each and every time you render.

I wish Sony could fix this. They've had five years to get their act together. Even for those of you who will post that it can be made to work, I'll bet dollars to doughnuts that you will get bitten some day. The bug is there, lurking ... you will eventually get bit.

BTW, do you know the exact make and model of your video card, and can you determine what video driver you have?

[edit]

Here is the video, split into its separate fields. The top is the odd fields (OK), and the bottom is the even field. The two should look virtually identical, but obviously do not.

Dear all,
I'm always concerned about matching right properties of the project (always the same as original file prperties).
I had resample disabled but both files and project were in 25 fps.
But suprisingly it looks like I solved the problem (in a totally ridiculous way) - both project and original file have in properties "upper field first" so each time I also used upper field first in render. This time I chose lower field first and... it worked :)
I tried on the small part of the video, and now I'm rendereing large, 7-hour part so I hope it will work too... I will let you know...
I didn't see previous post so I have GPU still switch on.

Changing the field order of the render will probably just make the problem pop up somewhere else. It is definitely not the cause of the problem (i.e., this is NOT a field order problem). My suggestions in my last post is what you should do instead. Look again at the video I posted: field order issues show consistent problems with each and every frame, not inconsistent, random jumps. That just is not the nature of a field order reversal problem.

Ok, thanks, I will change this option after render and try to render with upper field than.

Upload some original footage somewhere. Its the only way to know for sure.

Upload some original footage somewhere. Its the only way to know for sure.He enabled the "download original file" option on Vimeo, so you can indeed get the original footage. That's how I created the video I posted above and how I determined what the problem is.

John, I have 1080p30 footage and project. When previewing I sometimes see exactly what you are showing for the even field render. Oddly, it renders ok. I have gpu on for preview and auto for render. I am using nvidia 550ti graphic card. I agree that SCS should have gpu support worked out by now.

/jerry

I have 1080p30 footage and project. When previewing I sometimes see exactly what you are showing for the even field render. Oddly, it renders ok.I have no idea how it could render correctly, but if you see this during preview, it will, some day, give you problems during render. And, unless you can take the time to walk through every second of footage, you may not spot it before you send the results out to a client. And then you'll get the phone call: "why does the screen flash just as the groom is toasting the bride?" Or, "there is something strange going on just as my kid sinks the shot to win the game." Murphy will ensure that Sony's bug bites you just where it hurts the most.

I cannot imagine a worse bug than this one, and it has been around since version 8.1. I cannot imagine working at a place that has neither the collective competence nor the pride to track this down and fix it. I use Vegas every day, but 98% of my work is still using versions 7 & 8. I only use 10, 11, & 13 ( skipped 12) when very specific features are needed. I long ago learned to give up performance gains in order to have the peace of mind to know that when I ship a project out, it won't have problems lurking.

Shame on the entire SCS development team for letting this bug continue to fester through six releases: 8.1, 9, 10, 11, 12, & 13.

Hmmm.... I never had this bug. Not in any of the versions from 7-13; I didn't skip any.

As for not upgrading. I guess it depends on what you are working with. I doubt VP8 can handle 1080 60p well and certainly not XAVC 4K files.

@TeeTime: The GTX550Ti is not strong enough to provide any significant improvement and might even cause problems. Sorry, but it is just simply the truth. I have a G210M in my laptop which is supported but just way under powered. So much so, that it will slow down everything when I switch it on as the CPU alone is more powerful.

I doubt VP8 can handle 1080 60p well I edit 1920x1080 60p from my Sony CX700 in VP 8.0c all the time. Works fine. Playback is most definitely much faster in later versions of Vegas, but stability is not always great. I've reported many specific problems over the years, but finally gave up when I realized it was better simply not to use these later versions unless I really needed something.

John,
is this only a problem with interlaced footage?

I don't even understand why anyone is uploading interlaced footage to a streaming service.

Bob.

is this only a problem with interlaced footage?I'm the wrong person to ask: I simply downloaded from Vimeo what was supposed to be the original video, deconstructed it, and then reported what I found. SCS will have to determine why this is happening.


I don't even understand why anyone is uploading interlaced footage to a streaming service.Because it is easy and is what most people do. Most people -- including some professionals -- don't really have a clue about interlacing and what it means. Instead, they simply think of their creation as "video." They edit it, and then upload it. I'm sure the streaming services receive millions of uploads a week of interlaced video, and they have long since learned how to deal with it. Obviously you can get better results deinterlacing before uploading, but as we've discussed countless times, Vegas provides only the poorest of deinterlacing functionality, and users get into all sorts of trouble when they try to resize and deinterlace in Vegas.

So, I'd actually recommend, for most Vegas users, that they edit and deliver in interlaced format, if their source is interlaced. This includes uploading.

This is yet another major flaw in Vegas which SCS continues to ignore.

I don't mean to keep being so negative, but it is so exasperating to be tied to a development team that doesn't understand how fundamental these problems and deficiencies have always been, and how it relegates their product to second-tier status.