Sorry for pushing this. But I have to ask: is this the correct thread to
post my problem 'report'? I realize this is not a top priority problem
but maybe it has been overlooked among all these other posts here? And
if it's something nobody else is interested in I can live with that. I
would just l
Much appreciated your efforts. Thanks for the info.
RiCat's Profile: http://forums.slimdevices.com/member.php?userid=65311
View this thread: http://forums.slimdevices.com/showthread.php?t=105225
___
I don't think so. Most of the architectures are to specific and
therefore some updates would brake LMS on Synology.
I my first attempt to provide updates I used a Repository, which could
be added to the Package manager. You would receive updates via your
package manager in DSM. Unfortunately this
Is there a way to aim the auto update feature in the LMS to your update
page?
RiCat's Profile: http://forums.slimdevices.com/member.php?userid=65311
View this thread: http://forums.slimdevices.com/showthread.php?t=105225
_
afriend wrote:
> I have a problem with compilations and artists/album artist tag in
> *iPeng* that may be caused by the server (more information & screenshot
> 'here'
> (http://forums.slimdevices.com/showthread.php?103494-Compilation-Tag-causing-Artist-Album-Artist-problems&p=845826#post845826)):
mherger wrote:
> >[16-02-22 14:02:56.9585] Slim::Schema::Storage::throw_exception
> (100) Error: DBI Exception: DBD::SQLite::db do failed: database disk im
> >age is malformed [for Statement "UPDATE tracks_persistent SET
> lastplayed = ?, playcount = ? WHERE ( id = ? )"]
>
> Your library
[16-02-22 14:02:56.9585] Slim::Schema::Storage::throw_exception (100) Error:
DBI Exception: DBD::SQLite::db do failed: database disk im
age is malformed [for Statement "UPDATE tracks_persistent SET lastplayed = ?,
playcount = ? WHERE ( id = ? )"]
Your library.db is corrupted. You'll have
I had a crash when changing tracks. I'm running Version: 7.9.0 -
1455690385 @ Wed Feb 17 06:37:56 UTC 2016 .
I was using a custom browse menu, and squeeze2upnp, so it could be
something wrong there. I have disabled the fulltext plugin in the hope
of avoiding API change issues. I don't know if
