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 <t...@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-requ...@ffmpeg.org with subject "unsubscribe".