976433 - new brightcove player demo doesn't show video, plays sound only

Status: RESOLVED INVALID

(Core :: Audio/Video, defect)

Description

[Hallvord R. M. Steen [:hallvors]]

This demo of the Brightcove beta player is set up to play one ad and then a video. The ad plays fine, the video plays only sound and shows a black screen.

(It works as expected on desktop and in Firefox on Android)

Comment 1

[Hallvord R. M. Steen [:hallvors]]

GPC, haven't done much digging here yet - time-consuming stuff to try to debug - but do you have any ideas?

Comment 2

[Gian-Carlo Pascutto [:gcp]]

Wrong person.

Comment 3

[Sotaro Ikeda [:sotaro]]

I tested the site by using v1.4 hamachi. I confirmed the video playback failure. On b2g, mp4 video playback has 2 limitations.
- [1] only one video can be playback at a time.
- [2] some b2g phones add a limitation to the playable video size.

In my case, [2] was hit. The video size is [960*400]. hamachi's size limitation is [640*480]. b2g phones can playback videos at lest the screen size, but the size limit is depends on the phone. For the time being, it mainly depends on the phone's memory amount limitation.

http://mxr.mozilla.org/mozilla-central/source/content/media/omx/OMXCodecProxy.cpp#177
https://github.com/mozilla-b2g/android-device-hamachi/blob/master/full_hamachi.mk

Comment 4

[Sotaro Ikeda [:sotaro]]

changed to a correct component.

Comment 5

[Brad Lassey [:blassey] (use needinfo?)]

Sotaro, what do you want to do with this bug?

Comment 6

[Sotaro Ikeda [:sotaro]]

(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #5)
> Sotaro, what do you want to do with this bug?

This is a b2g phone's hardware limitation. There seems nothing we can do to this problem. application/content side need to change to fix the problem.

Comment 7

[Brad Lassey [:blassey] (use needinfo?)]

Sotaro, can you elaborate on how the content side should change? I don't think there is any support in the video tag for communicating that the video is too big. And we don't want content authors just sending all FxOS devices low res video as a work around

Comment 8

[Sotaro Ikeda [:sotaro]]

I talked with jrmuizel. Current implementation does not return error even when gecko failed to instantiate video decoder. Therefor a content side can not know the load failure. It should be fixed soon. Though, all b2g phone in the market handle it incorrectly :-(

Comment 9

[Sotaro Ikeda [:sotaro]]

(In reply to Sotaro Ikeda [:sotaro] from comment #8)
> I talked with jrmuizel. Current implementation does not return error even
> when gecko failed to instantiate video decoder. Therefor a content side can
> not know the load failure. It should be fixed soon. Though, all b2g phone in
> the market handle it incorrectly :-(

I am going to check the above assumption is correct.

Comment 10

[Sotaro Ikeda [:sotaro]]

In media framework, MediaDecoder::DecodeError() is implemented, but no one call the function. It might be better to fix the problem in a new bug.

Comment 11

[Sotaro Ikeda [:sotaro]]

(In reply to Sotaro Ikeda [:sotaro] from comment #10)
> In media framework, MediaDecoder::DecodeError() is implemented, but no one
> call the function. It might be better to fix the problem in a new bug.

Sorry, it was my misunderstanding. When video size is too big, MediaDecoder::DecodeError() is correctly called. If there is another candidate, try another one by HTMLMediaElement::DecodeError().

http://mxr.mozilla.org/mozilla-central/source/content/html/content/src/HTMLMediaElement.cpp#2923

Comment 12

[Sotaro Ikeda [:sotaro]]

(In reply to Hallvord R. M. Steen from comment #0)
> This demo of the Brightcove beta player is set up to play one ad and then a
> video. The ad plays fine, the video plays only sound and shows a black
> screen.

Hallvord, I tried the hamachi/nexus-4/nexus-5. But I did not see audio only playback. It seems that unexpected thing happening. Which devide and b2g version did you used?

I tried the hamachi/nexus-4/nexus-5. On Nexus-4 and nexus-5, video was playback correctly. On hamachi, video did not playback, just showed spinning animation after the google's video. All works as expected.

Comment 13

[Hallvord R. M. Steen [:hallvors]]

This is on a Geeksphone Peak, it used to run Fx OS 1.2 and now runs 1.4 preview (nightly build from Geeksphone). In both versions I saw/see the plays-sound-only state. Also, other colleagues on the site compat team have tested this and reported the same issue on their various phones.

Comment 14

[Sotaro Ikeda [:sotaro]]

(In reply to Hallvord R. M. Steen from comment #13)
> This is on a Geeksphone Peak, it used to run Fx OS 1.2 and now runs 1.4
> preview (nightly build from Geeksphone). In both versions I saw/see the
> plays-sound-only state. Also, other colleagues on the site compat team have
> tested this and reported the same issue on their various phones.

Hallvord, can you attach a logcat when the problem happens?

Comment 15

[Sotaro Ikeda [:sotaro]]

(In reply to Hallvord R. M. Steen from comment #13)
> This is on a Geeksphone Peak, it used to run Fx OS 1.2 and now runs 1.4
> preview (nightly build from Geeksphone). In both versions I saw/see the
> plays-sound-only state. Also, other colleagues on the site compat team have
> tested this and reported the same issue on their various phones.

Can you describe the all b2g phone names?

Comment 16

[Sotaro Ikeda [:sotaro]]

And can you confirm the problem on hamachi/buri device?

Comment 17

[Sotaro Ikeda [:sotaro]]

I got geek phone device and tested the problem. I confirmed the problem. It is caused  by buffer starvation at hw codec. The hw codec was instantiated, but video data did not decoded because of buffer starvation. There is already a patch to fix the problem. The patch in Bug 864230 is not applied to geekphone's gonk.

Then I applied the patch to the source. The peak becomes crash during decoding. The hw codec does not work correctly. The peak uses very old qcom unsupported platform(ics_chocolate). qcom support only ics_strawberry on b2g. Therefore I suspect that geekphone can not update hw codec.

Comment 18

[Sotaro Ikeda [:sotaro]]

(In reply to Sotaro Ikeda [:sotaro] from comment #17)
> 
> The peak uses very old qcom unsupported platform(ics_chocolate).

About ics_chocolate unsupported on b2g, See Bug 878981 Comment 10.

Comment 19

[Sotaro Ikeda [:sotaro]]

From Comment 17, it becomes clear that the problem is caused by peak specific problem. And the root problem is peak uses qcom's ics_chocolate(unsupported) platform.

Comment 20

[Sotaro Ikeda [:sotaro]]

(In reply to Sotaro Ikeda [:sotaro] from comment #15)
> (In reply to Hallvord R. M. Steen from comment #13)
> 
> Can you describe the all b2g phone names?

Hallvord, can you answer the question?

Comment 21

[Mike Taylor [:miketaylr]]

I tested this for Hallvord on my Geeksphone Peak (and had the same behavior from his original description).

Comment 22

[Karl Dubost💡 :karlcow]

From an email about testing the new brightcove player.

On Firefox 1.2 ZTE Open, model roamer2, inari/1.2.0/default build 20131210004008.

> landscape, portrait ok for initial load. 
> The play button is not centered on the initial image.
> The initial image is some kind of water with reflections. 
> Click on the play button.
> Video and sound are working.
> The video about Google is starting well. It's finishing on Search On, then black screen on a never ending spinning wheel, but no network transfer.
> If you rotate the device, the video adjusts to the screen.

Comment 23

[Hallvord R. M. Steen [:hallvors]]

So not surprisingly, Mike saw the same issue (because he has the same hardware) while Karl's test result was actually different. I missed the difference on first reading, sorry about that.

So, if this is caused by Geeksphone using ics_chocolate (whatever that means), and we don't want to add code to work around ics_chocolate's shortcomings, this is invalid - right?

Comment 24

[Sotaro Ikeda [:sotaro]]

(In reply to Hallvord R. M. Steen from comment #23)
> So, if this is caused by Geeksphone using ics_chocolate (whatever that
> means), and we don't want to add code to work around ics_chocolate's
> shortcomings, this is invalid - right?

From Comment 19, there is no way to fix peak's problem except peak changed to using ics_strawberry(supported platform). And geekphone did not do that. So, this bug is invalid.

Comment 25

[Hallvord R. M. Steen [:hallvors]]

Thank you for your help investigating this!