-
Notifications
You must be signed in to change notification settings - Fork 132
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
LG Webos 6: changing live channels can cause PIPELINE_ERROR_DECODE #1196
Comments
Hi @TomaszKowalik, For the BIF error, I guess that the RxPlayer wrongly believe that the MPD contains a URL to a A Can you try just playing audio (e.g. by calling It's weird that it completely blocks further contents from being played also :/ A huge source of bugs on such devices are linked to DRM. I see you're relying on widevine here, does the device have PlayReady? Can you try with that key system? Sadly this is a difficult error to debug, all this tells us is that the device is not able to decode it and we now have to guess what went wrong... |
@peaBerberian thank you for your answer According to your questions:
We were able to reproduce it for livestreams only so far (but it migh be because we are able to zap through channels only with live streams), I've noticed now that we are using also:
params (didnt mentioned it before, sorry). But removing these parameters is not fixing the issue, looks like it can happen for every quality.
With audio only (I've used
No, creating new player instance with new media element after crash is not fixing it. App has to be closed and run again. (I saw few times that TV was completely freezed, and has restarted itself)
Unfortunately, we are using only DASH streams with Widevine for rxPlayer, but we tried to reproduce this issue with other player that is also using widevine for the same content, and this bug seem to occur only with RX. Additional note:
in the manifests of streams from provider for which I couldnt reproduce this issue:
|
@peaBerberian I've used RX 3.30.0 version to see if it will solve this issue, but sadly it still occurs.
Sometimes I can see some other errors as the first error, like:
Or once I saw error about buffer appending but every consecutive error is this |
Hi, OK, as that second error do refer to decryption, I'm even more under the impression that this is DRM-related. Do you have multiple keys depending on the quality of the content (e.g. other more restrictions for higher qualities)? Do the issue still appears if you lock the lowest video bitrate in place before any playback (for example by setting Do you set some widevine robustnesses? We could try with forcing the less restrictive Widevine L3 security level. In your
|
Hi.
|
And yes, we indeed support multi-key drm |
We found an issue on LG Webos 6 device when using rxPlayer 3.29.0. I couldnt reproduce it on the devices with lower Webos. This is randomly happening after starting the live stream, sometimes it can happen after the first 5 zaps, sometimes user needs to zap through the channels 20 times or more. If this error is not occuring on the start, streams are playing fine. Speed of changing channels seems that doesnt matter, we could reproduce it when changing channels slowly and quickly.
After starting the channel black screen is observed, and when this will happen, user needs to restart the app because any consecutive play request will throw an error. Looks like the live channels are triggering it, but after recieving such error there is no possibility of running any other asset (replay, vod, etc.).
Parameters we are using when starting stream:
During debugging session I found out this in the logs:
there is a BIF parse error, but I was able to reproduce this issue also with channels where there was no such error. Then these logs were printed:
And after this message:
Any consecutive play request leads to the
API: The player stopped because of an error MediaError: MediaError (MEDIA_ERR_DECODE) PIPELINE_ERROR_DECODE error
In the network tab I can see cancelled request for audio (and as I can see there is always at least one cancelled request for audio):
What might be causing this issue? Please let me know if you need any additional information.
The text was updated successfully, but these errors were encountered: