similar to: documentation for interfacing with libflac?

> I just joined the development team for audacity, a corss platform > open source multitrack audio editor. > > I would like to add support for importing and exporting files in FLAC > format. > > I was wondering if any of you could point me to some documentation > about using libflac to add FLAC support to other programs? > (note to self... write libFLAC documentation

Brian Willoughby wrote: > Hi Justin, > > Are you saying that 24-bit support does not work for you? Which > version of FLAC are you using? What platform? What kind of files are > you trying to compress? > We're using FLAC 1.1.2, and we're compressing any kinds of PCM audio. The software that we make that uses it is REAPER, www.reaper.fm. We sent some messages

Hello Fellow-Vorbisites, I've written a multi-track encoding/decoding library based upon fishsound. Utilized Visual Studio 2010 to build 32-bit DLL's (Debug mode - no optimization) of all the following: libogg 1.3.1 libvorbis 1.3.3 libspeex 1.2rc1 libflac 1.2.1 liboggz 1.1.1 libfishsound 1.0.0 Currently testing under Windows 7 (64-bit). Test Scenario: ========== Recording from two

So some research and experimentation I think I found the problem, but I'm not sure how to go about fixing it. If I import one of the wav files into Audacity then export them as "16 bit PCM" then they encode to flac and play fine. The files bitrates are currently at 24. If I export them from audacity as a 24 or 32 (anything higher than 16), flac fails on me. With a bitrate of 24, the

Dear All, I've sent yesterday this issue, but as it contained two screenshots, I'm not sure if it reached the list. I post it again with some updates. 1) I had encoded a WAV file three years ago. Examining the FLAC file with an HEX/text viewer, i find at the beginning, after some headers, it declares reference libFLAC 1.3.1 20141125. However, I'm pretty sure I didn't use that

> On Dec 17, 2009, at 8:50 PM, dathead2 at gmail.com wrote: > > On Dec 17, 2009, at 8:42 PM, Ron Decline <rutlecorps at gmail.com> wrote: > >> Is it possible to switch the Left / Right channel when encoding in FLAC? >> (I have some flac files with incorrect left/right channel assignment that I would like to re-encode with flac) >> _____________________________

lvqcl wrote: > 1) > Current MSVC solution (FLAC.sln and numerous .vcproj files) was made with > VC2005 Express and doesn't allow to build 64-bit files/libraries. > > IMHO it's time to add 64-bit support for MSVC builds, but AFAIK only Visual Studio > 2012/2013 Express are free and allow to build 64-bit files. > > VS 2005/2008 use .vcproj files, and VS

Now that the new libFLAC interface has stabilized, I'm wondering if I should put out one more source release before 1.0? Or is it enough just to have you guys look it over? Binary compatibility should be easier to maintain now since 1) there are no structures passed or altered and 2) the constructors set reasonable defaults so that when parameters are added/ changed/deleted there should be a

I have also asked this question on stackoverflow (http://stackoverflow.com/questions/8694676/compiling-64-bit-flac-libflac-in-os-x-lion), which you can answer if you're interested in reputation points. I am very unfamiliar with compiling C/C++ source of this size, and I'm having trouble debugging the issue. Basically, in the root folder of the FLAC bundle, even if I use the flags

(Sorry, Sylvia, about the duplicate, hit the wrong reply button.) On Fri, 2009-06-05 at 08:07 +1000, Silvia Pfeiffer wrote: > Hi Elaine, > > I flipped through some of the code but wasn't really about to > determine this: Do you also support Skeleton in libogg++ ? Hi, Silvia. I studied your multi-track work when I was working on ALingA. It was a valuable guide. No, libogg++ tries

Thanks for the tip, Brian. I did have a version that does everything in memory, but only had enough memory to get six threads going. (Although my system has 16GB, I have not taken the time to create 64-bit libraries for wxWidgets, TagLib, libFLAC, etc.) Based on the direction you are pointing me in, I assume that encoding from within the decoder is not permitted. I really like your idea of the

I am getting large, corrupted native FLAC files when trying to call the encoder from inside the decoder. The metadata in the output file is OK. Is initializing and calling an encoder from inside a libFLAC decoder write callback supported? The encoder is initialized on the first write callback. Environment is Win 7 Ult, 64-bit, VS 2008, libFLAC 1.2.1. Here is some context. The static

Hi, The GStreamer flac plugin broke due to libflac 1.1.0 and libflac 1.1.1 not being ABI/API compatible. Skimming through the archives I see that this breakage was intentional. I think it is quite common understanding that when you have a stable release of something you don't break your API, you only add to it. If you want to break the API that should be done by going to a new major number,

Hello FLACers, I'm working on implementing FLAC support for Audacity, a cross-platform audio editor (audacity.sourceforge.net). We're experimenting with using FLAC as the internal data representation. Unfortunately, the FLAC headers cannot be used in C++ programs because of the use of 'private' and 'protected' as variable names in stream_decoder.h, stream_encoder.h, and

Hi, Having worked on a 4 channel encode/decode system, which works just fine (using 4 channel audio on SGI systems). I now would like to think a little further about how 'n' channel encodes may be used for network collaboration in music. Let's imagine a 16 channel codec, and let's say we are working in a simple stereo in/out environment (i.e. like most consumer devices out

First, this dependency exists only on Windows. For obvious reasons such dependency cannot exist on Linux/FreeBSD/OSX/etc. Previous versions (up to 1.2.1) didn't support Unicode filenames on Windows. And then it was decided to add such support. Windows uses UTF-16, where characters have 16-bit wchar_t type. LibFLAC receives strings only via char*. So one way to add Unicode support is to add

Hello, I just tried to compile libFLAC (using Borland C++ Builder 6 on Windows). The compilers yells at me on line 233 of libFLAC/lpc.c *(residual++) = *(data++) - (sum >> lp_quantization); --> data is const and cannot be modified Funny thing is, if data is declared: const FLAC__int32 *data instead of const FLAC__int32 data[] everything is ok. Is this a bug in my compiler, or

For those of you using CVS, I have added a libFLAC section to the documentation page. I'm not sure how detailed to make it but I think it's a good start. Let me know if there's anything else you'd like to have in there. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/flac/flac/doc/documentation.html?rev=HEAD Also, I'm thinking about splitting the encoder into

lvqcl wrote: > Audacity still uses VS2008 and slowly tries to migrate to VS2012. > But as stated at <http://wiki.audacityteam.org/wiki/Developing_On_Windows>, > "Audacity is currently a 32-bit only application". So it doesn't need > 64-bit builds. > Currently its trunk contains 'audacity.sln' made with Visual C++ Express 2008 > and

> Any thoughts to perhaps integrating a quick sector-boundary check of the > wav file before encoding? Does this functionality extend beyond the scope > of FLAC? A quick check, and a "this wav file is not cut on a sector > boundary, continue y/n" warning would do the trick. Perhaps, an > option to > silence this check would be useful also. > it's easy to