Re: [pulseaudio-discuss] redirect output to headless machine
On Thu, 2010-07-08 at 14:59 +0200, Simone Neugierig wrote: Ive changed the configs and now there is a network connection from host1 to host2, but if i set sound playback to pulseaudio sound server on host1 pulseaudio on host2 exits with: pulseaudio I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root privileges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. Soft CPU time limit exhausted, terminating. E: cpulimit.c: Received request to terminate due to CPU overload. W: module-rescue-streams.c: Failed to move sink input 0 pulseaudio to auto_null. this is maybe because i cant play sound on this machine at all, its a ubuntu server installation. after boot the following sound modules are loaded. The fact that the CPU limit is exceeded indicates a bug in pulseaudio or the sound card driver. To get some more information, you could enable more verbose logging by running pulseaudio -. -- Tanu Kaskinen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] redirect output to headless machine
Ok, i got alsa working, output redirecting to the headless machine works and the cpu problem is fixed. this option did it: no-cpu-limit = yes theres a newer pulseaudio avaiable that has a fix (no concrete information), but for now i will stick with the ubuntu 9.04 one. what is a bit akward is that the two machines exchange ~350kbps on port 4713 even if no sound is playing. even if its not working perfectly, i would like to ask how the mic input can be redirected as well. with the current configuration (host1 = system that i work on) (host2 = headless system that does the output and (future) input) i can select pulseaudio server as mic input in the ubuntu sound dialog on host1, but so far nothing gets recorded when i speak? is mic input handled automatically via the working network connection or are there any other settings? -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] redirect output to headless machine
On Fri, 2010-07-09 at 15:31 +0200, Simone Neugierig wrote: what is a bit akward is that the two machines exchange ~350kbps on port 4713 even if no sound is playing. I didn't check this, but I guess the tunnel sink doesn't shut down the stream when it's not in use, so it transmits silence. There's probably no reason to do that, so filing a ticket for the bug would be a good idea (if no such ticket exists yet). even if its not working perfectly, i would like to ask how the mic input can be redirected as well. with the current configuration (host1 = system that i work on) (host2 = headless system that does the output and (future) input) What do you mean by future? If the mic isn't there yet, you of course can't record from it... i can select pulseaudio server as mic input in the ubuntu sound dialog on host1, but so far nothing gets recorded when i speak? is mic input handled automatically via the working network connection or are there any other settings? All devices on host2 should be visible on host1, including microphones. You can check whether the mic is actually available on host1 by running pavucontrol and opening the Input Devices tab. If the mic is there, but your record application still doesn't seem to get any data from there, open the Record tab in pavucontrol while recording, and right click the record stream that should be visible there. The context menu allows you to move the stream to the correct source. That hopefully solves your problem. -- Tanu Kaskinen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] redirect output to headless machine
Hi, i would like to redirect output off all applications to another machine that has no monitor attached. snip any ideas whats wrong? You try to make the connection in the wrong direction. Your sound hardware on host2 won't be making any connections to your applications - it's the other way around. So, do this: Load module-native-protocol-tcp on host2 like you did on host1 previously. Also load module-zeroconf-publish on host2. Then on host1 run paprefs and enable Make discoverable PulseAudio network sound devices available locally. Now all hardware on host2 should be visible also on host1. Ive changed the configs and now there is a network connection from host1 to host2, but if i set sound playback to pulseaudio sound server on host1 pulseaudio on host2 exits with: pulseaudio I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root privileges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. Soft CPU time limit exhausted, terminating. E: cpulimit.c: Received request to terminate due to CPU overload. W: module-rescue-streams.c: Failed to move sink input 0 pulseaudio to auto_null. this is maybe because i cant play sound on this machine at all, its a ubuntu server installation. after boot the following sound modules are loaded. snd_via82xx32152 0 gameport 19340 1 snd_via82xx snd_ac97_codec112292 1 snd_via82xx ac97_bus9856 1 snd_ac97_codec snd_pcm82948 2 snd_via82xx,snd_ac97_codec snd_timer 29704 1 snd_pcm snd_page_alloc 16904 2 snd_via82xx,snd_pcm snd_mpu401_uart15104 1 snd_via82xx snd_rawmidi29696 1 snd_mpu401_uart snd_seq_device 14988 1 snd_rawmidi pcspkr 10496 0 serio_raw 13316 0 snd62628 7 snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device vt8231 23180 0 soundcore 15200 1 snd ive checked the files in /etc/pulse against the one on my local ubuntu that has working pulseaudio support. besides the changes that i made to get network support they are identical. i followed the steps in the pulseaudi wiki, first steps and perfect setup. but nowhere is really mentioned what has to happen so that pulseaudio works with the hardware. how does pulseaudio know about my soundcard? dont know of this is important ls -alh /dev/snd total 0 drwxr-xr-x 2 root root 120 2010-07-08 12:39 . drwxr-xr-x 16 root root3.4K 2010-07-08 12:40 .. crw-rw 1 root audio 116, 5 2010-07-08 12:39 controlC0 crw-rw 1 root audio 116, 4 2010-07-08 14:51 pcmC0D0c crw-rw 1 root audio 116, 3 2010-07-08 14:51 pcmC0D0p crw-rw 1 root audio 116, 2 2010-07-08 12:39 timer -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] redirect output to headless machine
On 10-07-07 05:42 PM, Simone Neugierig wrote: host2 (the client, where my headset is connected) in /etc/pulse/client.conf i added this line: default-source = 192.168.11.200 (host1) default-server = ... ? -Nathan ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] redirect output to headless machine
host2 (the client, where my headset is connected) in /etc/pulse/client.conf i added this line: default-source = 192.168.11.200 (host1) default-server = ... ? -Nathan ive commented the default-source and set this instead: default-server = tcp:192.168.11.200:4713 still, the client side (host2) does not open a network connection to host1 -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
