Another red frame instance.

farss wrote on 8/7/2008, 3:09 PM

Last night I found that while doing mildly complex composits I can get frames rendered as red, increasing the amount of Blur or Intensity of the parent 2D drop shadow controls the onset of this condition. Thankfully the problem only happens when the values are way too high to be usable.
This only seems to happen with animated drop shadows using the parent 2D drop shadow. This 1080p project only contains PSD files, Sony 50MB/s MXF (rendered out of Vegas) and generated media. Not a show stopper for me but it does again show there's some nasty bugs aside from the mpeg-2 reader problem.

Bob.

Comments

Xander wrote on 8/7/2008, 4:53 PM

I will get red frame issues if I drop in large image files - .jpg (extremely large) or .png (very large). I usually save my Canon 5D files as 16-bit .png's. I have to remember to convert those to 8-bit or I do run into problems, especially the panoramas. I think red frames relate to memory issues (without the crash), but I could be wrong.

Rory Cooper wrote on 8/8/2008, 1:45 AM

I get the red frame now and then and I am pretty sure its proxy related

So I shut down re fire the project up maybe one or twice and then it’s ok

farss wrote on 8/8/2008, 3:52 AM

Played around with this some more. Switch to Preview / Auto frame renders OK. Switch back to Best / Full frame renders red....and then Vegas crashes with a memory access violation.

I'll try and see if I can induce this error using only generated media.
Reducing the number of tracks seems to prevent the error occuring, strange.

Whatever it is it's not related to frame size, most of the media is generated by Vegas itself and it's all only 1920x1080.

Bob.

Rory Cooper wrote on 8/8/2008, 4:24 AM

Mine are always related to plugins