Problem with still images

Yep wrote on 10/11/2014, 5:35 PM

I am working on a project in Vegas Pro. The first four minutes or so are made up of .jpg images with pan/crop & zoom applied. The resolution of the source images are 4000x2600(landscape) and 2600x4000(portrait).

When I try to render the project to Sony AVC 24p 10Mbps video stream, the render fails after four or five of the still images.First I get the error message below from Windows. And then I get a Vegas error message saying the program has crashed.

"Your computer is low on memory

To restore enough memory for programs to work correctly, save your files and then close or restart all open programs"

I also tried to render at a lower res of Internet 480p widescreen - but the same thing happens after about 10 still images.

I think my PC has reasonable specs - Windows Pro 64-bit, Intel i7 3.5GHz Processor, Nvidia GeForce GTX 560 Ti video card, 8 GB Ram, and 1.2 Tb free space on my hard drive.

I'm trying to figure out why the still images should be creating such an issue as I've never had similar problems when working with high bitrate HD video. This project is a recreation of a project I originally made in Roxio Videowave. Roxio was able to handle the exact same content and pan/crop effects without any problem.

Do I need more Ram, or is there possibly something in my workflow or project settings that could be contributing to the problem?

All views or comments would be appreciated.

TIA

Comments

ushere wrote on 10/11/2014, 5:43 PM

first i would convert pics to png.

btw. you do have gpu rendering turned off? and you're working with only one hard drive?

Yep wrote on 10/11/2014, 6:07 PM

Thanks ushere - I had GPU acceleration set for my video card. I've just set it to Off and rendered the problem area - it whizzed through it and didn't crash. So that would appear to be the problem solved. Many thanks for that.

In reply to your other question - I reserve my C drive for operating and programs exclusively. When rendering I render to a large internal hard drive.

Now I'm curious about the GPU acceleration issue. What is the accepted widsom (if any) for having it turned off or on?

ushere wrote on 10/11/2014, 6:38 PM

well, it all depends ;-(

frankly gpu in vegas is stuffed - works for some, not others, and that's even on the same system config. however, if you've got a umphy cpu it's not much of a loss really - but many of us have been more than frustrated with it's appalling implementation.

you'll find posts by 'oldsmoke' praising the 580 (justifiably), but nothing seems to have been done by scs to 'update' it to handle newer gen cards.

btw. vegas likes png's rather than anything else.

PeterDuke wrote on 10/11/2014, 6:42 PM

You get a low memory message because the images are held in memory. If you first convert your images to the project resolution you will get on better. However if you plan to pan and zoom you will want to start with a higher resolution such that the zoomed in resolution is about the same as your project.

TheHappyFriar wrote on 10/11/2014, 7:37 PM

I've had dozens of 8mp images on the TL without issues, so I doubt it's about the memory. I've had higher, but my Cannon takes 8mp so that's what I normally use.

What I'm thinking is that you have something in your project that's taking up the memory. Do you have 3D track motion, lots of FX, etc? What version of Vegas are you using? Could be a 32-bit limit on a plugin/fx you're using.

EDIT: if it were me I'd try rendering out small sections at a time to troubleshoot. Could be one of the images is bad could actually be out of RAM, but w/o troubleshooting nobody knows.

Yep wrote on 10/11/2014, 8:27 PM

Thanks for all the comments guys - very much appreciated.

ushere

For now turning off GPU acceleration seems to have sorted the problem completely. But I'll definetely consider using pngs in other projects.

TheHappyFriar

The only effects applied to the images are pan/crop/zoom. I'm on Vegas Pro 13 64-bit. And yes - any time I run into a problem like this I start with rendering small areas around where the problem is. ;)

TheHappyFriar wrote on 10/11/2014, 10:13 PM

Does it render the small sections ok?

Yep wrote on 10/12/2014, 2:18 AM

"Does it render the small sections ok?"

Yes - with GPU rendering turned off it now renders the entire project which is over 50 minutes long and contains 40 or more similar jpg pictures.

;)