Vegas Stutter

[Bob Peterson]

How are you viewing this rendered video?

[Jason Hauck]

Windows media player works well for me. Otherwise, the Picture Motion Browser (sony product) plays well too. I occasionally use Nero.

Should the playback of rendered video be different than raw footage?

[Bob Peterson]

How then do you know that the stutter is not being produced by your playback software for any one of several possible reasons? I suspect that it needs to be burned to the appropriate disk format, and played by a player before you can point at Vegas.

[Jason Hauck]

Let me explain again:

1. The three clips each playback just fine individually.
2. When I link them together using Vegas, the playback of this file will stutter if one of the scenes has too low illumination and continues to stutter even after it returns to a normal illuminated scene.
3. All other projects using well lit scenes linked together playback just fine (no stutter).

Thanks for the suggestion though. Any other ideas?

[Jason Hauck]

I have done a few experiments on the stuttering problem.

It appears the rendered video turns out fine using 32bitXP and 32bitVP9. I only get the stutter when using either 32bitVP9 or 64bitVP9 on 64bitWin7. No it is not a playback problem as another user already suggested.

Anyone else get problems in 64bit vs 32bit?

I wonder if its a video-audio sync problem…

[No Vegas]

In Windows 7 64 Bit with Sony Vegas Pro 10, I sometimes will get a rendered stutter near transitions. If I go back and re-render, it usually fixes it. But it’s very rare.

My main problem with Windows 7 64 bit is during Multicam editing. I can’t get more than 1 minute playing the timeline before Vegas stops responding. If I wait about 5 minutes Vegas will come back, but then stop responding again about 1 minute later. It does it randomly through any and all SD .AVI video files. The AVI files are standard which were captured from an SD Mini DV camera using VidCap. So there shouldn’t be an issue there.

If I swap hard drives over to Windows XP Pro SP3 on the same PC and use Sony Vegas Pro 10 32 bit, it’s flawless. I never have a crash, lock, or responding issue with Sony Vegas Pro 10.e on Windows XP Pro Sp3. I can’t remember when the last time was I got a crash or had an issue. But using Sony Vegas Pro 10 with my Windows 7 64 bit OS, is completely out of the question. It’s totally usable.

Yes, it’s a full clean install of Windows 7 64 bit professional on a brand new 7200 RPM WD HDD.

Yes, it’s a full clean install of Sony Vegas Pro 10.

Yes, my Bios, drivers, updates and patches have all been completed.

Sony Vegas Tech Support has refused to answer any of my questions regarding this. It’s now been 3 weeks since I submitted a report and not one single reply. How nice of Sony to provide such comprehensive support for a product they sell that seems to have issues with Windows 7 64 bit.

I contacted Microsoft and they said it’s not an issue with Windows but with Sony. Go figure.

So now I sit with a PC loaded with 8GB of Ram and having to use Windows XP Pro which only sees 3.8gb just so I can get projects out clients are paying for.

The only reason I switched to Vegas Pro 10 was to utilize CUDA and more ram with 64 bit.

I’m beyond frustrated at this point with Sony as I have been a paying customer for over 5 years now and spent over $2,000 dollars on their software.

The latest “E” patch complete reeked havoc and now Sony Vegas Pro 10 will not even load SD .AVI files into the time line in Windows 7 64.

That’s my issue. I know I’m not alone with this, I just wish SONY would get their act together and start fixing what they sell.

[Ron Lindeboom]

[Aaron Berg] “My main problem with Windows 7 64 bit is during Multicam editing. I can’t get more than 1 minute playing the timeline before Vegas stops responding. If I wait about 5 minutes Vegas will come back, but then stop responding again about 1 minute later. It does it randomly through any and all SD .AVI video files. The AVI files are standard which were captured from an SD Mini DV camera using VidCap. So there shouldn’t be an issue there.

If I swap hard drives over to Windows XP Pro SP3 on the same PC and use Sony Vegas Pro 10 32 bit, it’s flawless. I never have a crash, lock, or responding issue with Sony Vegas Pro 10.e on Windows XP Pro Sp3. I can’t remember when the last time was I got a crash or had an issue. But using Sony Vegas Pro 10 with my Windows 7 64 bit OS, is completely out of the question. It’s totally usable.”

Boy, this sounds like a hardware issue with your machine — and I say that after 16 years of building forums sites for people in video.

My guess, I’d start with RAM. The intermittent nature of your issues makes me want to look there first.

If the issue were in the codebase of Vegas, it would be the same all the time. After all, the code is not going to rewrite itself dynamically and change what it’s doing. It is being influenced by something transitory in your machine. I’d guess RAM.

It could also be an issue with one or more of your drives. I have seen that do things like you are describing.

But as I said elsewhere: Sony Vegas is really rock solid and considering that this week it sits in the #2 most trafficked forum spot, I’d say that were it Vegas at fault (which you claim) then this forum would be full of people wailing on the Sony Team in Madison Wisconsin.

You asked me to look at your posts, so I did. And that is what I suspect is the issue.

Best regards,

Ronald Lindeboom
CEO, Creative COW LLC
Publisher, Creative COW Magazine

Creativity is a process wherein the student and the teacher are located in the same individual.

“Incompetence has never prevented me from plunging in with enthusiasm.” – Woody Allen

[No Vegas]

Great thanks so much! It makes sense. I’ll go with the RAM. Someone else also said the RAM. Guess I’ll swap it out although it tests out fine in Memtest and other tests.

Could be a Win 7 driver as well.

[Ron Lindeboom]

A while back I had a RAM issue, Aaron, and the RAM tested fine — but it wasn’t. ;o)

One of the safest things to do is buy all your RAM for all the slots you are going to use and make sure it’s Certified RAM. That way, it’s all from the same batch and the micro-variances in speed won’t be there (hopefully) between the chips. They will all be theoretically processing at the exact same speed.

Usually, when RAM is bad, that is what is wrong, the speeds are not syncing and so the ship is sinking instead. (Drum roll and half-hearted cymbal crash for the joke, please.)

When I replaced the RAM in that machine, the whole world got prettier, birds were chirping, Bambi and Bambi’s mother were flitting through the woods — after a week of what felt like caffeine overload on the nerves, and too many B-movie blood and gore flicks.

Best regards,

Ronald Lindeboom
CEO, Creative COW LLC
Publisher, Creative COW Magazine

Creativity is a process wherein the student and the teacher are located in the same individual.

“Incompetence has never prevented me from plunging in with enthusiasm.” – Woody Allen

[No Vegas]

LOL Great! I’m going to look up and see what CERTIFIED ram they suggest.
I am running 1333 with an I-5 stead of 1066. Not sure that matters but could be an issue?

Thanks