VideoDecoder error PP_ERROR_RESOURCE_FAILED

98 views
Skip to first unread message

Alexey Bleikher

unread,
Oct 2, 2015, 1:07:44 AM10/2/15
to Native-Client-Discuss
Hi,

I have observed that the nacl VideoDecoder fails on H.264 stream with the error PP_ERROR_RESOURCE_FAILED.
This stream is played successfully 1-10 seconds and then fails. 
Mostly the issue reproduced on HLS streams, which are demultiplexed to elementary H.264.
What the error does mean and how to avoid the issue ?

Thanks,
Alexey

Bill Budge

unread,
Oct 4, 2015, 9:30:58 AM10/4/15
to Native-Client-Discuss
PP_ERROR_RESOURCE_FAILED is a generic error that is returned when Chrome's video decoder can't handle the bitstream, so it's hard to tell what went wrong in the plugin. Some questions that might help diagnose the problem:

Can you play the video in Chrome (i.e. from a web page that doesn't use a plugin)?

Is the problem specific to any one OS?

Alexey Bleikher

unread,
Oct 4, 2015, 10:08:36 AM10/4/15
to Native-Client-Discuss
The issue does not depend on system ( I have reproduced on Windows (8.1/10), Linux(Ubuntu 14.10), MacOS ) where Chrome(45) had supported WebGL feature. 
Also it does not depend on auxiliary classes, I tried the build without OpenGL rendering, audio etc, just video decoder tested.
It strange that every H.264 stream had demuxed from RTSP (like rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov ) works fine.
Every H.264 stream had demuxed from HLS ( like http://devimages.apple.com/iphone/samples/bipbop/gear1/prog_index.m3u8 ) fails after 1-10 seconds.

You can test the issue in my test page ( http://rtpstream.com/nacl_player/ ), just turn on "Show logs".

Thank you,
Alexey
 


воскресенье, 4 октября 2015 г., 19:30:58 UTC+6 пользователь Bill Budge написал:

Bill Budge

unread,
Oct 5, 2015, 1:23:51 PM10/5/15
to Native-Client-Discuss
I installed the plugin and see a -14 error (PP_ERROR_MALFORMED_INPUT) with the HLS stream.

That error is coming from Chrome's internal video decoder machinery, so it's not really a Pepper issue. Your plugin may have to massage the data, since demuxing is really at a higher level than PPB_VideoDecoder.


On Thursday, October 1, 2015 at 10:07:44 PM UTC-7, Alexey Bleikher wrote:

Alexey Bleikher

unread,
Oct 6, 2015, 12:26:14 AM10/6/15
to Native-Client-Discuss
I saw PP_ERROR_MALFORMED_INPUT, 
but what about PP_ERROR_RESOURCE_FAILED ? Several streams cause that video decoder returns  PP_ERROR_RESOURCE_FAILED and stream looks correct.



понедельник, 5 октября 2015 г., 23:23:51 UTC+6 пользователь Bill Budge написал:

Bill Budge

unread,
Oct 7, 2015, 2:12:51 PM10/7/15
to Native-Client-Discuss
Both errors come from Chrome's video decoder implementation so are not really Plugin-specific issues.

A way to diagnose this is to try to play the video in Chrome using something like the HTML <video> element. If it doesn't play, then the problem is in Chrome's video decoder. If it does play, the problem is with how you're de-muxing the video bitstream.

Alexey Bleikher

unread,
Oct 14, 2015, 8:21:47 AM10/14/15
to Native-Client-Discuss
Hi,
I've updated the chrome ( Google Chrome 46.0.2490.71  m (32 bit)) 
and the issue has gone away (!!!).
I wonder, what else improvements have done in the latest chrome concerning video. 
Also, I suspect the improvements were related to nacl_io sockets, due to I saw the broken data has gotten from network.

Thanks,
Alexey


четверг, 8 октября 2015 г., 0:12:51 UTC+6 пользователь Bill Budge написал:
Reply all
Reply to author
Forward
0 new messages