[FFmpeg-trac] #10165(undetermined:new): No Status for First Encoding Pass In Latest Version of FFmpeg?

[FFmpeg]

#10165: No Status for First Encoding Pass In Latest Version of FFmpeg?
-------------------------------------+-------------------------------------
             Reporter:  MogomraZero  |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:  git-
  undetermined                       |  master
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 I upgraded ffmpeg from the latest stable build (5.1.2) to one of the more
 recent git builds ( 2023-02-02-git-7d49fef8b4 ) by downloading the latest
 pre-compiled binary for Windows from gyan.dev. However, after doing so, it
 seems that two-pass encoding (I have tested with both libvpx-vp9 and
 liboam-av1) is no longer providing status updates for the first pass. My
 machine works like it is performing its first pass, but it doesn't show
 any frame progress, fps remains at 0.0, it just shows the time as
 "577014:32:33.77" and the speed as N/A. Once it "finishes", it proceeds to
 the second pass, which provides status updates just fine. I downloaded the
 pre-compiled binary from BtBn and it does the same thing. I have tried a
 variety of command line configurations for both libvpx-vp9 and liboam-av1
 and get the same result. The one that I primarily use is as follows:

 ffmpeg -i test.mkv -c:v libaom-av1 -crf 23 -pix_fmt yuv420p10le -g 60
 -keyint_min 60 -cpu-used 0 -aq-mode 0 -pass 1 -an -f null NUL && ^

 ffmpeg -i test.mkv -c:v libaom-av1 -crf 23 -pix_fmt yuv420p10le -g 60
 -keyint_min 60 -cpu-used 3 -aq-mode 0 -auto-alt-ref 1 -lag-in-frames 48
 -pass 2 -c:a libopus -b:a 192k test.webm
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10165>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker