Skip to content

src: Increase num_render_targets to 32 for Chromium - #270

Merged
elFarto merged 1 commit into
elFarto:masterfrom
antkir:master
Feb 11, 2024
Merged

elFarto merged 1 commit into
elFarto:masterfrom
antkir:master

Conversation

@antkir

@antkir antkir commented Jan 27, 2024

Copy link
Copy Markdown
Contributor

Without this change, nvEndpicture fails in cv->cuvidDecodePicture(nvCtx->decoder, picParams) when Chromium's VaapiVideoDecoder is used.

@elFarto

elFarto commented Feb 11, 2024

Copy link
Copy Markdown
Owner

Sorry, I meant to get to this earlier. Is 32 really required? Does any number >16 and <32 work? I'm just slightly concerned that NVDEC will allocate all those frames up front, and 32 is going to start taking a lot of memory, esp. at 4k resolutions.

@antkir

antkir commented Feb 11, 2024

Copy link
Copy Markdown
Contributor Author

The maximum surface index I saw in logs was 24, but I only ever tested a single YouTube video playing for no more than 5 minutes at a time and this number seemed to have a tendency to increase a bit while the video was playing, so I decided 32 would be a safer bet.

@elFarto

elFarto commented Feb 11, 2024

Copy link
Copy Markdown
Owner

Ok, I'll merge this in as-is but we may have to revisit it at some point.

@elFarto
elFarto merged commit 746d551 into elFarto:master Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants