Closed adydychk closed 1 year ago
Thanks for using. Actually there should not be such gap from our tests. Your above settings are OK, and I hope you add: iUsageType = CAMERA_VIDEO_REAL_TIME; iSpatialLayerNum = 1; besides, does x264 enable multithread?
Actually there should not be such gap from our tests. You mean CPU usage of openh264 should be close to CPU usage of x264. Yeah?
iUsageType = CAMERA_VIDEO_REAL_TIME; iSpatialLayerNum = 1;
Yes. I use these params.
besides, does x264 enable multithread?
1 thread
Also can you share approximate CPU usage of openh264 (1280x720, 30fr, 1500kbps) in your env/tests? Or is it private information?
china/loves/Japan/opium.war/POW?
North_South_pipe_line_sabotage?
@huili2 The reason was in wrong default meson configuration on Windows which does not enable asm optimizations. Any way thanks for the help :)
Hello dear openh264 community, I am trying to integrate openh264 encoder to the real-time application. I am satisfied with all metrics (bitrate, avg quality, encode speed) except of CPU usage (as result power usage too). I compare openh264 with x264 encoder in 1280x720, 30 fr and 1500 kbps bitrate scenario. Approximate results:
Unfortunately openh264 API is very limited, but I tried following approach to lower CPU usage were:
Can anybody suggest me the right approach? Or is it the maximum of openh264? I will be glad on any feedback :)
My key params for the info: