Hi,
I am currently trying to attempt to redirect pulse audio sound from a server
to a client through ssh. I am bit unclear on what the correct way is of
doing it.
Some guides on the net refer to paprefs and some refer to socat and others
again refer to loading modules via pactl. There is also so
quot;
br,
Quinn
On Fri, May 20, 2011 at 5:48 PM, Colin Guthrie wrote:
> Hi,
>
> 'Twas brillig, and Quinn Plattel at 20/05/11 15:52 did gyre and gimble:
> > I am currently trying to attempt to redirect pulse audio sound from a
> > server to a client through ssh. I am
(): Connection refused
Connection failure: Connection refused
---
Ideas?
Quinn
On Fri, May 20, 2011 at 5:48 PM, Colin Guthrie wrote:
> Hi,
>
> 'Twas brillig, and Quinn Plattel at 20/05/11 15:52 did gyre and gimble:
> > I am currently trying to attem
: 26e54bb2
-
br,
Quinn
On Fri, May 20, 2011 at 6:58 PM, Quinn Plattel wrote:
> Hi,
>
> This is interesting:
>
> client: ssh -XL 4713:localhost:4713 user@server
> server: PULSE_LOG=99 pactl stat
> --
n SSH? Then you get the native PA
> with SSH. I am not sure if there is some standard port.
>
> Fred Frigerio
>
>
>
>
> On Fri, May 20, 2011 at 1:01 PM, Quinn Plattel wrote:
>
>> Here is pactl stat on the client side:
>>
>>
>> PULSE_LOG=99 pactl st
t-ext.c: client-ext.c: Ca"..., 57) = 57
---
I am assuming the problem lies on the client side and not on the server
side. Any more ideas? How can I see what is going on with the pulseaudio
daemon when a remote client
otiated SHM: no
Connection failure: Connection terminated
--
Any ideas?
br,
Quinn
On Sat, May 21, 2011 at 10:53 AM, Quinn Plattel wrote:
> Hi,
>
> I found this message when I am trying to tunnel 4713 via ssh "ssh -L
>
-
br,
Quinn
On Sat, May 21, 2011 at 11:29 AM, Quinn Plattel wrote:
> Hi,
>
> I finally got some more details from pulseaudio. I did this on the client:
> --
> # stop pulseaudio
> # pulseaudio --system --high-priority -C
> -
"
D: client-ext.c: client removed (idx=9)
-
Still have not got further to solving the "protocol error" problem. Maybe
something to do with SHM?
br,
Quinn
On Sat, May 21, 2011 at 5:14 PM, Quinn Plattel wrote:
> Hi,
>
> Some more attempt
t; Cookie: d7756be2
> [media@(Media)centre ~]$
>
>
>
> --
>
> 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/]
> PulseA
0.9.14 of pulseaudio and it works
perfectly without the "protocol error" on the local server side.
I will see if I can downgrade the version of pulseaudio in Ubuntu Lucid
Lynx.
Question: Is it possible to force pulseaudio to use an older protocol?
br,
Quinn
On Sun, May 22, 2011 at
y?
br,
Quinn
On Sun, May 22, 2011 at 8:13 PM, Quinn Plattel wrote:
> Hi,
>
> I have now found a partial solution to the protocol error that happens when
> I try to play sound remotely through pulse.
> What I did was I played around with different versions of pulseaudio on the
> rem
Hi,
Correction on the last two lines:
local sound server: mkfifo *fifo.wav*
local sound server: paplay --volume=48000 -v fifo.wav & nc localhost 1234
>fifo.wav
br,
Quinn
On Sun, May 22, 2011 at 9:57 PM, Quinn Plattel wrote:
> Well, here is my almost perfect solution:
>
> lo
this is that the volume can be controlled manually with
the local sound server's volume control and the delay is cut down to 3-5
seconds.
br,
Quinn
On Sun, May 22, 2011 at 9:58 PM, Quinn Plattel wrote:
> Hi,
>
> Correction on the last two lines:
> local sound server: mkfifo *fif
ay 23, 2011 at 10:29 AM, Colin Guthrie wrote:
> 'Twas brillig, and Quinn Plattel at 23/05/11 05:52 did gyre and gimble:
> > HI.
> >
> > Last post on this thread, then I will start a new one.
> > I managed to cut down the delay considerably by simplifying the comma
h a 0.9.19 or 0.9.22
client.
Where do I begin to debug this error?
--
Best regards/Med venlig hilsen,
Quinn Plattel
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
16 matches
Mail list logo
