Re: [FFmpeg-user] signalstats

2019-02-14 Thread adam smith
Thanks very much. I was hoping to restrict the output using ffmpeg and not ffprobe; mostly so I could make a proxy with overlay and metadata text file at the same time. My question regarding bit depth was because the filter doc shows values between 0-255 which is cool for 8bit values, but

Re: [FFmpeg-user] signalstats

2019-02-14 Thread Chris Davis
In order to show specific entries with signal stats, I have used the following. input=[file to process] ffprobe -f lavfi movie=$input,signalstats -show_entries frame=pkt_pts_time:frame_tags=lavfi.signalstats.YDIF:frame_tags=lavfi.signalstats.VDIF:frame_tags=lavfi.signalstats.UDIF -of

Re: [FFmpeg-user] signalstats

2019-02-14 Thread Kieran O Leary
On Thu, 14 Feb 2019, 16:53 Gyan > > On 14-02-2019 09:47 PM, adam smith wrote: > > The other question regarding this filter, can it output 10bit values? > > The 8bit values appear to be covered, but I am not sure how to get 10bit > or higher. > > The filter works with inputs up to 16 bit depth.

Re: [FFmpeg-user] signalstats

2019-02-14 Thread Gyan
On 14-02-2019 09:47 PM, adam smith wrote: The other question regarding this filter, can it output 10bit values? The 8bit values appear to be covered, but I am not sure how to get 10bit or higher.  The filter works with inputs up to 16 bit depth. Gyan

[FFmpeg-user] signalstats

2019-02-14 Thread adam smith
Hi Is it possible to limit the return of signalstats filter to only return certain values (YMAX, YMIN etc) instead of always outputting all values. Perhaps only output values if they are outside of a tolerance eg <16 or >235 The other question regarding this filter, can it output 10bit values?