It does work on Windows, if you get the path right. Here's what I did
(without changing into the directory where the movie is located, and
omitting its path):
ffprobe.exe -f lavfi "movie=c\\:Temp12060.mp4,signalstats" -show_entries
"frame_tags=lavfi.signalstats.YDIF"
Trial and error.
On Tue, Jan 27, 2015 at 15:50:37 +0100, Christoph Gerstbauer wrote:
> > I'm not so familiar with ffmpeg on Windows, but suspect that the
> > error here relates to how the filepath is escaped. Could you try
> > quoting the filterchain or escaping the colon.
> I tried, but it didnt work. Mybe this f
Hi Dave!
I'm not so familiar with ffmpeg on Windows, but suspect that the error here
relates to how the filepath is escaped. Could you try quoting the filterchain
or escaping the colon.
Dave Rice
I tried, but it didnt work. Mybe this filter only works correct on linux?
bg
Chris
___
Hi Christoph,
> On Jan 23, 2015, at 8:39 AM, Christoph Gerstbauer
> wrote:
> Am 23.01.2015 um 13:57 schrieb Dave Rice:
>> On Jan 23, 2015, at 5:23 AM, Christoph Gerstbauer
>> wrote:
>>
The YDIF value in the signalstats filter could show this.
ffprobe -f lavfi movie=DETECT_CUTS.mov,s
Do you see signalstats when running 'ffmpeg -filters'?
Dave Rice
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
.S. signalstats V->V Generate statistics from video analysis.
yes!
bg
Chris
Am 23.01.2015 um 13:57 schrieb Dave Rice:
On Jan 23, 2015, at 5:23 AM, Christoph Gerstbauer
wrote:
The YDIF value in the signalstats filter could show this.
ffprobe -f lavfi movie=DETECT_CUTS.mov,signalstats -show_entries
"frame_tags=lavfi.signalstats.YDIF” -of flat
Perhaps filter out line
On Jan 23, 2015, at 5:23 AM, Christoph Gerstbauer
wrote:
>> The YDIF value in the signalstats filter could show this.
>> ffprobe -f lavfi movie=DETECT_CUTS.mov,signalstats -show_entries
>> "frame_tags=lavfi.signalstats.YDIF” -of flat
>>
>> Perhaps filter out lines where YDIF is higher than 10
The YDIF value in the signalstats filter could show this.
ffprobe -f lavfi movie=DETECT_CUTS.mov,signalstats -show_entries
"frame_tags=lavfi.signalstats.YDIF” -of flat
Perhaps filter out lines where YDIF is higher than 10.
Hi, that does not work on my machine. (Win7)
Command line output:
C:\
Hi Christoph,
> On Jan 22, 2015, at 3:18 AM, Christoph Gerstbauer
> wrote:
>
> Hello
>
> Is it possible to detect cuts with ffmpeg by using a DYNAMIC threshold?
The YDIF value in the signalstats filter could show this.
ffprobe -f lavfi movie=DETECT_CUTS.mov,signalstats -show_entries
"frame_t
Hello
Is it possible to detect cuts with ffmpeg by using a DYNAMIC threshold?
Additionally: Is it possible to detect fades? (Blackfades, Crossfades)
Best Regards
Christoph
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/li
10 matches
Mail list logo