Network connection

[bibo01]

In version 2.5.15:

Allow remote HQPlayer to be configured (in Options/Players)
- you will need to turn on "Allow control from network" in HQPlayer
- you will need to configure firewall rules to allow communication (port 4321)
- all media file paths used by Muso must also be valid for HQPlayer host (i.e. UNC path or common drive mapping)
- if "buffer folder" used it must be a path recognised by both Muso and HQPlayer hosts.
- "muso-specific config" not used - this config is for local HQPlayer only

Great features.
In the appropriate window I set "192.168.0.185/home/audiolinux/Desktop/HQplayer".
Is this writing correct? I cannot connect to main HQPlayer server yet.

If I was able to establish connection with HQPlayer, I would see it under Player in main window, right?!

[musoware]

No you just put the host name in to the "Remote HQPlayer Host" field, 192.168.0.185 in your case. Here's mine:

Capture.PNG (9.08 KiB) Viewed 4791 times

The "Local folder containing HQPlayer-desktop.exe" is only for a local HQPlayer instance (on the same machine as Muso). So the configuration as I have it will allow connection of BOTH a local and remote HQPlayer instance. Yes this will be apparent in the player selection:

Screenshot (9).png (13.19 KiB) Viewed 4791 times

[bibo01]

I have set "192.168.0.185" for my system, but I cannot detect HQPlayer yet ("Allow control from network" is enabled).
My firewall on Windows (Muso) is disabled. HQPlayer system is on a AudioLinux PC and I do not know about firewall.
However, in the same setup with Room I am able to connect to HQPlayer.
Any idea?

[musoware]

If the player isn't appearing in the player list, it's because Muso cannot even ping 192.168.0.185 - could you try that from a command window ? i.e. just type in:

ping 192.168.0.185

If the player is appearing but not responding to Muso on being selected, send me a muso2.log so I can investigate please. There might be some more work to be done for a Linux host due to the constraint "all media file paths used by Muso must also be valid for HQPlayer host (i.e. UNC path or common drive mapping)" - I'm not sure with Samba shares that it recognises paths like "\\192.168.1.69\..." or "E:\music\..." - I'm not really a Linux person - if so I may need to introduce a path prefix mapping for remote HQPlayer. The log file should tell me whether it's communicating at all with HQPlayer on linux or whether it's just the paths that are the issue.

[bibo01]

I can ping the address.
But I am not sure the destination PC responds at port 4321.

If I do
telnet 192.168.0185:4321
I get the message that it cannot connect with the host on port 23.

If I do
NETSTAT -a -n | find "4321"
I get no error but I go back to C: prompt.

I would like to send you muso2.log. Where do I find it?

[bibo01]

Furthermore, if it can be useful to you, the naming HQPlayer follows in its library to connect to my NAS in Windows is:
<directory album="Our Time In Eden" artist="10,000 Maniacs" cover="file://diskstation/public/Music/10,000 Maniacs/Our Time In Eden/folder.jpg" path="\\DISKSTATION\public\Music\10,000 Maniacs\Our Time In Eden"/>

In Linux is:
<directory album="Our Time In Eden" artist="10,000 Maniacs" cover="file:///media/samba/Music/10,000 Maniacs/Our Time In Eden/folder.jpg" path="/media/samba/Music/10,000 Maniacs/Our Time In Eden"/>

[musoware]

Yeah from that I think I have to introduce a Linux-specific path prefix mapping. If you play a track in the remote HQPlayer, can Muso at least pause/restart the track?

muso2.log is in a folder which is opened up for you if you turn on diagnostics mode (top right corner - "bug" icon).

[bibo01]

Linux-specific path prefix mapping is probably necessary.
However, I still have to connect to HQPlayer which I am not able to at the moment.

This is the output of muso2.log - the host refuses to connect at 192.168.0.185:4321:

+--------------------------------------------------------------------------------------------------------------------------------------------------------
| 01 | 05:15:23.592 | .073 | muso version 2.5.15
| 01 | 05:15:23.592 | | martedì 15 marzo 2016 17:15:23
| 01 | 05:15:23.592 | | Diagnostics turned on
| 01 | 05:15:34.892 | 011,300 | Choose Player
| 01 | 05:15:34.894 | | . HQPLAYER
| 01 | 05:15:34.899 | .005 | . Success
| 01 | 05:15:34.899 | | . HQPLAYER2
| 01 | 05:15:34.902 | | . EMBEDDEDPLAYER
| 01 | 05:15:36.067 | 001,165 | noNPTrack
| 01 | 05:15:36.069 | | Connect Player HQPLAYER2 HQPlayer (192.168.0.185)
| 01 | 05:15:36.069 | | P:new
| 01 | 05:15:36.069 | | Q: Start
| 05 | 05:15:36.069 | | Q: PRODUCER CONSUMER QUEUE -- WORKER THREAD
| 05 | 05:15:36.070 | | Q: Waiting...
| 01 | 05:15:37.079 | 001,010 | HQ: Exception connecting to TCP socket: Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione 192.168.0.185:4321
| 01 | 05:15:37.080 | | Error connecting player: Not connected to HQPlayer
| 01 | 05:15:37.080 | | Switch off erroneous Player
| 01 | 05:15:37.080 | | ------------------------
| 01 | 05:15:37.080 | | Disconnect Player:
| 01 | 05:15:37.082 | | P:dispose
| 01 | 05:15:37.082 | | Q: Dispose, enqueue null
| 05 | 05:15:37.082 | | Q: Dequeue (1)
| 05 | 05:15:37.082 | | Q: Got null so FINISH PCQ THREAD
| 01 | 05:15:37.083 | | Q: Joined (finished)
| 01 | 05:15:37.083 | | Disconnected.
| 01 | 05:15:37.083 | | ------------------------
| 01 | 05:15:37.083 | | Connect Failed

[musoware]

I get an error similar to that when I haven't turned on "Allow control from network" in the remote HQPlayer - are you sure you've done that?

[bibo01]

You are right!!
Sorry, my fault. The last time I tried I did not press the button.
Now I can see Linux HQPlayer, but If I launch playback from Muso, the application gets stuck in an endless calculation loop.
Linux-specific path prefix mapping is surely needed!