Bug 211 - Missing tracks in playlists should give better feedback
: Missing tracks in playlists should give better feedback
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Playlists
: unspecified
: All All
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-10 17:38 UTC by Blackketter Dean
Modified: 2008-09-15 14:37 UTC (History)
0 users

See Also:
Category: ---


Attachments
Player message for bad files (892 bytes, patch)
2004-03-11 23:39 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2004-03-10 17:38:13 UTC
Had a problem todat with our cron'ed playlists. I moved some files around
and forgot it would cause a problem with the file paths in the playlists.
The symptom was that the player would not play, it would not come out of
stop. I feel that for a robust system the software should write an entry to
the log for debugging and move on. Unless there are no tracks at all, it
should continue to play something.

Another neat and helpful thing would be if the layer would flash "Track not
found" for a moment.

Chris Mason
Comment 1 KDF 2004-03-11 23:39:49 UTC
Created attachment 15 [details]
Player message for bad files

Here is a possible fix.  It displays a short error message and waits 1/4 second
before moving to the next song.  This is long enough to see there is an error
and short enough to hopefully not be annoying if it has to move through several
songs before finding one that will open and play.
Comment 2 KDF 2004-03-31 22:09:02 UTC
player skips to next song, and displays a short message that song can't be read.
running the server with --d_source will show enough information to know the song
isn't found, or otherwise unplayable.
--d_playlist might also show the proper logging info for this case.
Comment 3 Chris Owens 2006-06-16 14:40:14 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.