Personal tools
You are here: Home Products RV Customization

RV Customization

RV Customization



RV was designed by industry veterans with a lot of experience both as artists and engineers. As a result, RV can be used to optimize your playback workflow rather than forcing you to adjust your pipeline to fit the limits of another black-box software component. RV can be configured by individual users, or extended and modified by scripters and developers.



RV can be customized in a variety of ways:

Furthermore, all the above varieties of RV extensions can be encapsulated in RV Packages.  Packages make it easy to distribute and share RV customizations. They are cross-platform, can be installed centrally for all users or locally by individual users, and they can be activated or deactivated as a unit by the user or based on per-show or per-shot environments, etc.


We designed RV so that users can customize it, and the possibilities are endless. But we are often surprised by the amazing things that users come up with. Here are some real-world examples of how users have customized RV.


RV's UI, Menus, Control Logic, and Heads UP Widgets are all written in RV's extension language, Mu. All of this source code comes with RV and can be inspected or changed by users. This code includes:

  • Menu definitions and hot keys
  • Keyboard, mouse, and other input device bindings
  • Control Logic and Behavior
  • Heads UP Widgets, like the timeline, pixel inspector, Image Info Widget
  • Image handling rules (such as how to configure RV's color settings based on incoming images, env. vars, etc)


RV's open architecture and extension language make it possible to build new tools inside RV. These can be very simple, such as adding a function to automate some settings with a single hot key. Or, they can be extreme, such as writing an OpenGL renderer to display geometry and camera moves over background plates. Most RV custom features use some combination of the following techniques:

  • Add menus and popup-menus
  • Automate repetitive actions
  • Get/set/create custom properties in RV session files (e.g. for dailies metadata)
  • Create heads-up widgets
  • Respond to RV's internal events to trigger custom code
  • Capture keyboard, mouse, or other input for your own interactive features
  • Use OpenGL to draw directly on RV's window
  • Write image format plugins

Interact with the Environment

RV's extension language can interact with the operating system, network, and filesystem You can make RV aware of shots, shows, artists or other important categories and make your extensions adapt based on the context. You can also use RV's networking and remote sync features in your own RV extensions.

  • Read files from disk (e.g. your own custom EDL format)
  • Get environment variables
  • Call other programs or scripts (e.g. to query a database) over a pipe
  • Watch files on disk, and trigger events in RV when the files are changed
  • Populate menus based on database queries, or contents of special directories (say a LUT directory per show)
  • Drag/Drop your own file types into RV, and handle them with custom code
  • Piggyback on RV's remote sync Package, and have your own features synced up during remote review sessions


RV can be integrated with, linked to, or controlled by other applications. RV can be used as the player component of your own proprietary applications

  • Control RV over the network from your own application
  • Export or import RV session files form or to you own tools
  • Render into RV with display drivers or other software
  • Embed RV so that RV acts as the viewer component of your own application, like a dailies browser

What Users have Done with RV

RV users around the world continue to surprise us with how they extend RV. Here are a few examples of things that users have done. 

  • Display shot metadata inside RV
  • Show custom image attributes in a heads up widget in RV
  • Automatically translate network paths from RV session files so the same session files work on Windows, Mac and Linux
  • Make a custom inspector reports info about  the 3D asset from each pixel in a rendered image
  • Render 3D geometry and camera moves over a background plate to review a matchmove
  • Record pan/scan animation and export as a Shake or Nuke node for quick repo tests
  • Chop a long quicktime movie into individual shots based on marked shot boundaries and automatically generate an RV session with the shots cut together. This is great for handling pre-vis or edited sequences that are delivered in one long quicktime movie.
  • Write custom display drivers to render directly into RV
  • Integrate RV with an in-house dailies browser including:
    • Launch RV with an edited sequence
    • Launch RV with A/B compare of selected shots
    • Mix and conform mixed image types and resolutions
    • Load stereo sources
    • Offset movie files to a given frame range (to align with frame sequences)
  • Integrate RV into production database and editorial system
    • Create special EDL format that automatically pulls in the latest take for each shot
    • Drag/Drop special EDL's onto RV
    • Query production database through scripts
    • Cut/Paste text into RV (say from emails) to trigger RV to retrieve a take, based on database information
    • Launch RV from a web-link on an intranet
    • Export RV session files with edls, audio, color corrections, LUTs etc. from production database for dailies
    • Create custom menus populated with items from an editorial database (latest cut, bookend shots, etc.)