[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: All flash videos playing far too quickly

On Sat, Feb 18, 2012 at 17:59:16 -0500, brian wrote:
> On 02/18/2012 04:09 PM, Florian Kulzer wrote:
> >On Sat, Feb 18, 2012 at 12:39:53 -0500, brian wrote:
> >>On 02/17/2012 05:11 PM, brian wrote:
> >>>On 02/17/2012 02:40 PM, Richard Owlett wrote:
> >
> >  [...]
> >
> >>>>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658128


> >The bug report cited above suggests that the HDMI alsa sink is the root
> >of the problem.


> >Are you actually using the HDMI output for sound?
> No.


> >cat /proc/asound/cards
> > 0 [SB             ]: HDA-Intel - HDA ATI SB
> >                      HDA ATI SB at 0xfe7f4000 irq 16
> > 1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
> >                      HDA ATI HDMI at 0xfe9e8000 irq 19
> > 2 [CODEC          ]: USB-Audio - USB Audio CODEC
> >                      Burr-Brown from TI USB Audio CODEC at usb-0000:00:12.1-1, full speed

So there is an USB audio device connected as well? If you want to use
that one with flashplayer then it might be enough to run

  modprobe -r snd_hda_intel
  modprobe -r snd_usb_audio
  modprobe snd_usb_audio index=0

as root or with sudo. You may have to log out from your desktop
environment and issue these commands on a terminal (you cannot remove
modules that are in use). After you have done this, verify that
/proc/asound/cards now lists the USB device as card number 0, then try
if you get sound output from flashplayer. The annoying thing about sound
with Flashplayer is that the browser plugin seems to be hell-bent on
using alsa's card number 0 directly; I have never managed to make it to
respect any KDE/phonon or pulseaudio setting that says otherwise.

If you want to use the Intel SB device then you can test if disabling
the HDMI sink is sufficient to make flashplayer behave:

  modprobe -r snd_hda_intel
  modprobe snd_hda_intel enable=1,0

(Verify that /proc/asound/cards lists SB as card 0 and that the HDMI
card is gone after you do that.)

If you find a configuration that works then you can make it permanent by
putting the corresponding module options in a file in /etc/modprobe.d/
to make them persistent across reboots. I recommend creating an extra
file for that rather than adding the options to an existing file. (This
approach ensures that your settings will never be overwritten by an

Regards,            |
          Florian   | http://www.florian-kulzer.eu

Reply to: