drum sound at start up only sometimes works

Creative actually recommends using the ALSA driver for their sond cards, which would explain why the OSS driver doesn't seem to be workng.

so, how do i use the alsa driver instead?

i know that with mednafen, alsa and oss don't work. i don't get any sound using the alsa driver. i have a feeling it might be more than just changing the drivers.

anything i could try?

also, the oss driver works with amarok when i hear that drum sound.

Next time the driver doesn't work, please do a dmesg and save the results to a file and post it. It sounds like you may be having hardware issues.

here is the dmesg output. thanks!

OK, please go ahead and gather the logfiles in the method specified here <https://wiki.ubuntu.com/DebuggingHardwareDetection>. One that's done, I can mark this as confirmed so the maintainer can take a look at it.

Thanks for your help. I attached the logfiles in an archive. The name and make of my sound card is listed above.

As all the logs are in place, I'm marking this as confirmed so the package maintainer can have a look.

can i get some help on this? it's still affecting me. i noticed that this bug is not assigned to anyone. should it be?

hello? anyone listening?!

some more info:

audacity was having the same exact problem. so, i fooled around with the settings. in Edit > Preferences > Audio I/O (Tab), for Playback it was set to "OSS: /dev/dsp". so, i noticed another option for "OSS: /dev/dsp3". the sound with that setting worked. what also worked was "ALSA: Audigy 2 ZS [SB0350]: ADC Capture/Standard PCM Playback (hw:3, 0)". so, now i left it at that option and it works.

then, i tried mednafen again. here are the settings in mednafen.cfg pertaining to the sound:

;Select sound driver.
sounddriver oss

;Select sound output device.
sounddevice /dev/dsp

that was the original settings, which didn't work. the mednafen team also says to try default for sounddevice, which didn't work either. then i tried /dev/dsp3 which worked! i thought i finally fixed the problem. but /dev/dsp3 doesn't seem to be consistent. sometimes i have to set it to /dev/dsp1. i don't know why. i don't understand what this means.

for amarok, if i select the oss sound engine i cannot choose /dev/dsp3, only /dev/dsp.

i have no idea how to change mplayer32 settings. but if i did, i would imagine it would be the same.

so, my question is now... what the hell is wrong with /dev/dsp? (whatever it is)

so, i updated to gutsy just recently and was having the same problem.

i read a post on the forums about getting system sounds to work in ubuntu and the workaround was to install esound from synaptic. that worked great. so, that fixed the problem of no system sounds.

but that still didn't fix the gdm drum roll sound not appearing. if i go to system -> administration -> login window and then to the accessibility tab, i can play the drum roll sound just fine. but it wasn't playing it at the gdm screen. then, i took a look at /etc/gdm/gdm.conf and noticed that the line SoundOnLogin was commented out. i uncommented it and restarted and it worked! so, why does gdmsetup have the checkbox for enabling the login screen ready sound checked when it is uncommented in gdm.conf?

in terms of getting the other packages to play sounds, they all work now. i just have to choose the correct dsp. in my case, it will always be /dev/dsp3

please close this bug. i do not believe it is an issue anymore. i'm not sure if upgrading to gutsy fixed it or just changing the settings fixed the numerous sound issues i was having.

thank you for your time.

reporter asked for it to be closed.

Thanks for your time.