similar to: version number

For those who are interested, I've run 3 EAQUAL tests on both the LAME and OGG encoders: LAME with the --alt-standard preset (with and without --nspsytune) and OGGENC (RC3) with -q 6 (my personal "sweet spot") I am somewhat unsure though about the validity of these tests, since the original and decoded files were not the same size (2 KB difference). The LAME encoded files were also

I've just Replaygained several of my Vorbis albums with Vorbisgain, ranging from 80's metal to present day soft rock. What I don't understand is why does Vorbisgain actually make all tracks QUIETER? I see an average of -7db on most albums. And after that, not only are they substantially quieter than my MP3s (which is a pain), but it also fails to really "even out" the volume.

ARGH! I am at a complete loss as to which OGG quality settings to use: 8? 10? 3? I'd like to be able to listen to my primarily Rock oriented music on a high-end system (though I don't own one - yet) without any noticeable sound degradation, but I don't want to go total overkill with -q 10. With LAME, I at least used to know 192 kbps with -q0 was a perfect size/quality proportion. I

Has anyone from the Vorbis team been in contact with the LAME camp? I'm sure with their knowledge, the people developing LAME could make a major contribution to the OGG development, if they were willing. Sure, MP3 and OGG are in some ways majorly different, but they are similarities, right? With the latest stable release of 3.91, I think the LAME crew has done their best and pulled a helluva

I just wanted to know if anyone has noticed a difference between MP3 and OGG encoded files when having the Winamp equalizer switched on? I seem to be missing bass and the sound doesn't fill the room as much with OGG. With the EQ turned off there is no discernable difference between both LAME and Vorbis encoded files (both at an average of 192 kbps). Is this an error with the OGG Winamp plugin?

I started thinking about this after doing a little testing with AAC, MP3 and Ogg Vorbis. I was comparing the different formats at similiar bitrates. After a while I finally realized that they all sound more or less the same to me. >From 160 kbps on, I usually cannot detect any difference between a lossy encoding and the original source. If LAME is used, I have to strain to notice anything at

Hi, today I learned that libogg 1.3.0 had been released in August 2011. Curiously, there seems to have been no announcement mail here, and it is not being mentioned on <http://www.xiph.org/press/> either. Is that on purpose? Is there some other channel I could subscribe to in order to learn about updates? Freecode.com doesn't have up-to-date info either (though I just submitted a 1.3.0

> And as long as the spec contains errors, it makes no sense at all > as Moritz did to claim, that everyone is free to implement their > own encoder or decoder, or as Jon did to claim that the file format > is documented. Actually, people have implemented perfectly valid Vorbis encoders and decoders before the specification was even published. I wouldn't go so far as to call other

I have found a bug in libvorbis-1.0. I have found a fix, but need to know in what format and to where to sumbit the patch. It involves a quirky qsort in Solaris 5.8 that dumps core without the patch. The fix involves editing vorbis/lib/psy.c <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Hi Ralph, Again, thanks so much for doing all this! Plus thanks to all the folks who contributed to the new release! Quick clarifying question -- Isn't CVE-2018-10392 (looks like it’s fixed in https://gitlab.xiph.org/xiph/vorbis/-/issues/2335) also included in new version 1.3.7? If so can you please add it to release notes? (I asked the same question in

Oops! I accidently sent the previous message before I finished it, sorry! However, the problem remains the same. I cannot succesfully compile ices2 for some reason. I've followed some instructions I found on the web at http://www.6809.org.uk/kja3/ices2-howto.shtml. So far, what I've done is: 1) Installation of Slackware 8.1 (with libxml2 2.4.22, gcc 2.95.3) 2) Update of the oggutils

Hello, On a machine with CentOS-5.6, I need libvorbis >= 1.2, so I have recompiled and packaged libvorbis. But I get the following error : $ rpm -U /usr/src/redhat/RPMS/x86_64/libvorbis-1.2.3-phn.1.x86_64.rpm /usr/src/redhat/RPMS/x86_64/libvorbis-devel-1.2.3-phn.1.x86_64.rpm package libvorbis-1.1.2-3.el5_4.4.x86_64 (which is newer than libvorbis-1.2.3-phn.1.x86_64) is already

This patch offers interface to get the library name which software uses. Function: char *vorbis_version_string(void); PATCH (for libvorbis-1.2.1RC2): diff -crN libvorbis-1.2.1RC2/include/vorbis/codec.h libvorbis-1.2.1RC2_NI/include/vorbis/codec.h *** libvorbis-1.2.1RC2/include/vorbis/codec.h Mon Aug 25 05:57:44 2008 --- libvorbis-1.2.1RC2_NI/include/vorbis/codec.h Sat Sep 13 05:00:22 2008

Hi! On March 17th I posted a message on this list concerning an artifact bug in beta4 that is audible in all available bitrates. It was this rumbling sound in the bass area. I made a demo clip, which still is available at http://www.stud.uni-karlsruhe.de/~us87/ogg/vorbis_bassrumble_demo.rar and that contains both the original .WAV and an .OGG @ 350kbps. This archive is 2.1 MB large. Today, I

On Sat, 8 Jan 2005, Henrik Bach wrote: > I think it first of all would be nice, if we could supplement this group with > a discussion list on this topic. The reason for this isn't to ad more > bureacracy, but to present public ideas and visions to a broader forum and I > belive in that the more elaboration within a broader forum the better the > ideas will get and the more

A new libvorbis release is now available. http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.bz2 http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.gz http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.zip This release fixes some robustness issues with corrupt streams, including a security issue. Also new in this release is support for multiplexed streams in

I'm trying to build libvorbis-1.1.0 on Cygwin and I discovered a missing dependency that may not affect other platforms. I found that I had to add -logg to the libvorbisfile.la rule in the Makefile. Working its way back upstream through configure and autogen, it looks like the following line in trunk/vorbis/lib/Makefile.am libvorbisfile_la_LIBADD = libvorbis.la just needs to be changed

Hello everyone, The LLVM project has evolved significantly since our first public release in Oct. 2003. Most importantly, we've gained many new users and several active contributors, and we want to encourage and support them and attract more. At the same time, the software itself has undergone some significant changes and improvements, and been ported to new platforms. We expect that

Hi OG, I think it first of all would be nice, if we could supplement this group with a discussion list on this topic. The reason for this isn't to ad more bureacracy, but to present public ideas and visions to a broader forum and I belive in that the more elaboration within a broader forum the better the ideas will get and the more people will get committed to start and finish the task.

Uaaargh ... between now and the last mail, everything's gone kaploohey. But I doubt that it concerns icecast too much in this case - the streaming computer has a cpu load of 90-100% for no reason (it's an athlon 1ghz with only winamp and ssh and the system monitor running under win98). The playback on the streaming computer sounds good, though, but what reaches the client side is no more