Re: [pulseaudio-discuss] Choose remote default sink fromcommandline?
'Twas brillig, and Dave at 15/11/10 01:25 did gyre and gimble: At 11:11 AM 11/14/2010, you wrote: 'Twas brillig, and Dave Markus at 13/11/10 17:54 did gyre and gimble: FWIW - the tunnel sink I created, sink-DGTM, does not show up in pavucontrol or padevchooser. It only shows up when I do '$ pacmd list'. Then you probably have the wrong filter chosen on the Output Devices tab in pavucontrol. Make sure you pick All Output Devices and not Hardware Devices... Col I tried All Output Devices and no luck. But I think the tunnel module may be crashing when I open pavucontrol. I did not check to see exactly what does and does not crash the tunnel. Since this is an old version of pulse, and it works ok in the newer versions, I did not think it was worth the time trying to pinpoint the problem. Here is what I finally did to get it to work on my ubuntu 9.04 system: Edit ~/.profile And add: export PULSE_SERVER=tcp:ubuntu-DGTM.gateway.2wire.net:4713 Reboot and the remote server is now the default sink. Technically the remote server is not the default sink, it's the default server. From there it's default sink will likely be used... but that's just me nit-picking! Glad you got a solution that works for you. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Choose remote default sink fromcommandline?
At 03:55 AM 11/15/2010, you wrote: 'Twas brillig, and Dave at 15/11/10 01:25 did gyre and gimble: At 11:11 AM 11/14/2010, you wrote: 'Twas brillig, and Dave Markus at 13/11/10 17:54 did gyre and gimble: FWIW - the tunnel sink I created, sink-DGTM, does not show up in pavucontrol or padevchooser. It only shows up when I do '$ pacmd list'. Then you probably have the wrong filter chosen on the Output Devices tab in pavucontrol. Make sure you pick All Output Devices and not Hardware Devices... Col I tried All Output Devices and no luck. But I think the tunnel module may be crashing when I open pavucontrol. I did not check to see exactly what does and does not crash the tunnel. Since this is an old version of pulse, and it works ok in the newer versions, I did not think it was worth the time trying to pinpoint the problem. Here is what I finally did to get it to work on my ubuntu 9.04 system: Edit ~/.profile And add: export PULSE_SERVER=tcp:ubuntu-DGTM.gateway.2wire.net:4713 Reboot and the remote server is now the default sink. Technically the remote server is not the default sink, it's the default server. From there it's default sink will likely be used... but that's just me nit-picking! ... No, it is good to know these things. I am still learning my way around pulse. Dave ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Avoiding 2ch upmixing to all speakers
Just to sum up because I've been rambling a bit, I would like to see; 1. Upmixing, downmixing and LFE mixing configurable independantly. (personally I think upmixing belongs as a toggle switch in the applet and not in a config file but that's not really important) 2. LFE mixing to always take place regardless of the existence of a discrete LFE track (I was wrong earlier when I said this is already the case) 3. Downmixed 'virtual' channels increased a little in output or configurable (not a deal breaker) Thanks Dom ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
Is it possible to change the sampling rate that the alsa sink or source is configured for? For example, in some scenarios, 44.1kHz is used, then in another scenario, to avoid sample rate conversion and some other hardware problems, configure the alsa device to 8kHz within the module-alsa-sink/source. Thanks! -- -baeksanchang ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
'Twas brillig, and Baek Chang at 15/11/10 21:16 did gyre and gimble: Is it possible to change the sampling rate that the alsa sink or source is configured for? For example, in some scenarios, 44.1kHz is used, then in another scenario, to avoid sample rate conversion and some other hardware problems, configure the alsa device to 8kHz within the module-alsa-sink/source. No, this is not something we support at present due to the practical problems that this presents. Whenever changing the sample rate mid stream you'll obviously get some kind of click/pop as the device is closed, reconfigured and reopened, so this has to be avoided. The alternative is to take the first sample rate and stick with it. But then consider playing an 8kHz effect sound and then playing a nice 196kHz audio track just a moment later... it would be converted to 8kHz which is almost certainly not what the user would want. So whichever way you cut it, there is no nice solution to do dynamic sample rate switching of the hardware and the only logical and practical solution is to use a fixed sample rate on your system and covert to this. I wont say it will never be supported (if someone writes a well formed patch that doesn't introduce any significant complications/overhead then I can't see any problems with merging it), but I doubt any of the main developers or companies supporting PA will want to do this any time soon (although I could of course be wrong here). I hope this answers your question. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
I wont say it will never be supported (if someone writes a well formed patch that doesn't introduce any significant complications/overhead then I can't see any problems with merging it), but I doubt any of the main developers or companies supporting PA will want to do this any time soon (although I could of course be wrong here). It's on my radar, this is a change that is required for compressed data support, and while we are at it we could modify the behavior for PCM as well. Jyri seemed in favor of this as well on the Nokia side. What I had in mind is that changes in sampling rates would be allowed only if a sink/source is inactive and the actual hw device closed, and only if the application has a role where such a change makes sense. That would enable low-power use cases without requiring resampling. -Pierre ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
On Tue, Nov 16, 2010 at 09:21:47AM EST, Colin Guthrie wrote: So whichever way you cut it, there is no nice solution to do dynamic sample rate switching of the hardware and the only logical and practical solution is to use a fixed sample rate on your system and covert to this. Its also worth noting that there is audio hardware around that doesn't support lower than say 32000Hz sample rate. This is more often than not found in higher end hardware, but there may be consumer level hardware that only supports 44100 and up. Luke ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
On Mon, Nov 15, 2010 at 8:50 PM, pl bossart bossart.nos...@gmail.com wrote: I wont say it will never be supported (if someone writes a well formed patch that doesn't introduce any significant complications/overhead then I can't see any problems with merging it), but I doubt any of the main developers or companies supporting PA will want to do this any time soon (although I could of course be wrong here). It's on my radar, this is a change that is required for compressed data support, and while we are at it we could modify the behavior for PCM as well. Jyri seemed in favor of this as well on the Nokia side. What I had in mind is that changes in sampling rates would be allowed only if a sink/source is inactive and the actual hw device closed, and only if the application has a role where such a change makes sense. I think that would solve the (or my) most common use-case (imho): play music (usually 44100hz) stop music play movie (usually 48000hz) stop movie (rinse and repeat) Cheers, Sander ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] dynamically changing alsa sink/source sampling rate
I think that would solve the (or my) most common use-case (imho): play music (usually 44100hz) stop music play movie (usually 48000hz) stop movie (rinse and repeat) Yeah, I am only talking about 44.1 and 48 changes. All the other frequencies can be resampled fairly easily. -Pierre ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
