On May 25, 2013, at 1:03 AM, Kalileo <[email protected]> wrote: > As Robert said, please, please, please: "Please, take a step back and > reality-check your statements. You're so off-track here."
I am going to conclude my discourse here by passing on one more nugget of info about how "off-track" I am. I was contacted off-list by a self-proclaimed list-vetteran (5+ years) who explained to me that because most of the list devs first language wasn't English, posting anything of substance or length provides an obstacle to them. Furthermore, these non-first-language-English speakers considered my "style" of communication "colloquial", and didn't like it. Even my writing proper English on an English mailing list is a foul -- the pettiness here apparently has few bounds. All I have done here is point out inconsistencies in explanations I was given, omissions in documentation and examples, reported what I was seeing in source code I provided, and reported a verified crash in avcodec_encode_audio2. For that I've been called "troll" and had my posts publicly written off as "FUD", and now I'm "off-track" simply for quoting the ones who said so. I'm not all that slow on the uptake -- I've been around these mailing lists for 20+ years, and I've seen many open source projects that are driven by personality, and willingly set aside potential progress to protect personal fiefdoms. I had thoughts a while back of attempting to document FFmpeg, or putting some more pragmatic HOW-TO examples together, or maybe even putting a whole OS X Cocoa wrapper around FFmpeg (which would have produced another public API for Mac users which *could* be documented). But it is clear that there's no point in such an attempt. I get that you want me gone...and as my presence here is merely an extension of my customer's FFmpeg needs, I've already recommended to them that they need to migrate off of FFmpeg for support reasons. Provided they agree to do it, that will happen, and I'll take our user feedback (which in other places is welcomed, in the commercial world, even paid for) elsewhere. In the meantime, you can label it however you want, excoriate me for it again for merely reporting it if that floats your boat, but you've got a bug in libavcodec. It may well be caused by a usage issue, but it is an error condition FFmpeg doesn't catch either by assertion or error handling, and it crashes inside FFmpeg code. Investigate it or ignore it...that's up to you. That's the last I have to say about any of this. Brad _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
