Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Red Red Red – Why?

  • Red Red Red – Why?

    Posted by Ben Hen on January 24, 2009 at 6:24 pm

    Now that I’ve had some experience using Vegas, I still have a problem with it arbitrarily turning my video clips red – and un-previewable. I’m forced to save, close the program, then open it again in order to get my preview back. This happens USUALLY on the short vids I’m creating.

    Closing and opening makes it viewable again – no troubles.

    Any ideas why this is happening?

    Running Vista Home Basic on a 2.8Gz Duo with 2GB RAM.

    Rob Mack replied 17 years, 3 months ago 4 Members · 8 Replies
  • 8 Replies
  • John Frey

    January 24, 2009 at 6:58 pm

    Do you have any extra large still images on the timeline? Red on the timeline is often associated with still images that are way too big.

    John D. Frey
    25 Year owner/operator of two California-based production studios.

    Digital West Video Productions of San Luis Obispo and Inland Images of Lake Elsinore

  • Charles Avanti

    January 24, 2009 at 8:59 pm

    Ben,

    I had that happen to me yesterday when I put a 1200 dpi png on the timeline.

    Charlie

  • Ben Hen

    January 25, 2009 at 12:08 am

    I have still images about 2mb each on the timeline – but on a separate track. I’m working on a project now with two 3MB still photos and one short vid, and I get the same response. And it doesn’t make the still images red, just the vids.

  • Ben Hen

    January 25, 2009 at 12:10 am

    Maybe that’s the issue – as John said – that it doesn’t like oversized still photos. Some of mine are 3072 x 2304. They are only links to the files though – not saved inside the project. I’m surprised it’s a problem, really.

  • Ben Hen

    January 25, 2009 at 1:12 am

    Do you think it might be that I don’t have enough RAM (2GB)?

  • Rob Mack

    January 26, 2009 at 12:58 am

    Yes, red frames happen when an image/clip is too large (in pixel dimensions), or when it has some other problem being decoded. Your image’s pixel dimensions don’t seem so large, though. Perhaps they’re tiffs or some format variant that gives Vegas a fit.

    The fact that the images come back after a restart suggests that memory was made available for a bit. That could be a problem with the media you’re using or maybe indicates a problem with your RAM Preview setting. If your system has 2GB installed i might set the Ram Preview anywhere between 16 MB and 512 MB, the general idea being that too much or too little will give you trouble.

    As far as an image file being nMB, that’s not too meaningful. If I take a huge image and compress the heck out of it then it’ll still take a tremendous amount of RAM when it’s decompressed. Similarly, it’s not meaningful to say an image is 1200DPI unless you know the supposed physical dimensions. If it’s 1/2″ across then it’s 600PX wide, if it’s a foot across then it’s 14400PX wide. These pixel dimensions are more important to know than file size or DPI.

    Rob Mack

  • Ben Hen

    January 26, 2009 at 7:24 am

    Thanks Rob – I’ll give it a go.

    It still happens even without still images, as it turns out. Is 2GB RAM just not enough?

  • Rob Mack

    January 27, 2009 at 12:07 am

    Well, it probably means that stills aren’t the issue 🙂

    Could be your chosen media type or possibly the RAM preview setting. 2GB ought to be pretty serviceable. Vegas is saying “I can’t play that” until you restart the program which usually means memory usage is an issue.

    Changing the preview settings for the preview window often has the same effect if it forces Vegas to discard all its cached information

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy