kdf Wrote: > Quoting jth <jth.1shuob (AT) no-mx (DOT) forums.slimdevices.com>: > > > > > Dan Sully Wrote: > > > * jth shaped the electrons to say... > > > > > > >I'm having a pretty rough time with playlists. Even on the > 2005-07-20 > > > >build, many of my playlists are doubled when scanned into > slimserver > > > - > > > >the m3u will have 15 entries, but slimserver will catalog > 1-15,1-15. > > > > > > > >Some of my playlists have had metadata added by slimserver like > this: > > > > > > > >#CURTRACK 0 > > > >#EXTM3U > > > >#EXTINF:-1,Tomorrow > > > > >file:///export/music/various_artists/annie/annie_-_01_tomorrow.mp3 > > > >#EXTINF:-1,It's The Hard-knock Life > > > > > > >file:///export/music/various_artists/annie/annie_-_02_its_the_hard-knock_life.mp3 > > > > > > > >But even after I remove the commented entries and wipe the db, > the > > > >playlists are still doubled. It doesn't seem to affect every > playlist > > > >though. > > > > > > Those aren't commented entries.. that's how the file is supposed > to > > > be. > > > > > > Ok - but with or without the hashed lines > > > the playlist is parsed twice so that slimserver's generated > > > playlist contains twice as many songs as it should. > > d_parse logs woudl be useful during the scanning of these playlists. > either the > path is getting munged from some source, or you have differing > charsets > interfering somehow. > > -kdf
I've created bug #1847 regarding this issue with sample m3u files and --d_parse output attached. -- jth _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
