New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 12 users
Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
Flash sound sometimes distorted using internal flash plugin on PulseAudio
Reported by rocketra...@gmail.com, Sep 2 2010 Back to list
Chrome Version       :  Google Chrome	5.0.375.127 (Official Build 55887)
WebKit	533.4
V8	2.1.10.15
User Agent	Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 Safari/533.4
Command Line	 /usr/bin/google-chrome

URLs (if applicable) : http://www.youtube.com/watch?v=kombvI9V-MI&NR=1

Other browsers tested:
Safari 4:
  Firefox 3.x: OK
IE 7:
IE 8:

PulseAudio version 0.9.21, Fedora 12

What steps will reproduce the problem?
1. Enable the internal flash plugin (Description: Shockwave Flash 10.1 r82, Location: /opt/google/chrome/libgcflashplayer.so)

2. Disable the external flash plugin (Description: Shockwave Flash 10.1 r82, Location: /usr/lib/flash-plugin/libflashplayer.so)

3. Kill the flash plugin using the Chrome task manager to ensure the new plugin is being used.

4. Go to the YouTube URL http://www.youtube.com/watch?v=kombvI9V-MI&NR=1 and play the video, listening to the sound.

What is the expected result?

- The sound should play without any distortion.

What happens instead?

- The sound will be distorted because of clipping.

Please provide any additional information below. Attach a screenshot if
possible.

When ALSA is configured to use PulseAudio as the default device, the sound from Flash is routed via PulseAudio. The sound when using the internal flash plugin distorts due to clipping but the sound when using the system-installed external flash plugin is fine (reverse steps #1 and #2 above). 

I have attached two ogg files for a 10s clip from the video -- both recorded by configuring an Audacity recording stream in Pulse to monitor the relevant Pulse output device. The difference is clear from the clips.

Many other videos have this problem as well, though not all.
 
internalflash_clipping.ogg
219 KB Download
adobeflash_noclipping.ogg
143 KB Download
A couple more notes:

1) Steps #1 and #2 are done via about:plugins.

2) I have also tried this on google-chrome-beta and google-chrome-unstable with the same result.
Labels: -Area-Undefined Area-Internals Feature-Flash OS-Linux
Comment 3 by karen@chromium.org, Sep 10 2010
Labels: Mstone-8
I have the same issue. It appears on Youtube videos with the audio quality that corresponds to the 360p resolution, higher or lower quality levels seem to be fine. 
Labels: -Mstone-8 Mstone-9
Since we are passed the branch, moving all mstone-8 issues to mstone-9 for triage/punting
Labels: -mstone-9 Mstone-10
Given our current velocity, we need to punt 500 bugs from m9.  Moving p2 bugs, that are not started and have an owner, to the next milestone.  If this issue absolutely needs to be fixed in the current milestone please move it back, however, at this time the focus should be on p1 bugs.
Comment 7 by kerz@chromium.org, Dec 9 2010
Labels: -Mstone-10 MovedFrom-10 Mstone-11
P2 bugs with an owner that are not marked as started are being automatically moved to mstone:11.
Comment 8 by kareng@google.com, Mar 9 2011
Labels: -Mstone-11 MovedFrom-11 Mstone-12
rolling non releaseblocker mstone 11 bugs to mstone 12. 
Comment 9 by k...@google.com, Apr 25 2011
Labels: -Mstone-12 Mstone-13 MovedFrom12
Moving out of M12.
This doesn't seem to be a problem for me anymore -- Chrome 11.0.696.34 beta, flash 10.2.154, pulseaudio version 0.9.21.7.fc14 (Fedora 14).
Labels: -Mstone-13 Mstone-14 MovedFrom13
Moving !type=meta|regression and !releaseblocker to next mstone
Labels: -MovedFrom12 MovedFrom-12
Comment 13 by k...@google.com, Jul 28 2011
Labels: -Mstone-14 Mstone-15 MovedFrom-14
Punting out non-critical bugs.  Please move back to 14 if you believe this was done in error.
As I said in comment #10, this is not a problem anymore -- at least for me. As the original reporter, I'd be fine with marking this as fixed or worksforme or whatever.
Comment 15 by kareng@google.com, Sep 8 2011
Labels: Mstone-16 MovedFrom15 bulkmove
moving non-essential bugs from 15 to 16. Please feel free to move back if this is an error and your bug is a blocker for 15.
Comment 16 by laforge@google.com, Oct 24 2011
Labels: -Mstone-16 MovedFrom-16 Mstone-17
Comment 17 by k...@google.com, Dec 6 2011
Labels: -Mstone-17 MovedFrom-17
Removing milestone for all Unconfirmed M17 bugs.
Project Member Comment 18 by bugdroid1@chromium.org, Aug 10 2012
Labels: -Pri-2 Pri-3 Action-NeedsReview
Status: IceBox
Due to the age of the issue, changing the priority to P3, however because it has at least 10 stars, marking it for review.
Comment 19 by laforge@google.com, Aug 10 2012
Status: Unconfirmed
Status: WontFix
Since this bug was filed against a version of Flash that we no longer bundle (not just an older version, but also NPAPI Flash), I'm closing it as obsolete.

(There are other current bugs against the current bundled plugin, if you're still having problems.)
Nope, as stated in comment #10 and #14, this is no longer an issue. Thx.
Project Member Comment 22 by bugdroid1@chromium.org, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
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.
Project Member Comment 23 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-Internals -Feature-Flash Cr-Content-Plugins-Flash Cr-Internals
Project Member Comment 24 by bugdroid1@chromium.org, Apr 6 2013
Labels: Cr-Blink
Project Member Comment 25 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content-Plugins-Flash Cr-Internals-Plugins-Flash
Sign in to add a comment