Re: [FFmpeg-devel] [PATCH] ffmpeg: add -fpsmin to clamp output framerate

2021-06-14 Thread Matthias Neugebauer
Anything I can do to not land in spam? On another Google groups mailing list I (and many others including the admin accounts) had the same issue a couple of times. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH v2] ffmpeg: add -fpsmin to clamp output framerate

2021-06-03 Thread Matthias Neugebauer
> Can you send this again? Patchwork hasn't appeared to pick it up earlier? Sent again to a new thread. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email

[FFmpeg-devel] [PATCH] ffmpeg: add -fpsmin to clamp output framerate

2021-06-03 Thread Matthias Neugebauer
Add -fpsmin analogously to -fpsmax for setting a lower bound to the auto-set frame rate. Signed-off-by: Matthias Neugebauer --- doc/ffmpeg.texi | 7 +++ fftools/ffmpeg.c | 7 ++- fftools/ffmpeg.h | 3 +++ fftools/ffmpeg_opt.c | 26 +++--- 4 files changed

Re: [FFmpeg-devel] [PATCH v2] ffmpeg: add -fpsmin to clamp output framerate

2021-05-11 Thread Matthias Neugebauer
Add -fpsmin analogously to -fpsmax for setting a lower bound to the auto-set frame rate. Signed-off-by: Matthias Neugebauer --- doc/ffmpeg.texi | 7 +++ fftools/ffmpeg.c | 8 +++- fftools/ffmpeg.h | 3 +++ fftools/ffmpeg_opt.c | 26 +++--- 4 files changed

[FFmpeg-devel] [PATCH] ffmpeg: add -fpsmin to clamp output framerate

2021-05-11 Thread Matthias Neugebauer
Add -fpsmin analogously to -fpsmax for setting a lower bound to the auto-set frame rate. --- doc/ffmpeg.texi | 7 +++ fftools/ffmpeg.c | 8 +++- fftools/ffmpeg.h | 3 +++ fftools/ffmpeg_opt.c | 26 +++--- 4 files changed, 40 insertions(+), 4 deletions(-)

Re: [FFmpeg-devel] [PATCH v2] avformat/nut: Store display matrix side data

2020-12-11 Thread Matthias Neugebauer
> Am 06.11.2020 um 22:25 schrieb Michael Niedermayer : > > see: > > https://git.ffmpeg.org/nut.git > svn://svn.mplayerhq.hu/nut > https://lists.ffmpeg.org/mailman/listinfo/nut-devel > > thx I submitted a patch for nut.txt some time ago. Is there still something missing on my part?

Re: [FFmpeg-devel] [PATCH v2] avformat/nut: Store display matrix side data

2020-11-05 Thread Matthias Neugebauer
Am 04.11.2020 um 19:24 schrieb Michael Niedermayer : > > Is this FFmpeg specific or why is the X- prefix preferred over adding > this to nut.txt ? > > thx No, side data such as the display matrix is commonly used in other formats and outside of FFmpeg. Having it in the NUT spec is probably

Re: [FFmpeg-devel] [PATCH v2] avformat/nut: Store display matrix side data

2020-11-03 Thread Matthias Neugebauer
Stream side data such as display matrix is currently lost when using NUT. Signed-off-by: Matthias Neugebauer --- libavformat/nutdec.c | 9 + libavformat/nutenc.c | 18 ++ 2 files changed, 27 insertions(+) diff --git a/libavformat/nutdec.c b/libavformat/nutdec.c index

Re: [FFmpeg-devel] [PATCH] avformat/nut: Store display matrix side data

2020-11-02 Thread Matthias Neugebauer
Am 03.11.2020 um 00:23 schrieb Michael Niedermayer : > "st_sd_displaymatrix" is not listed in nut.txt > that either needs to be added or if its a non standard field it needs a > X- prefix Thanks for the feedback. Adding X- is not a problem, but what is the difference to "r_frame_rate“ for

[FFmpeg-devel] [PATCH] avformat/nut: Store display matrix side data

2020-11-01 Thread Matthias Neugebauer
Stream side data such as display matrix is currently lost when using NUT. Signed-off-by: Matthias Neugebauer --- libavformat/nutdec.c | 9 + libavformat/nutenc.c | 18 ++ 2 files changed, 27 insertions(+) diff --git a/libavformat/nutdec.c b/libavformat/nutdec.c index