[Niki Patton]

Reporting back..

I went back and pared down services/startup etc. in case of conflicts (note that this is a new computer and so I don’t have much on it) and re-rendered and still had a problem — tried render in safe mode (is that even recommended? Figured it was worth a try..) — but still had a problem.

So after some more tracking down, it turns there were some issues with the NVidia 720 GeForce Video Graphic Card after all. Nvidia has just released a 300 MB update which took care of some but not all of my glitches. Then I came across a post on this forum where the user found that Windows Media Player was getting ‘overloaded’ in playback — that would have been the last place I’d look since there had never been an issue with WMP on any of my previous machines or on my laptop. But it seems the combination of Vegas/the new computer/graphics card and WMP was not a happy one all the way around. I played the video newly re-rendered using the updated NVidia and using another media player and the rest of the glitches were gone…whew!

Just goes to show…best to check all variables when a problem comes up — even the ones you are absolutely sure are no problem. Thanks for your help on all of this…back to work!

[Niki Patton]

Thanks for your quick reply — I’m capturing a mini-dv in an SD AVI format. And it’s from the same camera that this org has been using for about three years. I’ve been using Vegas Pro 12 on my Lenovo laptop to do this until now — capturing/editing/rendering — without an issue re the codec or the capture or render. Now I am still capturing the mini-dv on the laptop (yes, yes..I’ll let go of firewire eventually…) and then transferring that file to the new desktop to edit and render — once again in Vegas Pro 12…and that’s when the problem shows up.

I’m fairly certain that if I transfer all the elements back to the laptop and do the render in Vegas pro 12 on the laptop it will be fine…since it’s always been fine in the past. (I do know the playback from the file rendered on the new computer has the same issues playing back on the laptop that it does on the desktop — so the problems are created in the render on the desktop) .