similar to: libao compiling error

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

The last few threads have really been interesting. Technologies that are currently on the market are MP3, RealAudio, and Windows Media (pre-version8). Technologies currently in progress or just shipped are Ogg Vorbis and mp3pro. I don't think anyone has mentioned TwinVQ on this list. While exploring alternatives to MP3 (which is when I also found Vorbis), I noticed TwinVQ. I encoded

Hello. As the subject of my email states, I've noticed that oggenc never encodes the same twice. i.e., encoding the same file twice, using the same settings and same OS, never results in identical files (checked using 'diff'). I know that a randomly generated serial number is put it, but it gets better: a diff (- a -u0) between these two encodings is ~120KiB. Umm... why?

i'm recently started to encode my cd's into ogg vorbis format (192kb/s), and i am very much pleased with the quality. however, i will certainly feel awful after encoding 1gb of files and beta5 comes out, claiming to increase the sound quality. in other words, should i be using ogg vorbis for long-term audio storage without fear that those files are crappy quality and should be

... for download from http://home.earthlink.net/~noodlez84/other_files/oggenc20010704.z ip . I am not, however, the man behind the work: Send kudos to Peter Harris. -- noodlez: Karol Pietrzak PGP KeyID: 0x3A1446A0 --- >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

http://www.blorp.com/~peter/zips/in_vorbis.zip fixes some problems with streaming, better tag updating logic, etc. -Peter --- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed.

does anyone compiled a oggenc windows binary from the cvs sources? please send it to me :) --- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the

80kbps test stream using oddcast DSP and new test win32 port of icecast2 server.... http://www.djlithium.com:8064/djlithium.ogg oddsock --- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No

a comparison between the two formats can be read at http://www.digit-life.com/articles/oggvslame/index.html . i first heard of this from Vorbis Extreme ( http://solair.eunet.yu/~aldov/ ). anyone see any problems with the review? -- noodlez: Karol Pietrzak GPG/PGP-KeyID: 0x3A1446A0 --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

I am trying to convert some a few WAV files to ogg format (using vorbis-tools-1.0beta4 oggenc). I tried: $ oggenc -o nash.ogg nash.wav ERROR: Wav file is unsupported subformat (must be 16 bit PCM or floating point PCM ERROR: Input file "nash.wav" is not a supported format And: splay -d - nash.wav | oggenc -r -o nash.ogg - The resulting file when played with ogg123 played so

Okay, here's the patch that should fix byte-ordering madness. The basic rule with libao is that samples have to be in native byte order. All of the drivers will assume this, and libao provides a ao_is_big_endian() function for library clients (and sometimes drivers) to test their byte ordering. I would appreciate it if someone on a big endian platform test ogg123 and make sure that it works

Well we're testing scheduled Ogg streaming, but it would be nice to test with an audience bigger then me and a few irc users, so I thought I'd drop a note to the list. http://support.bbc.co.uk/oggstreams.shtml This will contain any scheduled tests to come and anything currently being streamed. For scheduled stuff, only things we're given permission to do by producers can go on

Peter Schuller wrote : > > I use it a lot, but I still get people mailing me > > .gifs and even worse .jpgs (of things like text!!!) > > That's okay let them. > > JPEG worse than GIF? What are you on? :) At least JPEG supports more than > 256 colors and you don't need to pay $100000 (or whatever) to write an > encoder... Uh, should I send you a GIF and

This patch fixes three problems with the current configure script: 1. Manual exclusion of drivers: Now you will be able to force drivers NOT to be compiled, even if they are detected. This was specifically requested with so that ALSA could be disabled. 2. Selecting the default device: Now you can override the default driver chosen by the script with your own preference. Again, this enhancement

Hi, I noticed there was some discussion on this list about the desire for ogg123 to support output to stdout via Sun's .au file format, so I decided to give implementing an AU driver for libao a shot. Here is my first attempt. To test the driver: * Apply the patch below (against ao in CVS) * Copy the attached ao_au.c into ao/src * Run ao/autogen.sh, compile, and

Seeing that the au driver has been committed, I wonder if there is a particular reason my sun driver (native NetBSD/OpenBSD/Solaris sound support) never has been added. Relevant files attached. Again. -- Christian "naddy" Weisgerber naddy@mips.inka.de <HR NOSHADE> <UL> <LI>text/plain attachment: ao.patch </UL> -------------- next

Xiph.Org announces the release of libao-1.0.0, libvorbis-1.3.1 and vorbis-tools-1.4.0. This is a coordinated update of the audio libraries and tools to deploy improved surround-sound support across the libraries and toolchain. libao improvements: - AO returned to active development - Added surround channel mapping API and capability - Updated all drivers on modern installs - New config file

Xiph.Org announces the release of libao-1.0.0, libvorbis-1.3.1 and vorbis-tools-1.4.0. This is a coordinated update of the audio libraries and tools to deploy improved surround-sound support across the libraries and toolchain. libao improvements: - AO returned to active development - Added surround channel mapping API and capability - Updated all drivers on modern installs - New config file

Hi there. Sorry I may be a little off topics with this mail but I have already written to the official libao maintainer (volsung@xiph.org) and he is the one who suggest me to write here. As I did not see any more suitable mailing list @xiph.org here I am. My point is that I have recently written a win32 driver for the libao and I would be glad to see this contribution include to the official