RSMB – Avoiding rendering black frames.

loocas | Nuke,software,technical,videotutorials | Saturday, December 18th, 2010

Get the Flash Player to see this content.

RSMB is a fantastic plugin that I use very often to speed up my renderings, however, there is one little glitch that almost made me go crazy! Hopefully I’ll be able to save you some time by explaining this issue and offering a fix in the video above.

5 Comments »

  1. that’s great and it’ll save a lot of time! in my case, the problem was a CONSTANT node, but after set up his frame range for the entire comp length, rsmb worked.

    Comment by Rafael — September 1, 2011 @ 19:12

  2. Thanks. Have run into this here and there and just worked around by using oflow or kronos but it’s nice to know what the deal was. Now to fix the random SOLID RED frames that will sporadically appear in some frames when rendering complex sequences. No rhyme or reason. As awesome as this plugin is, ReVision really needs to put some time into working out the bugs in the OFX version. Hasn’t been an update released in 2 years! Anyways, thanks again man.

    Comment by Travis — October 19, 2012 @ 20:53

  3. if you have one frame only and need to extend it’s length, it’s easy enough. But if you want to hold (first ,last) images in offseted sequence, you’re still fucked. And there is no in Nuke setup (that I know of). Just plain old duplicating and renaming frames..
    This is also problem with Kronos and most likely lots of others
    I had to find out the hard way, when Kronos denoiser just kept giving me black frames (and empty alpha channel, which was screwing out merge nodes) :/

    old blog post but some things stay the same

    Comment by Michal — November 9, 2014 @ 01:26

  4. This helped me out today, thanks! =)
    Stupid RSMB…

    Comment by Thanks — November 27, 2014 @ 20:24

  5. This is still a big problem, circa 2016. To take this a step further, you can stick a retime in your comp right before the RSMB node and change the input range to the frame range of your comp.

    This will save you time from having to go dig back through your comp to find the one node that has an off frame range. It’s also probably way safer if you’re working on a relatively complex comp.

    Comment by ben — November 2, 2016 @ 00:58

RSS feed for comments on this post. TrackBack URI

Leave a comment

Powered by WordPress | Theme by Roy Tanck