sndio | Portable version of OpenBSD 's lightweight audio | Audio Utils library

What you are experiencing is the nature of large filtergraphs. Every link between filters requires a frame buffer (at least 6 MB) and filtering operation itself may require additional memory space. So, it must use up your iDevice's memory (which must be smaller than the Androids).

So, the solution must be the one which minimizes the number of filters, and you can do that by using the concat demuxer so all your images originates from one (virtual) source, and use overlay with more complex enable option.

png_list.txt

You are using formData with the HTTP PUT method which corrupts the upload as a binary data stream is expected and not MIME data.

To use formdata:

Upload an object with HTML forms

From your log I can see that your input audio is MP3.

I got solution so I answered here, issue is not of flutter_ffmpeg, issue is caused because app had not permission to write in external storage to resolve this add "MANAGE_EXTERNAL_STORAGE" in mainfest.xml file and set output path is File('storage/emulated/0/my_folder/o.mp4').path , and everything works fine.

So what happened is that the library in Debian providing support for live555 was removed in February of this year, this affects all downstream distros including but not limited to RPi OS and Ubuntu:

https://askubuntu.com/a/1363113

The 2 active versions were 2020.01.19-1 and 2018.11.26-1.1, Live555 has since added GPL license headers to the offending files, however the RFC issue remains.

Now you may be tempted to just download the latest Live555 source code and compile it... it does not work. There have been changes to function names and structures referenced by VLC, and as such VLC will not compile against the source. You need to get an older version, I specifically used this one, which is a tweaked snapshot from 2020 prior to the modifications that prevent VLC compilation:

https://github.com/rgaufman/live555

The configuration you want is ./genMakefiles linux-with-shared-libraries, I do not know if it is required but since my system is x86-64-bit I added -m64 to the compiler options first

After compilation and install, I went on to compile VLC, adding '--enable-live555' and '--with-live555-tree=extras/live555-master' after placing the root Live555 folder in the VLC extras folder, however VLC failed to compile, it turns out the Live555's make install does not copy all the header files needed to where VLC is looking. They were dropped as 4 subfolders into /usr/local/include/, and the actual libs into /usr/local/lib/. Adding the correct CXX/CPP flags will make it look where they were put, however I put them all in a single folder and used 1 flag.

I also had to '--disable-mod' to work around a dependency version issue that I had no interest in fixing, since I do not use modplug or any mod files.

50 minutes later... VLC successfully compiled! However it was expecting the libraries for Live555 to be in /usr/lib/ not /usr/local/lib/, since it took so long to compile I was just fine with linking or copying the libraries into the expected folder, and after that VLC works with RTSP when linked to the new file. Or you can choose to maintain the original VLC and run the new file directly if you need to load the camera feeds.

Combine answers from How do I convert a video to GIF using ffmpeg, with reasonable quality? and Resizing videos with ffmpeg to fit into specific size.

This happens when target output file already exists. Make sure it is not the same file as the input. Then add -y to force overwrite output in case it already exists.

Remove -framerate 1/5. That's too low of a value for your given -t and it won't work well with fade (image a fade at 0.2 fps). You're only applying that to the first input, while the rest are using the default -framerate 25. Remove it and the image will be visible.

Alternatively, use -framerate 1 for each image input, and add fps=25 after each setsar. It will be significantly faster.

The solution is in one of the link you shared

For native development, it looks like you can configure a preferred library with the OTHER_LDFLAGS flag in the Pods-.debug.xcconfig file but I don't see where to do that with Xamarin.Forms. Source: https://github.com/tanersener/mobile-ffmpeg/wiki/Using-Multiple-FFmpeg-Implementations-In-The-Same-iOS-Application

Xamarin.Forms is still native development, so you can do this the same way a Swift iOS developer would.

• You need to open your native iOS app project in XCode (not the shared project one).
• Create a xcconfig file. This guide looks good enough with screenshots to help you navigate XCode.
• A xcconfig look like this. You want to put the mobile-ffmpeg frameworks before the mobilevlckit one.
• Xamarin.iOS might require some framework as well, so before all this I'd build your app in verbosity diagnostics mode to see what the current OTHER_LDFLAGS value is.