| 1 |
On Tue, 12 Feb 2013 12:16:22 +0100 |
| 2 |
Luca Barbato <lu_zero@g.o> wrote: |
| 3 |
|
| 4 |
> On 12/02/13 08:21, Ian Whyman wrote: |
| 5 |
> > Guys, |
| 6 |
> > |
| 7 |
> > Can we not just have a developer wide vote or something? This |
| 8 |
> > instance clearly not going to resole itself. |
| 9 |
> |
| 10 |
> It is a little bikeshed. Originally the virtual was ordered in a |
| 11 |
> way, then ordered in another and now we are discussing which one is |
| 12 |
> better for the user after we turned it around again. |
| 13 |
|
| 14 |
That's what he's suggesting to vote about. I consider my concerns |
| 15 |
important and, as such, will continue to use FFmpeg but e.g. your |
| 16 |
arguments are valid and important too and in the end it boils down to |
| 17 |
what one considers more important. |
| 18 |
So far I have been the only one voicing against libav being the |
| 19 |
default (besides comments on my blog) so I can live with it without |
| 20 |
vote since it is clear I am minority. Were there more people favoring |
| 21 |
FFmpeg I would say a kind of vote is needed, but so far I don't think |
| 22 |
it's worth it. |
| 23 |
|
| 24 |
> There isn't ANYTHING that is impacting users beside those that they |
| 25 |
> might get the next versions of gst-libav just end up with a runtime |
| 26 |
> error if they use ffmpeg (if the upstream authors follow up with their |
| 27 |
> plan) or those users wanting to use mencoder might get some compile |
| 28 |
> errors if I forgot to update the compatibility patch after somebody |
| 29 |
> bumped w/out testing. |
| 30 |
|
| 31 |
Well, this is important. You, as libav developer, could very well try |
| 32 |
to convince gst-libav people that it's stupid to ban FFmpeg for no |
| 33 |
technical reason and that the big fat warning when not using the |
| 34 |
internal version is more due to historical reasons than anything recent |
| 35 |
since all decent distributions do not use their bundled libav version. |
| 36 |
mplayer is not that libav-hater as you may think since I believe some |
| 37 |
libav-compatibility fixes landed before 1.1 (maybe not all, but at |
| 38 |
least the PIX_FMT hell was resolved). |
| 39 |
|
| 40 |
> It really boils down to decide to be extra careful with mplayer and |
| 41 |
> xbmc or being extra careful with gst-libav and maybe vlc. |
| 42 |
|
| 43 |
IMHO this has to be done whatever the default is. |
| 44 |
|
| 45 |
> Sadly this whole discussion turned to discussing who is right or |
| 46 |
> wrong, who is the fork or not and who's an evil bastard oppressing |
| 47 |
> the poor Austrian genius or not. |
| 48 |
|
| 49 |
I didn't want to have it go that way. I was mainly pointing out that, |
| 50 |
personal issues apart, FFmpeg has its technical merits that are |
| 51 |
completely ignored by libav. |
| 52 |
|
| 53 |
> I'm ok discussing technical merits and spend time fixing issues, not |
| 54 |
> so much discussing stuff I'd rather not discuss such as if I'm an evil |
| 55 |
> bastard for not working with somebody that joked about my death. |
| 56 |
|
| 57 |
+1 |
| 58 |
|
| 59 |
Alexis. |
Archives