playback finish is not handled properly

Question

playback finish is not handled properly

jussi-kalliokoski opened this issue 13 years ago · comments

Jussi Kalliokoski commented 13 years ago

when a file's end is reached, jsmad throws

Uncaught Header decoding failed
Mad.Frame.decodeframe.js:366
refillplayer.js:62
(anonymous function)player.js:92
AUDIOLIB.SinkClass.processaudiolib.js:2550
bufferFill

then it starts throwing

Uncaught TypeError: Cannot read property 'flags' of null
Mad.Frame.decodeframe.js:362
refillplayer.js:62
(anonymous function)player.js:92
AUDIOLIB.SinkClass.processaudiolib.js:2550
bufferFill

Amos Wenger (old) · Answer 1 · Wed Nov 23 2011 10:33:45 GMT+0800 (China Standard Time)

@jussi-kalliokoski How do you plan to fix that?

Jussi Kalliokoski · Answer 2 · Wed Nov 23 2011 18:47:29 GMT+0800 (China Standard Time)

I'm not sure yet, I was thinking of adding another check to see if we actually have a frame and a header, but maybe jsmad should let the developer know of the stream end somehow... A callback? Trigger stop? Imho, it would be best to do both, but can I tell if it's just buffering or if the stream really ended? Does stream have information on whether it's ended?

Amos Wenger (old) · Answer 3 · Wed Nov 23 2011 22:17:32 GMT+0800 (China Standard Time)

@jussi-kalliokoski imho, the underlying I/O layer should let jsmad know whether it just ran out of buffer or that it reached the end of the stream. jsmad could then let devs know through callbacks, that's a good idea yes.