[MPlayer-dev-eng] [PATCH] Play previously played entries in shuffled playlist

Adam Buechler butchler at gmail.com
Fri Jul 27 02:13:40 CEST 2012

Woops, I forgot something. New patch.

On Thu, Jul 26, 2012 at 7:58 PM, Adam Buechler <butchler at gmail.com> wrote:
> I agree that it would probably be better to just keep a list of
> previously played or something like that, but I'm not sure what the
> best way of doing that would be. In the mean time, I made a new patch
> which adds a command line option, called -shuffle-remember, to enable
> my changes.
> On Sun, Jul 15, 2012 at 4:40 PM, Adam Buechler <butchler at gmail.com> wrote:
>> On Sun, Jul 15, 2012 at 4:12 PM, Reimar Döffinger
>> <Reimar.Doeffinger at gmx.de> wrote:
>>> On 15 Jul 2012, at 20:43, Adam Buechler <butchler at gmail.com> wrote:
>>> > Allows you to play previously played entries again in a shuffled playlist
>>> > by stepping backward in the playtree. It does this by shuffling the
>>> > playtree as you step through it, choosing a random song and swapping it
>>> > with the next entry every time you're about to step onto an entry that
>>> > hasn't been played before.
>>> I suspect it changes behaviour quite a bit.
>>> But I don't really understand what exactly the condition you added will end up doing.
>>> In particular the case of using -loop 0 -shuffle I suspect will behave strangle (I suspect it selects a random entry when you backstep when a new loop iteration has just begun?)
>> Yes. When a new loop iteration begins, it just plays the first entry
>> in the playlist, and then when you backstep past the beginning of the
>> playlist it just chooses a random (and not yet played) item and puts
>> it at the beginning of the playlist. What would the correct behavior
>> be for backstepping at the beginning of a new loop iteration?
>>> What it clearly changes is that the playtree step functions no longer actually step in the playtree but do a "previously played", it might be better to make that a separate command.
>> Sounds like a good idea. What do you think would be a good name? Maybe
>> -shuffle-previous or -shuffle-experimental?
>>> What seems less risky would be to just add a last-played index, or even links to played previously/next, however any implementation will act questionably at some point with -loop 0....
>>> _______________________________________________
>>> MPlayer-dev-eng mailing list
>>> MPlayer-dev-eng at mplayerhq.hu
>>> https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shuffle-remember.diff
Type: application/octet-stream
Size: 5043 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20120726/ab4b7ac3/attachment-0001.obj>

More information about the MPlayer-dev-eng mailing list