Why is the genre selection "excluded" rather than "included"?
It's been there for so long I can only guess: in the beginning it
probably was "Randomize all my songs". Then somebody didn't like the
Christmas songs mixed in in July, asking "can we exclude some genres
from the mix?".
--
Do you know a way of limiting the log size to, I don't know, maybe 5MB?
LMS has a very simplistic log rotation built in - for systems which
usually don't do log rotation themselves. Eg. it's disabled for Linux.
If QTS or QLogitechMediaServer don't do log rotation you'd have to shut
down LMS
I decided to do a clear and full rescan of the music files. Since the
rescan the genre selections have been stable.
Why I didn't look in the "plugin" folder is beyond me. I read through
the server.prefs file then decided on the rescan.
Why is the genre selection "excluded" rather than
dolodobendan wrote:
> Do you know a way of limiting the log size to, I don't know, maybe 5MB?
>
> I deleted server.log and restarted the server. Looks peaceful now.
> Strange.
>
> And now it's 9 MB already. I'll go back to 2.03.31 and do the same stuff
> and see what happens.Oké curious about
Do you know a way of limiting the log size to, I don't know, maybe 5MB?
QLMS 7.9.2@2.03.36 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
dolodobendan's Profile:
Ok, maybe some small problem here. The server.log is now 22GB. Not sure
how that happened. It coincides with the update to 2.03.36.
server.log:
Code:
[19-02-22 06:13:18.4405] main::init (387) Starting Logitech Media Server
(v7.9.2, 1550612824, Tue Feb 19 23:22:28
So far, no problems here.
QLMS 7.9.2@2.03.36 x64 (digimaster) with perl 5.28 dedicated to me. :D /
QNAP 469L QTS 4.3.4
dolodobendan's Profile: http://forums.slimdevices.com/member.php?userid=67663
View this thread:
After a bit more digging I found that this line is in the log for every
.cue file!
Scanner::Local::new (891) Handling new playlist
file:///[path]artist-album-blah.cue
All scanner logs are set to Error, so given there are *lots* of these
entries, surely this event should only be logged at the
There must be some reason why a Database Optimize step is done -
otherwise why include it?
Yes, there is. But it's not always necessary. When you do a lot of
changes (eg. new scan), then it's worth optimizing the database. If
you're dealing with a few changes only (only a few new tracks or
Roland0 wrote:
> 'This article '
> (https://www.qobuz.com/ie-en/info/hi-fi/bancs-d-essai/will-my-internet-bandwidth-be179216)
> gives a good overview regarding audio streaming bandwidth requirements.
> 'Here's'
> (https://www.jeffgeerling.com/blogs/jeff-geerling/getting-gigabit-networking)
>
After a bit more digging I found that this line is in the log for every
.cue file!
Scanner::Local::new (891) Handling new playlist
file:///[path]artist-album-blah.cue
All scanner logs are set to Error, so given there are *lots* of these
entries, surely this event should only be logged at the
Wow I never knew of that option - or indeed the other stuff!
I guess the ideal would be an option for the scanner to ignore missing
errors, but I guess I need to do some housekeeping.
File under "Things I wish I'd known when I started ripping". At least I
ripped to flac in the first place ...
dolodobendan wrote:
> Or just exclude them:
>
> 26812
yes exclude is good option here , but you miss the unconverted whole
albums so you have to decide to convert all to single files and then
exclude .
I just remove all those *.cue files and *.m3u files ?
Explanation some rippers i used in
Thanks DJanGo - I'll stop worrying about it.
I would still like to know why it suddenly stopped working though.
steve-g's Profile: http://forums.slimdevices.com/member.php?userid=52057
View this thread:
14 matches
Mail list logo
