RV 7: SDI MANUALimage: 0_Users_arasiah_git_tweak-release_rv-cxx98-release-qt4-python2_7_html_temp_images_rv_small.png

USERREFERENCESDIRELEASE NOTESimage: 1_Users_arasiah_git_tweak-release_rv-cxx98-rele___7_html_temp_images_logo_shotgun_grey_551x79.png
Table of Contents
Chapter 1 Overview >
Chapter 2 AJA >
Chapter 3 Blackmagic Design >
Chapter 4 Configuring the SDI Device >
Chapter 5 Command Line Invocation >
Chapter 6 Useful RV Features for SDI Output >

Chapter 1 Overview

This manual describes RV's implementation of the BlackMagic and AJA SDI hardware as a presentation mode device. For more information on presentation mode and how it relates to RV in general see the RV User's Manual.
RVSDI is a 64 bit only application which runs on Mac OS X, Linux, and Windows 7. It can be used to output to either BlackMagic or AJA SDI hardware. Note suppport for NVIDIA-SDI has been removed from RVSDI v7.2.0 onwards.

Getting Started

Prior to RVSDI version 7.2.0, you should have received a license file containing both an RVSDI license and an RV license. Both licenses can be floating if desired. However, from RVSDI version 7.2.0 onwards RV or RVSOLO licenses can be used for RVSDI too. The rvsdi executable (or rvsdi.exe on windows) differs from the regular rv binary in that it can interact with the SDI hardware.
On Windows: navigate to the RV installation's bin folder and launch the rvsdi.exe binary.
On Linux: go the bin directory of the RV installation tree and start the rvsdi program.
Once the RVSDI executable has started, the first thing you should do is open the video preferences tab under RVPreferencesVideo. This is the primary interface to configure the SDI device for presentation mode.

1.1.1 Quick Start

  1. Start RVSDI go to the Video prefs
  2. For SDI select the Blackmagic or AJA video module
  3. Select the SDI device (e.g. the DecLink Extreme 4k for Blackmagic or Kona4 or IO 4K in the AJA case)
  4. Select the video and data formats and sync method
  5. Click the "Use as Presentation Device" check box
  6. If you want audio output to SDI check "Output audio to this device"
  7. Exit preferences
  8. Select ViewPresentation Mode to start SDI output
Next time you're in RV you only need to do step #8. You can always start the prefs to change the SDI parameters as described below.

Chapter 2 AJA

RVSDI will drive a number of AJA products but not all features are available with all hardware. RVSDI can use the AJA drivers on Mac OS X (with the Kona3G or thunderbolt devices), Linux (Kona3G, Kona4), and Windows 7 (Kona3G, Kona4, and thunderbolt devices). Other AJA cards may also work on each of the platforms.
For use with NVIDIA GPUs you will need GPUDirect capable quadro (P6000, P5000, M6000, M5000, M4000, K6000, K5000, 4000, 5000, 6000). Some older quadros or consumer GeForce cards may also work with the AJA hardware, but we do not guarantee any kind of performance with non-quadro kepler or fermi cards. Note that the k4000 is not recommend since it lacks dual copy engines. RVSDI can use both the NVIDIA dual copy engine and DVP/GPUDirect only on professional fermi and kepler quadros.
On Mac OS X RVSDI can drive the Io4K, IO XT, and T-Tap thunderbolt devices using either AMD or NVIDIA GPUs.
For Windows and Mac Appropriate AJA drivers can be obtained from the AJA website and installed on any system that RVSDI will run on. For Linux drivers must be compiled or obtained from AJA.
To obtaining driver source code for linux requires enrollment in AJA's developer program. At that point you can download the driver source code, utility programs, and up-to-date firmware for various hardware.

Tested Hardware

There are a lot of possible hardware configurations + OSes for AJA playback. In general we recommend the Kona3G or Kona4 for non-thunderbolt use and the Io4K or IO XT for thunderbolt machines.
We do not recommend using the T-Tap for RVSDI playback: its possible that we had a damaged test device or RVSDI does something the T-Tap doesn't like, but we were unable to get steady 1080p@24 HD play back out of the T-Tap. If you're not concerned with stable play back speeds the T-Tap is fine. It will output the correct color and image.
Here are the ones we've tested:

2.1.1 2014 Apple Mac Pro (Trash Can)

We tested 4K AJA playback with the Io4K, 2K and stereo 2K with IO XT, and HD mono with the T-Tap. Images were stored on the built in SSD. We were able to use all of the Io4K and IO XT modes. RVSDI was not able to drive the T-Tap for 1080p@24 and we've never figured out why.
The Io4K HDMI output was also verified.

2.1.2 Apple MacBook Pros with Nvidia GPUs (thunderbolt 2)

RVSDI cannot drive SDI or HDMI even at HD resolutions on these machines because of the poor GPU read back performance. Do not use Apple Macs with Nvidia GPUs with RVSDI if you're concerned about stable playback.

2.1.3 Apple MacBook Pros with ATI/AMD GPUs (thunderbolt 1)

We have successfully used the IO XT (which is thunderbolt v1) with Mid 2011 MacBook Pros.

2.1.4 Apple Mac Pro Towers

We have not tested the older Mac Pro Tower machines with AJA products. We have had reports that they work for 2K Kona3G and IO XT output. So far no reports with Kona3G in 4K mode or Kona4.

2.1.5 HP z800 Linux and Windows (PCIe 2)

For Linux and Windows SDI testing we have an HP z800 workstation. In order to use this machine you must put the AJA Kona3G into slot #4 and the GPU in slot #2. The GPU should be GPUDirect capable quadro. These GPUs have “dual copy engines” which RVSDI can use to facilitate fast I/O to and from the Nvidia card. If you plan on using 4K output please avoid using the k4000/k4200; these GPUs have only a single “copy engine”.
Linux ubuntu 10.04, Centos 6.2, and Windows 7.

2.1.6 HP z820 Linux and Windows (PCIe 3)

We also have a z820 for SDI testing. This machine requires use of slot 6 for the Kona3G/Kona4 card and slot 2 for the GPU. The GPU should be a GPUDirect capable quadro. These GPUs have “dual copy engines” which RVSDI can use to facilitate fast I/O to and from the Nvidia card. If you plan on using 4K output please avoid using the k4000/k4200; these GPUs have only a single “copy engine”.
If you have a choice between a z800 and z820 choose the z820 especially of you will be using a Kona 4.
Linux ubuntu 10.04, Centos 6.2, and Windows 7.

The “AJA” and “AJA (Control Panel)” SDI Modules

RVSDI has two different Video Modules both which can operate the AJA hardware. The “AJA” module operates like the NVIDIA SDI module; it allows you to set all aspects of the video and data output formats as well as set up stereo output and ancillary HDMI output.
The “AJA (Control Panel)” module does not set up the hardware formats itself, but will use the current settings from the AJA control panel and/or cables program. This makes it possible to set up unique routing on the AJA card. This module is currently unable to produce stereo output but is planned for a future release.

DCI 2K, 4K, and UHD 4K Output

AJA products may support mono and stereo DCI 2K (2048 x 1080) and in the case of the Kona 3G with appropriate firmware installed quad DCI 4K (4096 x 2160) and quad UHD 4K (3840 x 2160).
Not all formats are available on all platforms and devices.

High Frame Rate (HFR) DCI 2K and 4K at 60hz and 48hz

With recent firmware and drivers (late 2014) its possible to run the Kona3G using RVSDI with mono or stereo DCI 2K 60hz. The Kona4 additionally supports mono and stereo DCI 2K and 4K at 48hz and 60hz.

AJA Specific Configuration Options

There are additional options which can be passed to the AJA device via environment variables or from the preferences Additional Options field.
The preferences field takes command line-like syntax:
AJA NTV2 Device Options:
  -h [ --help ]                      Usage
  -v [ --verbose ]                   Verbose
  --rec601                           Use Rec.601 Color Matrix (default is 
                                     Rec.709)
  -p [ --profile ]                   Output Debugging Profile 
                                     (twk_aja_profile_<ID>.dat)
  -m [ --method ] arg                Method (dvp, sdvp, ipbo, ppbo, basic, p2p)
  --flip                             Flip Image Orientation
  -s [ --ring-buffer-size ] arg (=4) Ring Buffer Size
  -n [ --no-aquire ]                 Do not attempt to aquire device from AJA 
                                     control panel
So for example the following forces the use of Rec.601 color conversion matrix and a ring buffer size of 4:
--rec601 --ring-buffer-size 4
Its possible to use environment variables instead which correspond to the command options above:
        TWK_AJA_HELP
        TWK_AJA_VERBOSE
        TWK_AJA_REC601_MATRIX
        TWK_AJA_PROFILE
        TWK_AJA_METHOD <method>
        TWK_AJA_FLIP
        TWK_AJA_RING_BUFFER_SIZE <size>
        TWK_AJA_NO_AQUIRE
In the case of TWK_AJA_METHOD and TWK_AJA_RING_BUFFER_SIZE the value of the environment variable determines the argument. In the other cases the presence of the environment determines the value (i.e. if TWK_AJA_VERBOSE is not set there will not be verbose output).

2.5.1 Method

Normally, the best possible method given the hardware and OS will be used. However, you can override this behavior using the method argument with one of these values:
Method
Description
dvp
Use NVIDIA DVP when available (default on Windows)
sdvp
Use NVIDIA DVP without overlapping DMA (useful for profiling only)
ipbo
Use immediate copy OpenGL PBOs for read back
ppbo
Use shared pointer OpenGL PBOs for read back (mac only)
basic
Use simplest possible GL read back scheme (not recommended)
p2p
Use SDI-Link (AMD firepro only)

2.5.2 Ring Buffer Size

There is a mimum and maximum ring buffer size for a given hardware setup. The lowest possible value is 2, but in practice 3 or 4 is usually required. The maximum value is 4 to 6 depending on the format begin used. For example 10 bit DCI 2K stereo requires extra memory limiting the ring buffer size to a maximum of 4. The ring buffer size should be set to the lowest possible value in order to reduce latency.
When the size is set too small, play back will be slow and stutter.

HDMI Output

RVSDI will hook up HDMI output on devices that have HDMI to mimic the SDI settings. In most cases you should be able to hook the output up to an HDMI capable device and get the same output that SDI is providing. On the Io4K and Kona4 the HDMI output will be the same resolution as the SDI output including UHD and DCI 4K. For devices which cannot do 4K HDMI the HDMI will have a downconverted image where available.
In stereo modes HDMI is currently set up to show the first eye.

AJA Device Firmware (enabling 4K on the Kona3G)

The standard Kona3G firmware is not able to output 4K formats. In order to enable 4K “Quad” firmware must be loaded onto the Kona card. This converts the card into either four inputs or four outputs but no mixed inputs and outputs (like the standard firmware can do).
RVSDI only ever uses the Kona3G for output. When the Quad firmware is detected, RVSDI will enable 4K output in the Video preferences for the Kona device. The usual HD and DCI 2K formats are still available with the Quad firmware installed.
The Kona4 and Io4K support 4K with their standard firmware.

Rendering and Hardware Configuration

Throughput from main memory to the GPU, back to main memory, and finally to the AJA hardware requires fine tuning of RVSDI's rendering options. There are a number of requirements that need to be met in order to obtain best results:
Most importantly, when using a Kona3G/Kona 4 card in a PCIe2 or PCIe3 slot, make sure that the GPU and the Kona card reside in slots which have different controllers. For example in an HP z800 or z820 workstation the GPU is frequently used in slot #2. By putting the Kona card in slot #4 which is not serviced by the same controller maximum bandwidth between the two cards can be achieved. AJA's website has a page describing recommend configurations for various hardware:
KONA PC Configuration
KONA Mac Configuration

2.8.1 NVIDIA Fermi and Kepler Quadros (Windows and Linux)

Supported Quadros with a propertly installed Kona3G on a fast machine (z800) is currently the only option for DCI and UHD 4K output.
NVIDIA fermi and kepler quadro GPUs allow the use of GPUDirect (called DVP in video applications) to transfer data between the GPU and an external video card like the Kona on Windows and Linux. RVSDI can use DVP to parallelize IO between the two cards and main memory. This can result in a huge performance win if set up properly.
However, in order to fully utilize the bandwidth to and from the GPU multithreaded upload, prefetch, and PBOs must be enabled in RVSDI's render preferences when the GPU has dual copy engines. Fermi 4000 and 6000 Quadros and Kepler 5000 and 6000 Quadros all have dual copy engines. The Kepler 4000 has only a single copy engine so using multithreaded upload is not a good idea on that card when using DVP.
In addition vertical sync (v-sync) must be enabled in the NVIDIA driver and disabled in RVSDI on Linux.

2.8.2 AMD FirePro on Windows

RVSDI can use SDI-Link to speed up communication between AMD FirePro GPUs and the Kona3G. Special “GMA” firmware is required for the Kona3G to use SDI-Link.

2.8.3 Geforce and Low end Quadro NVIDIA cards (Windows and Linux)

Geforce and lower end Quadro cards without dual copy engines are not supported for AJA SDI output on Windows and Linux. However, these may work using non-DVP methods (ipbo method). GPUs with one copy engine (k4000) are preferable to those with none.
With these GPUs try multithreaded upload, PBOs, and prefetch on in the Render preferences. If the results are not good try turning off multithreaded uploads.
In some cases you may get a GPU to work by increasing the size of the ring buffer. The maximum size for HD formats is 6.

2.8.4 NVIDIA Kepler GPUs on Apple Computers

On Apple computers PBOs with prefetch are also recommended, but multithreaded upload may or may not be helpful. Alternately, using Apple Client Storage (also in the Render tab of the preferences) instead of PBOs may be more beneficial with some GPUs.
RVSDI will use a specialized asynchronous read back scheme on Apple computers (corresponding to the “ppbo” method).
Thunderbolt AJA devices are supported along with Kona 3G in older Mac Pro desktop machines.

2.8.5 AMD GPUs on Apple Computers

On Apple machines with AMD GPU always use Apple Client Storage (with prefetch) instead of PBOs.
RVSDI will use a specialized asynchronous read back scheme on Apple computers (corresponding to the “ppbo” method).
Thunderbolt AJA devices are supported along with Kona 3G in older Mac Pro desktop machines.

2.8.6 Intel Graphics on Apple Computers

The Intel 4000 or earlier integrated graphics GPUs are unlikely to work with RVSDI and are not supported.

Chapter 3 Blackmagic Design

RVSDI can output to Blackmagic Design devices which use the DeckLink API. This includes the DeckLink capture and playback cards and thunderbolt UltraStudio devices. Although it may work with other devices like the UltraStudio for USB 3.0 they have not yet been tested.
RVSDI can drive stereo SDI and HDMI when available.

Tested Hardware

We have tested only two Blackmagic devices: an UltraStudio Mini Monitor and a PCIe DeckLink Extreme cards. There are a lot of possible hardware configurations + OSes for Blackmagic playback. We have only test some very specific configurations, but have had reports of success from most users.
Here are the ones we've tested:

3.1.1 2014 Apple Mac Pro (Trash Can)

We tested the UltraStudio Mini Mintor successfully on the Mac Pro Trash Can. We have not yet tested the UltraStudio 4K with thunderbolt 2 output but have had reports that it works.

3.1.2 Apple MacBook Pro with Nvidia GPUs (thunderbolt 2)

RVSDI cannot drive SDI or HDMI even at HD resolutions on these machines because of the poor GPU read back performance. Do not use Apple Macs with Nvidia GPUs with RVSDI if you're concerned about stable playback. The best we've been able to achieve with these machines is UltraStudio Mini Monitor output.

3.1.3 Apple MacBook Pros with ATI/AMD GPUs (thunderbolt 1)

We have successfully used the UltraStudio Mini Monitor with these machines. We would expect other DeckLink thunderbolt 1 devices to operate as well.

3.1.4 HP z800 Linux and Windows (PCIe 2)

For Linux and Windows SDI testing we have an HP z800 workstation. In order to use this machine you must put the BM DeckLink card into slot #4 and the GPU in slot #2. The GPU should be a k5000, k6000, or fermi 6000 or 4000 quadro. For 6G output the k4000 may also work well.
Linux ubuntu 10.04 and Windows 7.

3.1.5 HP z820 Linux and Windows (PCIe 3)

We also have a z820 for SDI testing. This machine requires use of slot 6 for the DeckLink card and slot 2 for the GPU. The GPU should be a k5000, k6000, or fermi 6000 or 4000 quadro. For 6G output the k4000 may also work well.
Linux ubuntu 10.04 and Windows 7.

DCI 2K, 4K, and UHD 4K Output

Blackmagic's DCI 2K and 4K output is supported when available but only on machines capable of sustaining 4K throughput from the GPU to the SDI device.
Not all formats are available on all platforms and devices.

Blackmagic Specific Configuration Options

There are additional options which can be passed to the AJA device via environment variables or from the preferences Additional Options field.
The preferences field takes command line-like syntax:
Blackmagic Device Options:
  -h [ --help ]                      Usage
  -v [ --verbose ]                   Verbose
  -m [ --method ] arg                Method (dvp, ipbo, basic)
  -s [ --ring-buffer-size ] arg (=4) Ring Buffer Size
Its possible to use environment variables instead which correspond to the command options above:
        TWK_BLACKMAGIC_HELP
        TWK_BLACKMAGIC_VERBOSE
        TWK_BLACKMAGIC_METHOD <method>
        TWK_BLACKMAGIC_RING_BUFFER_SIZE <size>
In the case of TWK_BLACKMAGIC_METHOD and TWK_BLACKMAGIC_RING_BUFFER_SIZE the value of the environment variable determines the argument. In the other cases the presence of the environment determines the value (i.e. if TWK_BKACKMAGIC_VERBOSE is not set there will not be verbose output).

3.3.1 Method

Normally, the best possible method given the hardware and OS will be used. However, you can override this behavior using the method argument with one of these values:
Method
Description
ipbo
Use immediate copy OpenGL PBOs for read back
basic
Use simplest possible GL read back scheme (not recommended)

3.3.2 Ring Buffer Size

There is a minimum and maximum ring buffer size for a given hardware setup. The lowest possible value is 2, but in practice 3 or 4 is usually required. The maximum value is 4 to 6 depending on the format begin used. For example 10 bit DCI 2K stereo requires extra memory limiting the ring buffer size to a maximum of 4. The ring buffer size should be set to the lowest possible value in order to reduce latency.
When the size is set too small, play back will be slow and stutter.

HDMI Output

HDMI output is always enabled for devices which have HDMI.

Rendering and Hardware Configuration

Throughput from main memory to the GPU, back to main memory, and finally to the Blackmagic hardware requires fine tuning of RVSDI's rendering options. There are a number of requirements that need to be met in order to obtain best results:
Most importantly, when using a DeckLink card in a PCIe2 or PCIe3 slot, make sure that the GPU and the DeckLink card reside in slots which have different controllers. For example in an HP z800 or z820 workstation the GPU is frequently used in slot #2. By putting the DeckLink card in slot #4 which is not serviced by the same controller maximum bandwidth between the two cards can be achieved.

3.5.1 NVIDIA Fermi and Kepler Quadros (Windows and Linux)

Supported Quadros with a properly installed DeckLink on a fast machine (z800) is currently the only option for DCI and UHD 4K output.
NVIDIA fermi and kepler quadro GPUs allow the use of GPUDirect (called DVP in video applications) to transfer data between the GPU and an external video device. RVSDI can use DVP to parallelize IO between the two cards and main memory. This can result in a huge performance win if set up properly.
However, in order to fully utilize the bandwidth to and from the GPU multithreaded upload, prefetch, and PBOs must be enabled in RVSDI's render preferences when the GPU has dual copy engines. Fermi 4000 and 6000 Quadros and Kepler 5000 and 6000 Quadros all have dual copy engines. The Kepler 4000 has only a single copy engine so using multithreaded upload is not a good idea on that card when using DVP.
In addition vertical sync (v-sync) must be enabled in the NVIDIA driver and disabled in RVSDI on Linux.

3.5.2 AMD FirePro on Windows

SDI-Link is not yet supported with Blackmagic devices.

3.5.3 Geforce and Low end Quadro NVIDIA cards (Windows and Linux)

Geforce and lower end Quadro cards without dual copy engines are not supported for Blackmagic SDI output on Windows and Linux. However, these may work using non-DVP methods (ipbo method). GPUs with one copy engine (k4000) are preferable to those with none.
With these GPUs try multithreaded upload, PBOs, and prefetch on in the Render preferences. If the results are not good try turning off multithreaded uploads.
In some cases you may get a GPU to work by increasing the size of the ring buffer. The maximum size for HD formats is 6.

3.5.4 NVIDIA Kepler GPUs on Apple Computers

On Apple computers PBOs with prefetch are also recommended, but multithreaded upload may or may not be helpful. Alternately, using Apple Client Storage (also in the Render tab of the preferences) instead of PBOs may be more beneficial with some GPUs.
RVSDI will use a specialized asynchronous read back scheme on Apple computers (corresponding to the “ppbo” method).
Thunderbolt UltraStudio devices are supported along with DeckLink cards for older Mac Pro desktop machines.

3.5.5 AMD GPUs on Apple Computers

On Apple machines with AMD GPU always use Apple Client Storage (with prefetch) instead of PBOs.
RVSDI will use a specialized asynchronous read back scheme on Apple computers (corresponding to the “ppbo” method).
Thunderbolt UltraStudio devices are supported along with DeckLink cards for older Mac Pro desktop machines.

3.5.6 Intel Graphics on Apple Computers

The Intel 4000 or earlier integrated graphics GPUs are unlikely to work with RVSDI and are not supported.

Chapter 4 Configuring the SDI Device

In the Video preferences tab choose the AJA/Blackmagic video module. Make sure you understand what data and video formats your output device will accept. In the case of stereo, make sure it can use dual SDI outputs — one for each eye.
The AJA hardware can output progressive, interlaced, and progressive segmented frame (PsF) video formats up to 4096x2160 resolution.
image: 2_Users_arasiah_git_tweak-release_rv-cxx98-release-qt4-python2_7_html_temp_images_video_prefs.png
Figure 4.1:
Video Preferences Showing NVIDIA-SDI Configuration
image: 3_Users_arasiah_git_tweak-release_rv-cxx98-release-qt4-python2_7_html_temp_images_latency.png
Figure 4.2:
Latency Configuration Panel With a Manually Added External Frame Latency
Output Module
This should be set to Blackmagic or AJA. If you don't see Blackmagic or AJA as an option you may be using the vanilla rv binary or you don't have SDI hardware drivers installed. Make sure you are using rvsdi on a machine with the proper hardware.
Output Device
In the AJA/Blackmagic case the hardware product name will be displayed for each device detected.
Output Video Format
The video format determines the resolution, frame rate, and whether or not the video scanlines are sent interlaced or progressive. Most projectors will use either a progressive or progressive segmented frame (PsF) format.
Output Data Format
The data format indicates how the the pixels are to be presented to the device. This can include the numerical precision as well as color space (e.g. RGB or YCbCr). The current version of RVSDI can output stereo via dual SDI outputs by choosing the Stereo Dual 4:2:2 data format. This is the only stereo SDI format which we currently support. You can still use the typical anaglyph, side-by-side, and similar formats found under the ViewStereo menu; these will work regardless of SDI data format.
Sync Method
Typically in the scenarios RVSDI is used in this will be set to free running.
Sync Source
If the synchronization can come from an external device it can be configured here. This option will usually change depending on the sync method.
Use as Presentation Device
Check this box to make RVSDI use the SDI device for presentation mode.
Output Audio to this Device
If checked, audio will be packaged as ancillary data in the SDI frames. Otherwise, audio will be output through the selected audio device on the computer. RVSDI currently will output audio data on the first four audio channels. Only a left and right channel is supported and each is duplicated.
Incorporate Video Latency into Audio Offset
If checked, the total latency as indicated in the Configure Latency dialog box will be applied to the audio offset – but only if audio is being played by the controller instead of the output device (i.e. Output Audio to this Device is not checked). This is especially useful with SDI output because the device can have up to five frames of latency. The buffer size can vary over time so RVSDI can measure and automatically add latency to the computer's audio output to aid in keeping audio synced with video. When outputting the audio in the SDI packets directly (Output Audio to this Device) then this is not an issue. If you have additional SDI devices that also buffer frames connected to the output, you may have incorporate that into the total latency in the Configure Latency dialog box.

Issues with Stereo

The SDI device has a single additional stereo mode beyond stereo emulation that rv already has — stereo dual output. This data format outputs the left and right eyes each on its own SDI output.
When using SDI stereo you do not need to set any of the stereo modes under the ViewStereo menu; you should leave this off for most situations.
The ViewStereoHardware mode is not only unnecessary, but can be confusing in this situation. That mode is for use only by the controller window — it has no effect on the SDI output. This mode enables Quad-Buffered Stereo which is only available with Quadro cards connected to 120 Hz or faster DVI or DisplayPort monitors.
The other stereo emulation modes (anaglyph, etc) will function with SDI when not using the dual output format. When the dual stereo output format is selected, the stereo emulation modes will output images for each eye. So for example, anaglyph will output a red left eye image and cyan right eye image for each SDI output. Right and left eye only modes will duplicate the eye on each output.

Chapter 5 Command Line Invocation

You can start RVSDI like this to fully specify
To use the -presentDevice option you could do e.g.:
rvsdi -presentDevice AJA/Kona3GQuad
for the first SDI device.
These can also be set using the prefs by selecting the "Use as Presentation Device" check box.
The -presentVideoFormat and -presentDataFormat will search for a video or data format that contains the passed in string. So for SDI you could do:
rvsdi -presentVideoFormat "1080p 24Hz" -presentDataFormat "Dual"
which would find "1080p 24Hz SMPTE274" as the video format and "Dual 8 Bit YCrCb 4:2:2" as the data format. Some other examples:
rvsdi -presentVideoFormat "720p" -presentDataFormat "4:4:4" 
would be 8 bit 720p 59.94Hz because that is the first 720p format. The first matching data format to 4:4:4 is 8 bit YCrCb 4:4:4. You can be more specific like:
rvsdi -presentVideoFormat "720p 60Hz" -presentDataFormat "10 Bit YCrCb 4:4:4" 
RV will pick the first video or data format that contains the passed in string. These strings are device dependent. Ideally you specify the entire string as it appears in the preferences.
To force audio output:
rvsdi -presentAudio 1
or
rvsdi -presentAudio 0
for no audio.

Chapter 6 Useful RV Features for SDI Output

There are a number of features of RV which are particularly useful with SDI output. RV 4 has added some new ones which can be used to provide fine control over color.

Display Profiles

RV 4 adds the ability to save a display configuration and assign it whenever a certain video device is being used.

Hierarchical Preferences

View station setup

Remote Sync

See user manual

Shotgun Screening Room

Shotgun for dailies