Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7.1.2011 15:34, Benoit Bolsee wrote: > After that, the patches were finally accepted by FFmpeg development team > and we started to use the automatic build provided by > http://ffmpeg.arrozcru.org > My custom build was probably used for some 2.49 RC releases but > certainly not for the official 2.49b > > Is it possible that Carl stumbled on an old or mixed-up package? My > build was based on FFmpeg revision 17993. We currently use FFMPEG autobuild from April 22nd, 2010, r22941. It's configuration and build log: http://ffmpeg.arrozcru.org/autobuilds/logs/2010-04-22-OK Currently we have not updated, as there are not yet win64 builds of the latest svn. The maintainer of these builds estimates new builds from mid-late March onwards. /Nathan - -- Nathan Letwory Letwory Interactive http://www.letworyinteractive.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNJzNgAAoJEKtfN7KsE0TtQXgH/jmrc7P8nnTjCfBJ7OVxXpr4 9NWbEWB3ZJZQhrEZE6h5BA6ia/Et2bIjA7P1mNd4APMqjNnl9nIUA2WZw+uj4xF5 3yyKOfU40rXCz9V1id+1oye/EVj75rOJ8v2Gp1lL26KcF0LdimPiVLppDjBrY1hi f9XEFb0DZDLLHQqy8ZirnJ3q2vnhS1zlM70Up7jt1BIWQePg4FVAUw9qtSbQhYny fi/0xkXzKIUbyxIbC7fVwIZJJ4WmKd7a+XMf4+y3zjjUzUbQyZ9DJ82q42PxulTj Hd7Ep+ZOHfzkxDlG3M4B01Z5MMVGP2SJFDSuuTG2qUxrW8+O0yCikKUYR8/ei7U= =cQJD -END PGP SIGNATURE- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
A bit of history.. Between April 2008 and March 2009 I was the maintainer for the FFmpeg Windows DLL. I've provided the DLL from Blender releases 2.46 up to 2.49 RC. It was necessary to do a custom build because of some patches that were needed for Blender and not yet included in the official FFmpeg repository. During this period, I included libfaac without knowing that it would create a license conflict of course. Here is the configure command that I used: ./configure --enable-shared --disable-static --enable-memalign-hack --extra-ldflags=-L/shared/lib --extra-cflags=-I/shared/include --enable-libmp3lame --enable-libfaac --enable-libfaad --enable-libx264 --enable-gpl --enable-libxvid --disable-ffplay --disable-ffserver --enable-zlib After that, the patches were finally accepted by FFmpeg development team and we started to use the automatic build provided by http://ffmpeg.arrozcru.org My custom build was probably used for some 2.49 RC releases but certainly not for the official 2.49b Is it possible that Carl stumbled on an old or mixed-up package? My build was based on FFmpeg revision 17993. /benoit On Fri, 07 Jan 2011 01:50:10 +0100, Leo Sutic wrote: > > Carl and everyone else, > > I've done some checking of the FFmpeg integration in Blender 2.49b. > > I came up with the following: > > I can confirm that the default configuration for compiling > FFmpeg into Blender has --enable-gpl set and no > --enable-nonfree. So it *ought* to be all right. > > It is linked against libfaad, but I find no trace of libfaac > in the dll. For example, the string "faac: codec init failed" > is in the dll, but that's from libfaad (libfaad.c), which > does not link to libfaac, as far as I know. In libfaac.c, the > FFmpeg interface to libfaac, are the strings "wrong libfaac > version" and "libfaac AAC (Advanced Audio Codec)", neither > of which can be found in avcodec-52.dll. Unless these strings > are stored somewhere else, shouldn't they be present if > libfaac.o is linked in? > > I am really unfamiliar with the FFmpeg codebase, so I don't > know what the significance of the above is. Carl, could you > give me some guidance as to what to look for to confirm the > existence / absence of libfaac code in the dll? Basically, > what did you see? > > /LS > > On 2011-01-06 17:41, Ton Roosendaal wrote: > > Hi devs, > > > > Please advise. I recall libavcodec is quite old already, > and probably > > obsolete mostly because of FFmpg? > > > > -Ton- > > > > > -- > -- > > Ton Roosendaal Blender Foundation t...@blender.org > www.blender.org > > Blender Institute Entrepotdok 57A 1018AD Amsterdam The > Netherlands > > > > Begin forwarded message: > > > >> From: Carl Eugen Hoyos > >> Date: 6 January, 2011 17:15:37 GMT+01:00 > >> To: foundat...@blender.org > >> Subject: Copyright violation distributing faac binaries together > >> with GPL software > >> > >> Hi! > >> > >> I am an FFmpeg developer and I just found out that Blender binaries > >> are distributed containing GPL'd versions of libavcodec linked > >> against non-free software (this is a copyright violation). > >> > >> I don't know where to report this (should I open a bug report?), so > >> I write to the only email adress I easily found on the web-site. > >> > >> I downloaded blender-2.49b-windows, it contains libavcodec.dll, a > >> binary distribution of libavcodec. The dll contains code > from x264, > >> making it GPL (and not LGPL). It also contains code from > the libfaac > >> project. > >> Originally, libfaac claimed to be free software (under the LGPL), > >> but unfortunately, this was never true: libfaac is (and > always has > >> been) proprietary software. > >> Since you cannot fulfill the requirements of the GPL for libfaac, > >> you cannot distribute a GPL'd version of libavcodec with libfaac > >> support enabled. Please remove it from your download page > / update > >> your libavcodec version. > >> > >> Thank you, Carl Eugen Hoyos > > > > ___ > > Bf-committers mailing list > > Bf-committers@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers > > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
On 6 January 2011 21:47, Dan Eicher wrote: >> I think it would be trivial to get a source package checked in there >> as well. The corresponding source tarball is here: >> >> >> http://ffmpeg.arrozcru.org/autobuilds/ffmpeg/sources/ffmpeg-r22941-swscale-r31050.tar.bz2 > That's not a GPL violation since the sources only have to be provided on > demand. It's best to plan ahead so such requests can be satisfied promptly and accurately from resources within one's own organisation. -r ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
On Thu, Jan 6, 2011 at 7:17 PM, Leo Sutic wrote: > No probs, dude. > > Regarding the 2.56 version - right now we have a libavcodec dll binary > checked into SVN - there is no source code in the blender tree: > > https://svn.blender.org/svnroot/bf-blender/trunk/lib/windows/ffmpeg/lib/ > > (We have ffmpeg binaries for other platforms checked in as well) > > I think it would be trivial to get a source package checked in there > as well. The corresponding source tarball is here: > > > http://ffmpeg.arrozcru.org/autobuilds/ffmpeg/sources/ffmpeg-r22941-swscale-r31050.tar.bz2 > > I don't have commit access, so I'm leaving this to someone who does now. > > Anyone? > > /LS > That's not a GPL violation since the sources only have to be provided on demand. Dan ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
On Thursday, January 06, 2011, Ton Roosendaal wrote: > Hi devs, > > Please advise. I recall libavcodec is quite old already, and probably > obsolete mostly because of FFmpg? > > -Ton- > > > From: Carl Eugen Hoyos > > Date: 6 January, 2011 17:15:37 GMT+01:00 > > To: foundat...@blender.org > > Subject: Copyright violation distributing faac binaries together > > with GPL software > > > > I downloaded blender-2.49b-windows, it contains libavcodec.dll, a > > binary distribution of libavcodec. The dll contains code from x264, > > making it GPL (and not LGPL). It also contains code from the libfaac > > project. > > Originally, libfaac claimed to be free software (under the LGPL), > > but unfortunately, this was never true: libfaac is (and always has > > been) proprietary software. I'm not sure where he is getting this from. There is no libfaac dll shipped in the zip archive, and the dll deos not appear to be statically linked with libfaac. reu...@subterfuge ~ $ strings avcodec-52.dll | grep aac aac_main aac_low aac_ssr aac_ltp Read beyond end of ff_aac_codebook_vectors[%d][]. index %d >= %d jaac faacDecInit2 failed r:%d sr:%ld ch:%ld s:%d faac: codec init failed. faac: frame decoding failed: %s aac_adtstoasc aac_adtstoasc_bsf aac_decoder aac_encoder aac_parser ff_aac_ac3_parse ff_aac_codebook_vectors ff_aac_coders ff_aac_kbd_long_1024 ff_aac_kbd_short_128 ff_aac_num_swb_1024 ff_aac_num_swb_128 ff_aac_parse_header ff_aac_pow2sf_tab ff_aac_pred_sfb_max ff_aac_psy_model ff_aac_scalefactor_bits ff_aac_scalefactor_code ff_aac_spectral_bits ff_aac_spectral_codes ff_aac_spectral_sizes I believe all of those strings are comming from the ffmpeg codebase. On _MY_ system where I compiled ffmpeg with libfaac: reu...@subterfuge ~ $ less /usr/lib64/libavcodec.so.52 Dynamic section at offset 0x69e848 contains 47 entries: TagType Name/Value [ ... ] 0x0001 (NEEDED) Shared library: [libfaac.so.0] -Reuben ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
On Thursday, January 06, 2011, Leo Sutic wrote: > The solution is to compile FFmpeg / libavcodec without libfaac. > (Throwing out x264 is not an option, as libfaac has more problems than > just being GPL-incompatible) It should be a build config change and > that's it - but someone has to build a new distribution. Then we should > be OK. SVN is down fot the moment, so I haven't been able to look at the > 2.49 source to figure out where the change needs to be made. > > We lose the ability to encode sound using AAC, but nothing more. > FFMPEG has their own AAC decoder which should work for the decode side. They have been developing their own AAC encoder as well, but it's still a work in progress. I've always built against my system's ffmpeg (0.6.1+) without any issues. (at least for building) -Reuben ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
No probs, dude. Regarding the 2.56 version - right now we have a libavcodec dll binary checked into SVN - there is no source code in the blender tree: https://svn.blender.org/svnroot/bf-blender/trunk/lib/windows/ffmpeg/lib/ (We have ffmpeg binaries for other platforms checked in as well) I think it would be trivial to get a source package checked in there as well. The corresponding source tarball is here: http://ffmpeg.arrozcru.org/autobuilds/ffmpeg/sources/ffmpeg-r22941-swscale-r31050.tar.bz2 I don't have commit access, so I'm leaving this to someone who does now. Anyone? /LS On Fri, Jan 7, 2011 at 2:38 AM, Carl Eugen Hoyos wrote: > Hi! > > Sorry for the noise! > > Your analysis is absolutely correct, given that I am the one hunting real > FFmpeg license violators, I should really know better! libavcodec.dll > shipped with Blender 2.49b was NOT linked against libfaac, there is > absolutely nothing wrong with the dll (license-wise, since it is quite old, > I fear there are a few known bugs in it)! > > Note that there may be another problem, > http://download.blender.org/release//Blender2.56abeta/blender-2.56a-beta-windows32.zip > contains libavcodec, but the source package > http://download.blender.org/source/blender-2.56-beta.tar.gz may be missing > FFmpeg sources (probably because you removed FFmpeg from your source tree, > iiuc), > Am I right or am I again missing something? > > Thank you for reacting so quickly (I wish the real license violators would > be so fast!), and please excuse me again for making wrong assumptions! > > Carl Eugen > > PS: The reason I went to your forum today (and believed I saw the wrong > information there that Blender uses libfaac) is this bug report that claims > a problem using libavcodec: > http://roundup.ffmpeg.org/issue2485 > If anybody knows which "posts in the blender's bugtracker" user chaos means, > I can try to help (although I am very bad in using libavcodec outside of > FFmpeg/MPlayer). I didn't find anything remotely similar, but perhaps you > know what he is talking about. > > On Fri, 7 Jan 2011, Leo Sutic wrote: > >> Carl and everyone else, >> >> I've done some checking of the FFmpeg integration in Blender 2.49b. >> >> I came up with the following: >> >> I can confirm that the default configuration for compiling FFmpeg into >> Blender has --enable-gpl set and no --enable-nonfree. So it *ought* to >> be all right. >> >> It is linked against libfaad, but I find no trace of libfaac in the dll. >> For example, the string "faac: codec init failed" is in the dll, but >> that's from libfaad (libfaad.c), which does not link to libfaac, as far >> as I know. In libfaac.c, the FFmpeg interface to libfaac, are the >> strings "wrong libfaac version" and "libfaac AAC (Advanced Audio >> Codec)", neither of which can be found in avcodec-52.dll. Unless these >> strings are stored somewhere else, shouldn't they be present if >> libfaac.o is linked in? >> >> I am really unfamiliar with the FFmpeg codebase, so I don't know what >> the significance of the above is. Carl, could you give me some guidance >> as to what to look for to confirm the existence / absence of libfaac >> code in the dll? Basically, what did you see? >> >> /LS >> >> On 2011-01-06 17:41, Ton Roosendaal wrote: >>> >>> Hi devs, >>> >>> Please advise. I recall libavcodec is quite old already, and probably >>> obsolete mostly because of FFmpg? >>> >>> -Ton- >>> >>> >>> Ton Roosendaal Blender Foundation t...@blender.org www.blender.org >>> Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands >>> >>> Begin forwarded message: >>> From: Carl Eugen Hoyos Date: 6 January, 2011 17:15:37 GMT+01:00 To: foundat...@blender.org Subject: Copyright violation distributing faac binaries together with GPL software Hi! I am an FFmpeg developer and I just found out that Blender binaries are distributed containing GPL'd versions of libavcodec linked against non-free software (this is a copyright violation). I don't know where to report this (should I open a bug report?), so I write to the only email adress I easily found on the web-site. I downloaded blender-2.49b-windows, it contains libavcodec.dll, a binary distribution of libavcodec. The dll contains code from x264, making it GPL (and not LGPL). It also contains code from the libfaac project. Originally, libfaac claimed to be free software (under the LGPL), but unfortunately, this was never true: libfaac is (and always has been) proprietary software. Since you cannot fulfill the requirements of the GPL for libfaac, you cannot distribute a GPL'd version of libavcodec with libfaac support enabled. Please remove it from your download page / update your libavcodec version. Thank you, Carl Eugen Hoyos >>> >>> _
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
Carl and everyone else, I've done some checking of the FFmpeg integration in Blender 2.49b. I came up with the following: I can confirm that the default configuration for compiling FFmpeg into Blender has --enable-gpl set and no --enable-nonfree. So it *ought* to be all right. It is linked against libfaad, but I find no trace of libfaac in the dll. For example, the string "faac: codec init failed" is in the dll, but that's from libfaad (libfaad.c), which does not link to libfaac, as far as I know. In libfaac.c, the FFmpeg interface to libfaac, are the strings "wrong libfaac version" and "libfaac AAC (Advanced Audio Codec)", neither of which can be found in avcodec-52.dll. Unless these strings are stored somewhere else, shouldn't they be present if libfaac.o is linked in? I am really unfamiliar with the FFmpeg codebase, so I don't know what the significance of the above is. Carl, could you give me some guidance as to what to look for to confirm the existence / absence of libfaac code in the dll? Basically, what did you see? /LS On 2011-01-06 17:41, Ton Roosendaal wrote: > Hi devs, > > Please advise. I recall libavcodec is quite old already, and probably > obsolete mostly because of FFmpg? > > -Ton- > > > Ton Roosendaal Blender Foundation t...@blender.orgwww.blender.org > Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands > > Begin forwarded message: > >> From: Carl Eugen Hoyos >> Date: 6 January, 2011 17:15:37 GMT+01:00 >> To: foundat...@blender.org >> Subject: Copyright violation distributing faac binaries together >> with GPL software >> >> Hi! >> >> I am an FFmpeg developer and I just found out that Blender binaries >> are distributed containing GPL'd versions of libavcodec linked >> against non-free software (this is a copyright violation). >> >> I don't know where to report this (should I open a bug report?), so >> I write to the only email adress I easily found on the web-site. >> >> I downloaded blender-2.49b-windows, it contains libavcodec.dll, a >> binary distribution of libavcodec. The dll contains code from x264, >> making it GPL (and not LGPL). It also contains code from the libfaac >> project. >> Originally, libfaac claimed to be free software (under the LGPL), >> but unfortunately, this was never true: libfaac is (and always has >> been) proprietary software. >> Since you cannot fulfill the requirements of the GPL for libfaac, >> you cannot distribute a GPL'd version of libavcodec with libfaac >> support enabled. Please remove it from your download page / update >> your libavcodec version. >> >> Thank you, Carl Eugen Hoyos > > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
FYI, the OSX ffmpeg libs are build with version 0.6.1 and are not linked against libfaac. Damien Le 6 janv. 2011 à 18:42, Sergey Kurdakov a écrit : > Hi Ton, > > > I checked ffmpeg code (0.6.1 - it should be there for some time though since > version 0.5 I think)- if it is possible to link against ffmpeg 6.1 why not > to use it?) and it contains native ( for ffmpeg) aac encoder it is there > as a replacement for libfaac. It is of lower quality thought. > > as an alternative VP8/WebM+ Vorbis is preferred now - it is of comparable > quality ( video ) and good sound quality. But then again - ffmpeg contains > acc encoder even without libfaac, just not of high quality > > Regards > Sergey > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
Hi Ton, I checked ffmpeg code (0.6.1 - it should be there for some time though since version 0.5 I think)- if it is possible to link against ffmpeg 6.1 why not to use it?) and it contains native ( for ffmpeg) aac encoder it is there as a replacement for libfaac. It is of lower quality thought. as an alternative VP8/WebM+ Vorbis is preferred now - it is of comparable quality ( video ) and good sound quality. But then again - ffmpeg contains acc encoder even without libfaac, just not of high quality Regards Sergey ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
Ton, libavcodec *is* FFmpeg. (Or part of it, anyway.) The problem that is claimed is that libfaac is included in Blender's version of libavcodec that is distributed with Blender 2.49. The solution is to compile FFmpeg / libavcodec without libfaac. (Throwing out x264 is not an option, as libfaac has more problems than just being GPL-incompatible) It should be a build config change and that's it - but someone has to build a new distribution. Then we should be OK. SVN is down fot the moment, so I haven't been able to look at the 2.49 source to figure out where the change needs to be made. We lose the ability to encode sound using AAC, but nothing more. Could you run this past Carl Hoyos and see if I got this thing right? See here for some others who have run into the same issue: https://bugs.launchpad.net/ubuntu/+source/faac/+bug/374900 http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2009-October/006221.html Also look here for a libfaac license change (?): http://faac.cvs.sourceforge.net/viewvc/faac/faac/libfaac/tns.c?r1=1.8&r2=1.9 Here's the libfaac license, for reference: BEGIN LIBFAAC LICENCE __ COPYRIGHTS FAAC is based on the ISO MPEG-4 reference code. For this base code the following license applies: ** This software module was originally developed by FirstName LastName (CompanyName) and edited by FirstName LastName (CompanyName) FirstName LastName (CompanyName) in the course of development of the MPEG-2 NBC/MPEG-4 Audio standard ISO/IEC 13818-7, 14496-1,2 and 3. This software module is an implementation of a part of one or more MPEG-2 NBC/MPEG-4 Audio tools as specified by the MPEG-2 NBC/MPEG-4 Audio standard. ISO/IEC gives users of the MPEG-2 NBC/MPEG-4 Audio standards free license to this software module or modifications thereof for use in hardware or software products claiming conformance to the MPEG-2 NBC/ MPEG-4 Audio standards. Those intending to use this software module in hardware or software products are advised that this use may infringe existing patents. The original developer of this software module and his/her company, the subsequent editors and their companies, and ISO/IEC have no liability for use of this software module or modifications thereof in an implementation. Copyright is not released for non MPEG-2 NBC/MPEG-4 Audio conforming products. The original developer retains full right to use the code for his/her own purpose, assign or donate the code to a third party and to inhibit third party from using the code for non MPEG-2 NBC/MPEG-4 Audio conforming products. This copyright notice must be included in all copies or derivative works. Copyright (c) 1997. ** For the changes made for the FAAC project the GNU Library General Public License (LGPL), version 2 1991 applies. For the changes the following statement applies: ** FAAC - Freeware Advanced Audio Coder Copyright (C) 2001 M. Bakker This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ** Please note that the use of this software may require the payment of patent royalties. You need to consider this issue before you start building derivative works. We are not warranting or indemnifying you in any way for patent royalities! YOU ARE SOLELY RESPONSIBLE FOR YOUR OWN ACTIONS! END LIBFAAC LICENCE -- /LS On 2011-01-06 17:41, Ton Roosendaal wrote: > Hi devs, > > Please advise. I recall libavcodec is quite old already, and probably > obsolete mostly because of FFmpg? > > -Ton- > > > Ton Roosendaal Blender Foundation t...@blender.orgwww.blender.org > Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands > > Begin forwarded message: > >> From: Carl Eugen Hoyos >> Date: 6 January, 2011 17:15:37 GMT+01:00 >> To: foundat...@blender.org >> Subject: Copyright violation distributing faac binaries together >> with GPL software >> >> Hi! >> >> I am an FFmpeg developer and I just found out that Blender binar
[Bf-committers] Fwd: Copyright violation distributing faac binaries together with GPL software
Hi devs, Please advise. I recall libavcodec is quite old already, and probably obsolete mostly because of FFmpg? -Ton- Ton Roosendaal Blender Foundation t...@blender.orgwww.blender.org Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands Begin forwarded message: > From: Carl Eugen Hoyos > Date: 6 January, 2011 17:15:37 GMT+01:00 > To: foundat...@blender.org > Subject: Copyright violation distributing faac binaries together > with GPL software > > Hi! > > I am an FFmpeg developer and I just found out that Blender binaries > are distributed containing GPL'd versions of libavcodec linked > against non-free software (this is a copyright violation). > > I don't know where to report this (should I open a bug report?), so > I write to the only email adress I easily found on the web-site. > > I downloaded blender-2.49b-windows, it contains libavcodec.dll, a > binary distribution of libavcodec. The dll contains code from x264, > making it GPL (and not LGPL). It also contains code from the libfaac > project. > Originally, libfaac claimed to be free software (under the LGPL), > but unfortunately, this was never true: libfaac is (and always has > been) proprietary software. > Since you cannot fulfill the requirements of the GPL for libfaac, > you cannot distribute a GPL'd version of libavcodec with libfaac > support enabled. Please remove it from your download page / update > your libavcodec version. > > Thank you, Carl Eugen Hoyos ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
