Thanks philippe_44 for detailed explanation the LMS! I learn so much from your reply. I am surprised that there is a difficulty for LMS to determine the accurate position of music file. I am not familiar with music streaming, so I could not give an useful technical suggestion. I describe more situation for your reference. In the example of jump to the last 10 seconds of the track, the music will keep playing after the slider ends. The slider will wait for seconds or minutes even after the music reach the end(with no sound). Sometime the waiting time is not short. I feel that it seems to play the whole music time after time jumping(not very sure). I hope these experience could be helpful.
" seeks N bytes into the file" may be the key problem. Maybe it's difficulty to determine the "precise" byte position. On the other hand, about the sentence "file format and how that file has been created", my music files are apple m4a format and flac format , which are created using Apple itunes or foobar2000. philippe_44 wrote: > For many formats, it is not possible to have a precise "jump to > position" because the bitrate is not constant or the seektable is not > granular enough. In addition, the time reported by LMS on the UI is not > perfect. It is the estimation that LMS does, added to the playback time > reported by the player. Players do *not* report absolute time (they > don't know it), but how many milliseconds they have been playing since > the last request. > > So when you seek to a position P in seconds, LMS stops playback, seeks N > bytes into the file to its best estimation of where is P seconds and > starts sending a *new* track to the player from byte N+1. LMS then > starts to count time from the estimated position using an autonomous > counter and adjust that counter when it receives the player's actual > played time which has started at 0 second with first bytes received, so > at byte N+1 of the actual file > > This explain why playback counter it often not very precise, it's just > an indication sometimes and especially jumping 10s before the end of a > track is unlikely to display things properly. R > > Remember that "jump to" accuracy depends on the file format and how that > file has been created. ------------------------------------------------------------------------ cshin1213's Profile: http://forums.slimdevices.com/member.php?userid=71995 View this thread: http://forums.slimdevices.com/showthread.php?t=114937 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
