On 23-Aug-05, at 6:33 PM, kbelinski wrote:
I wanted to run 6.2 but its unicode support did not work correctly for
me. A big part of the unicode characters were not displayed correctly
resulted in only half of my album collection being picked up during a
scan.
I am running 6.1.x now. I hope that 17 will also go into the 6.1.x
nightlies.
why not take on 6.2 for a while longer, and help provide information
about your problems (in more detail than above). I have 10,000 tracks
and i can't say that any have been a problem (at least none I've
actually looked for). As such, my efforts are useless at fixing
anything. There are dozens to character code sets, 2 different
platforms, and dozens of flavours of linux/unix on top of that. If
everyone just complains and runs back to 6.1, those particular
problematic combinations are likely to still be there.
I have asked for details before, and get bitched at in return.
Hopefully this time can be different. Please file a bug report, and
attach some sample tracks that are giving you grief. Make mention of
the exact nightly date, what software you use to rip/tag the tracks.
Make sure you check old playlists for old metadata too, they can bring
back bad tags.
All of this stuff is critical to the improvement of slimserver. With
those details, the cause can be found or duplicate configurations built
in order to test. Say nothing, and it all gets left to chance that
someone else with the same configuration will post their details.
cheers,
kdf
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
