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?!
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 4798 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:
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?
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.
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"/>
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).
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!