Alex (12020-09-11): > This filter has options: url and content-type header for requests and it's > not hardcoded.
The format for the parameters is hard-coded. > Format and resolution can be changed after this filter later in filter > graph, it's not a job for this filter, for example: It is a job for this filter if the external processing requires it. As it is, the external processing must return frames with the same format and resolution as its input, which is a completely unacceptable limitation. > For my opportunity this filter open door for postprocess frames outside of > ffmpeg We do not accept patches for somebody's opportunity. Patches need to be generic enough to work for many people. The hard-coding of HTTP, the hard-coding of the parameters passing, the arbitrary limitations make this unacceptable. The sooner you accept it and start thinking more globally, the sooner you can consider making something that would be accepted. I have given an indication: what you need a movie sink. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".