Examples for Performing Common Tasks

To encode to H.264/H265/VP9/AV1

Enter the command:

./nvm_iep_sci -cf enc_h264_sample.cfg
./nvm_iep_sci -cf simple_h265_cif.cfg
./nvm_iep_sci -cf enc_av1_sample.cfg

The encoding is performed using parameters supplied in the configuration file.

The base configuration file specifies the input and output file information, but it is more convenient to use a specific configuration file (with the ‑sf option) for these parameters or pass them through the command line using -p option as follows.

./nvm_iep_sci -cf enc_h264_sample.cfg -p FramesToBeEncoded=10

To run in event data recorder mode

Enter the command:

./nvm_iep_sci -cf enc_h264_sample.cfg -eventDataRecorder <sec>

In event data recorder mode, the application saves a specified number of seconds of bitstream in the output bitstream file. The number of seconds is specified by the eventDataRecorder option.

In event data recorder mode, the application forces the following encode parameters:

GOP size = frame rate, which equals to 1 second encode time
IDR period = GOP size
H264RepeatSPSPPSMode = 2, SPS/PPS is repeated for every IDR frame[JS1]

The settings guarantee that each GOP bitstream is decoded independently. The GOP size and IDR period can be set to half second encode time, or other values. The user application can choose values which fits the use case as desired.

To use a specific configuration file

Enter the command:

./nvm_iep_sci -cf enc_h264_sample.cfg -sf enc_h26x_specific_config.cfg

The encoding is performed using parameters supplied in the enc_h264_sample.cfg and enc_h26x_specific_config.cfg files. If a parameter is present in both files, the value in the specific configuration file enc_h26x_specific_config.cfg is used.

To enable profiling

Enter the command:

./nvm_iep_sci -cf enc_h264_sample.cfg -sf enc_h26x_specific_config.cfg -profile <FPS>

The "-profile" option dumps the latency information. A non-0 value for the <FPS> parameter indicates rate limiting.