[Bug 92055] Player should cache songs in advance of playing them
Matthias Welwarsky
matze at stud.fbi.fh-darmstadt.de
Fri Nov 5 19:34:29 GMT 2004
Hi,
I've briefly read through the comments on this bug. I think the best way to
handle buffering is within the play objects. You just have to tell it how
much memory it is allowed to buffer. This will solve the problem of the disk
spinning up too frequently. Also, you can apply this concept to video
playback quite easily.
I don't know how amarok or juk work internally, but it seems sensible to
assume that there's some kind of playback engine that knows what song is
going to be played next (even for a shuffled playlist).
You can even go and buffer more than one song in advance, by having a list of
playobjects for the next N songs. Doing it that way, the disk would only have
to spin up once every N songs - but believe me, it does not matter much, in
terms of power consumption.
regards,
matthias
On Thursday 04 November 2004 17:28, Allan Sandfeld wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=92055
> kde carewolf com changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
>- AssignedTo|kde carewolf com |kde-multimedia kde org
> Status|UNCONFIRMED |NEW
> everconfirmed|0 |1
>
>
>
> ------- Additional Comments From kde carewolf com 2004-11-04 17:28 -------
> Assigning to kde-multimedia, because it requires a different way of using
> decoders. _______________________________________________
> kde-multimedia mailing list
> kde-multimedia at kde.org
> https://mail.kde.org/mailman/listinfo/kde-multimedia
More information about the kde-multimedia
mailing list