Audacity

Hi,

a user (Email: audacity at fabian-franz dot de) has implemented 
FFMPEG-Support for Audacity. The files are available here:

http://debian.tu-bs.de/knoppix/experiments/audacity/ 
<http://audacity.fuchsi.de/forum.php?req=derefer&url=http%3A%2F%2Fdebian.tu-bs.de%2Fknoppix%2Fexperiments%2Faudacity%2F>

FFMPEG is a Library which can read file formats like WMA and Quicktime 
without native OS support. Do we have any interest in that? How do you 
think about the legal situation (MPEG patents etc.)?


Markus

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Alexandre Prokoudine <alexandre.prokoudine@gm...> - 2005-09-20 21:29 On 9/21/05, Markus Meyer <meyer@...> wrote: > Hi, >=20 > a user (Email: audacity at fabian-franz dot de) has implemented > FFMPEG-Support for Audacity. The files are available here: >=20 > http://debian.tu-bs.de/knoppix/experiments/audacity/ > <http://audacity.fuchsi.de/forum.php?req=3Dderefer&url=3Dhttp%3A%2F%2Fdeb= ian.tu-bs.de%2Fknoppix%2Fexperiments%2Faudacity%2F> >=20 > FFMPEG is a Library which can read file formats like WMA and Quicktime > without native OS support. Do we have any interest in that? How do you > think about the legal situation (MPEG patents etc.)? I don't think there will be problems unless Audacity statically links to FF= MPEG. Alexandre

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Dominic Mazzoni <dominic@au...> - 2005-09-21 07:18 On Sep 20, 2005, at 2:29 PM, Alexandre Prokoudine wrote: > On 9/21/05, Markus Meyer <meyer@...> wrote: > >> Hi, >> >> a user (Email: audacity at fabian-franz dot de) has implemented >> FFMPEG-Support for Audacity. The files are available here: >> >> http://debian.tu-bs.de/knoppix/experiments/audacity/ >> <http://audacity.fuchsi.de/forum.php?req=derefer&url=http%3A%2F% >> 2Fdebian.tu-bs.de%2Fknoppix%2Fexperiments%2Faudacity%2F> >> >> FFMPEG is a Library which can read file formats like WMA and >> Quicktime >> without native OS support. Do we have any interest in that? How do >> you >> think about the legal situation (MPEG patents etc.)? >> > > I don't think there will be problems unless Audacity statically > links to FFMPEG. Agreed - including this in the source code should present no problems at all, similarly including it in lib-src. The only question is whether we should statically link FFMPEG in a binary release of Audacity. - Dominic > Alexandre > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or > your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/ > geronimo.php > _______________________________________________ > Audacity-devel mailing list > Audacity-devel@... > https://lists.sourceforge.net/lists/listinfo/audacity-devel >

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Markus Meyer <meyer@me...> - 2005-09-21 07:29 Dominic Mazzoni schrieb: >> I don't think there will be problems unless Audacity statically >> links to FFMPEG. > > > Agreed - including this in the source code should present no problems > at all, similarly including it in lib-src. The only question is > whether we should statically link FFMPEG in a binary release of > Audacity. But if we do not intend to link statically to FFMPEG that means we must use a dynamic link method similar to what we do with LAME now. And if we want to do that, the code must be changed, and UI code must be written similar to the "Locate LAME Library" UI now. I don't think it's a good idea to postpone the discussion about whether to include it to release time; we will have plenty of other stuff to discuss then. The question remains: Is this discussion necessary? Is FFMPEG any different than LAME, in the legal sense? Markus > > - Dominic > >> Alexandre >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App Server. >> Download it for free - -and be entered to win a 42" plasma tv or >> your very >> own Sony(tm)PSP. Click here to play: http://sourceforge.net/ >> geronimo.php >> _______________________________________________ >> Audacity-devel mailing list >> Audacity-devel@... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your > very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Audacity-devel mailing list > Audacity-devel@... > https://lists.sourceforge.net/lists/listinfo/audacity-devel >

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Richard Ash <richard@au...> - 2005-09-21 07:36 Alexandre Prokoudine said: > On 9/21/05, Markus Meyer <meyer@...> wrote: >> a user (Email: audacity at fabian-franz dot de) has implemented >> FFMPEG-Support for Audacity. >> FFMPEG is a Library which can read file formats like WMA and Quicktime >> without native OS support. Do we have any interest in that? How do you >> think about the legal situation (MPEG patents etc.)? > > I don't think there will be problems unless Audacity statically links to > FFMPEG. It looks like FFMPEG can be built for windows and OSX as well as linux, so it is a plausible way to get import for lots of obscure audio formats (and the soundtracks off video files as well?). We will inevitably find we have a library versioning issue, i.e. need to rebuild audacity when FFMPEG is rebuilt, if only becuase to get decent support we will probably have to use the CVS version not the release (gentoo has some quite stable snapshots it treats as releases). This means it would be nice to include it in the audacity CVS tree so we all have the same version in use. Minor niggle is that they don't support builds using Visual Studio, so we would need to build the windows dll seperately. That can be done by cross-compiling from linux however, so not a big issue. Richard

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Dominic Mazzoni <dominic@au...> - 2005-09-21 09:28 Markus Meyer wrote: >> Agreed - including this in the source code should present no problems >> at all, similarly including it in lib-src. The only question is >> whether we should statically link FFMPEG in a binary release of >> Audacity. > > But if we do not intend to link statically to FFMPEG that means we must > use a dynamic link method similar to what we do with LAME now. Sorry, I wasn't clear. What I'm proposing is that we check it into CVS, since it will benefit many Linux users and others who choose to build Audacity from source, but that unless the patent situation changes, we don't distribute it in a binary. Most of these formats are already supported by Audacity on Mac OS X (in CVS), thanks to the ability to import and export using QuickTime. I think that the solution for Windows is to use Windows API functions to import other audio formats. Then, thanks to this FFMPEG contribution, we would have all three platforms covered. - Dominic

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Markus Meyer <meyer@me...> - 2005-09-21 09:38 Dominic, thanks for the clarification! Markus Dominic Mazzoni schrieb: > Markus Meyer wrote: > >>> Agreed - including this in the source code should present no >>> problems at all, similarly including it in lib-src. The only >>> question is whether we should statically link FFMPEG in a binary >>> release of Audacity. >> >> >> But if we do not intend to link statically to FFMPEG that means we >> must use a dynamic link method similar to what we do with LAME now. > > > Sorry, I wasn't clear. > > What I'm proposing is that we check it into CVS, since it will benefit > many Linux users and others who choose to build Audacity from source, > but that unless the patent situation changes, we don't distribute it > in a binary. > > Most of these formats are already supported by Audacity on Mac OS X > (in CVS), thanks to the ability to import and export using QuickTime. > > I think that the solution for Windows is to use Windows API functions > to import other audio formats. Then, thanks to this FFMPEG > contribution, we would have all three platforms covered. > > - Dominic > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your > very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Audacity-devel mailing list > Audacity-devel@... > https://lists.sourceforge.net/lists/listinfo/audacity-devel >

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Richard Ash <richard@au...> - 2005-09-25 18:26 On Wed, 2005-09-21 at 02:28 -0700, Dominic Mazzoni wrote: > Markus Meyer wrote: > >> Agreed - including this in the source code should present no problems > >> at all, similarly including it in lib-src. How awkward would making lib-src a separate module in CVS be? I seem to spend a lot of time watching CVS check out the libraries, which haven't changed, and I don't really need (especially if FFMPEG source is in there, because it ain't small). I also get multiple sets for each branch of audacity I work on. I can see the value of having lib-src, but it can be a pain if you want to look at a particular change and have to check-out the whole lot first. Richard > The only question is > >> whether we should statically link FFMPEG in a binary release of > >> Audacity. > > > > But if we do not intend to link statically to FFMPEG that means we must > > use a dynamic link method similar to what we do with LAME now. > > Sorry, I wasn't clear. > > What I'm proposing is that we check it into CVS, since it will benefit > many Linux users and others who choose to build Audacity from source, > but that unless the patent situation changes, we don't distribute it in > a binary. > > Most of these formats are already supported by Audacity on Mac OS X (in > CVS), thanks to the ability to import and export using QuickTime. > > I think that the solution for Windows is to use Windows API functions to > import other audio formats. Then, thanks to this FFMPEG contribution, > we would have all three platforms covered. > > - Dominic > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Audacity-devel mailing list > Audacity-devel@... > https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] FFMPEG-Patch for Audacity From: Dominic Mazzoni <dominic@au...> - 2005-09-26 08:27 On Sep 25, 2005, at 11:26 AM, Richard Ash wrote: > How awkward would making lib-src a separate module in CVS be? > > I seem to spend a lot of time watching CVS check out the libraries, > which haven't changed, and I don't really need (especially if FFMPEG > source is in there, because it ain't small). I also get multiple sets > for each branch of audacity I work on. > > I can see the value of having lib-src, but it can be a pain if you > want > to look at a particular change and have to check-out the whole lot > first. Actually we have the reverse: everything other than lib-src is in this module, and "audacity" is an alias that gets lib-src also: cvs checkout audacity-src Alternatively, you can ask for a specific directory: cvs checkout audacity/help - Dominic > Richard > > > >> The only question is >> >>>> whether we should statically link FFMPEG in a binary release of >>>> Audacity. >>>> >>> >>> But if we do not intend to link statically to FFMPEG that means >>> we must >>> use a dynamic link method similar to what we do with LAME now. >>> >> >> Sorry, I wasn't clear. >> >> What I'm proposing is that we check it into CVS, since it will >> benefit >> many Linux users and others who choose to build Audacity from source, >> but that unless the patent situation changes, we don't distribute >> it in >> a binary. >> >> Most of these formats are already supported by Audacity on Mac OS >> X (in >> CVS), thanks to the ability to import and export using QuickTime. >> >> I think that the solution for Windows is to use Windows API >> functions to >> import other audio formats. Then, thanks to this FFMPEG >> contribution, >> we would have all three platforms covered. >> >> - Dominic >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App Server. >> Download it for free - -and be entered to win a 42" plasma tv or >> your very >> own Sony(tm)PSP. Click here to play: http://sourceforge.net/ >> geronimo.php >> _______________________________________________ >> Audacity-devel mailing list >> Audacity-devel@... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or > your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/ > geronimo.php > _______________________________________________ > Audacity-devel mailing list > Audacity-devel@... > https://lists.sourceforge.net/lists/listinfo/audacity-devel >

1 message has been excluded from this view by a project administrator.