Re: Setting default sound device (was Re: New Dell Inspiron 15 3000 Series 3511 sound problem on Debian 11 Stable)

On Mon 13 Feb 2023 at 17:49:19 (-0800), Charlie Gibbs wrote: > On Mon Feb 13 09:36:01 2023 David Wright wrote: > > > I think the section "Wrong card used by default" in: > > > > https://wiki.debian.org/ALSA > > > > should help. There's more detail at: > > > > https://alsa.opensrc.org/MultipleCar

Re: Setting default sound device (was Re: New Dell Inspiron 15 3000 Series 3511 sound problem on Debian 11 Stable)

[Sorry about the broken threading - I read this list through linux.debian.user] On Mon Feb 13 09:36:01 2023 David Wright wrote: > I think the section "Wrong card used by default" in: > > https://wiki.debian.org/ALSA > > should help. There's more detail at: > > https://alsa.opensrc.org/Multip

Re: Setting default sound device (was Re: New Dell Inspiron 15 3000 Series 3511 sound problem on Debian 11 Stable)

On Sun 12 Feb 2023 at 15:48:51 (-0800), Charlie Gibbs wrote: > This is going a bit off topic, but since there are probably > a number of sound gurus following the original thread, I > thought I'd throw out another sound question. > > I have a desktop machine running Debian 11. It contains an > nV

Setting default sound device (was Re: New Dell Inspiron 15 3000 Series 3511 sound problem on Debian 11 Stable)

This is going a bit off topic, but since there are probably a number of sound gurus following the original thread, I thought I'd throw out another sound question. I have a desktop machine running Debian 11. It contains an nVidia card which I've hooked to my TV via HDMI. Currently sound is comin

Re: USB sound device present but visible in ‘alsamixer’

Nicholas Geovanis writes: >> I am trying to make it work; so here is the update. >> >> I tried to experiment with my machine and found that if I plug-out and >> plug-in the USB sound card again, it is not shown by "aplay -l" command >> as normal user. But when I do "sudo aplay -l" it lists the US

Re: USB sound device present but visible in ‘alsamixer’

On Sun, Feb 6, 2022, 9:42 AM Pankaj Jangid wrote: > Pankaj Jangid writes: > > > When I boot system afresh, the card is visible in the ‘alsamixer’ and in > > Gnome settings as well. Shown as “Blue” S/PDIF input and output > > devices. But when system wakes up from sleep (suspended), it doesn’t >

Re: USB sound device present but visible in ‘alsamixer’

Pankaj Jangid writes: > When I boot system afresh, the card is visible in the ‘alsamixer’ and in > Gnome settings as well. Shown as “Blue” S/PDIF input and output > devices. But when system wakes up from sleep (suspended), it doesn’t > show the devices. > > However, ‘lsusb’ shows it and ‘/proc/as

Re: USB sound device present but NOT visible in ‘alsamixer’

When you stop pulseaudio, you did a good thing. since pulseaudio was started again, you're probably going to have to mess around in pactl to get this fixed if that will even be possible. On Mon, 31 Jan 2022, Pankaj Jangid wrote: > Andrei POPESCU writes: > > >> Thanks Andrei. I followed the fol

Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU writes: >> Thanks Andrei. I followed the following steps: >> >> 1. Found that it is pulseaudio that is blocking the module unload. >> 2. systemctl --user stop pulseaudio.socket >> 3. systemctl --user stop pulseaudio.service >> 4. Verified that now nothing is blocking snd_usb_audio

Re: USB sound device present but NOT visible in ‘alsamixer’

On Du, 30 ian 22, 14:58:29, Pankaj Jangid wrote: > Andrei POPESCU writes: > > > Something is keeping the module busy, but according to lsmod it's not > > another module. > > > > In case you get any output from > > > > lsof | grep /dev/snd > > > > (this needs root or sudo) > > > > try sto

Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU writes: > Something is keeping the module busy, but according to lsmod it's not > another module. > > In case you get any output from > > lsof | grep /dev/snd > > (this needs root or sudo) > > try stopping the applications listed in the first column (the second > column i

Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell writes: > rm /var/lock/asound.state.lock > > As I stated in a previous reply, I had tried to remove this file and then did "alsactl init" but no positive result. Just this output --8<---cut here---start->8--- pankaj@anant:~$ sudo alsactl init als

Re: USB sound device present but NOT visible in ‘alsamixer’

rm /var/lock/asound.state.lock On Sun, 30 Jan 2022, Pankaj Jangid wrote: > Jude DaShiell writes: > > > alsactl init I think will find everything. > > > > Then there is something else that is not letting "alsactl init" to > function properly; lock file as you suggested. But I couldn?t find > any

Re: USB sound device present but NOT visible in ‘alsamixer’

On Du, 30 ian 22, 12:47:27, Pankaj Jangid wrote: > Andrei POPESCU writes: > > >> During the boot process, the system detects everything. So there must be > >> something in the init sequence that I can trigger manually. > > > > You can try to unload and reload the corresponding kernel module. Chec

Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU writes: >> During the boot process, the system detects everything. So there must be >> something in the init sequence that I can trigger manually. > > You can try to unload and reload the corresponding kernel module. Check > the output of > > lsmod | grep snd > > (it's probabl

Re: USB sound device present but NOT visible in ‘alsamixer’

On Du, 30 ian 22, 11:02:34, Pankaj Jangid wrote: > Jude DaShiell writes: > > > alsactl --init > > may help. > > However alsa makes .lock files in /var/lock/alsa and you may find it > > helpful to delete the lock file first then once card is set run alsactl > > store. Those lock files sometimes p

Re: USB sound device present but NOT visible in ‘alsamixer’

Pankaj Jangid writes: > Jude DaShiell writes: > >> alsactl init I think will find everything. >> > > Then there is something else that is not letting "alsactl init" to > function properly; lock file as you suggested. But I couldn’t find > anything other than "/var/lock/asound.state.lock". I sho

Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell writes: > alsactl init I think will find everything. > Then there is something else that is not letting "alsactl init" to function properly; lock file as you suggested. But I couldn’t find anything other than "/var/lock/asound.state.lock".

Re: USB sound device present but NOT visible in ‘alsamixer’

alsactl init I think will find everything. On Sun, 30 Jan 2022, Pankaj Jangid wrote: > Jude DaShiell writes: > > > alsactl --init > > may help. > > However alsa makes .lock files in /var/lock/alsa and you may find it > > helpful to delete the lock file first then once card is set run alsactl >

Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell writes: > alsactl --init > may help. > However alsa makes .lock files in /var/lock/alsa and you may find it > helpful to delete the lock file first then once card is set run alsactl > store. Those lock files sometimes prevent alsa from doing a proper > detection and change. > Thank

Re: USB sound device present but NOT visible in ‘alsamixer’

alsactl --init may help. However alsa makes .lock files in /var/lock/alsa and you may find it helpful to delete the lock file first then once card is set run alsactl store. Those lock files sometimes prevent alsa from doing a proper detection and change. On Sun, 30 Jan 2022, Pankaj Jangid wrote:

Re: USB sound device present but NOT visible in ‘alsamixer’

"Andrew M.A. Cater" writes: >> Pankaj Jangid writes: >> >> > When I boot system afresh, the card is visible in the ‘alsamixer’ and in >> > Gnome settings as well. Shown as “Blue” S/PDIF input and output >> > devices. But when system wakes up from sleep (suspended), it doesn’t >> > show the devi

Re: USB sound device present but NOT visible in ‘alsamixer’

On Sat, Jan 29, 2022 at 10:28:32PM +0530, Pankaj Jangid wrote: > Sorry for the Wrong subject line earlier. > > Pankaj Jangid writes: > > > I have setup a new system. Apart from the display related issue, that I > > had posted in another thread, I am facing an issue related to my > > external ‘Ye

Re: USB sound device present but NOT visible in ‘alsamixer’

Sorry for the Wrong subject line earlier. Pankaj Jangid writes: > I have setup a new system. Apart from the display related issue, that I > had posted in another thread, I am facing an issue related to my > external ‘Yeti Blue’ sound card. I use it as Mic and Monitor audio. > > pankaj@anant:~$ l

USB sound device present but visible in ‘alsamixer’

I have setup a new system. Apart from the display related issue, that I had posted in another thread, I am facing an issue related to my external ‘Yeti Blue’ sound card. I use it as Mic and Monitor audio. --8<---cut here---start->8--- pankaj@anant:~$ lsb_release

Cannot use "line in" of USB CM106 Like Sound Device on 32 bit debian testing.

yesterday. The problem occurs with an external USB audio device from Sweex, with a CM106 chip. (Bus 001 Device 003: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device) Outputting sound via headphones or speaker plugs work OK. Also, inputting via the microphone input works OK. BUT

a SYMLINK for a sound device.

Hi again, According to https://wiki.archlinux.org/index.php/udev#Writing_udev_rules and http://www.alsa-project.org/main/index.php/Changing_card_IDs_with_udev I've added these lines to /etc/udev/rules.d/10-local.rules . root@dalton:/home/peter# tail --lines=6 /etc/udev/rules.d/10* SUBSYSTEM!="

Re: Re^2: A persistent name for a sound device.

On 2014-02-04, pe...@easthope.ca wrote: > Alan, > > * From: Alan Greenberger > *Date: Mon, 3 Feb 2014 09:34:42 -0500 >> When I plug in a Logitech C170 webcam, /proc/asound/cards shows: >> 0 [SB ]: HDA-Intel - HDA ATI SB >> HDA ATI SB at 0xfbdf4000 ir

Re: Re^2: A persistent name for a sound device.

On my Debian desktop I created the following file: $ cat /etc/modprobe.d/sound.conf alias snd-card-0 snd-emu10k1 options snd-emu10k1 index=0 alias snd-card-1 snd-intel8x0 options snd-intel8x0 index=1 The emu10k1 is a PCI sound card and the intel8x0 is the onboard sound. I have the emu10k1 connec

Re^2: A persistent name for a sound device.

On Tue, 2014-02-04 at 08:57 -0800, pe...@easthope.ca wrote: > Alan, > > * From: Alan Greenberger > * Date: Mon, 3 Feb 2014 09:34:42 -0500 > > When I plug in a Logitech C170 webcam, /proc/asound/cards shows: > > 0 [SB ]: HDA-Intel - HDA ATI SB > > HDA ATI

Re^2: A persistent name for a sound device.

Alan, * From: Alan Greenberger ine without changing the hardware. Does each device always retain its card number across the reboot? In my case no. Consequently I can reboot and find that the VoIP ring is being sent to the headset. Not acceptable. A persistent name remains associated wit

Re: A persistent name for a sound device.

On 04/02/14 02:33, pe...@easthope.ca wrote: > * From: Scott Ferguson scott.ferguson.debian.u...@gmail.com > * Date: Mon, 03 Feb 2014 16:30:49 +1100 >> There are a number of parent devices, don't try and match for more than >> one value per parent device. >> ... >> KERNEL=="controlC3", ATT

Re(2): A persistent name for a sound device.

* From: Scott Ferguson > KERNEL=="controlC3", ATTRS{idProduct}=="0008", ATTRS{id}=="Device", > ATTRS{product}=="C-Media USB Audio Device ", SYMLINK+="USBspeakers" > GROUP=="sound" Here ATTRS{idProduct} and ATTRS{product} are in the same node and you just said "one value per parent device

Re: A persistent name for a sound device.

On 2014-02-03, pe...@easthope.ca wrote: > I'm interested to make a persistent name for a sound device. > The output of "udevadm info -a -p $(udevadm info -q path -n /dev/... )" > follows. > What exactly is meant by the last sentence of the introductory paragraph? &

Re: A persistent name for a sound device.

On 03/02/14 16:30, Scott Ferguson wrote: > On 03/02/14 15:12, pe...@easthope.ca wrote: >> I'm interested to make a persistent name for a sound device. >> The output of "udevadm info -a -p $(udevadm info -q path -n /dev/... )" >> follows. >> What ex

Re: A persistent name for a sound device.

On 03/02/14 15:12, pe...@easthope.ca wrote: > I'm interested to make a persistent name for a sound device. > The output of "udevadm info -a -p $(udevadm info -q path -n /dev/... )" > follows. > What exactly is meant by the last sentence of the introductory paragra

A persistent name for a sound device.

I'm interested to make a persistent name for a sound device. The output of "udevadm info -a -p $(udevadm info -q path -n /dev/... )" follows. What exactly is meant by the last sentence of the introductory paragraph? Must the first match occur in the first stanza of the info? D

Re: Line-in of CM106 like sound device does not work

On 12/25/2013 03:20 PM, Robin wrote: As a start from a terminal run alsamixer, hit F6 to select device and check the line-in level. Thanks Ralf and Robin for the replies. I now somehow got it working properly, but I don't know what has changed. I first removed pulseaudio, but although I co

Re: Line-in of CM106 like sound device does not work

On 25 December 2013 11:30, Sietse Achterop wrote: > Dear List, > > Using Wheezy, version 7.3, with the 3.11 kernel from wheezy-backports, > I have an exteral USB sound device from Sweex, see >http://www.sweex.com/nl/assortiment/sound-vision/sound-cards/sc016/ > > lsu

Re: Line-in of CM106 like sound device does not work

On 12/25/2013 12:30 PM, Sietse Achterop wrote: lsusb says: Bus 003 Device 004: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device This hardware seems OK, because under Windows it is working properly. The problem is that no signal is seen from the line-in input. In addition

Re: Line-in of CM106 like sound device does not work

Pulseaudio + working audio = a paradox Perhaps your problems aren't related to pulseaudio, but at least for troubleshooting purge remove this idiotic, completely bad programmed sound server! My Linux PC is a DAW for audio productions, all mails that are pro pulseaudio are automagically moved to t

Line-in of CM106 like sound device does not work

Dear List, Using Wheezy, version 7.3, with the 3.11 kernel from wheezy-backports, I have an exteral USB sound device from Sweex, see http://www.sweex.com/nl/assortiment/sound-vision/sound-cards/sc016/ lsusb says: Bus 003 Device 004: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like

Re: Crackling sound from usb sound device

Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? Hi Ralf, changed the slot for the audio device, now it works. Thanks for the hint Klaus -- To UNSUBSCRIBE, email to debian-user

Re: Crackling sound from usb sound device

Does it crackle, when the USB storage device and the USB video device are unplugged? Were the USB storage and video devices plugged to other USB slots in the past? The video device is the builtin camera of the Thinkpad. I unplugged the USB CD and got the same behaviour (reboot, while mpd is p

Re: Crackling sound from usb sound device

On Sat, 2013-03-23 at 17:11 +0100, Ralf Mardorf wrote: > On Sat, 2013-03-23 at 16:04 +0100, Klaus Pieper wrote: > > > $ lsusb -t > > > > > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M > > |__ Port 5: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M > > |__ Port 1: Dev

Re: Crackling sound from usb sound device

On Sat, 2013-03-23 at 16:04 +0100, Klaus Pieper wrote: > > $ lsusb -t > > > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M > |__ Port 5: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M > |__ Port 1: Dev 6, If 0, Class=stor., Driver=usb-storage, 480M > |__ Port

Re: Crackling sound from usb sound device

On 03/23/2013 03:00 PM, Ralf Mardorf wrote: With a new kernel there could be a different IRQ assignment, run $ lsusb -t /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub,

Re: Crackling sound from usb sound device

With a new kernel there could be a different IRQ assignment, run $ lsusb -t $ cat /proc/interrupts And if in use $ /etc/init.d/rtirq status -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive:

Crackling sound from usb sound device

Hi, I have been using an external dac over usb for some months. Since about two weeks sometimes sound is distorted (irregualar crackles, which usually diappear after closing and reopening the application, i.e. mpd, xine, rhythmbox or a stream from firefox, some times). I am under the impress

No sound device after reboot

Hi, I have Squeeze - x86 version - and when I reboot the system on the panel the icon of the sound volume manager is disabled. How to solve this?

Re: sound device or resource busy

On Thu, 11 Aug 2011 13:24:05 -0500, Hugo Vanwoerkom wrote: > Running Sid. Which just upgraded libaudio2, libaudio-dev and nas from > 1.9.2-7 to 1.9.2-8. > > I run 2 sound apps: mplayer(sound nly) and a nas app, that uses nas and > libaudio2 and liaudio-dev. > > Since the upgrade I can only run

sound device or resource busy

Hi, Running Sid. Which just upgraded libaudio2, libaudio-dev and nas from 1.9.2-7 to 1.9.2-8. I run 2 sound apps: mplayer(sound nly) and a nas app, that uses nas and libaudio2 and liaudio-dev. Since the upgrade I can only run 1: either the nas app or mplayer, and for the other I get: [A

Re: figuring out sound device?

Kamaraju S Kusumanchi writes: > I want to extract sound from a youtube video (I dont care about the > video part, only sound). I did I would try this: ffmpeg -i filename filename.mp3 -- Regards, Pal -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org w

figuring out sound device?

I want to extract sound from a youtube video (I dont care about the video part, only sound). I did $ ffmpeg -i /dev/dsp -o /tmp/song.mp3 However that does not seem to work because I do not know how to tell ffmpeg that the video has finished and give me the output. If I press ctrl-c, the comman

squeeze sound device error problem

I have the following following sound card as in lspci -v 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) Subsystem: Sony Corporation Device 81ef Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at d01c (64-bit, n

Re (4): Default alsa sound device in Squeeze ...

* From: Camaleón * Date: Fri, 8 Oct 2010 20:26:53 +0200 > It's quite the same information you already sent, but adds another > method for setting the default sound device. For Iceweasel and the few multimedia I've tried, this works. Multimedia in this Squeeze no

Re: Re (2): Default alsa sound device in Squeeze ...

te the same information you already sent, but adds another method for setting the default sound device. > Mailing list detail: I've removed the erroneous "." from the Message-ID > field of the header. :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-u

Re: Default alsa sound device in Squeeze ...

On Wed, 06 Oct 2010 09:33:23 -0700, peasthope wrote: > ... is the on-board device in a system here. > > I'm interested to make a USB audio adapter the default and found this > discussion. > http://www.alsa-project.org/main/index.php/Asoundrc#The_default_plugin > Is it applicable for Squeeze? I

Default alsa sound device in Squeeze ...

... is the on-board device in a system here. I'm interested to make a USB audio adapter the default and found this discussion. http://www.alsa-project.org/main/index.php/Asoundrc#The_default_plugin Is it applicable for Squeeze? Is there a better way? Thanks, ... Peter E. -- Telep

Sound device missing in gnome

I have the following driver loaded: snd_hda_intel but pulseaudio is only giving me the dummy device. I'm not even being given the choice to select the onboard audio. Since everything "just worked" before, I have no idea what's changed since my last upgrade with testing/unstable. How can I ge

Re: where is the sound device in debian?

On Fri, May 29, 2009 at 8:12 AM, Yi Zhao wrote: > yes, it is!! > > thanks very much! > > --- On Fri, 5/29/09, Nigel Henry wrote: > > From: Nigel Henry > Subject: Re: where is the sound device in debian? > To: debian-user@lists.debian.org > Date: Friday, May 29,

Re: where is the sound device in debian?

yes, it is!! thanks very much! --- On Fri, 5/29/09, Nigel Henry wrote: From: Nigel Henry Subject: Re: where is the sound device in debian? To: debian-user@lists.debian.org Date: Friday, May 29, 2009, 5:06 PM On Friday 29 May 2009 10:26, Yi Zhao wrote: > hi, all, I'm using debian lenn

Re: where is the sound device in debian?

On Fri,29.May.09, 16:26:15, Yi Zhao wrote: > hi, all, I'm using debian lenny, but I can't found /dev/dsp or /dev/audio > device in /dev directory? where is it?? These "devices" are only needed if your app relies on OSS. Try switching it to 'alsa' for the output. If this is not possible then you

Re: where is the sound device in debian?

On Friday 29 May 2009 10:26, Yi Zhao wrote: > hi, all, I'm using debian lenny, but I can't found /dev/dsp or /dev/audio > device in /dev directory? where is it?? Try installing the oss-compat package, and they should turn up in /dev. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-use

where is the sound device in debian?

hi, all, I'm using debian lenny, but I can't found /dev/dsp or /dev/audio device in /dev directory? where is it??

Re: How To Find Which Sound Device Is Used?

On Thu, Apr 24, 2008 at 11:30 PM, Hal Vaughan <[EMAIL PROTECTED]> wrote: > In my config I am pointing to /dev/dsp, but I don't think that's > actually in use. It could be, but everything else with IceCast and I'm not familiar with blackice, so I don't know how relevant this is to your situation

How To Find Which Sound Device Is Used?

This could be an issue with Darkice, but I think at this point it's more that I'm not sure what sound device I'm using. I have a system running Sarge (yes, it'll be updated to Etch, then eventually Lenny in my copious amounts of free time!) and I have a radio hooked up to

Re: choosing a sound device.

On Sun, May 27, 2007 at 10:15:03PM -0700, [EMAIL PROTECTED] wrote: > How is a sound device selected in Iceweasel > and in Xine? AFAIK iceweasel can be configured to use either esd or alsa. alsa probably means it will use the primary device and esd should be configurable. I think in xi

choosing a sound device.

A machine can have more than one sound device. A PCI sound card and a USB headset for example. Skype allows devices to be chosen in Tools > Options > Sound Devices. Nothing similar is evident in iceweasel > Edit > Preferences nor in xine > Audio. How is a sound device select

Re: making usb headset the default sound device

AIL PROTECTED]> writes: > I am using debian sid, updated today. 17 Apr. > > The audio port on my t40 laptop is getting flaky. I have just purchased > a usb headset and wish for it to be the default sound device. I have > made sure that the snd-usb-audio module is loading n

making usb headset the default sound device

I am using debian sid, updated today. 17 Apr. The audio port on my t40 laptop is getting flaky. I have just purchased a usb headset and wish for it to be the default sound device. I have made sure that the snd-usb-audio module is loading not only at boot but also when plugging in after boot. I

Re: switching to kernel 2.6 - splay "Failed to open sound device" /dev/dsp

Daniel B. wrote: In trying to switch to kernel 2.6(.8) and udev on Sarge, I found that splay/xsplay fails, saying "Failed to open sound device". Using strace, I see that opening /dev/dsp is failing: open("/dev/dsp" ... ) = -1 EBUSY (Device or resource busy). I'm

switching to kernel 2.6 - splay "Failed to open sound device" /dev/dsp

In trying to switch to kernel 2.6(.8) and udev on Sarge, I found that splay/xsplay fails, saying "Failed to open sound device". Using strace, I see that opening /dev/dsp is failing: open("/dev/dsp" ... ) = -1 EBUSY (Device or resource busy). I'm not knowingly runn

Re: having esd release sound device in gnome...

use some > programs (e.g. festival, skype, realplayer etc.) which are unable to use esd > for sound support but instead insist on directly using the sound device > directly (e.g. /dev/sound/dsp). They obviously fail if I try to use them > when the automatically started esd is running, sinc

Re: having esd release sound device in gnome...

I also want to use some > programs (e.g. festival, skype, realplayer etc.) which are unable to use esd > for sound support but instead insist on directly using the sound device > directly (e.g. /dev/sound/dsp). They obviously fail if I try to use them > when the automatically starte

having esd release sound device in gnome...

esd for sound support but instead insist on directly using the sound device directly (e.g. /dev/sound/dsp). They obviously fail if I try to use them when the automatically started esd is running, since the sound device is allocated by it. However, it IS possible to have the esd daemon release the

Logitech Mobile Pro to use as sound device

Dear all, quite a while ago, I received a Logitech Mobile Pro to use with my cell phone. This works as expected. :) For handsfree communication via skype, it works also on a Windows installation :| However, I cannot get it to work under Linux :( After searching and browsing for this issue, I h

Re: Sound Device Not Shared -- Working Now

uot; } # # OSS Compability # pcm.!dsp0 { type plug slave.pcm "duplex" } ctl.!mixer0 { type hw card 0 } 4. for XMMS, I need to change preferences to use ALSA instead of OSS. [EMAIL PROTECTED] 03 9617 2235 05/01/2006 05:05 PM                 To:        debian-user@lists.debian.org  

Re: Sound Device Not Shared

[EMAIL PROTECTED] wrote: > I'm using ALSA and the only issue is if an application is using Sound > device (/dev/dsp) and another > application is trying to use it, it says "/dev/dsp" is already in use. > > What can I do it share the sound device?? Make your other s

Re: Sound Device Not Shared

On Thu, 05 Jan 2006 21:29:03 -0600 Adam Porter <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > if I stop the application which is using the sound device and then other > > application can use the sound device... > > its more like exclusive acce

Re: Sound Device Not Shared

On Wed, 04 Jan 2006 23:43:08 -0600 Adam Porter <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > I'm using ALSA and the only issue is if an application is using Sound > > device (/dev/dsp) and another > > application is trying to use it, i

Re: Sound Device Not Shared

[EMAIL PROTECTED] wrote: > if I stop the application which is using the sound device and then other > application can use the sound device... > its more like exclusive access to the sound device by ALSA > > even if there is a warning sound from Anti-virus program, sound devi

Re: Sound Device Not Shared

David Berg <[EMAIL PROTECTED]> writes: > On 1/4/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: >> this is a problem I've struggled with for a long while. Basically, >> you can set up alsa to share the sound device by doing its own >> software mixing. I

Re: Sound Device Not Shared

[EMAIL PROTECTED] wrote: > > if I stop the application which is using the sound device and then other > application can use the sound device... > its more like exclusive access to the sound device by ALSA This isn't correct. ALSA allows concurrent access by multiple progra

Re: Sound Device Not Shared

[EMAIL PROTECTED] wrote: > > I'm using ALSA and the only issue is if an application is using Sound > device (/dev/dsp) and another > application is trying to use it, it says "/dev/dsp" is already in use. > > What can I do it share the sound device?? Try and c

Re: Sound Device Not Shared

if I stop the application which is using the sound device and then other application can use the sound device... its more like exclusive access to the sound device by ALSA even if there is a warning sound from Anti-virus program, sound device get locked and I can not play music anymore until

Re: Sound Device Not Shared

[EMAIL PROTECTED] wrote: > I'm using ALSA and the only issue is if an application is using Sound > device (/dev/dsp) and another > application is trying to use it, it says "/dev/dsp" is already in use. > > What can I do it share the sound device?? If I understand

Re: Sound Device Not Shared

On 1/4/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Thu, 5 Jan 2006 10:08:02 +1100 > [EMAIL PROTECTED] wrote: > > > I'm using ALSA and the only issue is if an application is using Sound > > device (/dev/dsp) and another > > application is t

Re: Sound Device Not Shared

On Thu, 5 Jan 2006 10:08:02 +1100 [EMAIL PROTECTED] wrote: > I'm using ALSA and the only issue is if an application is using Sound > device (/dev/dsp) and another > application is trying to use it, it says "/dev/dsp" is already in use. > > What can I do it share

Re: Sound device not shared

Presumably your sound card has only one channel. To play sounds from more than one program together, you must use another program to mix them together. Two such programs are esd and arts. To use those, the programs playing the sounds will have to support output to esd or arts respectively. But A

Re: Sound device not shared

[EMAIL PROTECTED] writes: > I'm using ALSA and the only issue is if an application is using Sound > device (/dev/dsp) and another application is trying to use it, it says > "/dev/dsp" is already in use. > > What can I do it share the sound device?? Presumably your s

Sound Device Not Shared

I'm using ALSA and the only issue is if an application is using Sound device (/dev/dsp) and another application is trying to use it, it says "/dev/dsp" is already in use. What can I do it share the sound device?? Alliance Bernstein: Winner of Money Management "FUND MANA

gap in sound device numbering

Hello, in my PC there is a single on-board sound card that works great using ALSA and OSS emulation where necessary. The sound card is card 0 for alsa. I have a bluetooth headset as well. Whenever I attach the bluetooth headset, a new ALSA device for it is created, but it gets the device number 2

Re: Can't open default sound device!

On Wed, 20 Jul 2005 03:01:31 +, David Roguin wrote: > lsmod > > Module Size Used by > snd_pcm_oss48168 0 > snd_mixer_oss 16640 1 snd_pcm_oss > snd_pcm85384 1 snd_pcm_oss > snd_page_alloc 11144 1 snd_pcm > snd_timer

Re: Can't open default sound device!

On 7/19/05, Trace Green <[EMAIL PROTECTED]> wrote: > David Roguin wrote: > > >Yesterday i upgrade my system, and the sound card stop working. > >This is what it says when i try to play something with mpg123: > > > >Can't open default sound devi

Can't open default sound device!

Yesterday i upgrade my system, and the sound card stop working. This is what it says when i try to play something with mpg123: Can't open default sound device! Here it is what lspci tells me :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02) :00:00.

Re: Can't open default sound device during boot... works fine after boot

> The sound card has the standard Debian permissions, and all > users, including root, have been added to the audio group, so > that part checks out. Answering my own e-mail here, I ran this by a buddy, and he scratched his head, said dunno, and that it still sounded like a permissions problem.

Can't open default sound device during boot... works fine after boot

27; for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Can't open default sound device! play result = So, my question is, has anyone any idea why, at the very end of the boot-up process, I'm not able to write to my sound card, but just a few seconds later, f

Re: ALSA Cannot find Sound Device

Hi! I dunno whether Kenneth' idea helped you - if not maybe mine does There seems to be a problem with the ALSA driver not being able to find my sound card. I can get sound if I use the OSS Driver in XMMS but not ALSA. I even get sound when I us XINE. When I run alsaconf it also says "No suppo

Re: ALSA Cannot find Sound Device

Alexander B. Cheng wrote: Hi All, There seems to be a problem with the ALSA driver not being able to find my sound card. I can get sound if I use the OSS Driver in XMMS but not ALSA. I even get sound when I us XINE. Below is my log: Mar 14 03:22:49 knsmen kernel: Creative EMU10K1 PCI Audio Dri

  1   2   >