Here the two error messages I'm finding repeatedly in my log.
[18-02-16 15:19:45.9509] Slim::Utils::DbCache::__ANON__ (255) Error:
DBD::SQLite::st execute failed: database disk image is malformed
[18-02-16 15:19:45.9510] Slim::Utils::DbCache::__ANON__ (256) Error:
Yes you can create normalised mp3s, but the process is lossy.
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k
albums..
Fewer distractions when driving is a good thing, so I do my organizing
for drive-along-music ahead of time. I prefer to use USB drives but have
an ample selection on my always-with-me mobile for bluetooth or cable
access via USB port.
I always have a flash drive with newer music for checking
drmatt wrote:
> Yes you can create normalised mp3s, but the process is lossy in a way
> that's much worse than the lossy compression inherent in the medium.
>
> Ogg Vorbis gain leaves the raw data alone and requires all decoders to
> be able to apply the decibel correction from the headers.
Depends on the player. If the new player honour the gain tag then great,
but it was not a core feature.
Annoyingly android core media playback services do not honour replaygain
tags either, so I do wind up also permanently normalising my files used
for portable playback. Like you say, no issue
Here the two error messages I'm finding repeatedly in my log.
[18-02-16 15:19:45.9509] Slim::Utils::DbCache::__ANON__ (255) Error:
DBD::SQLite::st execute failed: database disk image is malformed
[18-02-16 15:19:45.9510] Slim::Utils::DbCache::__ANON__ (256) Error:
