Bug 244340 – MSE bandwidth switching case repeated frames observed

• Status: RESOLVED
• Resolution: INVALID
• Component: Media

[Bharanitharan]

Webkit Port Revision - 2.16.5

TITLE : MSE Bandwidth switching case repeated frames observed.

URL : http://refapp.hbbtv.org/production/catalogue/index_mse-eme.php
Problem 1:

We have used older webkit port revision which is v2.16.5.We have faced the bandwidth switching related problems while playing the MSE media content,
1.Some times bandwidth switching but repeated frames displaying.
2.Some times Bandwidth not switching 

But we have not integrated the Gstreamer in our webkit. Kindly confirm whether Gstreamer is a mandatory for MSE or not.
We have used below mentioned 3 major properties as per MSE specification. Could you please clarify any other properties we need to send to browser.
Mediasample:
+++++++++++++++++
PresentationTimeStamp(Audio,Video)
Decoded Timestamp(Audio,Video)
Frame Duration (Audio,Video)

Problem 2: We observed the multiple entries in buffered range vector table while after received the media samples from player.But some times frame duration value is added as start value in TimeRange object.Kindly share any test pages for check the bandwidth switching in MSE.

kindly any one help to conclude the issue.

[Radar WebKit Bug Importer]

<rdar://problem/99211850>

[Philippe Normand]

I guess this is about WebKitGTK? Version 2.16 is obsolete, likely crippled with unpatched security issues as well.

Yes, GStreamer is required for MSE playback.

About the other questions, I'd suggest to try again with a modern version of the web-engine (2.38.x).

[Michael Catanzaro]

Let's just close this:

 * GStreamer is required for all multimedia playback. If you can play media without GStreamer, you have an impressive fork and presumably have your own multimedia developers.
 * Please reproduce with the latest version, currently 2.38.2, before reporting bugs upstream.

[Bharanitharan]

Sorry for the late reply.
We have still observed the repeated frames after bandwidth switching happens from lower resolution(640) to higher resolution(1280).But we have not observed the issue when higher resolution(1280) to lower resolution switching case.

From our understanding they expecting media sample values from the script.
i.e) pts,dts,frameduration also check the TimeRange values start and end. We have properly send the timerange values but still we have not conclude the problem.

Kindly suggest me what are the properties are expect the script(dash.js) for bandwidth switching.

Note:
++++
We have not used the Gstreamer port,we have used our own media player layer.

[Bharanitharan]

Still we have observed the bandwidth switching in the MSE playback.

[Philippe Normand]

(In reply to Bharanitharan from comment #4)
> 
> Note:
> ++++
> We have not used the Gstreamer port,we have used our own media player layer.

This bugzilla is not the right place to report issues related with un-supported media backends. Sorry :)