![]() RTP does not have any way to negotiate media formats etc. But to be able to consume an RTP stream you need to know what the payload ID's correspond to. Could U give me some suggest with it?įFmpeg supports the rtp scheme (nothing supports the rtcp scheme it's part of RTP, did you mean rtsp?). But there is just build a sdp file and no any uri. I see there is a demo named webrtc-to-ffplay. How to build a URI about rtp:// or rtcp://. The SIPSorceryMedia.Abstractions package has been designed to be the interface between the main library and audio/video capabilities. If I want to write an audio or video endpoint to work with the main SIPSorcery library are all the required interfaces to implement in SIPSorceryMedia.Abstractions. Everything I need is just SIPSorceryMedia.Abstractions Right? Of the native libraries FFmpeg is one of the best, if not the best, option since it wraps up a bunch of other libraries in a consistent interface.įor Android and/or iOS if you can work out how to get FFmpeg installed then it shouldn't be too much of a leap to use this SIPSorceryMedia.FFmpeg library to use the install for VP8 and H264 encoding and decoding. To support a wide range of codecs, especially video ones, native wrappers are the only viable option. If some hard device just only use HEVC, I need to set it into somebody like ffmpeg to encoding new stuff out for SIP. I'm leaning towards spending time trying to port libvpx or openh264 rather than doing more native library builds and wrappers. I actually think C# would be fine for video encoding in client applications where there are likely to be a small number of streams. ![]() There are no free or opensource C# VP8 or H264 libraries that I know of. ![]() I still think is encoding task is almost nothing to do with C# libraries. Like any software the FFmpeg library will also change over time so there s maintenance involved.
0 Comments
Leave a Reply. |