[FFmpeg-devel] [PATCH] Playlist API
Wed Jul 15 10:36:26 CEST 2009
On Mon, Jul 13, 2009 at 01:37:28AM -0700, Geza Kovacs wrote:
> Sorry, that previous patch had some typos, unnecessary variables, and a
> scoping issue. Please review this updated version instead.
> On 07/13/2009 12:35 AM, Geza Kovacs wrote:
> > Hi all,
> > This is the public API component of a playlist abstraction layer I have
> > used to implement concatenation and playlist support with. It defines
> > structures for playlists and playlist items, and means to construct and
> > manipulate them.
> > To actually use this API for concatenation, another set of my patches
> > which implements playlist demuxers is necessary, which I will send for
> > review once this portion is accepted.
> > Regards,
> > Geza
Iam not against an API to work with playlists programmatically, that surely
could be usefull, but i dont feel this is the right part to start reviewing.
The way i see it, and iam of course open to suggestions and comments ...
* There are many applications using libav*, the less modifications they need
to support a new feature, the better.
From this it follows that a play list protocol&demuxer should ideally build
its playlist from the string provided by the user.
That way, something like ffmpeg -i localfile.mpg,http://www.a.com/xyz.avi
could work with minimal changes to ffmpeg.c
That of course does not preclude a API to manipulate playlists from C, but
that seems secodary to me because its design might be affected by the
other requirements ...
* We like to be able to transcode playlists, so that a avi+mpg can be
reencoded, into lets say a .mov.
Not only that but we also like the new .mov and the previous playlist
to represent their data to the user similarly so that applications dont
need to have 2 ways to extract things like (song)title for each part.
The obvious choice here would be the AVChapters of the .mov as well as
the AVChapters of the playlist demuxer ...
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored awnser#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel