atrocity wrote:
One thing I'm sure of is that SoA and the Wandboard are not the issue
here: The problem first appeared for me running an official LMS release
under Ubuntu.
I have also, now that I think of it, experienced gaps between tracks
when running a Touch away from home using the
gharris999 wrote:
PasTim: Have you looked at the records in the CONTRIBUTORS table? That
might give you a clue as to what's going on with the scan. The easiest
way I've found to do that is to copy the SQLite library.db from the LMS
cache folder to a windows machine and then use the free
I believe I am beginning to see a pattern. I got somewhat side-tracked
by my belief that ComposerSort was inspected by LMS. However, it seems
that neither it nor ConductorSort are, but BandSort, ArtistSort and
AlbumArtistSort are. That's all OK.
What isn't OK is that some valid ArtistSort and
marflao wrote:
Thanks for the swift response, livconcepts.
My DAC should be able to handle DoP as well as native DSD but I guess my
NAS will be the bottleneck, or?
The question I´m asking myself is if I will be able to play DSD files in
my current setup?
If the answer would be Yes then
Actually playing DSD on a Squeezebox Touch won't do much good compared
to the PCM version (24/96 or 24/192) . This is because LMS will
transcode DSD to PCM anyway. You need to have a DSD DAC in order to hear
the real benefit.
Thanks for the swift response, livconcepts.
My DAC should be able to handle DoP as well as native DSD but I guess my
NAS will be the bottleneck, or?
The question I´m asking myself is if I will be able to play DSD files in
my current setup?
If the answer would be Yes then the following question
Are you sure you understand the table relationships in the database?
The 'contributors' table is just a collection of names with name,
name_sort name_search fields. There's nothing in the contributors
table that identifies a contributor as a track-artist, album-artist,
conductor, etc. That is
PS: If I had to guess, I'd guess that the undesirable scan and sort
behavior you're seeing is a byproduct of code that was introduced as a
fix for bug 16956. See:
http://bugs.slimdevices.com/show_bug.cgi?id=16956
I've run into problems myself with that code. I've had to essentially
run a fork
Finally, it seems what you're really asking for is an enhancement to the
scanner to recognize your ComposerSort and ConductorSort tags. Is that
right?
gharris999's Profile:
Hi all,
A couple days ago I installed SSODS (I used pinkdots ssods version and
it´s now running LMS 7.9.0 - 142832773) successfully on my NAS (Syno
DS213) and wanted to give DSD a try.
[Out of curiosity I´d like to find out myself if there is a sonic
(audible) advantage with this kind of high
gharris999 wrote:
Are you sure you understand the table relationships in the database?
The 'contributors' table is just a collection of names with name,
name_sort name_search fields. There's nothing in the contributors
table that identifies a contributor as a track-artist, album-artist,
But here's the thing: if the scanner scans a file with
André_George_Previn_the_conductor_or_composer -after- it scans a file
with André_George_Previn_the_album_artist, then the contributor.namesort
field is always going to be overwritten with the default LMS generated
ANDRé GEORGE PREVIN
12 matches
Mail list logo
