Merging Technologies systems are normally part of a greater connection of equipment, potentially spanning a variety of Merging products, or connecting with the rest of a studio. This section is an information FAQ concerning the ways in which we have validated our systems to be connected, as well as a clear statement as to what you should and should not do in order to configure a stable and synchronous setup.

Please have a look at the chart below in order to determine the ASIO and Core Audio driver (Virtual Audio Device) compatibility with your OS.

These are all PREMIUM versions of the installer, intended for use with a Horus or Hapi. If you are looking for the STANDARD OSX AES67 Virtual Audio Device see here.

ASIO

Windows 7 32 bits ASIO driver 9.x 32 bits
Windows 7 64 bits ASIO driver 10.x and following
Windows 8 32 bits Not supported
Windows 8 64 bits ASIO driver 10.x and following
Windows 10 32 bits Not supported
Windows 10 64 bits Pending - Driver to be available in 2017

Virtual Audio Device(Core Audio)

Mac OS X Mountain Lion 10.8.5 Core Audio driver v2.0.23923
Mac OS X Mavericks 10.9 Core Audio driver v2.0.23923
Mac OS X Yosemite 10.10 Virtual Audio Device v2.0.30072
Mac OS X El Capitan 10.11 Virtual Audio Device v2.0.30072
macOS Sierra 10.12 Pending - Driver to be available in 2017

Please have a look at the flow chart here in order to determine the best way in which to connect your VCube to ensure frame accuracy without any possibility of drift.

Please view the Flow Chart below to see how best to upgrade your VCube system dependant on your workflow and what you are trying to achieve with your system.

Please view the Flow Chart below to see how best to upgrade your VCube system dependant on your workflow and what you are trying to achieve with your system.

1FS (44.1 – 48 kHz): 2 video streams
2FS (88.2 – 96 kHz): 2 video streams
4FS (176.4 – 192 kHz): 2 video streams
8FS (352.8 – 384 kHz): 1 video streams
DXD & DSD64/128/256: 1 video streams

There are a number of optimization changes to be made to the Windows operating system when running Merging Technologies software. For more in depth coverage please consult the Windows Configuration Guide

Increase Scheduling Priority

As RAVENNA uses network connections in order to transport hundreds of realtime audio streams, it will be a good idea to ensure that the rest of computer is managing its other network needs in a way that will not interfere with RAVENNA.

For full information about networking with RAVENNA, please consult the Ravenna Networking Guide

Connecting “Other” networks to the Merging system

  • Ensure that the other networks do not sit on the same subnet as the RAVENNA network
  • Do not connect your RAVENNA connections through networks which are also carrying internet or LAN traffic, use a dedicated network for your RAVENNA streams.

Configuring IP addresses for Merging RAVENNA equipment

Merging Technologies recommends that unless you have a specific requirement, that you leave all of your RAVENNA equipment in auto-assign mode. If you set static IP addresses, everything will work, but you have then the potential of operator error at a number of points depending on how the system may change over time. As well, the maintenance modes of the hardware interfaces requires auto-assigned IP addresses to work. So, if you did set static IP addresses, you would have to undo it all every time you wanted to update the firmware.

  • This will work fine with a switch that gives out IP addresses as well as if two devices are connected together without a switch.
  • If you are using a switch that gives out IP addresses, make sure that it is configured to use a different subnet than any of the other networks you may have connected to the computer.

What type of Switches can be used with RAVENNA networks?

Only managed switch are suitable for RAVENNA networks, and Merging has tested and validated DELL PowerConnect 2808 and 2816. Merging cannot guarantee that it will work with any other switch, so to be sure of seamless operation please consult your local Merging representative to get a unit for your setup.

Please refer to the Ravenna Networking Guide for more information

When configuring Virtual Transport 2 (VT2) for use in synchronizing multiple Merging software applications there are a few things to make sure are set for seamless operation.

Note: To ensure VT2 is operational you must have the same version (build number) of VCube and Pyramix. To check this you can click on Help>About… in the drop down menus of both applications and take not of the long number at the end of the version listing i.e. version 6.0.6 b28769

Pyramix & VCube on the same system (PyraCube)

  • In VS3 Control Panel
    • Set Pyramix to be ASIO Host Mode with 8 channels
    • Set VCube to Native Platform
    • Set VCUbe to MTASIOBridge for the driver
  • In Pyramix and VCube ensure that the audio buffer is set to 256 samples

This setup will then ensure that VCube uses the same clocking engine as Pyramix for its timing and will thus maintain sync properly.

Pyramix and VCube on separate computers

  • Ensure a common video reference for Pyramix and VCube

Other than the above, there are no special considerations to be made when operating Pyramix and VCube on separate systems.

How to use VT2 if you do not have an active network connection

If you do not have an active network connection, then VT2 will not be able to activate as it requires the use of an active network port. In this case, you can follow these intructions to create a Virtual Network Card

Download the instructions here

4K playback is a big strain for today’s PC systems. So, if are going to start using this feature of VCube 6, then you will need to ensure your computer is up to the job.

Requirements for 4K playback in VCube

  • SSD hard drives for video storage
  • i7 CPU as a minimum