No I don't have a native ffmpeg running at the moment. Failed recently to install it, which was the main reason I switched to the wasm version ...
Yes I requires some memory to load the wasm version of ffmpeg into memory. This memory will stay occupied until you stop the wasm worker.
Oeps yes I mean SD card.
Yes that is something I should perhaps do best in the future..
I have no particular use case. Would like to have a solution for all kind of use cases: image conversions, audio conversions, creating mp4 videos from images, decode rtsp streams, ...
Yes that is an alternative approach. But in this discussion I would only like to focus on ffmpeg, and find a setup that allows this kind of functionality also ...
The problem with the wasm approach might be memory full issues. E.g. when I want to create an mp4 file from a series of images (from my ip cam). Then both the images and the mp4 will be loaded into the in-memory filesystem. If you do that for multiple camera's, I think it would blow up your RAM. Therefore I'm now thinking that the file based approach might be the best way to go. But indeed that I should have an SSD disc or something similar ...
