Which OS are you using?

P2 bugs with an owner that are not marked as started are being automatically moved to mstone:11.

Hey are you still having issues with this?

Hey are you still having issues with this?

As of [10.0.648.18 (Official Build 73584) on glucid] expected behavior occurs - multiple mp3's overlap and the clicking one doesn't make previously-playing ones stop.  Resolve?

Still repros for me on OSX 10.0.648.45 (dev channel).

Chrome Version       : 8.0.552.0 dev
URLs (if applicable) : http://github.com/richtaur/chrome_audio and http://richtaur.com/misc/dev/chrome_audio/

What steps will reproduce the problem?
1. Open `sfx_and_music.html`
2. Press the `final_battle.mp3` button
3. Repeatedly press the `bat_damage.mp3` button (or any of the other buttons)

What is the expected result?
"Final music" should continue playing in the background, uninterrupted by the other audio elements on the page.

What happens instead?
"Final music" stops abruptly.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=81669

------------------------------------------------------------------------
r81669 | davej@chromium.org | Thu Apr 14 16:31:33 PDT 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/audio/linux/alsa_output.cc?r1=81669&r2=81668&pathrev=81669
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/audio/linux/alsa_output_unittest.cc?r1=81669&r2=81668&pathrev=81669

Fix Linux audio playback

Playing audio files shorter than about 11000 samples on Linux was either not working at all, or re-playing (starting and stopping on the same audio object) was working only intermittently.  It was possible to stop audio playback before the first buffer was played, resulting in no sound at all.  Also, if replaying, the buffer may have been dirty from the previous playback on the same device.

So on Linux at least, these issues appear fixed.

BUG= 73045 , 47761 , 59367 , 59369 , 59370 , 65618 
TEST=Manual, quickly playing short audio files on Linux should work

Review URL: http://codereview.chromium.org/6776024
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=81670

------------------------------------------------------------------------
r81670 | davej@chromium.org | Thu Apr 14 16:34:00 PDT 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/base/pipeline_impl.h?r1=81670&r2=81669&pathrev=81670
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/audio/audio_output_dispatcher.cc?r1=81670&r2=81669&pathrev=81670
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/audio/audio_output_dispatcher.h?r1=81670&r2=81669&pathrev=81670
 M http://src.chromium.org/viewvc/chrome/trunk/src/media/base/pipeline_impl.cc?r1=81670&r2=81669&pathrev=81670

Fix erratic HTML5 audio playback

This was affecting all platforms.  The major issue was that he SetPlaybackRate(1) which is used to start playback was being done in the middle of the series of Seek operations.  So doing Seek() followed by SetPlaybackRate(1) was done, the Seek could immediately stop the playback.  To fix, Seek() was made atomic with regards to SetPlaybackRate() by delaying the execution of SetPlaybackRate until after the Seek sequence has completely finished.

To make things run even smoother, a short delay was added before recyclilng a used audio stream in the Dispatcher.  This gives the stream time to 'power down' before being reused.

Tested on Linux, Chrome-OS (Cr48) and Mac with great results, making HTML5 audio much more usable for games.

BUG= 73045 , 59369 , 59370 , 65618 
TEST=Manual, Quickly playing/stopping HTML5 audio should play cleanly.

Review URL: http://codereview.chromium.org/6822019
------------------------------------------------------------------------

It looks like r81669 and r81670 fix this.

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.