similar to: Version string

I was going through some of my old CD-Rs and I found some really old Vorbis files. They sound pretty decent though the bitrate is really high(~200 kbps). Their vendor string is Xiphophorus libVorbis I 20000508. I looked on http://wiki.xiph.org/XiphHistory but that doesn't list any encoders from June 08, 2000. Could these files come from a pre-Beta1 encoder? It also says it was

Hi there. First of all, I'd like to congratulate to developers for making a free specification and LGPLed decoder/encoder. :-). I did some test, ripping 17 tracks of my CD and converting them to both MP3 and OGG format. MP3 encoder/player was Lame 3.70 OGG encoder/player was from a Saturday nightly tgz package. ------------------------------------ MP3: LAME-3.70 mpg123-0.59r-4 MP3: lame -S

Hi there. First of all, I'd like to congratulate to developers for making a free specification and LGPLed decoder/encoder. :-). I did some test, ripping 17 tracks of my CD and converting them to both MP3 and OGG format. MP3 encoder/player was Lame 3.70 OGG encoder/player was from a Saturday nightly tgz package. ------------------------------------ MP3: LAME-3.70 mpg123-0.59r-4 MP3: lame -S

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes,

Hiya: Since 1.0.1 is going to include minor tuning fixes that have an effect on audio quality in certain circumstances, I think the vendor tag should be updated according to the attached (and quite trivial) patch. (I chose 20030902 because that's the date of Monty's commits that included the tuning fixes.) -Carsten <p> Index: lib/info.c

Can someone explain this, I have both version of oggenc and oggenc-aotuv installed, wanted to compare theme.. BUT, when I type the commanded: rick@KB32bit:~$ oggenc-aotuv -v OggEnc v1.0.1 (libvorbis 1.0.1) rick@KB32bit:~$ Why don't I see OggEnc-Aotuv Beta 5...etc Odd? Thanks - Rich

A feature request that sounds reasonable and a bug report. ----- Forwarded message from Frank Klemm <pfk@fuchs.offl.uni-jena.de> ----- Delivery-Date: Sat Jan 6 06:35:21 2001 Date: Sat, 6 Jan 2001 15:26:43 +0100 From: Frank Klemm <pfk@fuchs.offl.uni-jena.de> To: xiphmont@xiph.org Subject: ogg123 X-Mailer: Mutt 1.0.1i For ogg123 I need the following feature: - Decode one .ogg file

Hay! Has anyone come across these errors using valgrind for the oggenc tool or the encoder_example.c: ==13108== Invalid read of size 4 ==13108== at 0x4155734: _vp_offset_and_mix (in /usr/local/lib/libvorbis.so.0.4.1) ==13108==

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in

Hello All, even though 'configure' for vorbis-tools-1.1.1 is OK 'make' fails - please see the command line and error messages below. Aby ideas why this happens ? Thanks, Sergei. The failing command line and error messages: 99 gcc -O20 -ffast-math -fsigned-char -o oggenc oggenc.o audio.o encode.o platform.o resample.o

I have a CD ripped with RC2, ogginfo from 1.0 claims they are all "broken". ogg123 also goes a little wild with them. I'll experiment a little more, maybe play with xmms, etc. RC3's ogginfo do not see anything wrong with them... an example: ---------- ogginfo 1.0 New logical stream (#1, serial: 2aab0567): type vorbis Vorbis headers parsed for stream 1, information follows...

Here is a patch that implements a check so that libvorbis complains when a comment string that is not UTF-8 is added. This patch will break oggenc without my UTF-8 patch. (http://noa.tm/oggenc-utf8.2.diff.gz) I've tested the verification algorithm on ~150k strings in various charsets (from the gnome translations) and about 0.02% of the strings that has chars with 8th bit set is valid UTF-8

Hello, i had nearly the same problem when compiling libao (of nightly snapshot of 2001/02/10) >checking for artsc-config... /usr/bin/artsc-config >I don't know enough about KDE to know if this file is supposed to be >there without any of the kde-devel packages installed (if not, then I >have a Mandrake bug). If I move this file so it can't be found, make >and make install

Hello, i had nearly the same problem when compiling libao (of nightly snapshot of 2001/02/10) >checking for artsc-config... /usr/bin/artsc-config >I don't know enough about KDE to know if this file is supposed to be >there without any of the kde-devel packages installed (if not, then I >have a Mandrake bug). If I move this file so it can't be found, make >and make install

Hello, I'm not a programmer or know well how to operate gdb. However I've made an attempt to backtrace the problem with 'make debug' and gdb. Please help if you can. I'd appreciate it, I have this problem for a couple of months now. The problem basically is that on debian unstable official packages for the past couple of months(even after debian updates) I get segfaults when I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <p>Hello, I have encountered a situation where oggenc core dumps. I am using vorbis-tools 1.0 on Solaris 8 x86. This is the command line: oggenc -b 128 -a "Keith, Toby" -t "Losing My Touch" -l "Unleashed" \ - -N "06" -o "Keith, Toby - 06. Losing My Touch.ogg" audio_06.wav Here is a

I download all the tarballs for rc3. I compiled and installed all the libraries successfully, but I wan't able to compile the vorbis tools (1.0rc3) package succesfully. I can run configure successfully, but when I run make it dies with this make[2]: Entering directory `/usr/local/src/vorbis-tools-1.0rc3/oggenc' /bin/sh ../libtool --mode=link gcc -O20 -ffast-math -fsigned-char -o

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,