> 5. How come web browser access is slow to move from one artist to
> another when looking for music yet the Android app for LMS is really
> quick? The browser doesn't appear to do anything extra that I can see.
The web server part in LMS is a real resource hog. In 7.9 I implemented
some caching which can help considerably. Browsing to artists or albums
would still be about the same the first time around. But then the full
page is cached on the server and subsequently loaded from the cache (as
long as you don't rescan or shut down LMS). You might give it a try.
> Finally, I was wondering how I could get involved in the development and
> maintenance of the LMS code. I have some Perl experience (been using it
> for a couple of years) so would be good to help out if I can.
Install 7.9 and use it. Sooner or later you'll hit bugs. Try to fix
them. Seriously: trying to fix some minor issue can get you a long way
to understanding how the LMS source is organized etc.
You might also want to get used to running LMS from the source. This way
you can clone the server code, edit it, fix bugs etc., and then post a
pull request. Plus updating or switching version is really easy and
doesn't require the download of that 120MB package (once you've cloned
the 900MB+ repository ;-)). I'm doing this on my main system, too. I
picked some of the startup scripts and adjusted it to run the code right
out of the repository clone I have (my system is CentOS based - but this
should work for Debian/Raspbian, too).
--
Michael
> another when looking for music yet the Android app for LMS is really
> quick? The browser doesn't appear to do anything extra that I can see.
The web server part in LMS is a real resource hog. In 7.9 I implemented
some caching which can help considerably. Browsing to artists or albums
would still be about the same the first time around. But then the full
page is cached on the server and subsequently loaded from the cache (as
long as you don't rescan or shut down LMS). You might give it a try.
> Finally, I was wondering how I could get involved in the development and
> maintenance of the LMS code. I have some Perl experience (been using it
> for a couple of years) so would be good to help out if I can.
Install 7.9 and use it. Sooner or later you'll hit bugs. Try to fix
them. Seriously: trying to fix some minor issue can get you a long way
to understanding how the LMS source is organized etc.
You might also want to get used to running LMS from the source. This way
you can clone the server code, edit it, fix bugs etc., and then post a
pull request. Plus updating or switching version is really easy and
doesn't require the download of that 120MB package (once you've cloned
the 900MB+ repository ;-)). I'm doing this on my main system, too. I
picked some of the startup scripts and adjusted it to run the code right
out of the repository clone I have (my system is CentOS based - but this
should work for Debian/Raspbian, too).
--
Michael