[FFmpeg-trac] #9600(ffmpeg:new): Fieldmatch ppsrc crashes

[FFmpeg]

#9600: Fieldmatch ppsrc crashes
-------------------------------------+-------------------------------------
             Reporter:  Viscerous    |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffmpeg
              Version:  git-master   |               Resolution:
             Keywords:  fieldmatch   |               Blocked By:
  ppsrc                              |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Description changed by Viscerous:

Old description:

> Every attempt to use fieldmatch's ppsrc feature seems to crash ffmpeg
> unless the two input streams are identical (?).
>
> I've been trying to eliminate residual combing on fade in/outs so I
> tried:
> {{{
> ffmpeg -i .\source.mp4  -map 0:v -c:v h264_nvenc -tune lossless -vf
> normalize preprocessed.mp4
> ffmpeg -i .\preprocessed.mp4 -i .\source.mp4  -c:v h264_nvenc -tune
> lossless -filter_complex fieldmatch=ppsrc=1 output.mp4
> }}}
>
> I've tried using -report but the log doesn't really list anything
> interesting.
>
> Windows' event viewer shows:
> {{{
> Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp:
> 0x00000000
> Faulting module name: msvcrt.dll, version: 7.0.22000.1, time stamp:
> 0x90483ed2
> Exception code: 0xc0000005
> Fault offset: 0x0000000000077e53
> Faulting process ID: 0x2670
> Faulting application start time: 0x01d80ad54d1fe1e7
> Faulting application path: E:\Utilities\ffmpeg\bin\ffmpeg.exe
> Faulting module path: C:\WINDOWS\System32\msvcrt.dll
> Report ID: 32dfca74-d300-4da7-a7c3-c2e655ec7797
> Faulting package full name:
> Faulting package-relative application ID:
> }}}
> Running Windows 11 (22000.434).

New description:

 Every attempt to use fieldmatch's ppsrc feature seems to crash ffmpeg
 unless the two input streams are identical (?).

 I've been trying to eliminate residual combing on fade in/outs so I tried
 (other params removed for testing):
 {{{
 ffmpeg -i .\source.mp4  -map 0:v -c:v h264_nvenc -tune lossless -vf
 normalize preprocessed.mp4
 ffmpeg -i .\preprocessed.mp4 -i .\source.mp4  -c:v h264_nvenc -tune
 lossless -filter_complex fieldmatch=ppsrc=1 output.mp4
 }}}

 I've tried using -report but the log doesn't really list anything
 interesting.

 Windows' event viewer shows:
 {{{
 Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp:
 0x00000000
 Faulting module name: msvcrt.dll, version: 7.0.22000.1, time stamp:
 0x90483ed2
 Exception code: 0xc0000005
 Fault offset: 0x0000000000077e53
 Faulting process ID: 0x2670
 Faulting application start time: 0x01d80ad54d1fe1e7
 Faulting application path: E:\Utilities\ffmpeg\bin\ffmpeg.exe
 Faulting module path: C:\WINDOWS\System32\msvcrt.dll
 Report ID: 32dfca74-d300-4da7-a7c3-c2e655ec7797
 Faulting package full name:
 Faulting package-relative application ID:
 }}}
 Running Windows 11 (22000.434).

 EDIT:
 I should've been paying more attention to the pixel formats, I forgot to
 set the one for the lossless encode and it looks like the filter
 definitely doesn't like gbrp that's used by default in this scenario. It
 works fine when using -pix_fmt yuv420p. Should ffmpeg handle this more
 gracefully though? Leaving this open just in case.

--
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9600#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker