Hi,
I tried the pulse cookie method. Here is what I did:
- on the local sound server side, I copied ~/.pulse-cookie to the remote
sound client to /etc/pulse/pulse-cookie-n900
- on the remote sound client side, I added the following two lines to
/etc/pulse/client.conf:
default-server =
Hi,
Here are my results
On Sat, May 21, 2011 at 7:58 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
Hi,
I think you're maybe getting a little confused by client and server in
terms of how things work here (perhaps not, as I've not thoroughly read
all the many posts in this thread).
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
remote side by using different versions of Ubuntu.
On the local server side, we are using
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 qie...@gmail.com wrote:
Well, here is my almost perfect solution:
local
HI.
Last post on this thread, then I will start a new one.
I managed to cut down the delay considerably by simplifying the commands:
local sound server: ssh -L 5901:localhost 5901 -L 1234:localhost:1234
remote sound client *parec | nc -l 1234
local sound server: nc localhost 1234 | pacat
The
Hi,
From what Colin says, the standard port is 4713 for pulseaudio. As I said
before all network ports are blocked except port 22 which is only for ssh
connections.
I should be able to tunnel port 4713 through ssh by doing this: ssh -L
4713:localhost:4713 user@server. Then I can tell pulseaudio
Hi,
I found this message when I am trying to tunnel 4713 via ssh ssh -L
4713:localhost:4713 user@server:
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 4713
Could not request local forwarding.
Hi,
I finally got some more details from pulseaudio. I did this on the client:
--
# stop pulseaudio
# pulseaudio --system --high-priority -C
--
Now, when I run pactl stat on the server, pulseaudio on the client
reports:
Hi,
Some more attempts. I have now tried this:
client (session 1): stop pulseaudio
client (session 1): pulseaudio --system --high-priority -C
client (session 2): ssh -R 4000:localhost:4000 user@server
client (session 3): socat TCP-LISTEN:4000,fork
UNIX-CONNECT:/var/run/pulse/native
server:
Hi,
I did a LANG=C pulseaudio --system --high-priority -
/root/pulseverbose.log 21 on the client to write a detailed log file.
Here is the results when the remote client tries to connect:
-
I: client.c: Created 9 Native client
Hi,
I think you're maybe getting a little confused by client and server in
terms of how things work here (perhaps not, as I've not thoroughly read
all the many posts in this thread).
As I know how to do what you want to do, I'll just write the
instructions here:
1. Start of on the machine you
HI,
Thanks for info, but I don't think it is the solution I am interested in. I
have to use ssh as my server is behind a firewall
and ssh is the only way to contact it. The other thing is I would like to
use vnc to work with my server.
Right now, I am doing this:
client: ssh -L
Hi,
This is interesting:
client: ssh -XL 4713:localhost:4713 user@server
server: PULSE_LOG=99 pactl stat
Using shared memory pool with 1024 slots of size 64.0 KiB each, total size
is 64.0 MiB, maximum usable slot size is 65472
Trying to connect to
Here is pactl stat on the client side:
PULSE_LOG=99 pactl stat
-
Using private memory pool with 1024 slots of size 16,0 KiB each, total size
is 16,0 MiB, maximum usable slot size is 16344
Trying to connect to
Have you tried redirecting the port in 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 qie...@gmail.com wrote:
Here is pactl stat on the client side:
PULSE_LOG=99 pactl stat
15 matches
Mail list logo
