I am using the example WowzaStreamingEngine-4.3.0 MPEGDASHPlayer.
I am trying to implement seeking frame by frame in a paused DASH stream.
When I set a new position using currentTime of the video element the
video does not move to the new frame. If I increment frame by
frame for many frames eventually after 20 to 40 frames a new
frame will be displayed.
Is there a setting on the wowza server or the shaka javascript
library that can be used to get frame accurate seeking to work?
Example: setting the HTML5 video element current time to three different frames
this.vidElement.currentTime = 19.566666666666666;
this.vidElement.currentTime = 19.6;
this.vidElement.currentTime = 19.633333333333333;
Example: shaka and video setup
…
…
Example: HTML5 video element
Reading the MPD URL syntax section: https://www.wowza.com/docs/how-to-do-mpeg-dash-streaming
When I change the manifest extension and examine the manifests for the profiles setting.
http://mysite.com/vod/mp4:sample.mp4/manifest_mvtime.mpd
profiles=“urn:mpeg:dash:profile:isoff-live:2011”
http://mysite.com/vod/mp4:sample.mp4/manifest_mvlist.mpd
profiles=“urn:mpeg:dash:profile:isoff-main:2011”
http://mysite.com/vod/mp4:sample.mp4/manifest_mvnumber.mpd
profiles=“urn:mpeg:dash:profile:isoff-live:2011”
Frame accurate manifests have on demand profiles
http://shaka-player-demo.appspot.com/assets/car-20120827-manifest.mpd
profiles=“urn:mpeg:dash:profile:isoff-on-demand:2011”
Could this be the problem?
Why does my VOD application use isoff-live profile setting for two of the manifest configurations?
I found a paragraph from Guidelines for Implementation: DASH-AVC/264 Interoperability Points:
Note: If accurate seeking to specific time is required and at the same time a fats response is required one may use On-Demand profile for VoD