Skip to content
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

[android] Exclude demuxer memory limit when low-end-device-mode is enabled #4663

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

borongc
Copy link
Contributor

@borongc borongc commented Jan 8, 2025

  • The demuxer memory limits cause rebuffering in 4k playbacks, resulting in it restarts with a lower resolution.
  • Removed the demuxer memory limits so that Cobalt can play 4k playbacks smoothly with low-end-device-mode.

b/388291268

…abled

- The demuxer memory limits cause rebuffering in 4k playbacks, resulting in it restarts with a lower resolution.
- Removed the demuxer memory limits so that Cobalt can play 4k playbacks smoothly with low-end-device-mode.

b/388291268
@@ -17,12 +17,14 @@ size_t SelectLimit(size_t default_limit,
if (!base::SysInfo::IsLowEndDeviceOrPartialLowEndModeEnabled()) {
return default_limit;
}
#if !BUILDFLAG(USE_STARBOARD_MEDIA)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am going to address this properly in b/322027866.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this be a separate PR, or you want to address this in this PR?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am going to upload a separate PR, which will address the issue on both ATV and Linux/Evergreen.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to clarify, as the memory limit will be determined by demuxer_memory_limit_starboard.cc, it doesn't matter if the low-end-device-mode is enabled or not.

I'll wait for this separate PR merged, and then re-enable low-end-device-mode.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR created #4674, the memory limit is now determined by Starboard without taking the low end device mode into account.

Note that in future we may still have a way for low end device to specify a reduced Demuxer memory limit, and it should be a decision under Starboard (currently supported on Android TV via RRO).

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