Re: New mailing list forprogrammers/developers usinglibav*?
----- Original Message ----
From: Mikael Hakman <[hidden email]>
To: FFmpeg user questions and RTFMs <[hidden email]>
Sent: Friday, 28 December, 2007 10:24:51 PM
Subject: Re: [Ffmpeg-user] New mailing list forprogrammers/developers usinglibav*?
On Friday, December 28, 2007 11:52 AM, Stefano Sabatini wrote:
> On date Thursday 2007-12-27 20:06:39 +0100, Mikael Hakman encoded:
>> Hello Kyle,
>> On Thursday, December 27, 2007 4:41 PM Kyle Mallory wrote:
>> > Can I make a request to the List Gods, to create a new mailing
>> > specifically for C programmers who are using the libav* libraries?
>> > It seems as a coder, who rarely uses the command-line tools, my
>> > requests
>> > seem to be often overlooked, as well as having to hunt through
>> > (literally) hundreds, if not thousands of messages before finding
>> > that is relevant to me as a developer.
>> > If such a mailing list already exists, or better yet, a web-based
>> > forum,
>> > that would just be cool.
>> I agree 100% percent. We need a list for users of libav* libraries
>> could discuss programming topics and libav* usage patterns.
>> ffmpeg-user list is mostly about using ffmpeg, which is entirely
>> topic from developing programs that use libav* libraries. On the
>> ffmpeg-developer list concerns itself with developing ffmpeg and
>> libav* libraries themselves.
>> For example, few weeks ago I asked a question concerning what flags
>> be set in program code in order to activate 2-pass mpeg encoding
>> obvious setting of PASS1/PASS2 flags didn't have the desired effect.
>> not receive any answers on ffmpeg-users list, and ffmpeg-developer
>> members didn't think that their list is an appropriate one for this
>> questions. Nevertheless, there is no doubt in my mind that there
>> people who know the answer because this is what ffmpeg does, if this
>> is still active that is.
>> The point of lists and exchanging information is reusing knowledge
>> gained by others so that you don't have to debug and dig deeply into
>> every time you need some information. Such a list could even be a
>> (not yet existent) libav* libraries programmers manual/guide.
> This has been already discussed on this list:
> Michael Niedermayer, the current lists maintainer, seems against it.
> I still think that such a split could ease the search for
> programming-related issues. On the other end the *use* of the ffmpeg
> tools require in many cases a good programming background and often
> reading and understanding of the code, so there would be a certain
> degree of overlap between the two lists discussions.
If people with knowledge on libav* internals and usage aren't
passing this knowledge on to other people so that the number of
using libav* increase then no list in the world can do anything about
nobody is interested in documenting libav* from its application
perspective, not even in passing that information to others, then of
no documentation will be done.
Otherwise, my experience from more than 2 decades both as a user,
and to some degree developer of software in the Open Source movement,
indicate the opposite. Normally you get all the help they can give you.
Then, you in your turn give all help you can to others - this is how it
grows! Why would libav* be different in this respect?
If this is the case, let everyone take up one or more module and do the documentation and share our knowledge. There are lot of people like me who are new to ffmpeg and can assist you. But for doing that we need to know in first place how to run the examples. If the list members who are using libav* can join we can get this working.