Re: [pulseaudio-discuss] module-tunnel-sink: where to start?

2008-12-13 Thread Colin Guthrie
'Twas brillig, and Chris Hamilton at 12/12/08 18:47 did gyre and gimble: > I apologize for the previous thread hijack... an inadvertant 'reply to' > instead of 'compose to'. > > Anyhow, the same message, but now with new thread goodness! > > - > > Alright... so, I've finally got an environme

Re: [pulseaudio-discuss] module-tunnel-sink: where to start?

2008-12-12 Thread Chris Hamilton
[snip] > Alright... so, I've finally got an environment with bleeding edge [/snip] Sorry for the blatant thread hijack! I'll let you get back to your previous discussion! Chris ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de htt

[pulseaudio-discuss] module-tunnel-sink: where to start?

2008-12-12 Thread Chris Hamilton
I apologize for the previous thread hijack... an inadvertant 'reply to' instead of 'compose to'. Anyhow, the same message, but now with new thread goodness! - Alright... so, I've finally got an environment with bleeding edge everything, and am able to build and run pulseaudio from GIT. Howe

[pulseaudio-discuss] module-tunnel-sink: where to start?

2008-12-12 Thread Chris Hamilton
Alright... so, I've finally got an environment with bleeding edge everything, and am able to build and run pulseaudio from GIT. However, the GIT version dies right away with a PA_SINK_INPUT_IS_LINKED assertion. I saw a mention on trac that this is known issue, and that there are a few workarounds