# frame accurate seeking in paused DASH playback

**URL:** <https://community.wowza.com/t/frame-accurate-seeking-in-paused-dash-playback/39174>\
**Category:** Wowza Streaming Engine\
**Created:** [November 23, 2015, 11:44am UTC](https://community.wowza.com/t/frame-accurate-seeking-in-paused-dash-playback/39174 "2015-11-23T11:44:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/7ea924/32.png) [@Mike\_Phillips](https://community.wowza.com/u/Mike_Phillips)\
**Post date:** [November 23, 2015, 11:44am UTC](https://community.wowza.com/t/frame-accurate-seeking-in-paused-dash-playback/39174/1 "2015-11-23T11:44:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Mike\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/7ea924/32.png) [@Mike\_Phillips](https://community.wowza.com/u/Mike_Phillips)\
**Post date:** [December 9, 2015, 3:44pm UTC](https://community.wowza.com/t/frame-accurate-seeking-in-paused-dash-playback/39174/2 "2015-12-09T15:44:54Z")

</div>

Reading the MPD URL syntax section: [https://www.wowza.com/docs/how-to-do-mpeg-dash-streaming](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](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](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](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](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