similar to: Next libvorbis release?

Hi all, I'm not sure if you are aware, but libvorbis has been scanned by the Coverity static analysis team : http://scan.coverity.com/ For libvorbis, it found 8 possible bugs. To fix these bugs Coverity need a repesentative from the project to contact them for access to the coverity reporting facilities. The reason I am keen to see Xiph take up this challenge is that when all

Hi all, I'm using the Linux to MinGW cross compiler toolchain to build windows binaries for one of my libraries. I'm also trying to run the cross-compiled binaries that make up the test suite under wine version 0.9.58 from ubuntu hardy heron. The DLL for my library gets built as: /home/erikd/Bzr/libsndfile-mingw/src/.libs/libsndfile-1.dll and the test suite binaries get built in:

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 experts, I am trying to use an example I found here: http://svn.xiph.org/trunk/vorbis/examples/encoder_example.c Could you please tell me what float** buffer is needed for (I don't see it used anywhere). Also, could you please tell me what this code is doing: for(i=0;i<bytes/4;i++){ buffer[0][i]=((readbuffer[i*4+1]<<8)|

Hi there, I maintain the libvorbis, libogg and vorbis-tool package for Fink <http://finkproject.org/ >. Recently I had time to wonder about those again. In particular, since I was informed libsndfile self-tests fails with 1.2.0, but not with a version dubbed 1.2.1rc1 somebody sent me. Also trunk seems to contain security fixes. In https://trac.xiph.org/browser/trunk/vorbis/CHANGES

* Matt Zimmerman (mdz@debian.org) wrote: > I agree with Josh (the other one) that abstraction libraries like > libaudiofile are a good way to make this a zero-maintenance feature. > Theoretically, support for new formats can be added to the library, and > all programs using that library will become instantly able to handle it. This is clearly the best solution. However, no abstraction

Avuton Olrich wrote: > On 7/11/05, Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote: > >>and I'm thinking of adding support for FLAC in a CAF container >>as well. Is anyone else working on this? If so please let me >>know so we can agree on how FLAC should be contained with CAF. > > > I'm sorry, but what are the advantages to the different

Hello, I have written a libsndfile (http://www.mega-nerd.com/libsndfile/) file output plugin for libao. For the moment I haven't done any changes to the core of libao. However some changes could make this more useful. Before I embark on anything like this I'd like to have your opinion on a few things. --- First, what do you prefer ? 1a. Keeping the AU/WAV/RAW plugins and adding

HI all, I have already added FLAC support to libsndfile and I am now working on adding support for OggFLAC. I have a couple of question about things that seem radically different between regular FLAC and OggFLAC. 1) FLAC has a function: FLAC__seekable_stream_decoder_get_decode_position but there seems to be no corresponding function:

I'm having trouble getting libvorbis to cut the beginning of a bitstream when I instruct it to do so with granulepos. I have constructed a file which I believe should have its beginning truncated. I have attached it to this mail. Here is a picture of what the bitstream looks like, as output by a python program that uses pyogg/pyvorbis to read the stream and print a representation:

2013/2/9 Erik de Castro Lopo <mle+la at mega-nerd.com>: > Johnny Rosenberg wrote: > >> For example, when loading an audiofile with libsndfile, all the >> samples are converted to floating point numbers, > > With libsndfile, converting to float is optional. You can just as > easily read int or short. > >> which is what I want >> anyway, but the

2013/2/8 Erik de Castro Lopo <mle+la at mega-nerd.com>: > Collin wrote: > >> It turns out it was an error on my part; sorry for the trouble. I misunderstood >> the format libflac was expecting my samples in. I found the wording in the >> documentation very confusing. >> >> My audio file has 2 channels and 16-bit samples, so I have to pull out each >>

On Oct 12, 2008, at 22:32, Paul Davis wrote: > On Sun, 2008-10-12 at 19:26 -0700, Brian Willoughby wrote: >> Is anyone here potentially up to the task of adding support for CAF >> (the CoreAudio Format) into the flac command-line? This would >> present minimal difficulty under OSX, due to the presence of the >> CoreAudio API, but the real challenge would be to support

2013/2/10 Erik de Castro Lopo <mle+la at mega-nerd.com>: > Johnny Rosenberg wrote: > >> Anyway, if I'm allowed to ask a libsndfile question here, > > Sorry, but no, this list is for FLAC related discussion. And of course you won't waste your time replying outside this mailing list? Is there a libsndfile mailing list? Hm? yet another stupid question, of course. If

XIPH_C_COMPILER_IS_CLANG in configury (commit a6a4b6f) is blocking many flags including the visibility attributes: I guess this needs relaxing, possibly a lot. What incompatibility led to this commit? -- O.S.

--- Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote: > HI all, > > I have already added FLAC support to libsndfile and I am now > working on adding support for OggFLAC. cool. > I have a couple of > question about things that seem radically different between > regular FLAC and OggFLAC. > > 1) FLAC has a function: > >

On 5/3/07, Erik de Castro Lopo <mle+la@mega-nerd.com> wrote: > Peter Grayson wrote: > > Personally I think universal binaries are a bad idea. They have obviously served some purpose, but I tend to agree that the concept does not seem to scale well once outside the Apple microcosm. > For one of my projects, libsndfile, endian issues is not the only > think that breaks in

I managed to get around it. I used the stream functions and provided my own callbacks for reading and writing. What's strange is that what I've done is just copied the contents of read/write/seek/tell/eof callbacks from the sources to my application and it works just fine, no glitches. When I use the build-in implementation, it just crashes without any reason. It's not a problem to

Hello, On a machine with CentOS-5.6, I need libvorbis >= 1.2, so I have recompiled and packaged libvorbis. But I get the following error : $ rpm -U /usr/src/redhat/RPMS/x86_64/libvorbis-1.2.3-phn.1.x86_64.rpm /usr/src/redhat/RPMS/x86_64/libvorbis-devel-1.2.3-phn.1.x86_64.rpm package libvorbis-1.1.2-3.el5_4.4.x86_64 (which is newer than libvorbis-1.2.3-phn.1.x86_64) is already

This patch offers interface to get the library name which software uses. Function: char *vorbis_version_string(void); PATCH (for libvorbis-1.2.1RC2): diff -crN libvorbis-1.2.1RC2/include/vorbis/codec.h libvorbis-1.2.1RC2_NI/include/vorbis/codec.h *** libvorbis-1.2.1RC2/include/vorbis/codec.h Mon Aug 25 05:57:44 2008 --- libvorbis-1.2.1RC2_NI/include/vorbis/codec.h Sat Sep 13 05:00:22 2008