[pulseaudio-discuss] Simultaneous output to local and remote sound cards

[Sergey M.]

I restored client.conf and used some magic in pacmd:

 load-module module-tunnel-sink server=192.168.1.2
 load-module module-combine sink_name=combined
slaves=alsa_output.hw_0_0,tunnel.192.168.1.2 adjust_time=5
resample_method=src-sinc-medium-quality
 set-default-sink combined

and now it works! But sound is noticeable desyncronized and laggy on _local_
machine. Also, local pulseaudio daemon says:

W: module-combine.c: [alsa_output.hw_0_0] sample rates too different, not
adjusting (44100 vs. 36692).
W: module-combine.c: [alsa_output.hw_0_0] sample rates too different, not
adjusting (44100 vs. 38519).
W: module-combine.c: [alsa_output.hw_0_0] sample rates too different, not
adjusting (44100 vs. 38930).

Any way to fix this?

2011/6/13 Colin Guthrie <gmane at colin.guthr.ie>

> 'Twas brillig, and Sergey M. at 13/06/11 05:57 did gyre and gimble:
> > Hello. I am trying to make simultaneous output to local and remote sound
> > cards (i.e. to stream sound from my notebook both to notebook speakers
> > and to remote pc with hi-fi sound system). I tuned client.conf on
> > notebook and default.pa <http://default.pa> on remote machine. Network
> > streaming works nicely. Then, I tried to use alsa "multi" plugin to have
> > simultaneous output:
>
> snip...
>
> > But this doesn't work - I have sound only on remote machine somewhy. I
> > also tried "copy" plugin, unsuccessfully too.
>
> Don't use alsa level stuff. The only alsa level config should be to push
> audio to PA and then forget all alsa things!
>
> > Maybe pulseaudio has it's own instruments to implement this? I read tons
> > of howtos and documentation, but cannot realize what to do now. :(
>
> PulseAudio has a combine plugin. Just load the combine sink and you'll
> get a new virtual sink that outputs to both local and remove sinks.
>
> You can read about this on our wiki:
> http://pulseaudio.org/wiki/Modules#module-combine
>
> There is even a ticky box in paprefs (but here it only uses local
> devices, not network tunnels.
>
> Of course you say above you've tuned client.conf. This should also not
> be done. Machines should typically always talk to their own PA daemon on
> the local machine, but it in turn should be configured to use a Tunnel
> Sink. This will allow you to switch apps from local to remote with ease
> via pavucontrol. Again, module tunnel can be configured as per the
> details on the above link. It can even work automatically with
> zeroconf/avahi.
>
> 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 at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20110613/18f0e835/attachment-0001.htm>