Quantcast
Channel: Squeezebox : Community : Forums
Viewing all articles
Browse latest Browse all 6235

LMS 8 with large media collection

$
0
0
> * Is LMS able/designed to manage this amount of media files at all?

Designed? I doubt it. Will it work? I'd say yes. I haven't seen an
installation big as yours, but we know there are installations of 600k+
tracks out there. Make sure you have plenty of RAM and a fast disk
system for the database available.

> * Is it feasable to have LMS operaing on a read-only NFS mount (across
> Gigabit Ethernet) instead of local files?


Yes

> * LMS appears to scan the media file tags only. Is there a possibility
> of instructing the scanner to derive performer, album & track names from
> file names and paths instead?


LMS would prefer tags, but can fall back to path schemas like

/ARTIST/ALBUM/TRACKNUM - TITLE

to guess the information. But I'd strongly recommend you try to get the
tags done. If the files are well named and organized it should easy to
translate this into tags.

> * LMS displays paginated lists in the Web UI. For long lists (~15000
> entries), this is a royal pain in the behind. Are there any UI updates
> that improve/fix this?


There are 3rd party solutions which might be more suitable.

> * Playlist management: Do I see it correctly that playlists can be
> externally written to some playlist folder that is configurable in LMS,
> but each change requires a subsequent rescan of this playlist folder? Is
> there no easy way/interface for writing the changes directly to the
> corresponding SQLite DB (library.db, if I see it correctly)?


You can talk to LMS over a simple socket connection or JSON/RPC. This
gives you a lot of control over LMS' behaviour (see
http://htmlpreview.github.io/?https:...s/cli-api.html).
One of those commands would allow you to add/remove/move items in a
playlist
(http://htmlpreview.github.io/?https:...aylists%20edit).

--

Michael

Viewing all articles
Browse latest Browse all 6235

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>