cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Bartholomew (JIRA)" <>
Subject [jira] [Commented] (CB-5953) 'startPlayingAudio' causes audio file to be restarted; unable to resume from paused position
Date Fri, 31 Jan 2014 10:52:08 GMT


Stephen Bartholomew commented on CB-5953:

Scratch this ticket - I was *completely* mistaken.  

The audio *is* cached:;a=blob;f=src/ios/CDVSound.m;h=14b2fc24387cbf91e8e1aad15c3717af63b26ecd;hb=HEAD#l166

> 'startPlayingAudio' causes audio file to be restarted; unable to resume from paused position
> --------------------------------------------------------------------------------------------
>                 Key: CB-5953
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin Media
>    Affects Versions: 3.3.0
>         Environment: iOS
>            Reporter: Stephen Bartholomew
>              Labels: audio, ios, media
> The Media plugin uses 'startPlayingAudio' when Media#play() is called (;a=blob;f=www/Media.js;h=083af3623a56fded9fd25505a94d19bd901c5e6a;hb=HEAD#l75).
> The comment states that this will "play or resume" audio but every time, the audio starts
from the beginning.
> I've only tested on iOS and my cause/solultions only cover this. I'm not familiar enough
with the other platforms right now to make a judgement.
> CDVAudioFile is initialised from scratched each time startPlayingAudio is called, rather
than reusing the current playing instance:;a=blob;f=src/ios/CDVSound.m;h=14b2fc24387cbf91e8e1aad15c3717af63b26ecd;hb=HEAD#l297
> 1. Store the current playing instance and reuse the resource path is unchanged
> 2. Add a 'resume' method to use instead of using play
> I'm happy to look into either of these but I'd like confirmation of my assessment of
the problem and some kind of consensus on the solution.
> I'm now attempting to store the audio position at the time of pausing then doing a seek
after play to put the audio in the correct place via the JS - not ideal.

This message was sent by Atlassian JIRA

View raw message