| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| all | ||
| common | ||
| core | ||
| dash | ||
| database | ||
| datasource | ||
| decoder | ||
| extractor | ||
| hls | ||
| rtsp | ||
| smoothstreaming | ||
| transformer | ||
| ui | ||
| README.md |
We have seen devices running on API21/23 fail transcoding because of setting encoding profile/level. Some devices (ale-123/nexus 7) on API21 returns ENOSYS (Function not implemented) when being configured with a profile setting. (although API21 introduced the capability of setting encoding profile) Some devices (nexus 5) on API23 fails configuration with a specific parameter set, despite advertising support for it. Not setting the baseline profile has no effect on encoding, because when not set, the encoding will pick a suitable profile to use. Since baseline is the lowest possible profile, the auto-picked value can't be worse than baseline. Ref: b/218696352 PiperOrigin-RevId: 427792124
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| all | Loading commit data... | |
| common | Loading commit data... | |
| core | Loading commit data... | |
| dash | Loading commit data... | |
| database | Loading commit data... | |
| datasource | Loading commit data... | |
| decoder | Loading commit data... | |
| extractor | Loading commit data... | |
| hls | Loading commit data... | |
| rtsp | Loading commit data... | |
| smoothstreaming | Loading commit data... | |
| transformer | Loading commit data... | |
| ui | Loading commit data... | |
| README.md | Loading commit data... |