similar to: (no subject)

> 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

Torsdag, 10 oktober 2002, skrev du: >On the other hand, it's certainly possible that the published >specification contains errors that need to be addressed. It is not a >monolithic document written in stone. The only way we'll really be able >to sort those issues out is when people try to build stuff from scratch >using the published data, and come across discrepancies.

Hi everybody: It's time for another weekly update from the Xiph.org team. The plain text version is below, and the HTML version will appear on vorbis.com later today. Enjoy! <p>Ogg Traffic for Tuesday, March 18, 2003 [1]Carsten "Purple" Haese March 18, 2003 _________________________________________________________________ Table of Contents 1. Editorial

Hi everybody: Here is the latest edition of Ogg Traffic. The HTML version is at http://www.vorbis.com/ot/20030429.html Enjoy! -Carsten <p>Ogg Traffic for Tuesday, April 29, 2003 [1]Carsten "Purple" Haese April 29, 2003 _________________________________________________________________ Table of Contents 1. Status Updates 1.1. Monty 1.2. Stan

Josh Coalson <xflac@yahoo.com> wrote: > That is the question I put before you all tonight :) > > (Short background, Xiph is the corp behind Vorbis and Ogg, > among other things; see http://xiph.org/about.html . I > think Emmett is here now so correct any of this if it's > wrong.) > > I've been talking a little with Emmett Plant and Monty about > this.

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

That is the question I put before you all tonight :) (Short background, Xiph is the corp behind Vorbis and Ogg, among other things; see http://xiph.org/about.html . I think Emmett is here now so correct any of this if it's wrong.) I've been talking a little with Emmett Plant and Monty about this. If it were to happen, it would mean the following: 1. FLAC would benefit from the

My understanding -- Monty or Emmett, feel free to chime in if you think this is incorrect -- is as follows: www.theora.org is the home for all new releases of the Theora video codec (formally known as VP3). This includes the main OGG/Vorbis integration product, which Monty is working on personally, as well as the QT and Windows codecs, both legacy VP3 versions and new versions reflecting any

Whatever became of Ogg Theora? There seems to be still almost no news from Xiph or its developers regarding Ogg Theora. None at all since Mid-December, when the release of Alpha 2 was pushed back to a month ago... No news on plans for the second Alpha? No news of development "roadmaps"? No news on current developments or challenges that are stalling development? No CVS updates

Hi Ralph and libvorbis developers, I thought the vorbis gitlab project was the main development site (https://gitlab.xiph.org/xiph/vorbis) because that's what the NVD CVE tracker points to for the two CVEs I mentioned. But I just realized there's also a vorbis github project (https://github.com/xiph/vorbis). Both appear to have recent activity. Is the gitlab project the correct one

[Cc: changed to vorbis-dev] On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On Fri, Apr 11, 2008 at 10:11 PM, Conrad Parker <conrad at metadecks.org> wrote: > > No, vorbiscomments are meant to be human-readable. > > > But I CAN read base64! :-) > It's a win-win situation, with the added bonus that it wouldn't > require

Ok, I wasn't able to track down the original steps to reproduce this issue,s but we believe CVE-2018-10393 is a dupiicate of CVE-2017-14160, both fixed by commit 018ca26dece6. Because of the confusion, I added additional bounds checks to the bark_noise_hybridmp function, which make it clear to local analysis that no for bugs in this class are possible. This change is in commit a9eb99a5bd6f.

> On Fri, Jan 26, 2001 at 05:49:08PM -0800, Monty wrote: > > Do you still have this problem using decoder_example, > > vorbisfile_example or XMMS? > > decoder_example shows the same problem, after playing around for > a while, I'm convinced that the problem is in libvorbis somewhere. This would indeed place the problem in libvorbis. > As you can see, the dump is

Yes, the gitlab instance is the correct upstream development repository. We maintain a mirror at github for the convenience of developers there. Cheers, Ralph On Mon, 2020-06-29 at 21:27 +0000, Ellen Johnson wrote: > Hi Ralph and libvorbis developers, > I thought the vorbis gitlab project was the main development site ( > https://gitlab.xiph.org/xiph/vorbis) because that's what

I've decided it's probably a good idea to wrap up the 'chaining_example.c' functionality into a library interface as the functionality inside is going to be commonly useful enough. It would be silly for everyone who wants to do trivial things to have to reproduce it unless they really want to. It's not going to be as 'carved in stone' as the libvorbis interface.

Chris, re the DLL additions: In a word, *no*. That much Win32 specific code does not belong in a lib that's pure math and totally platform agnostic. It may be appropriate, assuming it's necessary, to add this in the win32 specific SDKs, but it has no business in the core libvorbis. Please move it out to a more appropriate place as soon as you possibly can. Secondly: I'd like to

I wasn't sure where else to ask, so I'm asking here. I was banned from #vorbis for 24 hours supposedly for "trolling," about three weeks ago, by Emmett. I guess he got removed from the team soon after, because I'm still banned. I seemed to be Emmett's favorite person to pick on. He told me to "eat a bag of dick" in his Ogg internet radio station thing, and

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