Still Images not rendering in Vegas Pro 11

Yachtie Dave wrote on 4/25/2013, 11:58 PM

Can anyone tell me why 129 still images set to match Output Aspect with pan & zoom, a few fades & cuts & only 3 or 4 transitions will not render. Vegas stops after around 20% but not always at the same spot. The project settings are 1920 x 1080 25i rendered to MPEG2 HDV 720 25p. There is a short video with Titler start & end & these render ok. The 129 still image sequence renders without a problem in Vegas Studio 10.

Thanks Dave

Comments

Grazie wrote on 4/26/2013, 12:55 AM

Hi Dave - Vegas is choking on something. Just for checking, render out to something other than MPEG2 HDV, anything.

There is something in your workflow that is making the MPEG render tough for Vegas to wobble at the knees. From reading and re-reading your post it would appear that it is the insertion/combination of the Video and Stills sequence that's doing it. How about doing an interim render of the areas that are troublesome and bringing that back into Vegas?

It may, of course, be the MPEG encoder now not performing in VP12. Actually ARE you using VP12? What Build?

Cheers

Grazie

Yachtie Dave wrote on 4/26/2013, 3:56 AM

Thanks for the quick reply Grazie,

It's Vegas Pro 11 Build 701. Would you believe this is the first major problem I've had .
Your observation of the 'workflow making the MPEG render tough' is one of the first things I thought of so I have tried to render the stills sequence separately & had the same problem. The video parts are fine . I have completed the project by rendering the stills in Vegas Studio 10 & brought that back into Vegas with reasonable success, however I have 3 to 400 still images to do & following that work around is not the way I want to go. I will try a few different renders & see what happens.

Not sure what country your in, I am in Australia so there may be a delay in replies.

Cheers Dave

Duncan H wrote on 4/26/2013, 4:01 AM

Hi Dave,

I'm in Melbourne, so no time lag here. Our friend Graham is in the U.K and probably still tucked up in bed at the moment.

How do you go if you try rendering to .mxf as an intermediate and then reload that into the timeline and try rendering. A nuisance having to do it twice, but if you've got to get this project done, that's what I'd try.

Duncan

Grazie wrote on 4/26/2013, 4:21 AM

Actually, Pal, it's 10:15am in London, and I have been up and answering questions and colour grading for 3 hours.

Intermediaries are a great way to go. If they work, hence my invitation to do something else too, would flag up an issue with MPEG-ing.

And now it's 10:20 in London. <wink>

Grazie

Duncan H wrote on 4/26/2013, 4:28 AM

Hi Grazie, nice to see you up and at it.

Duncan

NormanPCN wrote on 4/26/2013, 9:59 AM

Vegas Movie Studio, MS, is tons better at stills than Vegas Pro, VP.

I started with MS12 and "upgraded" to VP12 and my project choked in Vegas.

I have experienced the random hang/lockup you state. I have been trying to get Sony support to download a sample project which duplicates the issue on my machine.

You have VP11. I have noticed VP12 is not so stable with stills with crop/zoom and especially rotate when GPU in turned on. Try turning GPU off in Video Preferences. I found VP12 stable with my stills project with GPU off.

VP12 seems to have a lot more overhead than MS and cannot smoothly handle jpegs as large as MS. This should not be an issue but you might resize your jepgs if you cannot find any other workaround for VP stills limitations. For me, I reduced the the 12MP GoPro files to 4MP and 99% of my crops are still above project size, which is 1080. The remaining 2-3 are still large.

I have only rendered to SonyAVC or Main Concept AVC at 4:3 1440x1080p24, but that should not matter. In my short experience, the issue is typically within Vegas rendering the video stream.

Tech Diver wrote on 4/26/2013, 1:03 PM

Dave wrote: "Vegas stops after around 20% but not always at the same spot."

This is exactly the sort of problem that I experienced when using several Boris Red effect in a chain. I fixed it by increasing the "Dynamic RAM Preview max" setting in the Video tab of the Options dialog box. With the 8 GB that you have indicated in your systems spec, I would set the Dynamic RAM Preview to about 5 or 6 GB if you have not already done so and give the render another try.

Peter

Peter Riding wrote on 4/26/2013, 1:51 PM

Most of my projects contain a lot of stills. They are PNGs and are resized and sharpened (the originals having been shot in RAW) prior to bringing into Vegas, sized approx twice the size of 1920x1080 to allow for zooms. I have had the same problem and I have only been able to get around it by turning off GPU acceleration. Wouldn't you just know it :- (

Once upon a time GPU acceleration worked for me but now it has not for several builds of Vegas and updates to my GTX570 card. Currently I'm on Vegas 12-563 and Nvidia 314.22

Pete

Yachtie Dave wrote on 4/26/2013, 4:15 PM

Great suggestions from all you guys. IT'S FIXED!

It was the Dynamic Ram & GPU acceleration. A couple of months ago I had to install a new C Drive & Graphics Card. Re install programs including Vegas.
I originally had Dynamic Ram set at 4GB, forgot on reinstall & it was set at 200mb.
Tried render with new setting 4GB & GPU on, didn't work, turned GPU off & all is well.

I am surprised at the amount of projects I have done with the Ram set at 200mb.

Rendered at HDV 720 25 was a bit jumpy in spots however at HDV 1080-50i it is perfect.

Thanks again for all of the help.

Dave