Vision Apps User Guide
Multi Camera + Codec Application

Table of Contents

Introduction

This application demonstrates the use of Hardware Codec along with Capture and Display in multichannel mode. This is an extension of the Multi Camera VPAC Application with added codec functionality.

The application supports 3 modes of operation:

  1. Capture + Encode : en_encode = 1, en_decode = 0
    1. Captures video from IMX390 cameras
    2. Encodes the video using Hardware H264 encoder
    3. Writes the output as a video file
  2. Decode + Display : en_encode = 0, en_decode = 1
    1. Reads a H264 encoded Video file
    2. Decodes the video stream using Hardware H264 decoder
    3. Displays the output after mosaic
  3. Capture + Encode + Decode + Display (Default) : en_encode = 1, en_decode = 1
    1. Captures video from IMX390 cameras
    2. Encodes the video using Hardware H264 encoder
    3. Decodes the video stream using Hardware H264 decoder
    4. Displays the output after mosaic

The application assumes that all cameras are identical. Any number of channels from 1-4 can be selected by the user, subject to constraints of sensor and codec drivers.

Supported plaforms

Platform Linux x86_64 Linux+RTOS mode QNX+RTOS mode SoC
Support NO YES YES (Capture+Encode Only) J721E
Support NO YES YES (Decode+Display Only) J721E
Support NO YES YES (Capture+Encode Only) J721S2
Support NO YES YES (Capture+Encode Only) J784S4

Note on expected performance:

Due to limitations of the Codec (Hardware or driver), the demo may not hit 30FPS for 4 channels of 1080p resolution. Following table lists the expected performance of the codec across devices

LINUX

Mode / SOC J721E J721S2 J784S4
Encode 2x1080p20 4x1080p30 4x1080p30
Decode 4x1080p30 4x1080p30 4x1080p30

QNX

Mode / SOC J721E J721S2 J784S4
Encode 2x1080p30 4x1080p23 4x1080p30
Decode 2x1080p30 Unsupported Unsupported

Note on CMA size requirements:

The Codec in J721S2/J784S4 requires CMA memory allocation, and due to memory constraints the application may fail for higher number of channels. Following is the table showing out of box support for these devices:

LINUX

Mode / SOC J721S2 J784S4
Encode 4 channel 4 channel
Decode 4 channel 2 channel
Enc + dec 3 channel 2 channel

QNX

Mode / SOC J721S2 J784S4
Encode 4 channel 4 channel

Data flow (RAW12 input)

app_multi_cam_codec_data_flow.png

Steps to run the application on J7 EVM (Linux + RTOS mode)

  1. Build the application and related libraries as mentioned in Build Instructions for Linux+RTOS mode
  2. Build and install the edgeai components required to run the codec application. This is an additional step required only for the codec application. The steps can be found below:
    make edgeai
    make linux_fs_install_sd
  3. Connect four D3-IMX390 RCM sensor boards on cam0, cam1, cam2 and cam3 input ports of the Fusion1 board.
  4. Use the is_interactive flag to run the demo in an interactive mode which allows the user to print performance characteristics on the UART console.
  5. Run the app as shown below
    cd /opt/vision_apps
    source ./vision_apps_init.sh
    ./run_app_multi_cam_codec.sh
  6. Depending on the mode of operation, the processed output for each of the captured channels is either displayed through DSS on display or written to a H264 encoded video file (.mp4).

Steps to run the application on J7 EVM (QNX + RTOS mode)

  1. Build the application and related libraries as mentioned in Build Instructions for QNX+RTOS mode
  2. Connect four D3-IMX390 RCM sensor boards on cam0, cam1, cam2 and cam3 input ports of the Fusion1 board.
  3. Use the is_interactive flag to run the demo in an interactive mode which allows the user to print performance characteristics on the UART console.
  4. Run the app as shown below
    cd /ti_fs/vision_apps
    ./vision_apps_init.sh
    ./run_app_multi_cam_codec.sh
  5. Depending on the mode of operation, the processed output for each of the captured channels is either displayed through DSS on display or written to a H264 encoded video file (.264).