similar to: Merge of current Monty branch

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hi folks, My wife and I are taking a long weekend to celibrate our anniversary. I won't be around again until Wednesday to answer email or do anything else on Vorbis. Yeah, I know, I usually answer my email once a month anyway (so likely no one would notice me being gone), but just so folks know if anything really juicy comes up :-) I'll be merging my latest branch with mainline

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

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,

Hello! I tested some songs with the new code that Monty merged into the snapshot. It works better than the previous code ;-), but I noticed some strange noises made at high frequencies, even at very high bitrates : a continuous, high-pitched noise is added over the medium voice, and it sounds like a whistle. The previous code didn't do that. On the other hand, very low bitrates sound much

Nothing on a branch yet; I'll be building a temp branch for my changes soon. First, I'm eliminating ordering dependancies in vorbis_block structures. They'll be totally sepreate and vorbis_analysis won't have a global state in vorbis_dsp_state that requires them being done in order. That way, a parallel-threaded encoder can run multiple vorbis_blocks through multiple

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

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, 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

I just finished the merge of branch_jackoggsvorbis into branch_postbeta2 Vorbis is now split into two libs, libogg, and libvorbis in this branch. the follow modules are a result: ogg - basic framing library, all ogg code and docs, etc vorbis - the vorbis codec, depends on ogg vorbis-plugins - all the audio plugins for ogg vorbis, depends on ogg and vorbis ao - libao a cross platform audio

Go monty! jack. ----- To: cvs@xiph.org Subject: [xiph-cvs] cvs commit: vorbis/vq huffbuild.c latticetune.c make_residue_books.pl Date: Sun, 3 Jun 2001 22:50:13 -0700 (PDT) From: xiphmont@xiph.org (Monty) Precedence: bulk Reply-To: cvs@xiph.org xiphmont 01/06/03 22:50:12 Modified: lib codebook.c codebook.h floor0.c mapping0.c os.h res0.c vq

I would very much like a lowpass option because for FM radio broadcasting I don't want to encode frequencies above 15khz. I'm waiting for this option before switching to ogg from mp3(lame). Ross. > -----Original Message----- > From: owner-vorbis@xiph.org [mailto:owner-vorbis@xiph.org]On Behalf Of > Gian-Carlo Pascutto > Sent: Tuesday, 4 September 2001 01:46 > To:

I don't know enough to tell if this is pilot error on the user's part or a legit problem. Advice requested (also Cc: the original user if you can). ----- Forwarded message from Bryan Kennedy <bryandanielkennedy@hotmail.com> ----- Delivery-Date: Mon Feb 26 22:07:54 2001 From: "Bryan Kennedy" <bryandanielkennedy@hotmail.com> To: "Monty"

Hello, I've been postponing some of my encoding for when joint stereo gets implemented. The reason I've been doing this, is that I am under the impression this is the largest step in the quality/bitrate ratio that's left. Now I'm wondering if I am correct in thinking this. lame's documentation seems to imply it doesn't make much of a difference at higher than 128kbps (I