Bug 1847 – m3u playlists are doubled when scanned by slimserver

Bug 1847 - m3u playlists are doubled when scanned by slimserver

Summary:

m3u playlists are doubled when scanned by slimserver

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Playlists
Version:	6.1.0
Platform:	PC Other

Importance:	P3 normal (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-21 07:54 UTC by Jason Holtzapple
Modified:	2011-03-16 04:40 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
m3u with plain filenames (10.42 KB, text/plain) 2005-07-21 07:55 UTC, Jason Holtzapple	Details
m3u with #EXTINF entries (12.56 KB, text/plain) 2005-07-21 07:56 UTC, Jason Holtzapple	Details
db file (bzip2'd) (3.09 MB, application/x-bzip2) 2005-07-26 15:17 UTC, Jason Holtzapple	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jason Holtzapple 2005-07-21 07:54:10 UTC

Many of my m3u playlists in my playlist dir have doubled and appended entries:
when viewed in slimserver they consist of track a-n,a-n instead of a-n. This is
with 2005-07-21.

I will attach 2 example playlists along with --d_parse debug output.

perl 5.8.7, NetBSD 1.6, C locale.

Thanks

Comment 1 Jason Holtzapple 2005-07-21 07:55:53 UTC

Created attachment 659 [details]
m3u with plain filenames

Comment 2 Jason Holtzapple 2005-07-21 07:56:27 UTC

Created attachment 660 [details]
m3u with #EXTINF entries

Comment 3 Blackketter Dean 2005-07-21 08:52:42 UTC

Jason, please try this with the 6.1 final and see if the problem is resolved.

Comment 4 Jason Holtzapple 2005-07-21 09:45:16 UTC

I installed 6.1.0 final and removed the database and let it rescan.
Unfortunately the doubling behavior is still there.

Comment 5 Dan Sully 2005-07-26 13:17:37 UTC

Jason - can you upload your .db file?

Thanks.

Comment 6 Jason Holtzapple 2005-07-26 15:17:00 UTC

Created attachment 674 [details]
db file (bzip2'd)

Comment 7 Dan Sully 2005-07-27 07:47:58 UTC

Jason - I just checked in change 3803, which I believe will fix the problem.

Can you see if that's the case?

Thanks.

Comment 8 Dan Sully 2005-07-28 14:43:43 UTC

Jason - can you please confirm that this has been fixed?

Thanks.

Comment 9 Jason Holtzapple 2005-07-28 18:10:36 UTC

This is now fixed in 2005-07-28

There's an extra entry for current track, but I assume that's intentional. It 
looks good now, thanks for the fix.