On Mon, 2011-01-17 at 14:24 -0600, pl bossart wrote:
[...]
> I can see cases where you have 1 compressed stream and 1 PCM, and you
> mix the two in hardware, but I am having a really hard time finding a
> use case where you would have multiple (more than 2) PCM streams at
> different rates. Maybe a
'Twas brillig, and Luiz Augusto von Dentz at 17/01/11 21:55 did gyre and
gimble:
> Hi Colin,
>
> On Sun, Jan 16, 2011 at 4:24 PM, Colin Guthrie wrote:
>> Hiya Luiz,
>>
>> I notice a few BT related changes (including the fix for building with
>> older dbus on your branch:
>> git://gitorious.org/pu
Hi Colin,
On Sun, Jan 16, 2011 at 4:24 PM, Colin Guthrie wrote:
> Hiya Luiz,
>
> I notice a few BT related changes (including the fix for building with
> older dbus on your branch:
> git://gitorious.org/pulseaudio/mainline.git
>
>
> Luiz Augusto von Dentz (5):
> bluetooth: fix case of profil
2011/1/17 pl bossart :
>> I've tested module-loopback by playing to a null-sink and looping its
>> monitor to the real alsa sink. This showed good behaviour, but may be
>> the algorithm I used for module-rtp-recv should also be used here.
>> Does anyone has a better suggestion for a setup to test
>
Thanks Colin for reading my prose.
> Yeah, doing it server wide makes no sense IMO. The default-sample-rate
> configure option predates our mixer profile logic and really (IMO)
> somehow be wrapped up into card profiles or sink/source ports anyway,
> but I digress.
That's actually a good point. I
> I've tested module-loopback by playing to a null-sink and looping its
> monitor to the real alsa sink. This showed good behaviour, but may be
> the algorithm I used for module-rtp-recv should also be used here.
> Does anyone has a better suggestion for a setup to test
> module-loopback? null-sink
'Twas brillig, and Dr. Adrian Wrigley at 17/01/11 18:05 did gyre and gimble:
> Dr. Adrian Wrigley wrote:
>> I am attempting to invoke pavucontrol on a particular X server by
>> setting the DISPLAY environment variable.
>>
>> DISPLAY=192.168.1.3:2.0 pavucontrol
>
> I needed to set the following env
Dr. Adrian Wrigley wrote:
I am attempting to invoke pavucontrol on a particular X server by
setting the DISPLAY environment variable.
DISPLAY=192.168.1.3:2.0 pavucontrol
I needed to set the following environment variable too:
PULSE_SERVER=Machine1
This produces three messages in the xterm:
Hi all,
I am attempting to invoke pavucontrol on a particular X server by
setting the DISPLAY environment variable.
I logged in to Machine1 using Gnome. This machine runs Pulse and
an X server at :0.0.
I then create a xterm window from Machine1 to display on Machine2, which
runs an X server at
