-discuss@mail.0pointer.de
Subject: Re: [pulseaudio-discuss] Controlling where module-rtp-send sends
multicast packets?
On 2/20/08, Paul Fox [EMAIL PROTECTED] wrote:
matt wrote:
In an effort to use more of the pc that I already have running
24 7 I have opted to keep the amps right
On 2/21/08, Paul Fox [EMAIL PROTECTED] wrote:
jon wrote:
... You just have to keep the clocks tightly synchronized and all
of the zones will stay synchronized by starting the play of each song
at a synchronized instant. The clock drift that occurs while a song is
playing never
pulseaudio-discuss@mail.0pointer.de
Subject: Re: [pulseaudio-discuss] Controlling where module-rtp-send sends
multicast packets?
On 2/20/08, Paul Fox [EMAIL PROTECTED] wrote:
matt wrote:
In an effort to use more of the pc that I already have running
24 7 I have opted to keep the amps
On Fri, 15.02.08 15:18, Kevin Fox ([EMAIL PROTECTED]) wrote:
Are there any plans to support rtp syncing in the future?
Yes. The hard part is actually already done. It's just a matter of
putting things together.
Lennart
--
Lennart PoetteringRed Hat, Inc.
lennart [at]
On 2/16/08, Lennart Poettering [EMAIL PROTECTED] wrote:
On Fri, 15.02.08 15:18, Kevin Fox ([EMAIL PROTECTED]) wrote:
Are there any plans to support rtp syncing in the future?
Yes. The hard part is actually already done. It's just a matter of
putting things together.
This is a good way to
I'm more intrigued by the possibility of turning my dumpster bound PC
hardware into something useful using PulseAudio.
Work out the electricity and AC costs and you won't think they are so
cheap.
This node I working on right now is a 1.1Ghz Celeron laptop. Power
consumption is probably
Ok, a laptop breaks the old pc concept a little. It is definitely the
way to go. Its funny though, for me, 50 kw would cost a little over a
dollar. My new core 2 duo server only pulls 65 watts while on, the old
machine pulled 265! And to top it off my old machine had a power factor
of ~55,
I thought about this route, but the issue is I don't want interruptions
in the rooms already listening to music. Maybe if feed all four input
sources into split out sinks (splitting each input into 4 null-sink
outputs in the end), I could then attach the final sound card outputs on
demand
On Fri, Feb 15, 2008 at 08:27:39AM -0800, Matt Patterson wrote:
I thought about this route, but the issue is I don't want interruptions
in the rooms already listening to music. Maybe if feed all four input
sources into split out sinks (splitting each input into 4 null-sink
outputs in the
Yeah, that would work. I wonder what the processing loads would be? I
assume that the sync has to be maintained on all outputs for all
streams, independent of muting state. It also may not scale should I
want to add more zones, but that's a while off. No better way to know
than to try it.
On Thu, 14.02.08 22:23, Matthew Patterson ([EMAIL PROTECTED]) wrote:
Now for my question: This implementation obviously spews a lot of
multicast traffic onto my network. I didn't think this would be a
problem, but my router/ap/switch seems to crap out when it gets hammered
with all the
Are there any plans to support rtp syncing in the future?
Thanks
Kevin
On Fri, 2008-02-15 at 14:51 -0800, Matt Patterson wrote:
I tried setting the routing table to direct to other interfaces but
the packets keep appearing on the interface i didn't want. Each of the
4 rtp send modules goes to
Hello all,
I just discovered PulseAudio about 2 weeks ago and was struck by how
applicable it could be in creating a whole home audio solution where
each room can subscribe to the same or a different audio stream as
another room. To create this I setup 4 mpd instances, each talking to a
13 matches
Mail list logo
