You mention using YAML, but do I really need to use that when a simple grep will allow me to get the url value?
If you can handle it using grep, then that's perfectly fine. It's just that you have more control using YAML, as it would not only filter out the url, but give you access to the additional information about the track. But whatever suits you best.
url: lms://827dcefa-1829-4a1f-ada9-13989c591ba8/music/41511/download.flac Would it be difficult to log the actual path and filename as located on the remote server?
Probably not difficult technically, but in many cases useless. I therefore didn't spend much time on this. I'm running LMS on a Linux box, another copy sometimes on my Mac. Paths from one system wouldn't be of any use on the other system.
Also, I minor thing I noticed that I wasn't able to use localhost or 127.0.0.1 to define a remote LMS, even though it's using a different port # (the remote LMS is connected via SSH), so I simply tweaked Plugin.pm by commenting out the check for this on line 76.
Yeah, that check is a bit simplistic, but likely covers >99% of all cases ;-). Why would you run multiple instances on the same host, then try to access the other instance anyway?!?
I realize this is probably to avoid loop back, and I also see some checking code that looks for port 9000, but since this default can be modified, this should probably be tweaked.
That's only setting a default value in case the port was missing. -- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
