similar to: beta 4 frozen

Hi folks, We're gearing up to the next full release of the Vorbis codec; I've just tagged a release candidate in SVN in order to encourage wider testing toward final 1.1 release. This release includes the following updates: 1) Adoption of AoTuV and other tuning work by Vorbis developers outside of Xiph into the mainline codebase 2) New bitrate management code 3) bugfixes In more

Hi folks, We're gearing up to the next full release of the Vorbis codec; I've just tagged a release candidate in SVN in order to encourage wider testing toward final 1.1 release. This release includes the following updates: 1) Adoption of AoTuV and other tuning work by Vorbis developers outside of Xiph into the mainline codebase 2) New bitrate management code 3) bugfixes In more

Hello, When I compile either oggenc or encoder_example with static libraries, they work fine, but when I try them with the dynamic libraries, I get an access violation in vorbisenc.dll with both oggenc and encoder_example. Can anyone on win32 confirm this? It's strange because vorbisfile.dll *does* work with vorbisfile_example, and the configuration for vorbisfile.dll is exactly the same

The merge of the format changes and new psychoacoustics is complete. There's still tuning work left to do (most notably there's a somewhat higher-than-acceptable level of background low-midrange/upper bass noise; this is due mostly to incomplete psychoacoustic modelling data in the 100Hz-500Hz range) however, at this point, pending bugfixes, the Vorbis 1.0 stream format is frozen.

Hi folks, I'm doing a merge of my current branch onto the mainline (for testing) today. I believe it to be stable. Just a little more vorbisfile testing. After the merge, I have a few more patches to apply, then onto cascading/coupling. New stuff: Floor backend 1 and residue backend 1; both are present, but the mainline modes won't use either yet. Naturally, both are enabled for

Hi everybody: Below is the plain text version of this week's Ogg Traffic. The HTML version is due to be posted on vorbis.com sometime later tonight. Enjoy, Carsten. <p>Ogg Traffic for Tuesday, March 11, 2003 [1]Carsten "Purple" Haese March 11, 2003 _________________________________________________________________ Table of Contents 1. Status Updates

ltconfig placeholder shoud be removed. Makefile.am : some stuff copied from branch_beta3 ogg lib must be added only where necesary. vq subdir Makefile.am'ized, (but installs nothing) made distclean target slightly more clean -- check it by hand first, please --- also you'll want to remove vq/Makefile if the ...am passes inspection ------------------------------------------------- diff

king all in vorbisfile make[2]: Entering directory `/home/ronan/libvorbis-1.0.1/doc/vorbisfile' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/ronan/libvorbis-1.0.1/doc/vorbisfile' Making all in vorbisenc make[2]: Entering directory `/home/ronan/libvorbis-1.0.1/doc/vorbisenc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory

Hello folks, An incredible amount of work got done in the past week and a half. And I missed the arbitrary, meaningless launch deadline. Not much new there... In the past week, developers contributed plugins for Winamp (thanks Jack and Michael), and kmpg (thanks Martin). Sonique added Vorbis support (thanks Andrew), although that won't appear in the 1.5 version just released; expect to

Hello folks, An incredible amount of work got done in the past week and a half. And I missed the arbitrary, meaningless launch deadline. Not much new there... In the past week, developers contributed plugins for Winamp (thanks Jack and Michael), and kmpg (thanks Martin). Sonique added Vorbis support (thanks Andrew), although that won't appear in the 1.5 version just released; expect to

Greetings, On the official documentation page, http://www.xiph.org/ogg/vorbis/docs.html, there are links to the documents describing the released libraries, ie. libvorbis, vorbisfile and vorbisenc. However, the first one is not a link at all, although I seem to remember that it was so earlier. I also downloaded the SDK for Mac OSX, which sorta contains a documentation for libvorbis, but

My branch that I've been working on for the last few weeks is now the mainline; once I add a few more modes (mode_A.h through mode_E.h, corresponding roughly to 128,160,192,256,350 kbps stereo) and Mike Smith and Chad get the modes into OggEnc, we'll be at beta 2. A few things to note: I'd been really really hoping that I'd squeeze the last bit of performance out of non

Folks: Granted, this slipped past my review too, but do *not* submit patches that have not been tested. This bug was a no brainer; running the code only even once would have found it. The mainline of Vorbis is our face to the world. A simple mistake like this costs us credibility when we're already going to be fighting hard against some of the most powerful media organizations in the

OK, I've been a busy beaver tonight. More commits: Finished stabilizing psychoacoustic configuration API; binary compatability stability for libvorbis/vorbisfile would be nice to have by 1.0. Moved several additional return values and internal types to int64_t; basically wherever there's an absolute fine-grained counter. I also moved the vorbisfile API to taking a 64 bit seek callback

Audacity is preparing to release version 2.0.6 shortly, so I have been doing numerous test builds. Since the last Audacity release, my development system (Gentoo Linux) has updated to libvorbis-1.3.4 and libogg-1.3.1. As a result (I think) of this, I now get link errors when trying to compile Audacity against the system copies of libogg and libvorbis (standard dynamic linkage to the system

The Win32 SDK directory layout seems to need a small update in my eyes. Here's why: 1. Debug symbols get overwritten Problem: When the project files in the vorbis/win32 build, all temporary files of vorbis, vorbisfile and vorbisenc go into Dynamic_Debug (for the dynamic debug build as an example). The problems arise, when someone wants to debug the code. Since Visual C++ puts the symbols

Echoing Hiroka, who is likely on the right track. Simply telling the encoder 'one channel' and then passing stereo data will not convert the stereo data to mono. The encoder encodes whatever it is given... Monty On Tue, Jan 3, 2017 at 6:51 PM, IHARA Hiroka <ihara_h at live.jp> wrote: > Hello Ross, > > The attachment appears at least to me as a valid monaural Vorbis

Conrad Parker wrote: > On Tue, Mar 07, 2006 at 12:10:57PM -0500, Monty wrote: > >>On Wed, Mar 01, 2006 at 10:36:38PM +0000, Ian Malone wrote: >> >>>I assume what this all means is there's no desire for any kind of stop- >>>gap libvorbisfile that does the "vorbis out of any otherwise valid Ogg >>>stream"[1], and that anything along these

Hi. I've put up some docs related to my first encounter with the vorbis source code at http://surf.chimie.uqam.ca/~kruus/vorbis/encoder/index.html It documents a newbie's first look and [serious] attempts to trace through examples/example_encoder.c . Don't laugh too hard! Even though the docs are quite un-doc-like, I've stopped working on them indefinitely, since Monty

Forwarded, so the list knows about it. I'm making the changes now. Monty > Hey Monty, I have a few fixes that need to get made to the CVS tree to > fix a couple of broken things. None are worth sending you a diff. > > vorbisfile.o needs to be removed from the lib/Makefile in LFILES since > vorbisfile.a is a seperate lib now. As it stands I get unresolved > symbol errors