See Response below
On 8/11/2017 11:05 AM, Max Kellermann wrote:
Okay, I now understand that no changes are required to MPD. I believe I
can just attach to the existing local socket created by MPD.
On 2017/08/11 13:45, ed mcmurray <emcmur...@aevee.com> wrote:
On the MPD side I'm not so sure where in the code that I should create,
bind, listen and accept connections, for the socket.
That code already exists. Why do you believe a change to MPD is
I am trying to allow a second application to send a STOP command to MPD,
using the existing local socket created by MPD. I would like to allow a
form of Convenience Switching. So if music is playing through MPD from
an MPD client (JRiver). The second application could then STOP MPD play
safely(as though command came from MPD client (Jriver). I have attached
a terminal screen shot below, showing mpd socket assignment.
I'm sure this should be more obvious, but any help would be appreciated.
Still nothing here is obvious to me. I have no idea what you're
trying and why.
root@AeVeeStreamer:~# ss -np | grep mpd
u_str ESTAB 0 0 * 5147 * 5249
u_str ESTAB 0 0 * 6115 * 6116
tcp ESTAB 0 0 127.0.0.1:48337 127.0.0.1:6600
tcp ESTAB 0 0 ::ffff:127.0.0.1:6600 ::ffff:127.0.0.1:48337
This email has been checked for viruses by Avast antivirus software.
mpd-devel mailing list