I'd just batch em all over to PNGs and see if that helps, you can use the media swapper in USPro to exchange one extension for another.

Dave

Hi Ray!

Don't go above 2000 on either side. So when you resize, you want to constrain proportions and make whichever number is highest no higher than 2000.

I doubt there's any "safe" size at all. I've had Vegas handle enourmous tiffs without anything breaking although it took forever to render and playback was pretty painful.
I suspect the real issue is the size of the image AND the number you have active at the one time on the T/L. If you have a lot of images in a 3D composite being moved around in 3D you're more likely to have to reduce the size of the image than if it's just one track of images with cuts between them.

Bob.

I had some absolute nightmare render problems with large jpegs, David's advice about dimensions pretty much sorted it out. I also found that colour profiles other that RGB caused Vegas to crash.
It would be useful to have a sticky with tehese known horrors and any others that reliably reproduced


Derm

I'm not sure if PNG even supports cymk so that might not be a problem.

2kx2k dimensions might be a fairly useful size for SD but it doesn't give you any extra to work with in HD.

One approach to this might be to do several batches of resizings and make a library of folders for various sizes-1k, 2k, 4k, (in the past it's seemed like 8k was nearly impossible). Then finally make one last folder called "working" and copy the lowest rez images into it for use in Vegas. As you edit, if you need a higher rez image then go get it and copy it into the Working directory. As long as all the images had the same names this ought to work seemlessly. And this way you keep most of the images small. (This is speculation. I've not tried it.)

Rob Mack

Resizing them and keeping the largest dimensions at 2000 worked but to my eye at a considerable cost of clarity. Really a drag. I may try going with bigger with some images that are especially affected but wow, what a hassle, especially since it doesn't crash until way into the render.

Would love to see this fixed in future versions. Were working with HD now and this really is a problem. Being able to do any kind of pan/zooming or "Ken Burns technique" as some like to call it is nearly impossible with these limitations.

Appreciate all the suggestions and feedback.

- Ray
Some of my stuff on Vimeo
Me On Twitter

I regularly do Ken Burns' style pans on very large PNG panorama images (average of 10000x3000.) I often have 20-30 of these images in a project. Vegas v8.0c will quickly run out of memory and start hitting the page file, which slows the render to an absolute crawl. Vegas doesn't actually crash, but it's so incredibly slow that it might as well have crashed. On the other hand, Vegas v8.1 will just blaze right through these projects. v8.0c will take hours and hours to finish a render, whereas v8.1 can do them in about 15-20 minutes.

Using 8.0c here. Would love to run 8.1 but use to many plugins like Magic Bullet Looks that are, as far as I know, still incompatible. That said it straight up crashes here with just 20 or so and all of them less than 6000 at the largest point.

- Ray
Some of my stuff on Vimeo
Me On Twitter