The Teradek Cube 600 series is an SDI, H.264 video encoder. It can encode a video signal from your camera as a 1080p proxy and automatically upload clips into your Frame.io C2C Project.

Use this guide to quickly setup your Teradek Cube 600 series for C2C with settings recommended by Frame.io.

What you'll need

  • 1 Teradek Cube 600 series per camera

  • The latest firmware from Teradek installed on the Cube

  • C2C compatible camera system with SDI record triggers enabled

  • SD card formatted as FAT32 or ExFAT

  • SDI cable

  • A local network with internet access

  • Access to Frame.io or the Frame.io iOS app

  • A Frame.io Project with C2C Connections Integration enabled

  • A Frame.io account with permissions to add devices to the Project

Setup

  1. Power the Cube by connecting it to power and moving the power switch to the On (|) position then connect one end of the SDI cable to an SDI out port on the camera and the other end to the Cube. The Cube will display Initializing Encoder while it boots. Once it says Ready, you can continue with setup.

  2. Connect the Cube to your internet-connected network using the Network Setup menu. The internet is required to pair the device to Frame.io.

  3. Under the Recording Setup menu, check the following settings:

    1. Recording: On

    2. Trigger: Camera

    3. Camera: This should be set to match your camera system. Note: for ALEXA cameras, ARRI should be selected instead of ARRI/Canon.

  4. Under the Video Setup menu, check the following settings:

    1. Input: Auto

    2. Res: Native

    3. Native Framerate: Yes

    4. Bitrate: 3.5Mbps*

  5. Under Audio Setup, set the Audio Source to match your audio configuration.

  6. Finally, pair your Cube to your Frame.io Project by following the prompts in the C2C Connections tab on Frame.io or in the Frame.io iOS app. You can generate the Cube's pairing code under Recording Setup > Frame.io > Pair.

*This is a recommended starting point for the best balance between quality and upload performance. You may want to adjust this based on your needs.

Further configuration is available by using the Cube's WebUI. You can access the WebUI by entering the Cube's IP address into a browser on a computer or mobile device connected to the same local network.

Troubleshooting

My camera isn’t triggering a record on the Cube.

  1. When the Cube 655 is recording, you will see REC in the upper-right corner of the device's display. The WebUI will also say Recording. If you are not seeing these indicators, try the following troubleshooting steps:

  2. Make sure the camera system you are using supports run/stop record triggers and that they are enabled. Click here for more information on Frame.io C2C camera compatibility.

  3. Make sure there are no devices in the video pipeline that may be stripping the record triggers from the SDI stream (this can include certain transmitters, monitors, or other video processing devices).

  4. In the Cube WebUI, make sure Trigger is set to Camera under Recording > Settings.

  5. In the Cube WebUI, make sure Camera is set to match your camera system under Recording > Settings (ie, RED, ARRI Alexa, etc).

  6. Make sure the SD card is formatted, mounted, and has enough free space to record to.

  7. Finally, you can disable and re-enable Recording in the Cube WebUI by going to Recording, selecting Disable, then Apply, then Enable and Apply.

If these steps don’t work, please see Teradek Support or your camera’s documentation for more information.

My Cube isn’t recording clipname or timecode from the SDI stream.

  1. Make sure your camera system supports sending clipname and timecode over its SDI stream. Click here for more information about Frame.io C2C camera compatibility. If your camera system supports both, and you are still not seeing clipname and timecode, try the following troubleshooting steps:

  2. In the Cube WebUI, make sure Camera is set to match your camera system under Recording > Settings.

  3. Make sure Sync Pts. (or Sync Timecode to Video) under SDI Ancillary Data in the Video/Audio Input pane is set to Enabled.

  4. Make sure there are no devices in the video pipeline that may be stripping the record triggers from the SDI stream (this can include certain transmitters, monitors, or other video processing devices).

If these steps don’t work, please see Teradek Support or your camera’s documentation for more information.

I’m not getting audio on my proxies.

If you are attempting to send audio over the SDI from the camera, make sure Embedded is selected under Audio Input in the Video/Audio Input pane in the WebUI. If you are attempting to send audio to the 3.5mm port on the device, make sure Analog is selected. If you are still seeing an issue, make sure the settings for your audio mode match your audio signal. Refer to Teradek Support for more information.

I’m seeing a large delay between the start of my original camera files and the start of my proxies.

To reduce the start delay, you can change the Key Frame Interval setting under Encoding. We recommend setting this between 0.5 and 2.0.

The timecode on my proxies doesn’t match the timecode of my original camera files.

  1. Make sure Sync Pts. (or Sync Timecode to Video) under SDI Ancillary Data in the Video/Audio Input pane is set to Enabled.

  2. Make sure the camera system you are using supports passing timecode through the SDI and that they are enabled. Click here for more information on Frame.io C2C camera compatibility.

  3. If the timecode clock of the camera was changed (such as after a jamsync), you may need to reconnect the SDI to the Cube or reboot it.

Skip ahead to:

Did this answer your question?