[pulseaudio-discuss] [OT] Re: Help in setting up PA... SOLVED
mi madre es peruana y mi padre es escosés pero la mayoría de mi vida he pasado en los estados unidos... asi que, para evitar malentendidos, uso ingles en discuccioes tecnicas Saludos R Juan A Fuentes Bermudez wrote: no me digas que hablas español? saludos - Original Message - *From:* Richard Geddes mailto:[EMAIL PROTECTED] *To:* General PulseAudio Discussion mailto:pulseaudio-discuss@mail.0pointer.de *Sent:* Tuesday, June 03, 2008 11:56 PM *Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED de nada... fue un placer... tambien aprendi algo... Saludos R Juan A Fuentes Bermudez wrote: hi, very very thank you, now i am using the last configuration that you say me, now are 3 cards actives, only the HDMI is not working via PA, i will trying coment and uncoment one to one devices, i am think that HDMI device only have output not have input very very thank my friend you have a spanish jamon fron my :) - Original Message - *From:* Richard Geddes mailto:[EMAIL PROTECTED] *To:* General PulseAudio Discussion mailto:pulseaudio-discuss@mail.0pointer.de *Sent:* Tuesday, June 03, 2008 10:24 PM *Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED ok... 1) The/var/log/messages indicates that you are running the pa server as root (you say as well) and it also says the pa server is not intended to be run as root... so you might want to change to a regular user and use sudo for root related activities. 2) I think that the terjeta 3 requires some special parameters ... similar to tarjeta 2. I'm not familiar with ice1724 device driver, but you may want to try the same setup for tarjeta 3 as for tarjeta 2. This is just a guess... anyone with knowledge about how to setup an ice1724 source/sink in pa... please speak up now... 3) Of course, it looks like tarjeta 3 was identified by the module-detect/module-hal-detect. What we've done is disable this and tried to set the sources/sinks manually. module-detect/module-hal-detect seems to be an all or nothing proposition... if anyone knows of a way to auto-detect specific devices and manually set others in the same config file... please speak up now. Well, you might want to try this (once again, a guess): a) re-enable the auto-detect - we know this will detect tarjeta 0 and 3, and not tarjeta 1 and 2 b) add only the manual configuration for tarjeta 2, after that So your default.pa file would contain: ### Automatically load driver modules depending on the hardware available .ifexists module-hal-detect.so load-module module-hal-detect .else ### Alternatively use the static hardware detection module (for systems that ### lack HAL support) load-module module-detect .endif # Load the devices: #load-module module-alsa-sink sink_name=nvidia_out device=hw:0 #load-module module-alsa-source source_name=nvidia_in device=hw:0 #load-module module-alsa-sink sink_name=hdmi_out device=hw:1 #load-module module-alsa-source source_name=hdmi_in device=hw:1 load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=ewx2496_in device=hw:2 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 #load-module module-alsa-sink sink_name=e192m_out device=hw:3 #load-module module-alsa-source source_name=e192m_in device=hw:3 # Select default device #set-default-sink nvidia_out #set-default-source nvidia_in Let's see if module-hal-detect/module-detect allows manual loading of sources/sinks. R Juan A Fuentes Bermudez wrote: hi, the problem is partial solved i an coment and paste the module taht you say my the pa server not start after reboot, i am coment and uncoment one to one, to discart waht is the card tthat cause problem , # Load the devices: load-module module-alsa-sink sink_name=nvidia_out device=hw:0 load-module module-alsa-source source_name=nvidia_in device=hw:0 #load-module module-alsa-sink sink_name=hdmi_out device=hw:1 #load-module module-alsa-source source_name=hdmi_in device=hw:1 load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 channels=10
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
#load-module module-detect
#.endif
I forgot to mention, to see error/warning messages I used:
grep pulse /var/log/messages
there may be better ways, though
Juan A Fuentes Bermudez wrote:
hi
very thank , i will try this, only aquestion:
to coment the autodetec module what is the corret?
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
#load-module module-detect
#.endif
or
.ifexists module-hal-detect.so
#load-module module-hal-detect
.else
#load-module module-detect
.endif
very thank
- Original Message -
*From:* Richard Geddes mailto:[EMAIL PROTECTED]
*To:* General PulseAudio Discussion
mailto:pulseaudio-discuss@mail.0pointer.de
*Sent:* Tuesday, June 03, 2008 6:02 PM
*Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
Now as I understand it, when linux starts,
1) there is a program called hald (hardware abstraction layer
daemon) that identifies the hardware attached to your computer.
In the output of aplay, each card is given an identifier...
tarjeta {0 -3}
2) other programs like pa use the info hald provides to make
decisions about how to use the hardware.
In the case of tarjeta 2 - EWX2496 using the ice1712 driver
(this same chip is in my tarjeta), apparently pulseaudio or hald
did not identify it correctly, and when trying to connect to this
tarjeta, pa realizes this and says no.
The default global pa config file (/etc/pulse/default.pa) in
ubuntu has these statements:
.ifexists module-hal-detect.so
load-module module-hal-detect
.else
load-module module-detect
.endif
which is a means of auto-detecting the tarjetas on your system.
Let's change this:
1) make a copy of your original global config file
cd /etc/pulse/
sudo cp default.pa default.pa.original
2) comment out the lines that deal with auto detecting the
tarjetas (the lines above)
3) Add these lines in it's place: sudo [vi,gedit,...] default.pa
# Load the devices:
load-module module-alsa-sink sink_name=nvidia_out device=hw:0
load-module module-alsa-source source_name=nvidia_in device=hw:0
load-module module-alsa-sink sink_name=hdmi_out device=hw:1
load-module module-alsa-source source_name=hdmi_in device=hw:1
load-module module-alsa-sink sink_name=ewx2496_out device=hw:2
channels=10
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
load-module module-alsa-source source_name=ewx2496_in device=hw:2
channels=12
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9
load-module module-alsa-sink sink_name=e192m_out device=hw:3
load-module module-alsa-source source_name=e192m_in device=hw:3
# Select default device
set-default-sink nvidia_out
set-default-source nvidia_in
Note: We are telling pa to use devices identified by your system
labeled hw:{0,1,2,3}... nothing special, except for the ewx2496
that uses the ice1712 device driver. This is the same chip my
tarjeta uses, and in that case I had to add extra information
about the chip... the part that says channel_map=... I'm not
sure if the other tarjetas need special mappings or instructions,
but give this a try.
4) Restart pa ... in ubuntu, I would try sudo
/etc/init.d/pulseaudio {start,stop,...} and it would not give
feedback if the server status had changed. So I would use the pa
manager (paman) to start/stop the pa server. Frequently, I would
not know if the server was still running and would use ps aux |
grep pulse to check status.
Let's see what happens
Juan A Fuentes Bermudez wrote:
1) Tell me which cards are identified by the alsamixer and which
cards are identified by pa(pulseaudio).
asoundconf list
Names of available sound cards:
NVidia (identified by PA)
HDMI
EWX2496
E192M (identified by PA)
aplay -l
Lista de PLAYBACK Dispositivos Hardware
tarjeta 0: NVidia [HDA NVidia], dispositivo 0: AD198x Analog
[AD198x Analog]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 0: NVidia [HDA NVidia], dispositivo 1: AD198x Digital
[AD198x Digital]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 1: HDMI [HDA ATI HDMI], dispositivo 3: ATI HDMI [ATI HDMI]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 2: EWX2496 [TerraTec EWX24/96], dispositivo 0: ICE1712
multi [ICE1712 multi]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 3: E192M [ESI Waveterminal 192M], dispositivo 0: ICE1724
[ICE1724]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 3: E192M [ESI
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
Now as I understand it, when linux starts,
1) there is a program called hald (hardware abstraction layer daemon)
that identifies the hardware attached to your computer. In the output
of aplay, each card is given an identifier... tarjeta {0 -3}
2) other programs like pa use the info hald provides to make decisions
about how to use the hardware.
In the case of tarjeta 2 - EWX2496 using the ice1712 driver (this same
chip is in my tarjeta), apparently pulseaudio or hald did not identify
it correctly, and when trying to connect to this tarjeta, pa realizes
this and says no.
The default global pa config file (/etc/pulse/default.pa) in ubuntu has
these statements:
.ifexists module-hal-detect.so
load-module module-hal-detect
.else
load-module module-detect
.endif
which is a means of auto-detecting the tarjetas on your system. Let's
change this:
1) make a copy of your original global config file
cd /etc/pulse/
sudo cp default.pa default.pa.original
2) comment out the lines that deal with auto detecting the tarjetas (the
lines above)
3) Add these lines in it's place: sudo [vi,gedit,...] default.pa
# Load the devices:
load-module module-alsa-sink sink_name=nvidia_out device=hw:0
load-module module-alsa-source source_name=nvidia_in device=hw:0
load-module module-alsa-sink sink_name=hdmi_out device=hw:1
load-module module-alsa-source source_name=hdmi_in device=hw:1
load-module module-alsa-sink sink_name=ewx2496_out device=hw:2
channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
load-module module-alsa-source source_name=ewx2496_in device=hw:2
channels=12
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9
load-module module-alsa-sink sink_name=e192m_out device=hw:3
load-module module-alsa-source source_name=e192m_in device=hw:3
# Select default device
set-default-sink nvidia_out
set-default-source nvidia_in
Note: We are telling pa to use devices identified by your system labeled
hw:{0,1,2,3}... nothing special, except for the ewx2496 that uses the
ice1712 device driver. This is the same chip my tarjeta uses, and in
that case I had to add extra information about the chip... the part that
says channel_map=... I'm not sure if the other tarjetas need special
mappings or instructions, but give this a try.
4) Restart pa ... in ubuntu, I would try sudo /etc/init.d/pulseaudio
{start,stop,...} and it would not give feedback if the server status had
changed. So I would use the pa manager (paman) to start/stop the pa
server. Frequently, I would not know if the server was still running
and would use ps aux | grep pulse to check status.
Let's see what happens
Juan A Fuentes Bermudez wrote:
1) Tell me which cards are identified by the alsamixer and which cards
are identified by pa(pulseaudio).
asoundconf list
Names of available sound cards:
NVidia (identified by PA)
HDMI
EWX2496
E192M (identified by PA)
aplay -l
Lista de PLAYBACK Dispositivos Hardware
tarjeta 0: NVidia [HDA NVidia], dispositivo 0: AD198x Analog [AD198x
Analog]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 0: NVidia [HDA NVidia], dispositivo 1: AD198x Digital [AD198x
Digital]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 1: HDMI [HDA ATI HDMI], dispositivo 3: ATI HDMI [ATI HDMI]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 2: EWX2496 [TerraTec EWX24/96], dispositivo 0: ICE1712 multi
[ICE1712 multi]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 3: E192M [ESI Waveterminal 192M], dispositivo 0: ICE1724 [ICE1724]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 3: E192M [ESI Waveterminal 192M], dispositivo 1: ICE1724
Secondary [ICE1724 Secondary]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
tarjeta 3: E192M [ESI Waveterminal 192M], dispositivo 2: ICE1724
Surrounds [ICE1724 Surround PCM]
Subdispositivos: 3/3
Subdispositivo #0: subdevice #0
Subdispositivo #1: subdevice #1
Subdispositivo #2: subdevice #2
2) Can you make sound with your speakers with pa and the cards that it
does identify?
yes i need to route the sound thru the no identified sound cards via PA
when i por example, play a mp3, i can route via alsa the sound
thru devices that no identified in PA, i am sure that card is runing
correctly
sorry and very thank
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
de nada... fue un placer... tambien aprendi algo... Saludos R Juan A Fuentes Bermudez wrote: hi, very very thank you, now i am using the last configuration that you say me, now are 3 cards actives, only the HDMI is not working via PA, i will trying coment and uncoment one to one devices, i am think that HDMI device only have output not have input very very thank my friend you have a spanish jamon fron my :) - Original Message - *From:* Richard Geddes mailto:[EMAIL PROTECTED] *To:* General PulseAudio Discussion mailto:pulseaudio-discuss@mail.0pointer.de *Sent:* Tuesday, June 03, 2008 10:24 PM *Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED ok... 1) The/var/log/messages indicates that you are running the pa server as root (you say as well) and it also says the pa server is not intended to be run as root... so you might want to change to a regular user and use sudo for root related activities. 2) I think that the terjeta 3 requires some special parameters ... similar to tarjeta 2. I'm not familiar with ice1724 device driver, but you may want to try the same setup for tarjeta 3 as for tarjeta 2. This is just a guess... anyone with knowledge about how to setup an ice1724 source/sink in pa... please speak up now... 3) Of course, it looks like tarjeta 3 was identified by the module-detect/module-hal-detect. What we've done is disable this and tried to set the sources/sinks manually. module-detect/module-hal-detect seems to be an all or nothing proposition... if anyone knows of a way to auto-detect specific devices and manually set others in the same config file... please speak up now. Well, you might want to try this (once again, a guess): a) re-enable the auto-detect - we know this will detect tarjeta 0 and 3, and not tarjeta 1 and 2 b) add only the manual configuration for tarjeta 2, after that So your default.pa file would contain: ### Automatically load driver modules depending on the hardware available .ifexists module-hal-detect.so load-module module-hal-detect .else ### Alternatively use the static hardware detection module (for systems that ### lack HAL support) load-module module-detect .endif # Load the devices: #load-module module-alsa-sink sink_name=nvidia_out device=hw:0 #load-module module-alsa-source source_name=nvidia_in device=hw:0 #load-module module-alsa-sink sink_name=hdmi_out device=hw:1 #load-module module-alsa-source source_name=hdmi_in device=hw:1 load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=ewx2496_in device=hw:2 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 #load-module module-alsa-sink sink_name=e192m_out device=hw:3 #load-module module-alsa-source source_name=e192m_in device=hw:3 # Select default device #set-default-sink nvidia_out #set-default-source nvidia_in Let's see if module-hal-detect/module-detect allows manual loading of sources/sinks. R Juan A Fuentes Bermudez wrote: hi, the problem is partial solved i an coment and paste the module taht you say my the pa server not start after reboot, i am coment and uncoment one to one, to discart waht is the card tthat cause problem , # Load the devices: load-module module-alsa-sink sink_name=nvidia_out device=hw:0 load-module module-alsa-source source_name=nvidia_in device=hw:0 #load-module module-alsa-sink sink_name=hdmi_out device=hw:1 #load-module module-alsa-source source_name=hdmi_in device=hw:1 load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=ewx2496_in device=hw:2 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 #load-module module-alsa-sink sink_name=e192m_out device=hw:3 #load-module module-alsa-source source_name=e192m_in device=hw:3 in this mode, load pa server, and in the padevchooser apear the ewx2496 card :) very happy when un coment the e192 card, again pa server not start same when uncoment hdmi card i like active also e192 card, is posible? i am to paste this info, this is the first mail i want to send to list : hi, the server not start, always i am login as root can you test the information? # grep pulse /var/log/messages Jun 2 14:39:39 64-1 pulseaudio[6430]: main.c: This program is not intended to be run as root (unless --system
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
Hi, I'm back again. I upgraded to Ubuntu 8.04 which uses PA as the default sound server and new hardware(AMD Athlon X2) The PA server is version 0.9.10. My /etc/default.pa looks like this: .nofail load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav .fail load-module module-alsa-sink sink_name=intel_hda_out device=hw:0 load-module module-alsa-source source_name=intel_hda_in device=hw:0 load-module module-alsa-sink sink_name=delta_out device=hw:1 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=delta_in device=hw:1 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 set-default-sink delta_out set-default-source delta_in .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix load-module module-volume-restore load-module module-default-device-restore load-module module-rescue-streams load-module module-suspend-on-idle .ifexists module-gconf.so .nofail load-module module-gconf .fail .endif .ifexists module-x11-publish.so .nofail load-module module-x11-publish .fail .endif To get feedback from the PA server I used paman (pulseaudio sound manager in ubuntu) and it said that the intel_hda_out device is the default sink. I tried to force the default sink to be delta_out with pacmd, but that stopped the PA server... I didn't realize that when I exit paman, it shuts the pa server down. I was a little confused by that... expecting the server to stay alive. I noticed that I could play-sample to the delta_out and it sounded fine. It looked like I can get my Delta 66 card and PA to work but only in that play-sample mode. I did not realize that I had the volume-restore enabled, and it had quite a few settings from the past that were all related to intel_hda_out... also my ~/.pulse/default-sink file was also set to intel_hda_out... anyway even though the global config file(/etc/pulse/default.pa) set the default sink to delta_out, there are local config files in ~/.pulse/ that can also modify the defaults. It's probably in the literature somewhere, and it makes sense for clients that are sharing a server. Anyway, I after changing *all* (local and global) the config files, the system works... and pretty well. Hope this helps someone with their M-Audio Delta setup. R Tanu Kaskinen wrote: On Fri, Feb 01, 2008 at 03:02:40PM -0500, Richard Geddes wrote: You are correct... latest release Ubuntu 7.10 comes with PA 0.9.6. I'll look into getting the latest version of PA. My goal was to use PA as a replacement for esound server... I'd like to be able to record/mix different sound sources (midi, analog, sound from files (mp3, wav, ogg, etc)) and be able to create different file formats, including sound delivered in flash (I'm not a fan of flash as it consumes alot of cpu time, but it is in demand). I played with jackd for a while and was impressed with it's technical capabilities, but unfortunately, I haven't found a way to play flash sound through jackd... that is, flash in firefox. I found a how-to in the Ubuntu forum that seemed to patch together a solution the involved PA: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=548178 If you want to record midi and do other pro-audio stuff, then jack is the way to go. If you also want to do desktop stuff (like have every media player just work), then the best solution in my experience is to run pulseaudio on top of jack (like instructed in that link). A summary of what you'll have to do at minimum: - Get pulseaudio version = 0.9.7 - Remove device loading from /etc/pulse/default.pa and add the jack modules instead - Edit /etc/security/limits.conf as instructed in the link - Edit /etc/pulse/daemon.conf to enable realtime scheduling - Run jackd with -R parameter (i.e. in realtime mode) - Other stuff that I have forgot ;) If you are going to record midi, that probably means that you have some midi instrument that you want to be able to play live. That requires quite low latency. That's completely possible to achieve. Unfortunately it may require extensive tuning (mostly kernel, but you may need to tweak irq priorities as well). Vanilla kernels are AFAIK getting better and better regarding latency, so first try with your current kernel. The actual latency is controlled by jackd parameters -n and -p (read man jackd). If your kernel isn't able to provide low enough latency, you'll get drop-outs and xruns (the former being the audible consequence of the latter). If you have problems with setting pulseaudio to work in combination with jack, or anything else pulseaudio related, then feel free to ask further questions. If it turns out that your system needs latency-tuning, here are a few kernel options you could try without compiling an -rt patched kernel: CONFIG_NO_HZ=y CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_HIGH_RES_TIMERS=y (AFAIK
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
Juan, I'll try to help... 1) You have 4 sound cards in one computer... yes? 2) the alsamixer can identify all 4 cards. 3) The padevchooser identifies 2 cards 4) You want pulseaudio to identify all 4 cards -- If this sounds correct, I would start by getting hardware information about your cards. Are you familiar with CLI (command line interface)... ie how to use a shell in linux? or do you use the GUI (Grahpical User Interface) only? I'm asking this so I can explain better. R Juan A Fuentes Bermudez wrote: hi, sorry for my english i have 4 sound card in the alsamixer i can choice the 4 card to change parameters but when in the padevchooser i an click in te default sink only apears 2 card i use ubuntu hardy, with the default default.pa with hall_detect and detect module active how can list exact name of alsa devices to add module_alsa whit the correspond name of my 4 devices manually? sorry bye - Original Message - *From:* Richard Geddes mailto:[EMAIL PROTECTED] *To:* General PulseAudio Discussion mailto:pulseaudio-discuss@mail.0pointer.de *Sent:* Monday, June 02, 2008 3:34 PM *Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED Hi, I'm back again. I upgraded to Ubuntu 8.04 which uses PA as the default sound server and new hardware(AMD Athlon X2) The PA server is version 0.9.10. My /etc/default.pa looks like this: .nofail load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav .fail load-module module-alsa-sink sink_name=intel_hda_out device=hw:0 load-module module-alsa-source source_name=intel_hda_in device=hw:0 load-module module-alsa-sink sink_name=delta_out device=hw:1 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=delta_in device=hw:1 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 set-default-sink delta_out set-default-source delta_in .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix load-module module-volume-restore load-module module-default-device-restore load-module module-rescue-streams load-module module-suspend-on-idle .ifexists module-gconf.so .nofail load-module module-gconf .fail .endif .ifexists module-x11-publish.so .nofail load-module module-x11-publish .fail .endif To get feedback from the PA server I used paman (pulseaudio sound manager in ubuntu) and it said that the intel_hda_out device is the default sink. I tried to force the default sink to be delta_out with pacmd, but that stopped the PA server... I didn't realize that when I exit paman, it shuts the pa server down. I was a little confused by that... expecting the server to stay alive. I noticed that I could play-sample to the delta_out and it sounded fine. It looked like I can get my Delta 66 card and PA to work but only in that play-sample mode. I did not realize that I had the volume-restore enabled, and it had quite a few settings from the past that were all related to intel_hda_out... also my ~/.pulse/default-sink file was also set to intel_hda_out... anyway even though the global config file(/etc/pulse/default.pa) set the default sink to delta_out, there are local config files in ~/.pulse/ that can also modify the defaults. It's probably in the literature somewhere, and it makes sense for clients that are sharing a server. Anyway, I after changing *all* (local and global) the config files, the system works... and pretty well. Hope this helps someone with their M-Audio Delta setup. R Tanu Kaskinen wrote: On Fri, Feb 01, 2008 at 03:02:40PM -0500, Richard Geddes wrote: You are correct... latest release Ubuntu 7.10 comes with PA 0.9.6. I'll look into getting the latest version of PA. My goal was to use PA as a replacement for esound server... I'd like to be able to record/mix different sound sources (midi, analog, sound from files (mp3, wav, ogg, etc)) and be able to create different file formats, including sound delivered in flash (I'm not a fan of flash as it consumes alot of cpu time, but it is in demand). I played with jackd for a while and was impressed with it's technical capabilities, but unfortunately, I haven't found a way to play flash sound through jackd... that is, flash in firefox. I found a how-to in the Ubuntu forum that seemed to patch together a solution the involved PA: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=548178 If you want to record midi and do other pro-audio stuff, then jack is the way to go. If you also want to do desktop stuff (like have every media player just work
Re: [pulseaudio-discuss] Help in setting up PA... SOLVED
1) Tell me which cards are identified by the alsamixer and which cards are identified by pa(pulseaudio). 2) Can you make sound with your speakers with pa and the cards that it does identify? Juan A Fuentes Bermudez wrote: I'll try to help... thank 1) You have 4 sound cards in one computer... yes? yes 2) the alsamixer can identify all 4 cards. yes 3) The padevchooser identifies 2 cards yes 4) You want pulseaudio to identify all 4 cards yes, -- If this sounds correct, I would start by getting hardware information about your cards. ok, cards: 1. esi waveterminal 192m, ice1724 2. terratek ewx24/96, ice1712 3 hdmi ati, (integrated in my vga card) 4. soundmax 1988b, ad198x Are you familiar with CLI (command line interface)... ie how to use a shell in linux? or do you use the GUI (Grahpical User Interface) only? yes, i am use command line and gui, I'm asking this so I can explain better. very tahnk you for your interest Juan A Fuentes Bermudez wrote: hi, sorry for my english i have 4 sound card in the alsamixer i can choice the 4 card to change parameters but when in the padevchooser i an click in te default sink only apears 2 card i use ubuntu hardy, with the default default.pa with hall_detect and detect module active how can list exact name of alsa devices to add module_alsa whit the correspond name of my 4 devices manually? sorry bye - Original Message - *From:* Richard Geddes mailto:[EMAIL PROTECTED] *To:* General PulseAudio Discussion mailto:pulseaudio-discuss@mail.0pointer.de *Sent:* Monday, June 02, 2008 3:34 PM *Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED Hi, I'm back again. I upgraded to Ubuntu 8.04 which uses PA as the default sound server and new hardware(AMD Athlon X2) The PA server is version 0.9.10. My /etc/default.pa looks like this: .nofail load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav .fail load-module module-alsa-sink sink_name=intel_hda_out device=hw:0 load-module module-alsa-source source_name=intel_hda_in device=hw:0 load-module module-alsa-sink sink_name=delta_out device=hw:1 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=delta_in device=hw:1 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 set-default-sink delta_out set-default-source delta_in .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix load-module module-volume-restore load-module module-default-device-restore load-module module-rescue-streams load-module module-suspend-on-idle .ifexists module-gconf.so .nofail load-module module-gconf .fail .endif .ifexists module-x11-publish.so .nofail load-module module-x11-publish .fail .endif To get feedback from the PA server I used paman (pulseaudio sound manager in ubuntu) and it said that the intel_hda_out device is the default sink. I tried to force the default sink to be delta_out with pacmd, but that stopped the PA server... I didn't realize that when I exit paman, it shuts the pa server down. I was a little confused by that... expecting the server to stay alive. I noticed that I could play-sample to the delta_out and it sounded fine. It looked like I can get my Delta 66 card and PA to work but only in that play-sample mode. I did not realize that I had the volume-restore enabled, and it had quite a few settings from the past that were all related to intel_hda_out... also my ~/.pulse/default-sink file was also set to intel_hda_out... anyway even though the global config file(/etc/pulse/default.pa) set the default sink to delta_out, there are local config files in ~/.pulse/ that can also modify the defaults. It's probably in the literature somewhere, and it makes sense for clients that are sharing a server. Anyway, I after changing *all* (local and global) the config files, the system works... and pretty well. Hope this helps someone with their M-Audio Delta setup. R Tanu Kaskinen wrote: On Fri, Feb 01, 2008 at 03:02:40PM -0500, Richard Geddes wrote: You are correct... latest release Ubuntu 7.10 comes with PA 0.9.6
Re: [pulseaudio-discuss] Help in setting up PA
You are correct... latest release Ubuntu 7.10 comes with PA 0.9.6. I'll look into getting the latest version of PA. My goal was to use PA as a replacement for esound server... I'd like to be able to record/mix different sound sources (midi, analog, sound from files (mp3, wav, ogg, etc)) and be able to create different file formats, including sound delivered in flash (I'm not a fan of flash as it consumes alot of cpu time, but it is in demand). I played with jackd for a while and was impressed with it's technical capabilities, but unfortunately, I haven't found a way to play flash sound through jackd... that is, flash in firefox. I found a how-to in the Ubuntu forum that seemed to patch together a solution the involved PA: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=548178 and have run into configuration/version issues since. Question: PA, esound, jackd, etc.. are all called sound servers, implying that you can replace one with another... like apache vs iis is the main difference that they use different client/server communication protocols? So, the competition among the sound servers is really over the communication protocol... and it looks like sound performance/features is affected by the communication protocol. Tanu Kaskinen wrote: On Thu, Jan 31, 2008 at 08:52:32PM -0500, Richard Geddes wrote: The PA daemon is not starting and PA Manager is say connection refused . Not sure what to make of it, but your suggestions are welcome. Connection refused is the message you get when trying to use a pulse client program without having the daemon running. Here's some output from /var/log/messages: pulseaudio[7278]: main.c: Module load failed. pulseaudio[7278]: main.c: failed to initialize daemon. pulseaudio[7288]: pid.c: daemon already running. pulseaudio[7288]: main.c: pa_pid_file_create() failed. pulseaudio[7291]: pid.c: daemon already running. pulseaudio[7291]: main.c: pa_pid_file_create() failed. pulseaudio[7285]: module-alsa-sink.c: Failed to set hardware parameters: Operation not permitted pulseaudio[7285]: module.c: Failed to load module module-alsa-sink (argument: sink_name=delta_out device=hw:0 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7): initialization failed. pulseaudio[7285]: main.c: Module load failed. pulseaudio[7285]: main.c: failed to initialize daemon. pulseaudio[7294]: module-alsa-sink.c: Failed to set hardware parameters: Operation not permitted pulseaudio[7294]: module.c: Failed to load module module-alsa-sink (argument: sink_name=delta_out device=hw:0 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7): initialization failed. pulseaudio[7294]: main.c: Module load failed. pulseaudio[7294]: main.c: failed to initialize daemon. The Failed to set hardware parameters: Operation not permitted is an encrypted message, and means that pulseaudio couldn't open the device for 16-bit samples, because the device only supports 32-bit samples. You seem to have an older version of pulseaudio. Since 0.9.8 pulseaudio has supported 32-bit samples, so you'll have to upgrade to at least that version. An unrelated note: you seem to have made the decision to run pulseaudio as a system-wide daemon. That is not generally recommended way to run pulseaudio, it's only for the cases when the per-user way just doesn't cut it. This isn't a fatal mistake (if it's mistake at all, I don't know what kind of setup you actually have/need), and you don't necessarily need to fix it. Some information on this matter: http://www.pulseaudio.org/wiki/SystemWideInstance ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Help in setting up PA
The PA server has yet to deliver sound to my speakers. However, I noticed you had some special advice for someone configuring their M-Audio Delta44... I have an M-Audio Delta 66 and tried your suggestion for the M-Audio Delta 44: So, what you'll have to do is edit /etc/pulse/default.pa. Comment out module-hal-detect and module-detect, and then add these lines (if you don't need the sources, leave them out): # Load Delta 44: load-module module-alsa-sink sink_name=delta_out device=hw:0 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7 load-module module-alsa-source source_name=delta_in device=hw:0 channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9 # Set the default sink and source (not mandatory, intel-hda # would probably be used without this): set-default-sink delta_out set-default-source delta_in - The PA daemon is not starting and PA Manager is say connection refused . Not sure what to make of it, but your suggestions are welcome. Here's some output from /var/log/messages: pulseaudio[7278]: main.c: Module load failed. pulseaudio[7278]: main.c: failed to initialize daemon. pulseaudio[7288]: pid.c: daemon already running. pulseaudio[7288]: main.c: pa_pid_file_create() failed. pulseaudio[7291]: pid.c: daemon already running. pulseaudio[7291]: main.c: pa_pid_file_create() failed. pulseaudio[7285]: module-alsa-sink.c: Failed to set hardware parameters: Operation not permitted pulseaudio[7285]: module.c: Failed to load module module-alsa-sink (argument: sink_name=delta_out device=hw:0 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7): initialization failed. pulseaudio[7285]: main.c: Module load failed. pulseaudio[7285]: main.c: failed to initialize daemon. pulseaudio[7294]: module-alsa-sink.c: Failed to set hardware parameters: Operation not permitted pulseaudio[7294]: module.c: Failed to load module module-alsa-sink (argument: sink_name=delta_out device=hw:0 channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7): initialization failed. pulseaudio[7294]: main.c: Module load failed. pulseaudio[7294]: main.c: failed to initialize daemon. Tanu Kaskinen wrote: On Sun, Jan 20, 2008 at 02:49:25PM -0500, Richard Geddes wrote: Thanks for the response. Currently, I'd like to use PA as a replacement for esound... to basically send audio from different programs and from my audio capture card to my audio playback card (capture and playback are on the same card), taking advantage of mixing and syncing features of PA. Sending sound packets out to the network is interesting and I'd like to try that later. Here's the uncommented part of my /etc/pulse/default.pa file: The things that you wrote and pasted to your last message looked a lot like you were experimenting with the rtp modules, so I guess this is a different version of the file? If not, then that would be really strange behaviour (the RTP activity), I think. I haven't played with networking stuff at all myself, though. Anyway, I'll go through the file and give some comments. #!/usr/bin/pulseaudio -nF .ifexists /usr/lib/pulse-0.9/modules/module-hal-detect.so load-module module-hal-detect .else load-module module-detect .endif Here you have sound card autodetection set up. I think it's not compatible with the autoload stuff here: add-autoload-sink output module-alsa-sink device=hw:0 sink_name=output add-autoload-source input module-alsa-source device=hw:0 source_name=input Do you have a hotpluggable sound card, or why are these autoload entries here? module-hal-detect should take care of the hotplugging stuff, so I think the autoload feature is deprecated or for those cases when you do not want to use HAL. I'm not sure about the last statement. Anyway, if you don't have any special reason for these, remove them. .ifexists /usr/lib/pulse-0.9/modules/module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif With this line you should have support for esound applications (assuming that the module is installed on the system). You said that you wanted to replace esd. This should achieve that goal (along with the pulseaudio-esound-compat package, be sure to have that installed too). However, with this being the only loaded protocol, now your system doesn't support anything but esound apps. So add load-module module-native-protocol-unix too to have better application support. This will allow native pulse clients to connect. If you want support for applications using alsa as the interface (and why wouldn't you?), see the instructions at http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications. Or maybe you've done that already. Rest of the file seemed to be fine. If problems arise, output of pulseaudio -vv will be useful. ___ pulseaudio-discuss
[pulseaudio-discuss] Help in setting up PA
Hi, Just installed the PA packages on Ubuntu 7.10, with alsa drivers. Followed (I think) the steps for set up from the PA Perfect setup web page... when I try to run audio through PA (aplay -Dpulse music.mp3) no sound goes to the speakers, however, I can see quite a few udp packets being pushed through eth0... How can I get PA to send those audio packets back to my audio card? $0 sudo tshark ... 1200815959.616270 192.168.0.150 - 224.0.0.56 RTP PT=16-bit uncompressed audio, stereo, SSRC=0x97735F9C, Seq=56261, Time=4193600 ... $0 sudo netstat -entup Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name udp0 0 192.168.0.150:32776 224.0.0.56:46900 ESTABLISHED1000 38910 8009/pulseaudio udp0 0 192.168.0.150:32777 224.0.0.56:9875 ESTABLISHED1000 38911 8009/pulseaudio Some info about my audio hardware: $0 sudo lspci -v 00:0e.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) Subsystem: VIA Technologies Inc. M-Audio Delta 66 Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at 10a0 [size=32] I/O ports at 1080 [size=16] I/O ports at 1010 [size=16] I/O ports at 1040 [size=64] Capabilities: [80] Power Management version 1 Thanks Richard ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Help in setting up PA
Thanks for the response. Currently, I'd like to use PA as a replacement for esound... to basically send audio from different programs and from my audio capture card to my audio playback card (capture and playback are on the same card), taking advantage of mixing and syncing features of PA. Sending sound packets out to the network is interesting and I'd like to try that later. Here's the uncommented part of my /etc/pulse/default.pa file: #!/usr/bin/pulseaudio -nF .ifexists /usr/lib/pulse-0.9/modules/module-hal-detect.so load-module module-hal-detect .else load-module module-detect .endif add-autoload-sink output module-alsa-sink device=hw:0 sink_name=output add-autoload-source input module-alsa-source device=hw:0 source_name=input .ifexists /usr/lib/pulse-0.9/modules/module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-volume-restore load-module module-rescue-streams .nofail ### Load something to the sample cache load-sample x11-bell /usr/share/sounds/gtk-events/activate.wav ### Load X11 bell module load-module module-x11-bell sample=x11-bell ### Publish connection data in the X11 root window load-module module-x11-publish load-module module-gconf Tanu Kaskinen wrote: On Sun, Jan 20, 2008 at 03:07:44AM -0500, Richard Geddes wrote: Hi, Just installed the PA packages on Ubuntu 7.10, with alsa drivers. Followed (I think) the steps for set up from the PA Perfect setup web page... when I try to run audio through PA (aplay -Dpulse music.mp3) no sound goes to the speakers, however, I can see quite a few udp packets being pushed through eth0... How can I get PA to send those audio packets back to my audio card? You don't mention what kind of setup you want. RTP stuff doesn't get loaded automatically, so I assume you do want to broadcast all your audio to the LAN. If that is correct, then the fix is probably quite simple. You probably have this line in your default.pa, if you followed the FAQ: load-module module-null-sink sink_name=rtp Instead of a null sink, you want to use an actual alsa sink. So do not load the null sink, but replace the 'source' argument of module-rtp-send with the name of the alsa sink's monitor source. If you need further assistance, please explain what kind of setup you want, and attach your /etc/pulse/default.pa. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
