Delayed sound on Flash plugin

[oldcpu]

@6tr6tr

I can just plug and unplug it and it continues working.

Thanks. Thats clear now.

@6tr6tr

I HAVE to restart alsa (however, i’ve discovered that I do not have to bother with the .asoundrc file. I can just restart alsa in Konsole) or it doesn’t work.

Thanks, thats clear now too.

@6tr6tr

Also, I got this response on another forum. What do you think about this? Does it sound correct?

Edit “/etc/modprobe.d/sound” (create it if it does not exist) to add:

options snd-usb-audio index=-1
options snd slots=snd-usb-audio

Then reload the drivers.

The non-working case is apparently the OSS application. The OSS applciation doesn’t work (as default) with dmix, so it blocks other apps. That’s the reason. Thus it’s no bug but the application problem. You can try to use aoss wrapper instead.

In the not-working case, the module snd-pcm-oss isn’t loaded. Usually it’s loaded via alsasound init script. Either this script is disabled or the setting in /etc/sysconfig is disabled. This is thus no bug but your setup.

But, more interestingly, the app opens ALSA devices because OSS devices are unavailable.

It is plausable, but I can’t really say until I see the current contents of your /etc/modprobe.d/sound file. I asked for that some time above (asking you provide the output of “cat /etc/modprobe.d/sound” and I never did get a response to that).

[oldcpu]

@6tr6tr

Please look at my above post first ^. Thanks!

OK, I think I follow (with regard to dmesg output)…

When I restart Alsa but have not unplugged/replugged the USB headset, I get:
dmesg.txt - nopaste.com (beta)

When I then (after restarting Alsa) also replug in the USB headset, I get:
dmesg.txt - nopaste.com (beta)

The only difference between the two documents is:

usb 1-2: USB disconnect, address 3
usb 1-2: new full speed USB device using ohci_hcd and address 4
usb 1-2: configuration #1 chosen from 1 choice
input: Plantronics Plantronics Headset as /devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2:1.3/input/input5
input,hidraw0: USB HID v1.00 Device [Plantronics Plantronics Headset] on usb-0000:00:0f.2-2
usb 1-2: New USB device found, idVendor=047f, idProduct=0ca1
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: Plantronics Headset
usb 1-2: Manufacturer: Plantronics
usb 1-2: SerialNumber: 00500-0429034410003-V060000A
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 0 is different from the runtime rate 48000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 0 is different from the runtime rate 48000
usbcore: registered new interface driver snd-usb-audio
alsactl[4976]: segfault at 0 ip b7e2ef83 sp bf82b48c error 4 in libc-2.8.so[b7dbc000+13d000] 

OK, so the above happens when you plug in your USB headset and a sort of “automounting” / “autorecognition” takes place.

I am curious to see your dmesg after a boot, BEFORE you restart alsa and before you plug in your headset. The reason is I wish to determine if the following dmesg error comes from booting, or from restarting alsa:

ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 8000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 44100
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 8000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 44100
printk: 3 messages suppressed.
nscd[2402]: segfault at fe0782f4 ip b806c6f4 sp afca9fd0 error 4 in nscd[b805c000+1b000]
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 8000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 44100
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 8000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 48000 is different from the runtime rate 44100
usbcore: deregistering interface driver snd-usb-audio 

Also of interest would be the dmesg contents AFTER booting, without restarting alsa, and AFTER plugging in your headset (where you note your headset does not work).

[6tr6tr]

@oldcpu

Thanks. Thats clear now.
Thanks, thats clear now too.
It is plausable, but I can’t really say until I see the current contents of your /etc/modprobe.d/sound file. I asked for that some time above (asking you provide the output of “cat /etc/modprobe.d/sound” and I never did get a response to that).

Sorry, I thought I responded to that (as I’d responded on the other forum):

I do not have the file. My output of “cat /etc/modprobe.d/sound” is:

cat: /etc/modprobe.d/sound: No such file or directory

BTW, thank you SO MUCH for taking the time to go through all this with me. I REALLY appreciate it!

[6tr6tr]

Please see above post first.

@oldcpu

I am curious to see your dmesg after a boot, BEFORE you restart alsa and before you plug in your headset.

Done: dmesg.txt - nopaste.com (beta)

@oldcpu

Also of interest would be the dmesg contents AFTER booting, without restarting alsa, and AFTER plugging in your headset (where you note your headset does not work).

Done: dmesg.txt - nopaste.com (beta)

OK, I made a HUGE discovery here!

If I restart without the USB Headset plugged in and then after the OS is done starting up, plug it in then, it works fine! And Alsa’s set up fine then too!

Why is this? Why would having the headset plugged in on startup/boot screw up the alsa settings?

[oldcpu]

@6tr6tr

I am curious to see your dmesg after a boot, BEFORE you restart alsa and before you plug in your headset.

Done: dmesg.txt - nopaste.com (beta)

Interesting. No reference at all in the dmesg to any sound device! No errors. No seg faults.

@6tr6tr

Also of interest would be the dmesg contents AFTER booting, without restarting alsa, and AFTER plugging in your headset (where you note your headset does not work).
Done: dmesg.txt - nopaste.com (beta)

and that gives at the very end:

ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 0 is different from the runtime rate 48000
ALSA /usr/src/packages/BUILD/alsa-driver/usb/usbaudio.c:1330: current rate 0 is different from the runtime rate 48000
usbcore: registered new interface driver snd-usb-audio
alsactl[3041]: segfault at 0 ip b7eaff83 sp bf8ae91c error 4 in libc-2.8.so[b7e3d000+13d000] 

where the 1st 3 lines are benign, but that seg fault is ugly !! There appears to be a problem with the alsa compatibility with libc-2.8.so

@6tr6tr

OK, I made a HUGE discovery here!

If I restart without the USB Headset plugged in and then after the OS is done starting up, plug it in then, it works fine! And Alsa’s set up fine then too!

Well done in testing this!!

@6tr6tr

Why is this? Why would having the headset plugged in on startup/boot screw up the alsa settings?

I don’t know. It looks like an openSUSE bug to me. I recommend you write a bug report, and reference this thread in the bug report:
Submitting Bug Reports - openSUSE

From here on, to try and help you have the PC boot WITH the USB headset plugged in, and not have to do the alsa restart, would require speculation on my part, and experimentation on your part. We would need try custom /etc/modprobe.d/sound files (such as the one you suggested) and also try custom .asoundrc files. With your USB headset plugged in, it is possible running alsaconf (with root permissions) or going to YAST > Hardware > Sound to setup your headset might work (it may create a custom /etc/modprobe.d/sound file).

But this is speculation on my part.

[6tr6tr]

@oldcpu

From here on, to try and help you have the PC boot WITH the USB headset plugged in, and not have to do the alsa restart, would require speculation on my part, and experimentation on your part. We would need try custom /etc/modprobe.d/sound files (such as the one you suggested) and also try custom .asoundrc files. With your USB headset plugged in, it is possible running alsaconf (with root permissions) or going to YAST > Hardware > Sound to setup your headset might work (it may create a custom /etc/modprobe.d/sound file).

But this is speculation on my part.

I tried the YAST–>Sound but that did not work. It did not have any Plantronics cards.

Any idea where I can find info on the possible settings for either the modprobe.d/sound file or .asoundrc file? I would have no idea what to put in there. And I have no idea how/why it would affect alsa’s settings.