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.I tried to test this by converting an album to 24/96 > apple lossless and I can't play the tracks at all to a Touch or piCorePlayer. The server log says "Decoder does not support file format, code 0"
Sent from my Pixel 3a using Tapatalk ------------------------------------------------------------------------ slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=114937 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
