[FFmpeg-user] Capture from USB Dazzle: Interlaced or not interlaced. FFV1 level3 vs h264

[MrNice]

On 02/11/15 14:20, Andy Furniss wrote:
> MrNice wrote:
> 
>> However with x264 encoder and -flags +ilme+ildct output is
>>
>> [libx264 @ 0x2940600] interlace + weightp is not implemented [libx264
>> @ 0x2940600] using mv_range_thread = 24 [libx264 @ 0x2940600] using
>> SAR=16/15 [libx264 @ 0x2940600] using cpu capabilities: MMX2 SSE2Fast
>> SSSE3 SSE4.2 AVX XOP FMA4 LZCNT [libx264 @ 0x2940600] profile High
>> 4:4:4 Predictive, level 3.0, 4:2:2 8-bit [libx264 @ 0x2940600] 264 -
>> core 142 r2495 6a301b6 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014
>> - http://www.videolan.org/x264.html - options: cabac=1 ref=3
>> deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=0 mixed_ref=1
>> me_range=16 chroma_me=1 trellis=0 8x8dct=1 cqm=0 deadzone=21,11
>> fast_pskip=0 chroma_qp_offset=0 threads=12 lookahead_threads=2
>> sliced_threads=0 nr=0 decimate=1 interlaced=tff bluray_compat=0
>> constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25
>> scenecut=40 intra_refresh=0 rc=cqp mbtree=0 qp=0
>>
>> so interlaced=tff weightp=0
>>
>> and ffprobe -show_frames says interlaced_frame=1 top_field_first=0
> 
> Which is broken! - libx264 says tff ffprobe says bff. As your source is
> tff then trying to de-interlace this will produce broken output.
> 
>> I keep +ildtc to get interlaced even with the warning
> 
> As you now know your input is tff, for libx264 the correct thing to do is -
> 
> ......  -vf setfield=tff -c:v libx264 -preset slow -qp 0 -x264opts tff=1
> .....
> 

I changed the CL
Now I get
./ffmpeg -i ../Test/t_20151102_1504.mkv -vf idet -f null /dev/null  2>&1
| grep Parsed_idet
[Parsed_idet_0 @ 0x3b10120] Repeated Fields: Neither:   370 Top:     2
Bottom:     3
[Parsed_idet_0 @ 0x3b10120] Single frame detection: TFF:    11 BFF:
0 Progressive:     0 Undetermined:   364
[Parsed_idet_0 @ 0x3b10120] Multi frame detection: TFF:   375 BFF:     0
Progressive:     0 Undetermined:     0

and
 ./ffprobe -show_frames ../Test/t_20151102_1504.mkv
...
interlaced_frame=1
top_field_first=1
Very good!

Many thanks for you help...
May I ask for another favour?
Could you have a look at this thread
http://ffmpeg-users.933282.n4.nabble.com/Application-provided-invalid-non-monotonically-increasing-dts-to-muxer-in-stream-td4672326.html