On Mon, Aug 7, 2017 at 10:08 AM, Nicolas George <geo...@nsup.org> wrote: > > This issue seems fixed by these changes: > > https://ffmpeg.org/pipermail/ffmpeg-devel/2017-July/214306.html > ... > Also, it would help deciding stuff if you, as a user, told us: if you > had to write "scale=w=1536:h=512" instead of "scale=1536:512" to be > completely sure that your scripts will not break on upgrade, would you > consider that an unacceptable burden?
Thank you for letting me know about the incoming patch. Two of the hunks failed to apply but I'll try sorting those out later (need to go to a meeting right now). The question about abbreviating parameters to filters: I am fine about writing in the new way, but there are scripts run here regularly that will need updating if the abbreviated form is lost. However, the non-abbreviated form is far easier to read and, therefore, for others to maintain. JW _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel