libyuv | unofficial libyuv mirror

I think you should output a XCFramework.

1 - Use lipo to combine architectures per platforms like you did.

2 - Then use xcodebuild -create-framework to combine the platforms.

xcodebuild -create-framework -library libyuv-device.a -library libyuv-simulator.a -output libyuv.xcframework

Some of the libraries to link may not be built with the same toolchain. You can check with objdump.

Example (The "file format" may not be the exact result in your case):

Well Guys, After spending almost 12 hours of research, I have made my day. I have exactly figured out what was wrong with my development setup in (VS2019/Clion) of using static webrtc.lib in executable projects.

It looks like you are doing mostly correct things, but your time_base is too small for your purpose.

You are telling the muxer that your frames are produced in increments of 1/FPS, like 1/25, and in no case smaller than that. If sometimes you can have a smaller or larger time in between frames (variable framerate), increase your time_base.

I'm not sure why but a lot of video software (including FFmpeg client) seems to choose 1/12800 as the time_base for MP4. That's also what I used for my application with VFR (receiving video over UDP) and it worked well.

Don't forget use the version of your code with av_rescale() when setting the pts value of the frame, and after initialising AVCodecContext, you have to set time_base on that too. Never hard code the scaling AVRational, always re read it from the AVCodecContext as the libav internals can clamp the value.

As to "why" you have to set these fields, I'd recommend reading the header Doxygen of avcodec.h and avformat.h. Above all the useful functions, they have descriptions about what fields may be set, and which must be set for it to work. This was extremely useful to learn what the library expects from you as the user.

As also answered here, clCreateCommandQueueWithProperties is an OpenCL 2.0 thing. Nvidia GPUs only support OpenCL 1.2. Nvidia recently "upgraded" to OpenCL version 3.0, but this is just a new name for version 1.2. OpenCL 2.0 features are still not supported.

You should carefully read the documentation of avcodec_receive_frame:

Return decoded output data from a decoder.
Parameters
avctx codec context
frame This will be set to a reference-counted video or audio frame (depending on the decoder type) allocated by the decoder. Note that the function will always call av_frame_unref(frame) before doing anything else.

Returns 0: success, a frame was returned
AVERROR(EAGAIN): output is not available in this state - user must try to send new input
AVERROR_EOF: the decoder has been fully flushed, and there will be no more output frames AVERROR(EINVAL): codec not opened, or it is an encoder other negative values: legitimate decoding errors

I have highlighted two key pieces of information:

• First, the call to avcodec_receive_frame will invalidate vFrameOne. If your other thread is in the middle of decoding, your program will crash. You will need to establish a synchronization mechanism between receiving and displaying threads to make sure the receiver is always receiving into a frame only it has access to, and that it only passes full frames to the displaying side. (see next point)
• Second, you should check the return value of avcodec_receive_frame. If you see an AVERROR(EAGAIN) you have not received enough packets to produce a full frame. Only if this function produces 0 can you take the full frame and hand it over to the displaying thread.

So what I basically did was this:

• renamed the folder to libwebrtcx

• renamed the project