mherger wrote:
> > I have "Logitech Media Server Versie: 8.2.1 - 1641537226 @ Fri Jan
> 7[color=blue]
> This Windows version detection is all a bit of guess work. Would you
> know what that server's build number would be? Something like 22999?
It's fairly well documented. See the following
gavatoo wrote:
> The message you have entered is too short. Please lengthen your message
> to at least 1 characters.
That's exactly what a computer would say.
:o
Mike Sargent's Profile:
drmatt wrote:
> Ah, it's a Windows thing. Figured.
Wrong.
I just did my first "Look for new and changed media files" since the DST
change over and it took about 2 1/2 minutes (94,048 tracks, 4,965
artists). That's about the same time it always takes. This is Windows
10.
FWIW: Windows has
bpa wrote:
> IIRC This possibility was tested on Touch. CPU load is higher when
> playing WAV than Flac possibly because of higher network traffic, more
> packets, less space for buffering etc.
WAV is less compressed than FLAC (about 2 to 3 times larger typically),
so WAV will use more network
mherger wrote:
> >No, by design: the disc field in the database is of "tinyint" type.
> Which is 0-254.
Shouldn't that be 0-25*5*?
Mike Sargent's Profile: http://forums.slimdevices.com/member.php?userid=48115
View this
No, I have seen that behaviour in Chrome before.
I use Edge for (almost) everything these days. It seems to work better
than Chrome.
Mike
Mike Sargent's Profile: http://forums.slimdevices.com/member.php?userid=48115
View
I just tried it and it seems to be working fine.
Is your Windows 10 system completely up to date? Microsoft updates Win
10 and Edge all the time.
Mike
Mike Sargent's Profile:
I don't know if this will help, but I have had my Touch (using Wi-Fi) do
the "skip to next track early" thing on occasion. In my case, rebooting
the Touch (pull the plug, wait 10 seconds, plug it back in) has always
resolved the problem for me. I have never had to touch my LMS nor the
host
