From: Random Joe <ff.random.joe@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/cuviddec: update parser ulMaxNumDecodeSurfaces
Date: Sat, 12 Aug 2023 02:54:34 +0300
Message-ID: <CAO1_vfQQsWt29kTsqwk6SCcebmjDRFpocCdhET4DOKoqY=iMtw@mail.gmail.com> (raw)
In-Reply-To: <f146906d-5aba-e665-6b3d-cebc054606b1@rothenpieler.org>
Only update ulMaxNumDecodeSurfaces if necessary.
As for the stutter , I can't tell for sure , maybe it's a race
condition somewhere in the driver.
402d98c decoupled cuvid parser and decoder number of decode buffers ,
with parser buffers
set to be always CUVID_DEFAULT_NUM_SURFACES (5).
In NVDEC Programming Guide they recommend setting an equal number of
buffers for parser and decoder.
Here are my test outputs and logs , edited memory pointers for better
files comparison :
https://drive.google.com/drive/folders/1f0ehcNxQV-0sMvm2g66J97kHxAGeRKUT
On Sat, Aug 12, 2023 at 12:15 AM Timo Rothenpieler
<timo@rothenpieler.org> wrote:
>
> On 11.08.2023 19:50, Random Joe wrote:
> Any reason to not just always return nb_surfaces here?
> I don't really understand why this would cause stuttering though. It
> might waste a bit of memory to always set the maximum number to the
> allowed maximum, but why would it hurt performance?
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-08-11 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 17:50 Random Joe
2023-08-11 21:15 ` Timo Rothenpieler
2023-08-11 23:54 ` Random Joe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO1_vfQQsWt29kTsqwk6SCcebmjDRFpocCdhET4DOKoqY=iMtw@mail.gmail.com' \
--to=ff.random.joe@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git