Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer the bogus render

  • the bogus render

    Posted by Grinner Hester on April 28, 2007 at 2:07 pm

    when adrenaline goes through the motions of rendering in to out then doesn’t really render, does anybody know if those files are written as a precomputes?

    Grinner Hester replied 19 years ago 6 Members · 12 Replies
  • 12 Replies
  • Dan Archer

    April 29, 2007 at 2:06 am

    I have had that hapen several times. I would like to know as well. Shutting down avid and sometimes the machine will somketimes make avid recognize the rendered files so i think maybe it does actually render them.

  • Satesh Ramjattan

    April 29, 2007 at 2:38 pm

    I agree, but I don’t think you have to close Avid. When it happens at work, closing the sequence and reopening does the trick.

  • Grinner Hester

    April 29, 2007 at 3:43 pm

    that works for me as far as getting it to actual render after that but it doesn’t pen back upas renderd. I have to wait for another phat render.
    This is why I was wondering if it was written. I feel like it is. It goes though the motions and makes the client wait and all and I do believe the buggyness now in media tool revolves around these files.
    Ever notice how after this starts happeneing, thats when media tool stops showing files you know exist?

  • Satesh Ramjattan

    April 30, 2007 at 1:49 am

    I have noticed that Media tool thing as well. I wonder if it a Boris Continuum thing, because it only does when I have one of those plugins on, specifically the glows.
    How about you? Or is it just the native effects?

  • Rep_eric

    May 1, 2007 at 2:57 pm

    When I’ve had this problem in the past, precomputes were being created, the sequence was just not linking to them. One thing that I’ve found that can cause it is a motion effect. I had some shots that I was adding pulldown to, then adding an effect (probably CC) on top of that. It wouldn’t render for anything until I removed the motion effect. Put another add pulldown motion effect and the problem would come back. I also found (by trial & error) that I could get it to render by slipping the shot a few frames in one direction or the other.

  • Steve Pankow

    May 1, 2007 at 4:56 pm

    Usually closing the bin that the sequence is in, then reopening takes care of it.

  • Grinner Hester

    May 1, 2007 at 5:02 pm

    hmmm
    good discussion. We may be gettng close.
    I use alot of BCC glows and I use alot of time warps. I’m thinkin timewarp may be the candidate although I dont rule out bcc.
    you useing alot of timewarps?

  • Satesh Ramjattan

    May 1, 2007 at 11:24 pm

    I do motion effects, but I only notice with the BCC.

  • Grinner Hester

    May 2, 2007 at 7:00 am

    I hate to admit it but I use BCC glows in dang near every sequence.
    The bogus render does’nt always happen on that effect. Are you saying with yours it does happen on that effect every time or on any effect with the bcc glow on that sequence?
    Here. it tends to happen when I have effects stacked… but often that stack does include the glow.
    I will switch to only sapphire glows for a while and report back.

    … on that. Have you noticed that sapphire glows will alter you video levels? They clip em where bcc glows don’t. Also, I like how the bcc glows saturate the colors… not just white or a sigle color ya desinate.

  • Gary Oberbrunner

    May 2, 2007 at 1:09 pm

    Hi Grinner — in Sapphire, try turning off Clamp Output To Legal. It defaults On to prevent outputting too-hot colors.

    Hope that helps;

    — Gary

Page 1 of 2

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