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
Hi,
there are a few bug reports in our Mantis database about problems on
OS X. I have no Mac, I will never buy one. A while ago, when I had
access to a Mac, I tried to refactor our OS X plugin, but got lost in
Apple's horrible CoreAudio documentation, and decided I will not spend
another second
Max,
I hope don't do this. That would be pity, very.
I am using MPD on my macbook pro everyday, and it works just fine.
I didn't found any *playback* bug yet.(from Version 0.16.3 ~ 0.17)
I have no skill to take this task, but i still hope to keep this feature.
And keep the chance for someone
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,
