Still image sequence bug?

MTuggy wrote on 9/22/2008, 10:34 PM

Ok, here is something new. I have been doing a series of projects with a lot of 32-bit PNG 1280x720 image sequences of late (about 300-360 frames). I like the transparency you get out of them.

This last project, I overlapped 2 sequences in the timeline. Vegas-killer. Locked up every time I tried to render over the overlapping frames. Even playback choked up. Had to go to task manager to kill Vegas and start over.

I rendered each PNG sequence seperately into MOV files, then replaced them in the orignial project. Of course, that worked to fix the problem but my transparency is not as clean.

Anyone else seen this? I wouldn't have stumbled across it if I hadn't tried to overlap to still image sequences.

Mike

Comments

Marco. wrote on 9/23/2008, 1:03 AM

Images sequences are Ram eaters. In case there is trouble most of the time there is either not enough Ram available (take a look at the Ram usage in the Task Manager) or corrupt Ram.

Marco

Chienworks wrote on 9/23/2008, 3:27 AM

I regularly use sequences of 1920x1080 stills, often 600, 900, even 1800 images. I use both .tga and .png. Occasionally i've even had sequences over 10,000 images. Never had a crash or a RAM usage issue with them, ever.

MTuggy wrote on 9/23/2008, 8:26 AM

Were you importing them as image sequences or just a series of stills imported together? I haven't had trouble with stills that have been down sized to HD size image (from 6 or 10 MP images).

I have 6 GB of RAM, memtest hasn't shown any RAM problems.

Mike

Chienworks wrote on 9/23/2008, 1:05 PM

Image sequences.