similar to: Coverity and libvorbis

Prototype.js and Thomas''s effects scripts use repeated setTimeout calls for timed looping, for instance in time-based observers. On Konqueror 3.4.1 (possibly other khtml-based browsers, too), these observers reproducibly crash the browser. Just keeping open a browser with such an observer is enough. After some time it invariably segfaults. When I substitute setInterval for setTimeout

Hi all, Any ideas when the next libvorbis release will be? I'm particularly interested in this fix: r13571 | erikd | 2007-08-19 19:36:24 +1000 (Sun, 19 Aug 2007) | 1 line Make vorbis comment functions const correct. with which I get a warning when compiling libsndfile. The configure.ac for libsndfile I'm about to release currently depends on the SVN version of libvorbis so

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

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

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

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

Hi Josh, On Sat, 2004-10-09 at 22:41, Josh Coalson wrote: > --- Marek Peteraj <marpet@naex.sk> wrote: > > Hi all, > > > > i'd like to ask what the best options are for safe 24bit 96kHz > > archiving. Currently i'm only using -8 but there are also some other > > options like block size etc. Can anyone suggest? > > I haven't heard of

Hi all, i'd like to ask what the best options are for safe 24bit 96kHz archiving. Currently i'm only using -8 but there are also some other options like block size etc. Can anyone suggest? Also i'd like to ask whether a no-lax 192kHz mode is planned in flac, seems like 192kHz isn't directly supported although flac can compress such rate in lax mode. My last question - is there

Hi, sndfile-convert already converts from all these formats to FLAC, but the flac tool itself has more flac-specific options. Is it possible to use sndfile-convert to provide the input data? In any case Erik is maintaining both libsndfile and libflac, and it's unlikely he'd want to duplicate the code. If anything it'd make more sense to remove code for reading other formats from the

Hi there, I am working with opt-6.0 and try to generate a call graph of libsndfile, but it seems the call graph doesn't cover all call relationship. Actually, I am doing static analysis on *CVE-2014-8130*, which is a zero division on libtiff/tif_write.c TIFFWriteScanline. (see https://security-tracker.debian.org/tracker/CVE-2014-8130) Theoretically, the main function in

Hi Michal 2012/1/10 Michal Hlavinka <mihl-guest at alioth.debian.org> > Author: mihl-guest > Date: Tue Jan 10 09:10:04 2012 > New Revision: 3383 > URL: http://trac.networkupstools.org/projects/nut/changeset/3383 > > Log: > Creating a branch for Coverity reported problems > I'm very interested there! Have you been able to get NUT part of the Coverity Scan

> Jean-Marc, to generate a DLL using MinGW, you need to add -no-undefined > to the link line. For libsndfile, I do this using the following in > the Makefile.am file: > > libsndfile_la_LDFLAGS = -no-undefined -version-info @SHARED_VERSION_INFO@ @SHLIB_VERSION_ARG@ Could you tell me more about what that flag does? Any side effects? Is it gcc-specific? Jean-Marc

Ben Allison wrote: > Visual Studio files (which don't use config.h, but define various things > in the project settings) are compiling with the wrong FLAC version string > (1.2.0 or 1.2.1) Is there really no other way to set the version string? > I've attached the patch. Thanks. I'm wondering if it really should be 1.3.0 and not 1.3.0pre1 which is more accurate at least

I have a test program that loads an AIFF or WAV file with libsndfile and plays then using libao. After running around in circles for a while, I found and fixed the problem, but I'm still confused as to why the solution works. Would someone please explain this to me so I don't trip over this again later in my project? I used sf_open_fd() to get a SNDFILE* pointer and an AF_INFO

Coverity generates false positives when read_atomic() and write_atomic() are called with pointers to objects smaller than 64 bits (because it can''t see that the 64-bit access in the switych statement is dead code). I don''t want to automatically suppress all ofthose, because read_atomic() and write_atomic() could still be called with mis-cast pointers, but for atomic_t accessors

There are a few other issues that Coverity found, but I believe all can be ignored ... except one: We don't set umask anywhere inside nbdkit. Coverity complains that this is a problem where we create temporary files, since the result of mkstemp depends implicitly on the umask value. I think we might consider setting umask anyway (eg. to 022) just to make plugin behaviour more predictable.