On Tue, 2024-07-02 at 06:20 +0000, Daniel Stankewitz wrote: Yes, I'm really wondering why I only have this issue with the HEVC bitstream. h264, av1, mpeg2, mjpeg, vp9 ... they're all fine.
Do you know if anything has been changed with the latest version? We did change the GOP default value from -1(means determined by VPL runtime) to the fixed value 248 in hevc QSV encoder, but the commit should be included in 7.0. And as you said CLI works well, so that shouldn't be the bad point. You can check if the GOP value set to hevc QSV encoder correctly in your APP. ________________________________ Von: Libav-user <libav-user-boun...@ffmpeg.org> im Auftrag von Wang, Fei W <fei.w.wang-at-intel....@ffmpeg.org> Gesendet: Dienstag, 2. Juli 2024 04:46 An: libav-user@ffmpeg.org <libav-user@ffmpeg.org> Betreff: Re: [Libav-user] Long seek times when playing QSV HEVC encoded files Encoded file doesn't contain IDR frame except the 1st frame. You may need check why it leaks IDR frame. On Mon, 2024-07-01 at 19:06 +0000, Daniel Stankewitz wrote: No, I only have this issue with the HEVC bitstream. Thanks, Daniel ________________________________ Von: Libav-user <libav-user-boun...@ffmpeg.org> im Auftrag von Wang, Fei W <fei.w.wang-at-intel....@ffmpeg.org> Gesendet: Montag, 1. Juli 2024 06:49 An: libav-user@ffmpeg.org <libav-user@ffmpeg.org> Betreff: Re: [Libav-user] Long seek times when playing QSV HEVC encoded files Does all QSV codecs have this issue? Can you share a encoded bitstream by your app? Thanks Fei On Sun, 2024-06-30 at 10:01 +0000, Daniel Stankewitz wrote: Hello, Since I have switched my app from libav* / FFmpeg 6 to 7 I have noticed some issues with the Intel QSV HEVC encoder (NVENC works fine). When I exported a video with a length of min. 6 minutes and I play it with i.e. MPC-HC I experience a long seek time when jumping through the video. The later the point I seek to, the longer it takes. Just like it has to crawl through the whole file until it finds the right frame. This didn't happen with libav* from FFmpeg 6. It also doesn't happen when using the FFmpeg 6 or 7 CLI, only when I encode a file using libav*. Does anybody have any idea what this could be? Thanks, Daniel _______________________________________________ Libav-user mailing list Libav-user@ffmpeg.org<mailto:Libav-user@ffmpeg.org> https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-requ...@ffmpeg.org<mailto:libav-user-requ...@ffmpeg.org> with subject "unsubscribe". _______________________________________________ Libav-user mailing list Libav-user@ffmpeg.org<mailto:Libav-user@ffmpeg.org> https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-requ...@ffmpeg.org<mailto:libav-user-requ...@ffmpeg.org> with subject "unsubscribe". _______________________________________________ Libav-user mailing list Libav-user@ffmpeg.org<mailto:Libav-user@ffmpeg.org> https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-requ...@ffmpeg.org<mailto:libav-user-requ...@ffmpeg.org> with subject "unsubscribe".
_______________________________________________ Libav-user mailing list Libav-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-requ...@ffmpeg.org with subject "unsubscribe".
