Closed cmxl closed 3 years ago
Just to clarify what I am going to do with streams to and from ffmpeg:
I use this library in an ASP.NET Core application. I am retrieving media streams and want them to be converted on the fly. Let's say something like youtube's video options for different resolutions (1080p, 720p, 480, 320, etc.), or different bitrates for music. The user should also be able to recieve the stream as an actual stream, not a temporary file. That's why I'd want to give ffmpeg my (media) stream, let it do its magic and retrieve the resulting stream back from the process.
The API surface would change drastically though.
Maybe it's better to create a common base class for the engine and have two concrete Engines for Stream handling and File handling. But then what about Stream input and File output or vice versa. Ideas and suggestions are always welcome!
https://stackoverflow.com/a/50697975/2277280