[FFmpeg-soc] [soc] libavsequencer [PATCH 01/08] Music module public API header file.

[Sebastian Vater]

Ronald S. Bultje a écrit :
> Hi,
>
> On Tue, Jul 13, 2010 at 4:15 PM, Sebastian Vater
> <cdgs.basty at googlemail.com> wrote:
>   
>> Also some formats don't have even something close like a clear song-end
>> detection. In that case, the user can add it manually. That's the
>> purpose of this field.
>>     
>
> So who reads the value then? It seems to me that if the user wants to
> stop the song, he simply stops calling avcodec_decode_audio() and no
> more audio will come out. Who would need to know this user-set value
> to justify it being in BSS?
>   

It's free to someone to read it and use it, e.g. players which are in
play-once mode instead of play-repeat, they can simply break playback
when this time is reached and continue with the next song in the playlist.

I have encoutered this with some exotic amiga formats, which because
such a feature is not known (DeliPlayer has a global config file to set
a max. playback time in that case and skip ALL files after that simple
defined time), others simply loop the module forever in that case and
never skip on to the next, forcing the user to manually skip forward one
song.

This can be really nasty, I prefer to start a playlist of modules and
suddenly after some files have been playing, one loops forever and I had
to deal with that manually, so I invented:
Upon importing them to TuComposer, you can set a manual playback time
for each file and TuComposer stores it, the player knows the playback
time in that case and at reaching this it will skip normally to next module.

Just consider you start XMMS, having your favourite songs in it, and
suddenly one loops forever because lack of song-end detection...you're
midden in a work of sth. and have to deal with that.

FFmpeg coming soon formats having this issue can also set a default
value or sth. like that by the demuxer, just an idea.

-- 

Best regards,
                   :-) Basty/CDGS (-: