• Resolved Rahul Bansal

    (@rahul286)


    Hi Todd,

    Thanks for a nice plugin.
    While customizing it for a client, I found a bug. (actually client found this bug, I just fixed it)

    In HTML5 player function…

    function WpaudioHTML5 (parent) {
    			...
    }

    Lines…

    start = player.seekable.start();
    end = player.seekable.end();

    Should be

    start = player.buffered.start();
    end = player.buffered.end();

    seekable and buffered seems same but they have a small difference.

    “seekable” failed in my case because of following note at https://dev.w3.org/html5/spec/video.html#seeking

    If the user agent can seek to anywhere in the media resource, e.g. because it is a simple movie file and the user agent and the server support HTTP Range requests, then the attribute would return an object with one range, whose start is the time of the first frame (the earliest possible position, typically zero), and whose end is the same as the time of the first frame plus the duration attribute’s value (which would equal the time of the last frame, and might be positive Infinity).

    Related post on this topic is – https://happyworm.com/blog/2010/10/04/html5-media-seeking-and-the-buffered-attribute/

    Also, I noticed another strange thing.
    My safari started buffering automatically which I didn’t like.

    So I fixed by adding following line…

    player.preload = "none";

    after lines…

    player.src = parent.getUrl();
    player.volume = 1;

    If you find these fixes helpful, add them up in your code.

    Keep up the good work. ??

    Thanks,
    -Rahul

Viewing 7 replies - 1 through 7 (of 7 total)
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: WPaudio MP3 Player] Progress Bar issues on Chrome and Safari’ is closed to new replies.