Bug 11822 - song started then skipped
: song started then skipped
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Audio
: 7.3.2
: PC Windows XP
: -- normal (vote)
: 7.3.3
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-16 08:12 UTC by Sean Echevarria
Modified: 2009-06-04 08:43 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
server.log - player.source=info and network.protocol.slimproto=info (126.94 KB, text/plain)
2009-04-16 08:12 UTC, Sean Echevarria
Details
multiple extracts of log showing Slim::Player::Protocols::File::sysread (212) (5.60 KB, application/octet-stream)
2009-04-29 11:21 UTC, Sean Echevarria
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Echevarria 2009-04-16 08:12:02 UTC
Created attachment 5131 [details]
server.log - player.source=info and network.protocol.slimproto=info

Version: 7.3.2 - 24695 @ Mon Jan 19 18:55:04 PST 2009
Hostname: blacky
Server IP Address: 192.168.1.120
Server HTTP Port Number: 9100
Operating system: Windows XP - EN - cp1252
Platform Architecture: 586
Perl Version: 5.8.8 - MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt
Total Players Recognized: 1

shuffled is disabled
playlist repeat is enabled

playlist consists of two whole albums in flac format

first song played fine (Immersion)
second song played for about 2 seconds (The Garden of Proserphine)
then third song unexpectedly started playing (Great Expectations)

log attached for all of these events.  Also shows that I went back and pressed play on The Garden of Proserphine (which played fine).
Comment 1 Chris Owens 2009-04-27 09:40:57 UTC
Andy looked at this log and suggests Alan have a look.  Sean, is this recurring regularly or was this just a one-off problem?

This could easily be more of a support issue than a bug.

In the mean time, though, does this file play correctly on the local PC?  Can it be copied?  It looks kind of like SC can't read the file, maybe.  If SC can't read a file part way in, its behavior is to skip ahead to the next track.

Also, we're about to release 7.3.3 and the beta is very solid at this point.  Would you mind installing it and seeing if this continues to happen.
Comment 2 Sean Echevarria 2009-04-27 09:51:33 UTC
It was a one-off.  Hasn't happened since that I've noticed (that qualification being key).  Squeezecenter can play the file fine.  In a previous bug I filed, Alan also thought Squeezecenter was having trouble playing files.  see bug 11651.  Are these signs of a deeper problem?
Comment 3 Sean Echevarria 2009-04-27 09:52:30 UTC
I meant reading files (as opposed to playing).  I'll install the beta.
Comment 4 Sean Echevarria 2009-04-29 11:21:15 UTC
Created attachment 5168 [details]
multiple extracts of log showing Slim::Player::Protocols::File::sysread (212)

I've installed a 7.3.3 nightly and so far no problems.
Version: 7.3.3 - 26228 @ Mon Apr 27 04:08:11 PDT 2009
Hostname: blacky
Server IP Address: 192.168.1.120
Server HTTP Port Number: 9100
Operating system: Windows XP - EN - cp1252
Platform Architecture: 586
Perl Version: 5.8.8 - MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt
Total Players Recognized: 1


As far as the questions of being able to read the file, as far as I can tell, that sysread logging statement occurs at the end of every flac file I have.  The attachment show multiple extracts from my current playlist that has been playing fine.  Both Chris and Alan (in bug 11651) comment on my logs saying that SC is having trouble playing my content.  Does this message not normally appear for other users with flac content?

Would it help to attach a flac source file?
Comment 5 Alan Young 2009-04-29 23:26:42 UTC
That log message is normal. It does not indicate any error.

If one looks at the log message:

Slim::Player::Source::_readNextChunk (499) end of file or error on socket, song pos: 704577269, tell says: 11098186, totalbytes: 11098186

This would indicate an error is the "tell" value was less than the "totalbytes" value, although to some extent this depends upon the file type. If this message is preceded by the "Trying to read past the end of file" message, then the previous statement is always true. In the case of files with non-audio information (tags, etc.) at the end of the file, or when using CUE sheets, the tell value could be less than totalbytes (possibly nowhere close in the case of cue-sheet usage).
Comment 6 Sean Echevarria 2009-06-03 20:57:10 UTC
No recurrences since installing 7.3.3 - 26228 @ Mon Apr 27 04:08:11 PDT 2009