Yes, seconds is enough accuracy. Especially for large playlists!
It depends on 2 things:
- whether you care about absolute error or relative error (the relative
error will not increase with the number of sings, but the absolute
error might).
- whether each error is biased.
The second point
Dear guys,
For the duration of each song in the current playlist or in the database,
can we have *seconds.milliseconds* form instead of *seconds* only?
What i mean is like below:
*246.486* instead of *246*
Now in the current MPD version:
From asking MPD by using `client.playlistinfo()`
On 2012/07/29 18:58, zw g pekingmas...@gmail.com wrote:
I think that is not accurate enough for computing the duration of whole
playlist, especially for large playlist.
I think it is.
--
Live Security Virtual
Thanks for your explaination.
That would be still a problem.
Lots of area do not allow such a `big` tolerance，especially for radio and
television related area.
Is it hard to have the milliseconds form functionality in MPD core?
Or, can we have it in the future release?
Gui
On Mon, Jul 30,
