Try clearing the Cache in both LMS and your web browser.
--
toby10
toby10's Profile: http://forums.slimdevices.com/member.php?userid=12553
View this thread: http://forums.slimdevices.com/showthread.php?t=93463
Me too, the Spotify network tends to be overloaded in the eveneing.
Yesterday it began at 4.40PM to begin rebuffering constantly. Before
that time there wasn't one hickup.
The spotify plug-in cannot make use of the peer-2-peer technology,
which the PCMAC and I think also the official
Thanks for the heads up, Don.
Though it's disappointing news and a real shame as it does sound great
on the rare occasion that I can listen to a whole track uninterrupted.
Nothing ever works as advertised... I should have known!
--
Morgz
Spotify uses peer to peer for their desktop apps and streaming from
their central site for hardware players via libspotify (which always
require a premium subscription). Sometimes the server at the spotify
end if congested if so this is often resolved by the plugin moving
server, but is clearly
JohnSwenson;688921 Wrote:
The results are quite a bit better than without TT3.0, it was a pretty
shocking difference to me. Interestingly with the internal DAC the
daemon killer made a big difference, but with the Streamer II on the
hub it hardly made any difference at all.
That's
Mnyb;688900 Wrote:
And there are some embarrisng issues with the onboard server and the
Touch.
...
Which tells us that with some content it will always crash ?
...
a development where it can spit out problem files and log them without
crashing is needed...
Here's one note to
Thanks for explaining Triode... and really I love what you have made,
it's fabulous. Which is why this is so frustrating. I just want to
enjoy the music and your plugin would make that possible, but at the
moment it all seems broken and I know it's not your plugin at fault.
Hopefully Spotify
congole;689130 Wrote:
Here's one note to support the always part: when the artwork scan
starts it looks like in my case it really crashes at the same point
(cca 215/1220) every time(!)
And for the development part: How come that after all this
optimization it manages to pass somehow this
