Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Boris RED 5 vs. Sony Vegas Pro: Chroma Key chokes and Fade outs

  • Boris RED 5 vs. Sony Vegas Pro: Chroma Key chokes and Fade outs

    Posted by Carl Alessi on September 2, 2011 at 3:15 pm

    Sometimes I write subject lines that sound like the title of a “Yes” song, but not that one.

    Anyway…the problem I have is that imposing a Fade Out at the end of a video clip in Vegas, which is usually one of the easiest things in the world, is creating a conflict with the way I’m creating chroma keys with Boris RED 5. Part of the process involves using a “choke” filter in RED to cut a clean key; when I later subject that clip to a fade out, Vegas calculates the fade properties by squeezing the person’s image–the subject literally looks like they’re imploding from the edges inward, rather than fading uniformly.

    Any ideas for resolving this?

    Thanks in advance,

    Carl

    John Rofrano replied 14 years, 10 months ago 2 Members · 6 Replies
  • 6 Replies
  • John Rofrano

    September 2, 2011 at 6:40 pm

    [Carl Alessi] “when I later subject that clip to a fade out, Vegas calculates the fade properties by squeezing the person’s image–the subject literally looks like they’re imploding from the edges inward, rather than fading uniformly.”

    That sounds like a bug. I would report it to Boris over on the BorisFX forum and see if they can recreate it and report it to Sony. Make sure that you’re using the latest version of both Boris RED 5.0.6 and Vegas Pro 10.0e.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Carl Alessi

    September 2, 2011 at 8:06 pm

    Thanks John…I tried upgrading to RED 5.0.6, but I’m still having the same issue. Next week I’ll try recreating the problem with a fresh project in Vegas/RED…if the problem continues, I’ll report it.

    As severe as this is, I’m surprised that the Boris team has not been approached about this earlier.

    Carl

  • John Rofrano

    September 2, 2011 at 10:13 pm

    [Carl Alessi] “As severe as this is, I’m surprised that the Boris team has not been approached about this earlier.”

    Well… I said that it may be a bug, but not that it’s definitely a bug. So far… you may be the only one seeing this. I can’t reproduce it. I use Chroma Key in Boris RED all the time with the Matte Choker and I fade events in and out and all they do is fade as expected. It has to be reproducible for Boris to be able to determine if it’s a bug or not.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Carl Alessi

    September 8, 2011 at 9:15 pm

    John,

    I have a question for you regarding the integration of Boris RED and the problem I mentioned in this thread (i.e., the imperfect fade outs produced in Vegas when using Boris chromakey filters).

    What I’ve done on this project, which I’ve done differently than any previous project, is to apply the chromakey effect via compositing mode, rather than as a simple track effect.

    My question: how important is it to make the background video track a compositing child of the track containing the chromakey filter?

    I have not created such a child relationship. This is becoming an increasingly critical question for me, because I’m now having problems getting my renders in this project to complete (I started a new thread about this particular issue on Sept. 7). I now have to wonder if my possibly incorrect application of the filter via compositing mode is causing me a range of project crippling problems.

    Thanks in advance,

    Carl

  • Carl Alessi

    September 9, 2011 at 4:03 pm

    Alright, problem solved. Making the backplate track an explicit child, with the foreground track containing the RED chromakey filters the parent, has allowed the rendering to complete. And it completes much more quickly than before.

  • John Rofrano

    September 10, 2011 at 2:55 am

    Glad you got it working. You had to make it a compositing child because you changed the composite mode of the chromakey track from Source alpha.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

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