Nuke/RV integration

NOTE: this article and the docs mentioned below describe how to set up RV as "flipbook" for Nuke. We've recently released an integration package that implements a much tighter implementation between Nuke and RV. That package is described (with demo video) on this page, documentation for the package is here.

Appendix D of the RV User's Manual (available online here) covers these topics:

  • How to setup a custom plugins/scripts area for Nuke.
  • Configuring RV as a flipbook player for Nuke (the rv_this.py script discussed there is attached to this article).
  • Exporting OpenEXR files instead of RGB for flipping
  • Modifying the RV flipbook config to use different color spaces, LUTs, etc.
Follow

9 Comments

  • 0
    Avatar
    Jean-Paul LeDoux

    Currently the online manual is not displaying all of the information needed to get RV running as Nuke's flipbook.  I suspect your auto-documenting software is dropping the text meant to be entered into the python scripts. (Viewed in Chrome & Firefox anyways).   Are the steps for getting Nuke set up anywhere else?

  • 0
    Avatar
    Alan Trombla

    Hi Jean Paul,

    As you see this article is pretty old.  At the moment, we strongly recommend using the nuke integration described here: http://www.tweaksoftware.com/static/documentation/rv/current/html/rvnuke_help.html

    Did you try that ?

    Cheers,

    Alan

  • 0
    Avatar
    Jean-Paul LeDoux

    That is set up, though I'm not sure we will have the licenses to have RV running on every lighter/compositor's box all the time without impacting the rest of the faculity.  Hmmm, looking at this closer, I guess for what I'm asking for it's just a matter of remapping alt-f to the "View in RV" command, isn't it...

  • 0
    Avatar
    Jean-Paul LeDoux

    Actually, I guess "Render to RV" would be more appropriate - it seems to understand not to render when a read node is selected.  

  • 0
    Avatar
    Jean-Paul LeDoux

    Hmmm, I lied.  Render doesn't fall back to View when provided with a Read node.  :(

  • 0
    Avatar
    Jon Morley

    Hi Jean Paul,

    I cannot quite tell if you were able to get what you were after. If you have not, then can you please elaborate on what you are trying to do and where you are stuck?

    Thanks,

    Jon

  • 0
    Avatar
    Jean-Paul LeDoux

    HI, sorry for being cryptic.  Really I'm just looking for the same flipbooking behaviour from RV as I've known with Framecycler in Nuke.  So if I select a Read node, and alt-f it, it can pop up and play those frames.  If I select a node elsewhere in the tree, it 'renders' the tree to a temporary location and plays the result.

    I realize this is basically what "View in RV" and "Render to RV" do, so I think I will eventually write something simple that detects what the selected node is and call the appropriate behaviour.  Would be cool if Render to RV could detect that on its own, then you'd only need the one command.

     

    I tried the rv_this solution, but ended up using the custom flipbooking mechanism described in the Nuke manual.  (http://docs.thefoundry.co.uk/nuke/80/pythondevguide/flipbook.html#using-tweak-software-s-rv-as-the-default-flipbook-application)

     I will need to make it a bit smarter - to detect the actual frame range of the read node, for example - but this gets me most of what I need.

     

  • 0
    Avatar
    Alan Trombla

    Hi Jean Paul,

    Thanks for clarifying.   If you really want something FrameCycler-ish then, using the flipbook factory code you mention is the right way to go. The "rv_this" mechanism predates the FlipbookApplication class in Nuke by quite a bit, we should really just remove it.

    If you're using the RvNuke integration described here, Render in RV is not really interchangable with View in RV just because the Render in RV functionality only optionally renders the currently selected node (on the assumption that you'll want to render a target output node over and over, regardless of selection).  But it certainly would be easy for you to add a "render or view in RV" function that always operated on the selected node.

    I also wanted to point out that if you have the "sync read nodes" option turned on for the project, _all_ read nodes will be reflected in RV as soon as they are created, in which case "view in rv" is sort of unnecessary.

    Cheers,

    Alan

  • 0
    Avatar
    Jean-Paul LeDoux

    Ok, thanks for the additional information, Alan.  We're in pre-production right now and RV is pretty new to the studio so it's hard to say exactly what we're going to want once we get into full shot production.  At this point I'm just trying to get the familiar in place...

     

Please sign in to leave a comment.