similar to: FLAC won't allow project to build due to assert.h

Displaying 20 results from an estimated 4000 matches similar to: "FLAC won't allow project to build due to assert.h"

2013 May 08
3
Upsampling while decoding / Updating
Dear Nikos, thanks! But you use Opus only for resampling, not for entirely replacing Speex, don't you? Greetings! Hermie Am 07.05.2013 22:53, schrieb Nikos Chantziaras: > The Opus resampler is actually a bugfixed version of the Speex one. Same > interface/API, but with the bugs removed. It's why I recommended it :-) > Otherwise I would have recommended something entirely
2013 Jan 07
3
What's the value range of float samples?
I always assumed that ov_read_float() would get me samples in the range of [-1,1), and anything below or above that can be clamped (or clipped in the final conversion to an integer format.) However, I recently saw this: https://github.com/LaurentGomila/SFML/issues/310#issuecomment-9974550 Apparently, there are Vorbis streams that use float samples with values in the range of [-32768,
2013 May 07
2
Upsampling while decoding / Updating
Dear Nikos, thank you very much for your advice! I am not a little bit new to C++, and experiments (like using another third party library) always turn out to be days of work for me. That is why I would first like to try Speex's new internal resampling function. I am currently still using the old 1.0.4 version. I have now downloaded the new 1.2rc1 version. Unfortunately it does not want
2013 May 07
2
Upsampling while decoding
Hello! I would like to know if it is possible to request encoding to a higher samplerate than the original data. For example my uncompressed data was 22 kHz, and I would now like to decode the compressed data to 48 kHz (to feed it to a filter which expects a high "input" format). Is this possible with Speex? Thank you. Hermie
2012 Jan 12
1
Trying to run FL Studio results in invisible main window
I installed FL Studio (version 10) in Wine (version 1.3.36). Installation works correctly. The program also starts correctly after installation, and appears to be fully functional, but it's totally invisible. Only the task bar entry in the KDE task manager bar appears and the initial dialog from FL Studio that informs me about this being a demo version. I know that the application is
2007 Feb 22
1
R CMD CHECK question
hi, I have two private packages, the first (`pkc') depending on the second one (`roiutils'). The source code and DESCRIPTION files describes the dependency as it should be ('Imports', `require'), at least I think so. now, running R CMD CHECK pkc yields the following output in which I have inserted my questions (lines starting with -->): * checking for working latex ...
2008 Aug 21
3
[LLVMdev] Fix build on GCC 4.3
Index: include/llvm/ADT/APInt.h =================================================================== --- include/llvm/ADT/APInt.h (revision 55101) +++ include/llvm/ADT/APInt.h (working copy) @@ -20,6 +20,7 @@ #include <cassert> #include <iosfwd> #include <string> +#include <cstring> namespace llvm { class Serializer; -------------- next part -------------- An
2007 Mar 19
1
R CMD CHECK problem
I tried two times to get some help for this from the help list but to no avail. I hope, it's OK to post this here (once...). if not, please ignore (the rest of) this mail: for one of my private packages R CMD CHECK {package} givves me annoying warnings due to 'missing links' in the manpages for functions from another private package mentioned in the manpages. specifically, I have two
2008 Jun 18
1
[LLVMdev] Using asserts in LLVM
Hello, I am testing the new cool LLVM python bindings that Mahadevan wrote over the past few weeks. I came across a problem in the python binding which directed me to use of 'cassert'[1] in LLVM itself. When LLVM users make a mistake in using the library's constructs they usually hit an assertion. This form of defensive programming is great for detecting errors as soon as they
2003 Nov 13
4
[LLVMdev] llvm 1.0, g++, SuSE 9, internal compiler error
> > hm, sending bug report is not my favorite hobby :) > > Well if you don't, it might never get fixed :( OK-OK, let's save the world :) Well, I've made it. > It might be possible to hack your <cassert> header file or something > though... it is just a few places in three files as reported in my previous post. Then comes assert violation with message from
2017 Mar 08
3
Use of the C++ standard library in XRay compiler-rt
On Wed, Mar 8, 2017 at 2:28 PM Tim Shen <timshen at google.com> wrote: > On Wed, Mar 8, 2017 at 1:49 PM David Blaikie <dblaikie at gmail.com> wrote: > > So I stumbled across an issue that I think is a bit fundamental: > > The xray runtime uses the C++ standard library. > > This seems like a problem because whatever C++ standard library is used to > compile the
2008 Jun 18
5
paste data
Hello, I need a command. I have a lot of data in different dataframes(auto.0a, auto.0b, auto.0c, auto.5Na,...), that has similar names. I could print the names all at once wih a loop with the command paste(), see below:
2011 Mar 19
2
[LLVMdev] [Patch] Fix bug in llvm::SmallVectorIml<>::insert
This fixes a bug in SmallVectorImpl<>::insert, which were not behaving correctly on inserting an empty range into an empty vector: #include <llvm/ADT/SmallVector.h> #include <cassert> int main() { llvm::SmallVector<int, 1> v, w; llvm::SmallVector<int, 1>::iterator it = v.insert(v.end(), w.begin(), w.end()); assert(it == v.end()); } The insert function(s)
2006 Aug 08
3
[LLVMdev] build error
>From CVS: llvm[3]: Compiling SJLJ-Exception.cpp for Debug build (bytecode) SJLJ-Exception.cpp:16:19: cstdlib: No such file or directory SJLJ-Exception.cpp:17:19: cassert: No such file or directory SJLJ-Exception.cpp: In function `void SJLJDestructor(llvm_exception*)': SJLJ-Exception.cpp:43: error: `free' undeclared (first use this function) SJLJ-Exception.cpp:43: error: (Each
2008 Aug 21
0
[LLVMdev] Fix build on GCC 4.3
Please commit. On Aug 20, 2008, at 8:02 PM, Zhongxing Xu wrote: > Index: include/llvm/ADT/APInt.h > =================================================================== > --- include/llvm/ADT/APInt.h (revision 55101) > +++ include/llvm/ADT/APInt.h (working copy) > @@ -20,6 +20,7 @@ > #include <cassert> > #include <iosfwd> > #include <string> >
2008 Sep 26
0
[LLVMdev] build failure in Attributes.h
Works for me. Presumably #including <cassert> will fix it though? On Sep 26, 2008, at 4:30 PMPDT, Mike Stump wrote: > I'm seeing a build failure... > > In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ > Attributes.cpp:14: > /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member > function 'llvm::Attributes >
2011 Mar 19
0
[LLVMdev] [Patch] Fix bug in llvm::SmallVectorIml<>::insert
Johannes Schaub (litb) wrote: > This fixes a bug in SmallVectorImpl<>::insert, which were not behaving > correctly on inserting an empty range into an empty vector: > > #include <llvm/ADT/SmallVector.h> > #include <cassert> > > int main() { > llvm::SmallVector<int, 1> v, w; > llvm::SmallVector<int, 1>::iterator it = >
2013 Feb 09
5
Commonly getting FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA on valid audio
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 >>
2006 Apr 22
2
libao - libsndfile plugin
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
2008 May 05
2
flac/metaflac 32/64 Universal OS X builds
In my experience, with the gcc compiler, cross-compiling is highly reliable. If your code runs on one processor, then it will run on all. Linking and such might be an issue, which you will discover immediately when the first person tries to run what you've built on their system. It still would be great to run these tests on all four. Actually, you should be able to test 32-bit