OZO LIVE

Setup Guide

Introduction


OZO Live enables the Nokia OZO+ VR Camera to be used for multi-camera live VR broadcasts. A live production studio, OZO Live is a software product. Running GPU-assisted reference hardware, OZO Live converts the compressed 1.5Gb/sec HD-SDI signal from the OZO into a number of formats:

OZO Live provides advanced real-time multi-point stitching functionality, spatial audio processing, color correction, h.264 encoding, H.265 encoding, and a variety of advanced options in a powerful and easy-to-use package.

OZO Live is designed for professional broadcast production use, supporting three primary deployment modes:

  1. Single-camera workflow with direct RTMP uplink
  2. Single-camera workflow to a single external broadcast encoder
  3. Multi-camera workflows with full production switching and sound reinforcement.

OZO Live is available under three licensing agreements:

  1. Free
  2. Single node
  3. Multi node

Users with a Multinode license will have access to the Multiview

Hardware Specification

Disclaimers

OZO Live has significant demands on GPU, CPU and memory bandwidth. Both hardware and software are subject to frequent updates, and configuration problems will likely cause errors in software operation. We recommend the use of certified hardware with specified drivers. OZO Support cannot provide assistance with configuration issues caused by nonstandard hardware or drivers.

OZO Live runs on Windows 10 and on Ubuntu 16.04 LTS. The installation and configuration of OZO Live in Ubuntu requires familiarity with Linux system integration, up to and including the compiling of drivers from the source. If you do not have this expertise within your organization, we recommend the purchase of a pre-built Certified OZO Live system from one of our partners. Contact OZO sales for a list of OZO Live system integration partners.

We have tested multiple configurations of these machines, and list those below.

These specifications are current as of September 25, 2017, but may change at any time. We are committed to providing best-of-breed performance, and as a result future OZO Live releases may make a previously-specified machine obsolete or in need of extensive upgrade.

OZO Live Machine HW Specification

OZO Live runs under numerous configurations, depending on your budget and production needs. Please read the following tables to see which might work for you.

The Professional Broadcaster Configuration


A rackmount server configuration ensures that your setup is reliable and robust.

This configuration will support all OZO Live 2.x features.

Be sure to build your system with excellent cooling capabilities. As one of most important factors to ensure a stable system, efficient cooling also extends the lifespan of your system.

Required Components

GPU alt11 GTX 1080 Ti, 11GB RAM.
GPU alt21 Titan X Pascal or Titan Xp, 12GB RAM.
GPU alt32 GTX 1080 or better, 8GB of RAM in each card minimum. If Windows 10, will also run Creator.
PCIe slotsPCIe 3.0 x16 slots for each GPU installed, with GPUDirect preferably enabled using the most direct path traversal.
CPUIntel Core i7, Core i9 X-series or Intel Xeon, Quad core or better, 40 PCIe lanes or more, 2.8 GHz or more
RAM16 GB, DDR4, 2133 GHz or better
Disk256 GB SSD or better. The more, the better.
Network requirements1 Gbps or better
SDI Connectivity over PCIe2 BlackMagic Decklink SDI 4K or alternativly 1 AJA Corvid-88 (for 59.94 or 60 FPS output) and 1 BlackMagic Decklink Mini Recorder 4K (for camera input)
Power SupplyDual power supplies for redundancy
OSUbuntu 16.04 LTS or Windows 10 Pro 64bit

Optional Components

Dante Audio over Ethernet can provide up to 128 audio channels over dedicated Ethernet port in the PCIe card.

Recommended Dante Audio on Linux:

Recommended Dante Audio on Windows:

Recommended for future upgrade ability:

Keep room for 2 16-lane PCIe slots for full length GPU cards.

10 Gbps network port. Either on motherboard or as PCIe card.

The Cost-Efficient Configuration


If based on a PC Tower/Workstation form factor, this is the most cost efficient configuration for OZO Live. Some suggested alternatives will not support all OZO Live 2.x features.

Be sure to build your system with excellent cooling capabilities. As one of most important factors to ensure a stable system, efficient cooling also extends the lifespan of your system.

Required Components

GPU alt11 GTX 1070 or GTX 1080, 8GB RAM (see note about limited functionality)
GPU alt21 GTX 1080 Ti or better, 11GB RAM or better. Does support all OZO Live 2.0.1 features.
GPU alt32 GTX 1080 or better, 8GB of RAM in each card minimum. If Windows 10, will also run Creator.
PCIe slotsPCIe 3.0 x16 slots for each GPU installed, with GPUDirect preferably enabled using the most direct path traversal.
Other PCIe slotsEnough slots to accommodate all other PCIe cards
CPU6th or 7th generation Intel Core i7 or Core i9 X-series processors
CPU alt1i7-7700K + Z270 (cheapest)
CPU alt2i9-7900X + X299 (recommended for dual GPU setup)
RAM16 GB, DDR4, 2133 GHz or better
Disk256 GB SSD or better. The more, the better.
Network1 Gbps or better
SDI Connectivity over PCIe2 BlackMagic Decklink SDI 4K
OSWindows 10 Pro/Home 64bit

Note about using single GTX 1070/1080 GPU configuration

A single GTX 1070 or GTX 1080 will run OZO Live but will give a somewhat limited features:

Optional Components

Recomended Dante Audio on Windows:

Additional supported alternatives

SDI connectivity alternatives

SDI connectivity over Thunderbolt 2 (for a Windows laptop configuration)

SDI Connectivity over PCIe cards

SDI output is not needed if only using IP based output.

External audio connectivity alternatives

Dante is recommended for multinode camera configurations.

Other audio alternatives

Operating system alternatives

OS: Windows 10 Pro or Home, 64bit. Pro is Recommended (home does not give Remote Desktop support)

Ubuntu 16.04 LTS

Windows Configurations Quick View

The following applies to PCs running 2.0.1 for Windows.

Supported Operating System:Windows 10 Pro
Supported HardwareCPU: Intel Quad Core i7
RAM: 16 GB
For maximum performance: NVIDIA GTX 1080 (X 2)
For limited performance: NVIDIA GTX 1080 (X 1)
Blackmagic Recorder:
  • Blackmagic DeckLink Mini Recorder PCIe card (install in desktop)
  • Blackmagic DeckLink Mini Recorder 4K PCIe card (install in desktop)
  • Blackmagic UltraStudio Mini Recorder (Thunderbolt™ 2)
  • Blackmagic HyperDeck Studio Pro (Thunderbolt™ 2)
  • BlackMagic UltraStudio 4K (Thunderbolt™ 2)

Apple Thunderbolt™ 3 (USB-C) to Thunderbolt™ 2 Adapter or
StarTech Thunderbolt™ 3 to Thunderbolt™ Adapter (TBT3TBTADAP).
Wi-Fi antenna
Software requirementsThe latest Nvidia drivers installed
Blackmagic Desktop Video 10.9.7
Optional: Blackmagic Hyperdeck 5.1 pdate (for use with the Hyperdeck Studio Pro)
For CV1 - Oculus App; For HTC Vive – Vive Setup Tool and Steam VR
Windows power management set to High Performance
Nvidia power management set to Maximum

The following applies to Laptops running OZO Live 2.0.1 for Windows

Supported Operating System:Windows 10 Pro
Supported HardwareCPU: Intel Quad Core i7
RAM: 16 GB
MSI GT83VR SLI laptop with dual GTX 1080 8GB
Blackmagic Recorder:
  • Blackmagic UltraStudio Mini Recorder (Thunderbolt™ 2)
  • Blackmagic HyperDeck Studio Pro (Thunderbolt™ 2)
  • BlackMagic UltraStudio 4K (Thunderbolt™ 2)

Apple Thunderbolt™ 3 (USB-C) to Thunderbolt™ 2 Adapter or
StarTech Thunderbolt™ 3 to Thunderbolt™ Adapter (TBT3TBTADAP).
Wi-Fi antenna
Software requirementsThe latest Nvidia drivers installed
Blackmagic Desktop Video 10.9.7
Optional: Blackmagic Hyperdeck 5.1 pdate (for use with the Hyperdeck Studio Pro)
For CV1 - Oculus App; For HTC Vive – Vive Setup Tool and Steam VR
Windows power management set to High Performance
Nvidia power management set to Maximum

Selecting Dual GPU Motherboards

When you are selecting a motherboard or barebone system for OZO Live, in order to ensure the system can accomodate two dual-width GPU cards and work at best performance, please consult the user manual of your motherboard or barebones system. Most manufacturers provide very detailed user manuals on their web sites.

The block diagram in the manual will help you identify 2 x16 (16-lane) PCIE gen3 slots where the GPU cards can sit. Additionally you need to check the dimensions of motherboards to confirm your GPU cards have enough physical clearance along with SDI I/O cards.

The following block diagram shows the bus layout of a typical dual XEON motherboard.

In the example diagram, there are three x16 (16-lane) PCIe Gen 3 slots: PCIE1, 3 and 6. In order to maximize the performance, we should use PCIe slots under same CPU which are PCIE1 and 3 in this case. Although PCIE6 is x16 PCIe slot, we cannot use that for a GPU, since that will make GPUs communicate over CPU-to-CPU channel which is sub-optimal.

Once PCIe slots for GPU cards are chosen, check the layout/dimension diagram in the user manual to verify the clearance for dual-width GPU cards and spaces for SDI cards.

The example diagram shows that the slots for GPUs (PCIE1 and PCIE3) are spaced enough for dual width GPU cards. Since the two GPU cards will occupy the spaces for PCIE2 and 4, the only slots available for SDI cards are PCIE5 and 6.

Configuration and Setup

OS Configuration and Setup for Ubuntu 16.04 LTS


1. Install Ubuntu 16.04 LTS - 64bit PC (AMD64) Server install image

WARNING: YOU MUST BE CONNECTED TO THE INTERNET FOR THE FOLLOWING SERIES OF COMMANDS TO WORK.

You can download and install Ubuntu fromhttp://www.ubuntu.com/download/server.

During the installation, you will be asked the automatic update option. It is important to choose "No automatic updates" which is the default selection; otherwise the Ubuntu kernel will update itself automatically, which may cause system instability.

In Software Selection page, choose "OpenSSH server"

If you missed the above steps, please use following command after installation in order to disable the automatic updates and install ssh server package.

$ sudo apt remove unattended-upgrades
$ sudo apt-mark hold linux-signed-image-generic
$ sudo apt install openssh-server

Take a note of ip address of the machine. Static IP address may be pre-configured in the dhcp server in router. You can find the ip address of the machine with following command.

$ hostname -I

2. Disable GUI login

Ubuntu may install with the GUI enabled. If this is the case, follow these steps to disable the GUI before installing OZO Live.

During Ubuntu boot, pressCtrl+Alt+F1to switch to console mode, and login with the account that was set up during the Ubuntu installation Edit the Grub configuration located in /etc/default/grub:

$ sudo vi /etc/default/grub

Change the value ofGRUB_CMDLINE_LINUX_DEFAULTtoGRUB_CMDLINE_LINUX_DEFAULT="text"

Update GRUB

$ sudo update-grub

Tell systemd not to load the GUI:

$ sudo systemctl enable multi-user.target --force
$ sudo systemctl set-default multi-user.target

3. Install dependent packages

OZO Live depends on several third-party packages. Install them using the commands below.

$ sudo apt-get install libzip4 libpng12-0 libjpeg8 libjasper1
$ sudo apt-get install openjdk-8-jre

After installing openjdk-8-jre run the following command to fix dependencies

$ sudo apt-get install -f

4. Install Nvidia driver

You need to install Nvidia drivers in order to support OZO Live's requirements. Please run the following commands:

$ sudo add-apt-repository ppa:graphics-drivers/ppa -y
$ sudo apt-get update

Upgrading to the latest Nvidia driver is highly recommended, to uninstall the old driver:

$ sudo apt-get purge nvidia-*

Install the Nvidia driver:

$ sudo apt-get install nvidia-384

Reboot the system and check the installation

$ nvidia-smi

Thu Sep 21 02:30:01 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.69                 Driver Version: 384.69                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX TIT...  Off  | 0000:02:00.0     Off |                  N/A |
| 22%   38C    P0    70W / 250W |      0MiB / 12206MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX TIT...  Off  | 0000:03:00.0     Off |                  N/A |
| 22%   43C    P0    72W / 250W |      0MiB / 12206MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                              
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

5. Installing GPU cards

Be sure that GPU cards are installed in PCI Express slots running at 3.0 x16 mode. Check your motherboard manual to confirm PCIe operating mode for each slot configuration.

You can verify the GPU PCIe link info by running

$ nvidia-smi -q

...
GPU Link Info
  PCIe Generation
    Max                 : 3
    Current             : 3
  Link Width
    Max                 : 16x
    Current             : 16x
...

Some motherboards also have more than one I/O hub. In order to achieve the best performance we recommend that GPU cards be installed in PCIe slots attached to the same host bridge.

You can verify it by running

$ nvidia-smi topo -m

       GPU0    GPU1    CPU Affinity
GPU0     X     PHB    8-15,24-31
GPU1    PHB     X     8-15,24-31
 
Legend:
 
  X   = Self
  SOC = PCI path traverses a socket-level link (e.g. QPI)
  PHB = PCI path traverses a host bridge
  PXB = PCI path traverses multiple internal switches
  PIX = PCI path traverses an internal switch
  NV# = Path traverses # NVLinks

The example shows two GPU cards are connected via the same host bridge. If you see SOC in the output matrix, please consider rearranging the GPU slots.

6. Install Blackmagic driver

If you are using Blackmagic PCI cards for SDI input or output, you must install the Blackmagic driver. Download it from https://www.blackmagicdesign.com/support/family/capture-and-playback

You may need to install the dkms package:

$ sudo apt-get install dkms

Install the latest Desktop Video software.

$ tar xf Blackmagic_Desktop_Video_Linux_xxx.tar.gz
$ sudo dpkg -i Blackmagic_Desktop_Video_Linux_xxx/deb/amd64/desktopvideo_xxx_amd64.deb
$ BlackmagicFirmwareUpdater status

0:    (null) [/dev/blackmagic/io0]    0x41d7ca    PLEASE_UPDATE

$ BlackmagicFirmwareUpdater update 0

/dev/blackmagic/io0 firmware update completed successfully.
Please reboot your system now to activate new firmware

7. Install AJA driver

If you are using an AJA PCI card for SDI output, you must install the AJA driver. Download v12.4.1.1 Linux driver from the AJA website, and build according to the instructions. It is important to download this specific version. (e.g. v12.3.x doesn't work with OZO Live.)

Driver request page:https://www.aja.com/en/support/drivers/linux

Compile the driver with following commands:

$ unzip ntv2linux-driver-12.4.1.1.zip
$ tar zxf ntv2linux-driver-12.4.1.1.tar.gz
$ cd ntv2linux-driver-12.4.1.1/ntv2projects
$ make

Install the driver files:

$ sudo mkdir -p /opt/aja/bin
$ cd ..
$ sudo cp bin/* /opt/aja/bin

Check the installation with following commands:

$ cd /opt/aja/bin
$ sudo ./loadOEM2K

After installing OZO Live, see Install OZO Live, follow the instructions below to automatically load AJA drivers on boot.

$ sudo cp /opt/nokia/ozo_live/bin/aja-devices /etc/init.d/
$ sudo ln -s /etc/init.d/aja-devices /etc/rc2.d/S01aja-devices $ sudo chmod a+x /etc/init.d/aja-devices

Reboot the system and check if driver loaded automatically without error.

$ dmesg | grep oem2k0

<snip>
[    6.486557] oem2k0: Registered IRQ 0x78, dev_id ffffc9000b001000
[    6.486557] oem2k0: probe(): setup IRQ types
[    6.489180] oem2k0: Programmed Video FPGA with bit file built on 2016/02/16 at 17:45:42
[    6.489180] oem2k0: Successfully probed CORVID88
[    6.489182] oem2k0: PCI Version 0x20

You should see log message from "oem2k0"

If you have older firmware, please upgrade it. You may need to contact AJA support for the latest firmware and instruction for update.

8. Install Four-Audio Dante PCIe Linux kernel driver

If you are using Four-Audio dante PCIe card for Dante based audio input and output you have to install the card physically to the OZO Live server and then install the drivers.

With Four-Audio Dante cards the IOMMU needs to be disabled

$ sudo vi /etc/default/grub

Change the value of

GRUB_CMDLINE_LINUX_DEFAULT="text"

to

GRUB_CMDLINE_LINUX_DEFAULT="text iommu=off"

Remember to update and reboot:

$ sudo update-grub
$ sudo shutdown -r now

Find out the Linux kernel version

$ uname -r
4.4.0-66-generic

Request the driver for the specific kernel version (in this case 4.4.0-66) you are using by email from info@four-audio.com

Unpack, read the instructions, and install the received Dante PCIe kernel module

$ tar -xzf dante_pcie_4.4.0-66.tar.gz
$ cd 4.4.0-66
$ less README.txt
$ sudo make install
$ sudo depmod -a

You should verify that your account belongs to group audio by

$ id -nG "$USER"|grep -c "audio"

If the answer is 1, then you are already in the group but if answer is 0 then you should add your user to the audio group

sudo usermod -a -G audio $USER

You should verify now that the Dante card is usable and works by

$ aplay -L | grep DantePCIe

<snip>
aplay -L | grep DantePCIe
sysdefault:CARD=DantePCIe
DantePCIe, DantePCIe PCM
dmix:CARD=DantePCIe, DEV = 0
DantePCIe, DantePCIe PCM
dsnoop:CARD=DantePCIe, DEV = 0
DantePCIe, DantePCIe PCM
hw:CARD=DantePCIe, DEV = 0
DantePCIe, DantePCIe PCM
plughw:CARD=DantePCIe, DEV = 0
DantePCIe, DantePCIe PCM

If aplay is not installed in your machine, install it with

$ sudo apt-get install alsa-utils

You should also test that from command line prompt you are able to record through the Dante card five seconds of audio through two first channels. If you want to record something else than silence, make sure that you have connected audio sources to the two first input channels of the card.

$ arecord -v -M -D hw:CARD=DantePCIe,DEV=0 -f S24_LE -r 48000 -c 2 -d 5 -I 1.wav 2.wav

If the recording gets stuck, and the arecord command does not return after 5 seconds (-d 5), please see troubleshooting note below about Message Signaled Interrupts.

Troubleshooting Dante driver installation: Manual copying of the kernel module

If for some reason the installation does not succeed, or Dante driver is not automatically loaded during the next system reboot, you should manually copy the kernel driver to a location from where the module can be installed at boot time. The following command assumes your working directory is where you unpacked the *.tar.gz during the previous steps.

$ sudo cp dante-pcie.ko /lib/modules/`uname -r`/extra/

Add dante-pcie to /etc/modules-load.d/modules.conf as follows:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored
dante-pcie

$ sudo depmod -a
$ sudo shutdown -r now

Troubleshooting Dante driver installation: PCI Message Signaled Interrupt problem

Message Signaled Interrupts is a method of signaling an interrupt using a shared interrupt line. With some HW configurations MSI does not work properly between Dante and NVidia drivers. One symptom of this is hanging of 'arecord' command. In this case you should also notice pop up of "No irq handler for vector" message into the system log during execution of the 'arecord' command. Use second command prompt terminal to see this.

$ dmesg -w

do_IRQ: 1.164 No irq handler for vector

One workaround is to force the Dante card kernel module to load as the last module:

  • Add 'blacklist dante_pcie' to the file /etc/modprobe.d/blacklist.conf
  • Add 'modprobe dante-pcie' to /etc/rc.local
  • Reboot and check whether the 'arecord' command now works properly.

    $ sudo depmod -a
    $ sudo shutdown -r now
    $ arecord -v -M -D hw:CARD=DantePCIe,DEV=0 -f S24_LE -r 48000 -c 2 -d 5 -I 1.wav 2.wav

    8. Usage of Spatial Audio Mixer with ALSA sound cards

    Usage of spatial audio mixing capabilities of OZO Live ALSA compatible USB sound card. Simply, connect the powered USB sound card to OZO Live machine. The sound card will be available as input for sound sources and as output for your spatial mixes. You need to restart the pipeline service for OZO Live to detect the USB sound cards.

    $ sudo service ozo-live-pipeline restart

    Note on kernel upgrade:

    Whenever the Ubuntu kernel is upgraded, either automatically or manually, the AJA driver and Four-Audio Dante PCIe drivers are invalidated. Since AJA doesn't provide automatic installer or DKMS (dynamic kernel module support), the AJA driver must be recompiled and reinstalled using the instructions above after any kernel upgrade. You must also request Dante driver for your new kernel version from info@four-audio.com.

    OS Configuration and Setup for Windows 10 (64bit)

    Ozo Live services can be installed in any vanilla Windows 10 systems with a few dependencies.

    1. Install Blackmagic driver

    If you are using Blackmagic PCI cards or Thunderbolt devices for SDI input and output, you must install the Blackmagic driver. Download it from:
    https://www.blackmagicdesign.com/support/family/capture-and-playback

    2. Install AJA driver

    If you are using an AJA PCI card for SDI output, you must install the AJA driver. For compatible Kona devices, download the latest Windows driver from the AJA website:
    https://www.aja.com/products/kona-4#support.

    For AJA Corvid devices, the driver is shipped with the AJA ntv2 SDK, please contact AJA support for access. We recommend using the latest release version of 13.0.0.

    3. Install Nvidia driver

    You need to install the latest Nvidia drivers in order to support OZO Live video streaming. Download official Nvidia driver releases from:
    http://www.nvidia.com/Download/index.aspx

    Nvidia driver can be easily updated via the Geforce Experience application installed with the previous driver.

    To verify proper GPU configuration via the command line, "nvidia-smi" is installed under "C:\Program Files\NVIDIA Corporation\NVSMI".

    4. Install Java

    OZO Live depends on Java. Get the latest from here:
    https://java.com/en/download/

    5. Install Dante Driver

    Follow the installation instructions of your Dante PCIe card. If you have selected to use Dante Virtual Sound card, please install the software and configure it to use one of your computer's open Ethernet interfaces.

    You can use any professional hardware sound cards. There are many Dante-capable cards on the market by manufacturers such as Focusrite and Yamaha. At the time of this writing, Windows Drivers for the Four Audio Dante PCIe sound card are not available. (We are working with the manufacturer to enable a Windows driver as soon as possible. Stay tuned).

    OZO Live Windows supports devices that are accessible through WASAPI and ASIO interfaces. In practice, these two options cover all Windows-compatible sound devices.

    We have tested the Dante Virtual Soundcard (DVS) by Audinate. This driver turns a standard dedicated Ethernet connection into a Dante-enabled sound card.

    As of this writing, you can purchase a DVS from Audinate.

    Installing OZO Live

    Live Server supports both Ubuntu 16.04Ubuntu 16.04 or Windows 10

    Installing OZO Live for Ubuntu

    Copy the package file to your server

    To install OZO Live when not online, use a USB stick to copy the deb file to your hard drive.

    1. Make sure you are using a USB stick formatted as FAT32. (By default, Ubuntu doesn’t support exFAT.)
    2. Copy the deb file to the USB stick.
    3. Plug the USB stick onto the streamer machine.
    4. Use following step in the OZO Live machine to mount the USB stick and copy the file:

    $ dmesg

    You should see output similar to the following:

    [82807.081078] sd 6:0:0:0: Attached scsi generic sg1 type 0
    [82807.081234] sd 6:0:0:0: [sdb] 15728640 512-byte logical blocks:
    (8.05 GB/7.50 GiB)
    [82807.081370] sd 6:0:0:0: [sdb] Write Protect is off
    [82807.081372] sd 6:0:0:0: [sdb] Mode Sense: 0b 00 00 08
    [82807.081489] sd 6:0:0:0: [sdb] No Caching mode page found
    [82807.081858] sd 6:0:0:0: [sdb] Assuming drive cache:     write through
    [82807.103226]  sdb:
    [82807.103947] sd 6:0:0:0: [sdb] Attached SCSI removable disk

    Find the drive name for your removable disk; in this case it is myusb;


    /mnt is created to mount your USB

    $ sudo mount /dev/myusb /mnt
    $ cp /mnt/OZOxxx.deb ~/

    If the machine is connected to a network, transfer the file over IP:

    Find the IP address of OZO Live machine.

    $ ifconfig

    You can check the DHCP lease log in router or you can use ifconfig or the following command to find from the machine:

    $ hostname -I

    192.168.96.103

    In this case, the ip address is 192.168.96.103

    Use the following command from your PC to copy the deb file:

    $ scp OZO-Live-xxxx.deb nokia@192.168.96.103:/home/nokia

    Installing the OZO Live package

    The OZO Live application is delivered as a Debian package. You need to run following command to install:

    $ sudo dpkg -i OZO-Live-xxx.xxxx.xx-Linux.deb

    All the related files will be installed under/opt/nokia/ozo_live

    Take time to review release notes located in/opt/nokia/ozo_live/ReadMe.txt

    In some cases, an upgrade may require that you update dependencies, such as device drivers. Check the release notes for these requirements, but if you get an error for a dependency please install/update the dependent packages.

    As an example, an installation without properly installed GPU drivers might provide an error similar to the following:

    $ sudo dpkg -i OZO_Live-20160713.1249-Linux.deb

    (Reading database ... 129937 files and directories currently installed.)
    Preparing to unpack OZO_Live-20160713.1249-Linux.deb ...
    Unpacking ozo_live (20160713.1249) over (20160713.1249) ...
    dpkg: dependency problems prevent configuration of ozo_live:
    ozo_live depends on nvidia-381; however:
    Package nvidia-381 is not installed.
    dpkg: error processing package ozo_live (--install):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:
    ozo_live

    In this case please refer to the Nvidia Driver installation instructions in:  Configuration and Setup  and retry the installation after installing the required drivers.

    Once you have completed a successful installation, reboot the system. OZO Live will start automatically.

    OZO Live runs as two separate services: a core processing service, which performs the video and audio pipeline service, and a web service, which presents a graphical user interface to any browser.

    Both services start automatically on system boot; the GUI operates as a service (ozo-live-web) running on standard HTTP port 80, which communicates with the core service (ozo-live-pipeline) using port 3000.

    Please note: After installing OZO Live 2.0.1 and loading the web interface, some browsers (particularly Chrome) return an "Error Loading Page." In this instance, please just clear the cache and reload the web interface.

    Uninstalling OZO Live

    If you want to remove OZO Live from the system, use the following command.

    $ sudo apt remove ozo_Live

    Installing OZO Live for Windows


    Before you start, please ensure you have installed Java. If not, the OZO Live installer will prompt you to do so:

    Once Java is installed, simply follow the OZO Live installation dialogue boxes:

    OZO Live is installed in your system within "C:\Program Files\Nokia OZO" along with other OZO ecosystem applications.

    OZO Live pipeline and web services start automatically after installation.

    Uninstalling OZO Live

    Uninstall OZO Live either from the Control Panel -> Program and Features, or by invoking the "uninst.exe" you'll find within the OZO Live installation folder.

    OZO Live Windows specifics

    Interoperability with other applications

    OZO Live releases hardware resources when idle and not streaming.

    Before starting your stream, however, we highly recommend closing other applications such as OZO Creator, OZO Remote, or any other applications that heavily utilize the GPU.

    Working with OZO Remote, and OZO Live on the same System

    The release of OZO Live for Windows allows the user to use OZO Remote, OZO Creator, and OZO Live on the same system. However, as some hardware resources such as GPUs and SDI input devices are shared among these applications, it's a good idea to close one before starting another.

    Here are a couple workflow suggestions.

    1. Stop OZO Live pipeline from the web UI
    2. Launch OZO Remote
    3. Set exposure, color temperature, etc.
    4. Close OZO Remote
    5. Restart OZO Live pipeline from the web UI

    Please note that you will have to stop the stream before using OZO Remote.

    An alternative might be:

    1. Open OZO Remote
    2. Open Preferences
    3. Choose Other -> Disable preview and SDI. (this releases GPU resources and disables SDI).
    4. Restart OZO Remote

    This will allow you to use OZO Remote wirelessly, while using OZO Live for preview and broadcast.

    Troubleshooting failure to start stream

    If OZO Live fails to start, and returns error messages related to missing input and/or output devices. You may verify I/O device installation using the native Windows device manager, as shown below. Devices can be found under Sound, video and game controllers.

    If any attached PCI Express or Thunderbolt devices are not listed, or are shown as installed properly when they're causing a problem, try rebooting the system. If those solutions do not work, reinstall device drivers and update the device firmware if required.

    While you may also verify valid SDI input sources by using other applications such as Blackmagic Media Express or OZO Remote, ensure that all your software versions and drivers are up to date.

    Thunderbolt 3 support

    Host computers with Thunderbolt 3 ports can connect to Blackmagic devices, such as UltraStudio Mini Recorder, UltraStudio 4k and HyperDeck Studio Pro.

    Before connecting to your device, download and install the latest drivers from either your laptop or motherboard manufacturer's website. (As of this writing, driver support for Thunderbolt 3 is limited to Windows 10.)

    Unlike USB devices, users must manually authenticate Thunderbolt 3 devices before the system will recognize them.

    1. When first connecting a Thunderbolt 3 device, you should see an automatic notification above the system tray notifying a new device has been attached, click OK to proceed.
    2. If a Windows User Account Control pops up asking to allow this app to make changes to your PC, click Yes.
    3. To approve the device you just connected, select Always Connect from the drop-down menu, click OK.

    Verify newly-attached devices, and manage approved devices by accessing the Thunderbolt Software icon in the system tray.

    Please allow for up to 5 seconds for OZO Live to discover a newly attached Blackmagic input/output device via Thunderbolt.

    If the icon is not listed in the system tray, search the Start menu for Thunderbolt to open it manually. Also, if the attached device is not listed (this is a known issue when detaching and re-attaching a Blackmagic device via Thunderbolt), you will need to restart Windows and re-verify.

    Manually control OZO Live Services

    Though OZO Live services start automatically when Windows starts, you can start, stop or restart services manually in Windows Task Manager -> Services, or by running the local Services application, as shown below.

    Licensing OZO Live

    License Activation


    Without an active license, OZO Live installs and runs with full functionality, but watermarks the output video and audio. Audio watermark is a morse coded message on the audio tracks. To remove the watermark and validate the ability to use OZO Live for commercial broadcasts, you must apply an Activation Key.

    The turnaround for this license can be as long as 72 hours, so make sure you don't wait until production day to request your Activation Key!!

    Requesting Activation Key

    Open a web browser and go to http://<ip address of OZO Live machine>/, then click "System" on the left panel. You will see a screen like the following image.

    Clicking the "REQUEST ACTIVATION KEY" button opens this instruction window:

    Download the identifier file: "ozo_live.license_request".

    Email this file to OZOsupport@nokia.com with the reference to your purchase order number. The OZO Support team will validate your purchase and provide an Activation Key within 72 hours.

    Installing Activation Key

    Once you get an ozo_live_<anything>.licfile from OZO Support, open a web browser and move to "Settings" page. Click "add activation key" button and point to the Activation Key file that you saved from email.

    The Activation Key will be stored and validated.

    Additional Support

    Should you need additional support, press the "Download Report" button in the System tab. Email the downloaded report to OZOsupport@nokia.com

    Support

    System Alerts

    The system screen gives you access to support, additional features, system reset, licensing, etc.

    Logs

    The entire OZO team wants to make sure your experience with OZO Live is awesome. We are ready to help, and are eager for your feedback.

    OZO Live Forum


    The OZO Live Forum is a place for OZO Live users and partners to exchange information. It may be found as part of the "Support and Community" section of the Nokia OZO website, at http://support.ozo.nokia.com/

    Support


    Registered users of OZO may access the OZO Support team via email at OZOsupport@nokia.com or online form at https://ozo.nokia.com/ozo_en/contact/. Customer support requests will be responded to within 24 hours.

    It helps the whole community if you report any issues you find with OZO Live. Please run following command in the folder that you ran the ozo_live application.

    $ sudo /opt/nokia/ozo_live/bin/report.sh

    Or go to the System Tab and click Download Report:

    Report_201610281154.txt.gz is generated, please attach the file in the support request

    You will see report_xxxx.txt.gz in the same folder. Attaching this file to your support request will help the support team diagnose your issue quickly and efficiently.

    Legal Information

    OZO Live ships with both third-party and open source software. A listing of the open source software and the accompanying license terms is included with the software package. Please press the "Licensing Terms" button in the System tab to read the applicable license terms.

    Your use of the Licensed Software is only permitted if you comply with the terms and conditions of the open source software licenses.

    Copyright © Nokia Technologies Ltd. and/or its subsidiary(-ies).

    This OZO Live software, including the accompanying documentation, is protected by copyright controlled by Nokia Technologies Ltd. All rights reserved. Unless you have signed an individually negotiated license agreement with Nokia, the license terms applicable to your use of this software are available at:

    The OZO Live Software agreement is available at https://store.ozo.nokia.com/media/custom/upload/OZO_Live_Terms_and_Conditions_EN.pdf

    If you have signed an individually negotiated license agreement with Nokia, the terms contained in that license agreement shall govern your use of this software.

    About

    OZO Live is developed by a highly dedicated and skilled team of people. Contributions have been made by, in no particular order: