Results 1 to 2 of 2

Thread: frame accurate seeking in paused DASH playback

  1. #1

    Default frame accurate seeking in paused DASH playback

    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
    <script type="text/javascript" src="js/shaka-player.compiled.js"></script>
    ...
    <script type="text/javascript">
    var video1;
    var shakaPlayer;

    $(document).ready(function(){
    var html5VidElem = document.getElementById("video1");

    // Install polyfills for legacy browser support.
    shaka.polyfill.installAll();

    // Construct a Player to wrap around it.
    shakaPlayer = new shaka.player.Player(html5VidElem);

    // Attach the player to the window so that it can be easily debugged.
    window.player = shakaPlayer;

    // Listen for errors from the Player.
    shakaPlayer.addEventListener('error', function(event) {
    console.error(event);
    });

    // Construct a DashVideoSource to represent the DASH manifest.
    var mpdUrl = 'http://192.168.200.31:1935/vod/mp4:sample.mp4/manifest.mpd';
    var estimator = new shaka.util.EWMABandwidthEstimator();
    var source = new shaka.player.DashVideoSource(mpdUrl, null, estimator);

    // Load the source into the Player.
    shakaPlayer.load(source);
    });
    </script>
    ...

    Example: HTML5 video element
    <video id="video1" onloadeddata="video1.onLoadedDataEvent()" onpause="video1.onPauseEvent()" onplay="video1.onPlayEvent()" ontimeupdate="video1.onTimeUpdateEvent()" controls crossorigin="anonymous" >

  2. #2

    Default

    Reading the MPD URL syntax section: https://www.wowza.com/forums/content...DASH-streaming

    When I change the manifest extension and examine the manifests for the profiles setting.

    http://mysite.com/vod/mp4:sample.mp4...est_mvtime.mpd
    profiles="urn:mpeg:dashrofile:isoff-live:2011"

    http://mysite.com/vod/mp4:sample.mp4...est_mvlist.mpd
    profiles="urn:mpeg:dashrofile:isoff-main:2011"

    http://mysite.com/vod/mp4:sample.mp4...t_mvnumber.mpd
    profiles="urn:mpeg:dashrofile:isoff-live:2011"

    Frame accurate manifests have on demand profiles
    http://shaka-player-demo.appspot.com...7-manifest.mpd
    profiles="urn:mpeg:dashrofile: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

Similar Threads

  1. HLS Frame Accurate Playlist - Help needed
    By timdaytemp in forum On-Demand Streaming
    Replies: 1
    Last Post: 11-13-2015, 07:24 AM
  2. Frame accurate seekingin Wowza 4
    By a.gliznetsov in forum Performance and Tuning
    Replies: 11
    Last Post: 10-08-2015, 06:15 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •