View Full Version : Vegas Pro 10E- defective transition


Ron German
August 6th, 2011, 08:22 AM
After horror experiences with versions 9e and 10D trying to render Cineform codec mixed with Sony MXF and jpeg photos in a 90`timeline (black frames, low memory messages / render interruption, etc), now version 10E (64 bits) seems be a bit better in my recent tests, but it has generated this kind of problems (in this case, some defective frames in a transition):

What kind of error is this?
Thanks

Intel dual core 2, - 3GHZ processor - Windows 7 professional 64 bits - 6 RAM

Phil Lee
August 6th, 2011, 09:09 AM
Hi

Is it smart rendering? Do you see a black preview window for some of the time saying rendering isn't required?

What are you rendering to? The blocks tend to suggest an encoding problem. Fades and transitions are quite a challenge for lots of encoders, and they can struggle if pushed too hard or there are lots of transitions if quick succession for example.

What if you export it as Sony YUV and watch it back, is that problem free?

Regards

Phil

Mike Kujbida
August 6th, 2011, 09:13 AM
Ron, what's the source footage that you converted with Cineform?
Same thing for the MXF footage.
How big (in pixels) are your stills?
I'm wondering if this is a case of your computer (it is definitely underpowered) just can't handle the footage.

Ron German
August 6th, 2011, 01:41 PM
Thank you Phil and Mike
My system should be enough, according to Sony and Cineform minimum system requirements.
HDV (from HV20) converted to Cineform codec.
h.264 (from Canon T2i) converted to Sony MXF 35 mbits
Photos jpeg maximum 3200 X...resolution
Not smart rendering
This problem happened rendering to Cineform Codec and to (QT) DNXHD with 23`part of my doc project.
I didn`t try to export it to Sony YUV with Vegas Pro 10 E yet, but with version D the render was too slow and used to stop with low memory messages.
But surprisingly, with version E, the system crashes and black frames ramdomly found along the render process seems not happen.

Ron German
August 7th, 2011, 09:41 AM
More defective frames, but now one frame inside inside a rendered clip.
What`s the source of this error?
Maybe one error frame in a 20` rendered file (in this case, to DNXHD codec).
So I don`t know how to do a "safe" render.

Eric Olson
August 9th, 2011, 12:26 AM
It would appear you have defective hardware. Have you overclocked either your CPU, memory or graphics card? If so, set your hardware back to factory defaults.

Leslie Wand
August 9th, 2011, 12:48 AM
how many hd's in your system?

running any other apps at the same time, such as nortons?

Ron German
August 9th, 2011, 09:33 AM
Thank you Eric and Leslie
I didn`t overclock CPU, memory or graphics card.
No Norton. 3 hard disks.