#11557: FFMPEG long load of non-existing_PPS_0_referenced hdhomerun streams
-------------------------------------+-------------------------------------
             Reporter:  wazer        |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffmpeg
              Version:  git-master   |               Resolution:
             Keywords:  non-         |               Blocked By:
  existing PPS 0 referenced, no-     |
  frame                              |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Description changed by wazer:

Old description:

> Summary of the bug: Takes long time to load streams 5-10 seconds its
> really periodic, only some channels affected by this, been an ongoing
> issue for years, I checked the log window and saw as massive spam "non-
> existing PPS 0 referenced " & no frame!.
> How to reproduce: Consistent playing my HDHR channels,
> {{{
> % ffmpeg -v 9 -loglevel 99 -i "http://192.168.1.21:5004/auto/v9"; -ss
> 00:00:0.0 -t 10 -vcodec copy -acodec copy non-
> existing_PPS_0_referenced.mpeg
> ffmpeg version 2025-04-23-git-25b0a8e295
> built on Windows
> }}}
> Patches should be submitted to the ffmpeg-devel mailing list and not this
> bug tracker.

New description:

 Summary of the bug: Takes long time to load streams 5-10 seconds its
 really periodic, only some channels affected by this, been an ongoing
 issue for years, I checked the log window and saw as massive spam "non-
 existing PPS 0 referenced " & no frame!.
 How to reproduce: Consistent playing my HDHR channels,
 {{{
 % ffmpeg -v 9 -loglevel 99 -i "http://192.168.1.21:5004/auto/v9"; -ss
 00:00:0.0 -t 10 -vcodec copy -acodec copy non-
 existing_PPS_0_referenced.mpeg
 ffmpeg version 2025-04-23-git-25b0a8e295
 built on Windows
 }}}

 I used the above command to save 10 seconds maximum in order to have as
 small filezie possible while still maintaining getting perfect log of the
 issue.

--
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11557#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to