similar to: vorbis.m4 macro glitch

I have just downloaded the vorbis sdk for windows, for researching purposes. I have compiled the example 'encoder_example.c' just to start, and it compiles, but I got a error in the following line just at the beginning: vorbis_encode_init(&vi,2,44100, -1, 128000, -1); The error is more or less: The instruction at '0xaddresss' referenced memory at '0xaddress'. The

Yes, it works now. Thank you very much. -----Original Message----- From: Chris Wolf [mailto:cwolf@starclass.com] Sent: 05 September 2001 10:12 To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] Problems trying to run the examples in windows vorbis sdk On 9/4/2001 at 6:00 PM Pablos-Sanchez, Rolando wrote: >I have just downloaded the vorbis sdk for windows, for researching >purposes. >

Hi devs, I am developing winLAME, a frontend for LAME, and it also supports Ogg Vorbis decoding and encoding. I've got a question about the new API function vorbis_encode_init_vbr(). Do I have to call vorbis_encode_init() before to set the bitrate(s)? And what is a good default value for the "base_quality" parameter? I read on the mailing list that ABR use in Ogg Vorbis is not so

Just got around to compiling RC3 under beos and came across an anomaly when using managed bitrates. I haven't changed the code for the beos encoder but I now get double the bitrates so vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); now gives me vorbis files that average around 325 - 350. Is this now the correct

On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote: > This adds clang/gcc visibility macro detection to configure and util/macros.h. > This is can be used to conveniently add e.g. a "HIDDEN" attribute to a function. > > Signed-off-by: Marc Dietrich <marvin24 at gmx.de> > --- > v2: use VISIBILITY_*FLAGS instead of *FLAGS directly >

Hi, Maybe this is documented somewhere, if so, please send me a link to the documentation. My question is: how to set up different (VBR, CBR, ABR) modes when calling the Ogg Vorbis API? Currently I do: CBR: ret = vorbis_encode_setup_managed( &vorbisInfo, getInChannel(), getOutSampleRate(),

Hi, A short mail to let you know that the MSVC project files aren't OK compared to the Makefiles. Indeed they include the vorbisenc part (vorbisenc.c file, and vorbis_encode_* function names in the .def file) inside the vorbis library, and they also point to a non-existant file (bitbuffer.h) Here is a patch to fix this, in case you are interested (patch made on the win32 directory using

Using RH71. Got Lame, Vorbis, gcc3 and everything installed. When I try to make DarkIce I get this error. Can anyone help? $ make make all-recursive make[1]: Entering directory `/usr/src/download/darkice-0.6' Making all in src make[2]: Entering directory `/usr/src/download/darkice-0.6/src' c++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -Wall -c DarkIce.cpp In file included from

Hi Marc On 17/02/15 09:40, Marc Dietrich wrote: > This adds clang/gcc visibility macro detection to configure and util/macros.h. > This is can be used to conveniently add e.g. a "HIDDEN" attribute to a function. > I believe this should be OK to go in regardless of the status of patch 2. There are just a couple of trivial nitpicks. > Signed-off-by: Marc Dietrich

I would like to bring up two issues concerning C++11. First, the R-devel manuals contain incorrect statements regarding C++11: i) R-exts.texi: Although there is a 2011 version of the C++ standard, it is not yet fully implemented (nor is it likely to be widely available for some years) and portable C++ code needs to follow the 1998 standard (and not use features

Hi, I was reading through the R extensions website and noticed that the example code at the end of the section makes references to CXX11XSTD and CXX11XFLAGS, shouldn?t these be CXX1XSTD and CXX1XFLAGS respectfully? (on the second and fourth line) CXX1X=`"${R_HOME}/bin/R" CMD config CXX11X` CXX1XSTD=`"${R_HOME}/bin/R" CMD config CXX11XSTD` CXX="$(CXX1X) $(CXX1XSTD)"

Hi, It's a bit offtopic for this list, but you might be able to help. For libvorbis rc3, what is the correct bitrate parametrization for the call vorbis_encode_init()? For rc2, it worked calling it the following way: vorbis_encode_init( &vorbisInfo, 2, // two channels 44100, // 44.1kHz

In C++ code for use in a R-3.1.0 package, my specific problem is that I would like to use <unordered_map> if it is available, or <tr1/unordered_map> if not, or <map> if all else fails. I (think I) can accomplish this with configure.ac as AC_INIT("DESCRIPTION") CXX=`"${R_HOME}/bin/R" CMD config CXX` CXXFLAGS=`"${R_HOME}/bin/R" CMD config

Here are some minor things I noticed when updating the vorbis module for GoldWave: Bitwise.c, line 175 and 207 Warning: Negative unsigned value ret=-1UL; Info.c, line 385 Warning: Unreachable code break; vorbisfile.c, line 1407 Warning: Call to function with no prototype int host_endian = host_is_big_endian(); fix: add 'void' to line 1339: static int host_is_big_endian( void )

Hi, I'm trying to load the vorbis libs dynamicly on Mac OS X. I've got success for libogg, libvorbis and libvorbisfile. But libvorbisenc drives me crazy. The function "vorbis_encode_init" seems not to be in there if I am using "NSLookupSymbolInImage". But the tools "otool" and "nm" tell me that the function is declared. Does anyone know, what I

Hi, I want to encode audio at very low bitrates. however, vorbis_encode_init() does not allow me to set bitrates below 32kbps. How can i set 24kbps? Thanks, Flo --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word

Hi, I'm experimenting with IceCast2, using DarkIce to generate the stream. I have found some peculiarities with the vorbis bitrates. In DarkIce, I call vorbis_encode_init() with about the following values: vorbis_encode_init( &vorbisInfo, 2, 44100, 96, 96, 96); which by all reasons should generate a 96 kb/s stream, as all max_bitrate, nominal_bitrate and min_bitrate are set to 96.

Hi, Why do I get an error message when i'm running the "encoder_example.c" which is included in the SDK? The error occurs then the 44 bits are read and the vorbis_info struct is initiated (i.e. when the vorbis_encode_init(&vi,2,44100, -1, 128000, -1) - funcion is called. I also tried to read the data from a 16 bits 44,1 KHz stereo PCM - wave file but recived the same error.

Hi, I'm experimenting with managed mode encoding with specifying maximum bitrate. I call: vorbis_encode_init( &vorbisInfo, 2, 44100, -1, 96000, 96000); to initialize the encoding. To my surprise, it seems the maxbitrate value of 96000 doesn't have an effect, the bitrate of the

On Mon, 29 Jun 2020 at 11:24, I?aki Ucar <iucar at fedoraproject.org> wrote: > > On Mon, 29 Jun 2020 at 10:21, Roger Bivand <Roger.Bivand at nhh.no> wrote: > > > > In the rgdal package, configure.ac has had : ${LDFLAGS=`"${RBIN}" CMD > > config LDFLAGS`} at least since 2012, so picking up LDFLAGS known to the R > > version installed. Very