-
Notifications
You must be signed in to change notification settings - Fork 82
Expose cpu_fallback in VideoDecoder API #1093
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
NicolasHug
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @mollyxu ! Left a few comments and suggestions regarding the implementation, let me know if I can clarify anything.
Dan-Flores
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some small comments, but after those LGTM!
NicolasHug
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for working on this @mollyxu ! Left 2 last minor comments below but LGTM
Expose cpu_fallback in VideoDecoder API
Expose the
cpu_fallbackproperty in the public API to allow users to check whether the video decoder fell back to CPU decoding. #943The
FallbackInfoclass provides a clean interface for users to check decoder fallback status:bool(fallback_info)returns True if any fallback occurredstr(fallback_info)provides a human-readable explanation of why fallback happenedThe
cpu_fallbackproperty onVideoDecoderreturns aFallbackInfoinstance that can be queried after decoding at least one frame. This helps users understand why GPU decoding may not be used and debug performance issues.