Different Lossy H264 compression Zed Explorer VS C++ API?

Lossy H264 compression recordings with ZED Explorer produce much better video than SVO_COMPRESSION_MODE::H264 from the API with the default bitrate. H264_LOSSLESS produces files that are too big. What bitrate with SVO_COMPRESSION_MODE::H264 would give the same quality as recording in ZED Explorer?

ZED Explorer uses 0 as the bitrate setting. This means that it’s always the default value for each mode.

Thank you Myzhar

This is what I expected, and I used bitrate 0 too - but the output from ZED Explorer is really very different in quality (better) and file size (larger) than that from a C++ application using the same default settings.

HI @onthesofa
I just reported the issue to the ZED SDK team.
I’m waiting for feedback.

Thanks Myzhar

In both cases we are using 2K@15 FPS.

I think I may misunderstand this:

bool transcode_streaming_input = false

Defines whether to decode and re-encode a streaming source.
Default: false
Note
If set to false, it will avoid decoding/re-encoding and convert directly streaming input into a SVO file.
This saves a encoding session and can be especially useful on NVIDIA Geforce cards where the number of encoding session is limited.
[compression_mode] [target_framerate] and [bitrate] will be ignored in this mode.

After setting to false I get a better result.

1 Like