[FFmpeg-devel] Splitting libavformat (Was: [PATCH] IPv6 support v.2)

Michel Bardiaux mbardiaux
Fri Nov 16 15:50:13 CET 2007


Stefano Sabatini a ?crit :
> On date Friday 2007-11-16 15:21:23 +0100, Luca Abeni encoded:
>> Hi all,
>>
>>
>> Michael Niedermayer wrote:
>> [...]
>>> i think there are a few libs which could be created
>>>
>>> * low level protocols (tcp,udp,file,oss,alsa,v4l)
>>> * high level protocols (http, ftp, mms, ...)
>>>
>>> * a lib providing standard functionality which is missing on the target OS
>>> (exported names though should be prefixed with something to avoid name
>>> clashes)
>>>
>>> all just an idea, maybe there are better ways to split things ...
>> So, what happened to this? Anyone working on those libraries?
>>
>> I am leaving for the weekend in about one or two hours, and I'll not be
>> online until monday, but I'll have some time to hack ffmpeg.
>> If noone else is working on this, I'll split libavformat.
>>
>> I am thinking about 2 possibilities:
>> 1) a first lib for low level protocols, and a second one for high level
>>     protocols, as suggested by Michael
>> 2) a first library for network protocols (udp, tcp, http, rtp, rtsp) and a second
>>     one for grabbing from other devices (audio, v4l, v4l2, x11grab & friends)
>>
>> Anyone has other ideas? Which one is preferred?
> 
> What about a libavsource intended as a generalization of libavdevice
> (proposed in the second option)?
> 
> See:
> http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/57997/focus=58158
> 
> It should make possible to "grab" not only from physical devices but
> also from automatic pattern generators, which would be useful for
> testing/debugging (not to mention the coolness of having a psychedelic
> pattern video/audio generator).

There is no need to add that *in* libavformat. There is the vloopback 
device for such effects.

> 
>> In my plan, I will simply move code from one library to another, without changing
>> any API (I hope this can be done ;-). After this split, the only URLProtocols
>> remaining in libavformat will be file_protocol and pipe_protocol.
>>
>> Of course, if someone else is already working on this I'll find something else
>> to hack ;-)
>>
>> Comments?
> 
> My 2 cents.
> 
> Best regards.


-- 
Michel Bardiaux
R&D Director
T +32 [0] 2 790 29 41
F +32 [0] 2 790 29 02
E mailto:mbardiaux at mediaxim.be

Mediaxim NV/SA
Vorstlaan 191 Boulevard du Souverain
Brussel 1160 Bruxelles
http://www.mediaxim.com/




More information about the ffmpeg-devel mailing list