Bug 1271 - Softsqueeze2 (SB2?) elapsed time not reset WAV streaming
: Softsqueeze2 (SB2?) elapsed time not reset WAV streaming
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: 6.0.0
: PC Linux (other)
: P2 normal (vote)
: ---
Assigned To: Adrian Smith
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-31 16:42 UTC by Adrian Smith
Modified: 2011-03-16 04:19 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Smith 2005-03-31 16:42:29 UTC
With 6.1 (svn 2821) playing only remote streams, softsqueeze2 does not reset 
the elapsed time.  The value returned in status frames keeps counting up...  I 
would expect the elapsed time to be reset to 0 at the start of each new stream?

Tested with Alien based playlists, but these are handled the same as other 
remote streams.
Comment 1 Adrian Smith 2005-04-01 09:14:12 UTC
I've rechecked with mp3 streams and mms streams - these appear OK.  Hence this 
is a problem with Alien only :-(

Re-assigning to me!
Comment 2 Adrian Smith 2005-04-01 12:47:09 UTC
Further tests - this is not specific to Alien - it occurs whenever a stream is 
streamed as WAV to Softsqueeze2.  There is no STMs status message from 
softsqueeze and the elapsed time softsqueeze reports is not reset to 0 when a 
new stream starts.  Reproducable with MMS and Alien streams set to send PCM to 
softsqueeze.

Also occurs if local files are streamed as WAV rather than Flac [comment out 
flc flc * * in convert.conf]  There are no STMs status messages and elapsed 
time is not reset.

Conclude - this is a softsqueeze problem...
Comment 3 Adrian Smith 2005-04-01 12:48:06 UTC
Bug title changed
Comment 4 Adrian Smith 2005-04-03 15:25:38 UTC
Confirmed as a softsqueeze problem - Richard checked in a fix in svn 2854.
Comment 5 Chris Owens 2006-06-16 14:41:09 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.