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

Capabilities: VP8 video "exceeds capabilities" (but plays fine if forced) #2157

Closed
laurencedawson opened this issue Dec 5, 2016 · 6 comments
Labels

Comments

@laurencedawson
Copy link

When opening this file the first frame is never rendered and the file isn't played.

https://zippy.gfycat.com/ForsakenRedAllosaurus.webm

Tested with the sample and in my own Exoplayer deployment (v2.0.4)

Tried on multiple versions of Android (7.1, 7.0, and older).

The log is very minimal...

12-05 14:18:55.566: I/ExoPlayerImpl(5308): Init 2.0.4

@Mihuilk
Copy link

Mihuilk commented Dec 5, 2016

I'am not sure but I think you should install VP9 extension

@laurencedawson
Copy link
Author

Most webm files play fine, this one just doesn't even initialize / play the first frame. It seems strange that no error is thrown or debug logs written.

@ojw28 ojw28 changed the title First frame is never rendered Capabilities: VP8 video "exceeds capabilities" (but plays fine if forced) Dec 5, 2016
@ojw28 ojw28 added the bug label Dec 5, 2016
@ojw28
Copy link
Contributor

ojw28 commented Dec 5, 2016

The issue is similar to #2034, and occurs because the VP8 decoder under-reports its true capabilities. On dev-v2 you can enable "try and play anyway" behavior with:

trackSelector.setParameters(
    trackSelector.getParameters().withExceedRendererCapabilitiesIfNecessary(true));

on your DefaultTrackSelector instance.

@ojw28
Copy link
Contributor

ojw28 commented Dec 5, 2016

Note: The exact reason this video is rejected is because it has an odd height (397px). If you control the encoding side you should probably try and ensure the video dimensions are even for best compatibility. There were issues with Chrome and odd dimension VP8 as well (search Google for: vp8 odd resolution), for example.

@laurencedawson
Copy link
Author

@ojw28 setting the additional params on dev-v2 did the trick. Is there a timescale for this rolling to prod?

Thanks

ojw28 added a commit that referenced this issue Dec 12, 2016
Not sure what I think about this, but we're getting quite
a lot of issues reported where streams play fine but capabilities
indicate they wont. It's probably best just to cross our fingers
and hope for the best in such cases, as was the case in V1 when
using ExtractorSampleSource.

Issue: #2157
Issue: #2034
Issue: #2007

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=141758070
@ojw28
Copy link
Contributor

ojw28 commented Dec 12, 2016

We've enabled this by default in dev-v2 now, so you wont even need to do it yourself. We're looking to wrap up a release this week.

@ojw28 ojw28 closed this as completed Dec 12, 2016
@google google locked and limited conversation to collaborators Jun 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants