Turn from: Https://stackoverflow.com/questions/42220081/how-to-choose-between-openh264-and-x264-decoder
Ask:down vote Favorite
The I ' m using the dev build, zeranoe.com which has OpenH264 and libx264 in it. How can I choose between this two decoders to compare the decoding speed? avcodec_find_decoder (avcodecid.av_codec_id_h264); Only gives me the name "H264" but which decoder is it?
Today is the last year before the Spring Festival to work, but also because of the recent integration of MSDK, X264 two encoder, so today the small test of the Cisco OPENH264 Encoder, intends to integrate it into my code.
the first is the compilation problem:
System platform: Win7 x86
Compilation Environment: Mingw32/msys
1, download the source code, I downloaded is openh264-master, can be seen from the a
In this paper, the OPENH264 encoder is used in the WEBRTC project, and some conclusions and suggestions are given for the optimization of the key parameters of the encoder in practical application:
1.iRCMode: Bit rate control mode:
The 0 value corresponds to quality mode (Rc_quality_mode) more focused on ensuring video quality, bit rate stability control slightly worse, 1 value corresponding to bitrate mode (Rc_bitrate_mode), more emphasis on the stab
openh264 User Guide
Overview
At present, openh264 official website has only a few questions and answers, the key development information is all on the GitHub page wiki page (Https://github.com/cisco/openh264/wiki)
The same official binary library is also available for download on the release page of the GitHub page (https://github.com/cisco/
http://blog.csdn.net/nonmarking/article/details/47910043
This series is currently a total of three articles, follow up will also update
WebRTC Videoengine Ultra-Detailed tutorial (i)--the basic process of video Call
WebRTC Videoengine Ultra-Detailed tutorial (ii)--integrated OPENH264 codec
WebRTC Videoengine Ultra-Detailed tutorial (iii)-- Overview of Integrated X264 encoding and FFmpeg decoding
WEBRTC native support VP8 and VP9, but can also be sel
its main decoder, but using it is not very easy. In theory, H. 264 of patent fees are high.Patent License
And the first and second parts of the MPEG-2, the second part of the MPEG-4, using H. 264/AVC product manufacturers and service providers need to pay patent license fees to the holders of patents used by their products. The main source of these patent licenses is a private organization called MPEG-LA LLC, which has nothing to do with the MPEG Standardization Organization, but the Organizati
WebRTC represents the best technology in the field of real-time communication since the date of birth. But for a long time, it supported the video encoder only VP8, and later with H265/VP9 as the representative of the birth of the next generation of video Encoders, WebRTC appeared VP9 Codec. The most widely used H264 has been kept out of sight. Until Cisco announces its H264 codec open source for OpenH264, and has paid H264 royalties for all
layer uses the forward error correction FEC algorithm for intelligent protection to maximize the effectiveness of real-time audio and video calls. Based on our actual testing, audio and video calls can resist 20% drops and 600ms of network jitter after using the appellate QoS protection strategy.② Multi-person audio and video real-time call system in order to ensure the quality of the premise to minimize the call flow, audio codec mainly to Opus-based, Opus Fusion absorbed the Celt and silk cod
General Statement
In the previous article, we explained how to integrate the OPENH264 codec into the WEBRTC, but OPENH264 can only encode baseline H264 video, and in terms of encoding quality, X264 is the best, This article will explain how to integrate the X264 encoder into the WEBRTC, in order to achieve decoding, at the same time to use the ffmpeg. The overall process, as before, is divided into the re-
Recently experiment how to let WEBRTC support H264 code, record, for people who need reference.To illustrate, I was compiling the WebRTC under Ubuntu Server 14.04, using the native (c + +) API to develop WebRTC applications. So my adjustments are based on the native code.The end result is that the browser can send a video with H264 or receive H264 video.Note that WebRTC uses OpenH264 to do encoder (see h264_encoder_impl.cc), using FFmpeg to do decoder
Recently experiment how to let WEBRTC support H264 code, record, for people who need reference.
To illustrate, I was compiling the WebRTC under Ubuntu Server 14.04, using the native (c + +) API to develop WebRTC applications. So my adjustments are based on the native code.
The end result is that the browser can send a video with H264 or receive H264 video.
Note that WebRTC uses OpenH264 to do encoder (see h264_encoder_impl.cc), using FFmpeg to do deco
applications.
Thrift: Efficient cross-language ipc/rpc for c++,java,python,php,c# and many other languages, originally developed by Twitter.
Video
LIBVPX:VP8/VP9 encoding and decoding SDK
FFmpeg: A complete, cross-platform solution for recording, converting video and audio streams.
LIBDE265: The implementation of an open h.265 video codec.
OpenH264: Open source h.364 codec.
Theora: Free open source video compression
Simplebinaryencoding: Encoding and decoding of application information in binary format for low-latency applications.
Thrift: Efficient cross-language ipc/rpc for c++,java,python,php,c# and many other languages, originally developed by Twitter.
Video
LIBVPX:VP8/VP9 encoding and decoding SDK
FFmpeg: A complete, cross-platform solution for recording, converting video and audio streams.
LIBDE265: The implementation of an open h.265 video codec.
serialization Library
MessagePack: Efficient binary serialization library of C/C ++, such as JSON
Protobuf: Protocol buffer, Google's data exchange format.
Protobuf-c: Protocol buffer implementation in c Language
SimpleBinaryEncoding: used to encode and decode application information in binary format for low-latency applications.
Thrift: efficient cross-language IPC/RPC, used in C ++, Java, Python, PHP, C # and other languages, initially developed by Twitter.
Video
Libvpx: VP8/VP9 encodi
: Efficient cross-language ipc/rpc for c++,java,python,php,c# and many other languages, originally developed by Twitter.
Video
LIBVPX:VP8/VP9 encoding and decoding SDK
FFmpeg: A complete, cross-platform solution for recording, converting video and audio streams.
LIBDE265: The implementation of an open h.265 video codec.
OpenH264: Open source h.364 codec.
Theora: Free open source video compression format.
Virtual mach
other languages, originally developed by Twitter.
Video
LIBVPX:VP8/VP9 encoding and decoding SDK
FFmpeg: A complete, cross-platform solution for recording, converting video and audio streams.
LIBDE265: The implementation of an open h.265 video codec.
OpenH264: Open source h.364 codec.
Theora: Free open source video compression format.
Virtual machines
Interesting VMs in Carpvm:c, let's take a look at this.
application information in binary format for low-latency applications.
Thrift: Efficient cross-language ipc/rpc for c++,java,python,php,c# and many other languages, originally developed by Twitter.
Video
LIBVPX:VP8/VP9 encoding and decoding SDK
FFmpeg: A complete, cross-platform solution for recording, converting video and audio streams.
LIBDE265: The implementation of an open h.265 video codec.
OpenH264: Open source h.3
/proc/cpuinfoProcessor:ARMv7 ProcessorRev3(v7l)Processor:0bogomips:38.40Processor:1bogomips:38.40Processor:2bogomips:38.40Processor:3bogomips:38.40Features: SWP half thumb fastmult vfp edsp neon Vfpv3 TLS Vfpv4 Idiva idivtCPUImplementer:0x41CPUArchitecture7CPUVariant:0x0CPUPart:0xc07CPURevision:3Hardware:Qualcomm MSM 8226(flattened Device Tree)Revision:0007Serial:0000000000000000Indicates that the mobile phone has supported neon instructions, and H264 is the use of neon acceleration.3, Ideas So
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.