On Thu, Jun 10, 2010 at 08:49:20AM +0200, David Coppa wrote: > On Thu, 10 Jun 2010, Jacob Meuser wrote: > > > On Wed, Jun 09, 2010 at 10:07:06PM +0200, David Coppa wrote: > > > On Wed, 09 Jun 2010, Jacob Meuser wrote: > > > > > > > please update the license marker as well if you're going to do this. > > > > > > Updated diff following. I don't understand why ffmpeg needs gplv3 > > > since opencore-amr has an Apache 2.0 license.. > > > > probably that whole anti-patent thing. > > > > ffmpeg has had amr support for years, btw. it was never enabled in > > the port because the source of the source files, and thus the actual > > distribution terms, was not 100% known (as in, good chance it was > > copied from completely non-free code). I wonder if opencore-amr > > really changes the situation, or if they are just trying to use a > > license that adds more confusion to the situation/makes people > > think they're "protected". > > $ cat > ports/pobj/opencore-amr-0.1.2/opencore-amr-0.1.2/opencore/codecs_v2/audio/gsm_amr/patent_disclaimer.txt > > THIS IS NOT A GRANT OF PATENT RIGHTS. > > Google makes no representation or warranty that the codecs for which > source code is made available hereunder are unencumbered by > third-party patents. Those intending to use this source code in > hardware or software products are advised that implementations of > these codecs, including in open source software or shareware, may > require patent licenses from the relevant patent holders.
of course, but that's not what I was talking about. afaik, the source of the original amr code in ffmpeg was in question. as in, it perhaps was copied from code that was never meant to be distributed in any kind of "free" way. -- [email protected] SDF Public Access UNIX System - http://sdf.lonestar.org
