xiphmont: (Default)
[personal profile] xiphmont

Released last night: libogg 1.2.0, libvorbis 1.3.1, libao 1.0.0, and vorbis-tools 1.4.0.

*whew*

Aside from bugfixes, the major story here is the first wide release of all the surround hacking I've been doing the past two months. Previous demo pages (one and two) had documented my progress till now; there's actually one more coming that I've just started on.

In addition to that, we also tagged on a release of libogg with a new default page spill rule that reduces container overhead for higher bitrate streams like video. The change is simple, but it's a reduction in bitrate for free so why not. Applications don't have to do anything, just drop in the new lib. In addition to demo pages and blogging, I've also begun a comprehensive expansion of the Ogg documentation (the very beginnings of which are in the release-- not much yet).

The releases as usual can be had from the Xiph.Org downloads page.

What about the aoTuV merges?

Date: 2010-03-26 11:31 am (UTC)
From: [identity profile] vinipsmaker.wordpress.com (from livejournal.com)
This release is awesome. Good work xiphmonty, Chuck Norris loses against you. And what about the aoTuV merges?

I read that "The approximate roadmap is: the async error interface just added to libogg will be the next change to libvorbis, and will be the basis of the 1.2.3 release. AoTuV merges are scheduled for immediately after and will form the basis of 1.3.0." at http://www.xiph.org/press/2009/libvorbis-1.2.2/ .

Re: What about the aoTuV merges?

Date: 2010-03-26 09:11 pm (UTC)
From: [identity profile] xiphmont.livejournal.com
RedHat is eager to see Ghost development move forward, at least concurrently with everything else. Our feeling was that the surround work was more directly applicable to Ghost work than an AoTuV tuning merge, so that bumped ahead of AoTuV in the development line.

AoTuV merges take time, they're not simple patch and release situations. I'm guessing a merge is about two full-time weeks minimum, primarity because listening testing is not something that can be sped up by 'working smarter'. Even automated regression testing eats days at a time.

But it is still happening. It just didn't happen in 1.3.0/1

Re: What about the aoTuV merges?

Date: 2010-03-26 10:05 pm (UTC)
From: (Anonymous)
Is Ghost lossy or loseless?

Re: What about the aoTuV merges?

Date: 2010-03-28 05:44 am (UTC)
From: [identity profile] xiphmont.livejournal.com
Right now I intend it to be lossy only. But I'll be playing a bit with lossless during the research.
Edited Date: 2010-03-28 05:46 am (UTC)

Re: What about the aoTuV merges?

Date: 2010-03-28 11:37 pm (UTC)
From: [identity profile] danielhendrycks.myopenid.com (from livejournal.com)
What about making a loseless video codec? (Not a hybrid like Dirac) I thought of FLAV as a name; Free Lossless Agile Video. When my C skills evolve I'd be happy to make one with Xiph but as for right now what are your initial thoughts? (Remember, this would be in the distant future)

Date: 2010-03-26 01:59 pm (UTC)
From: [identity profile] danielhendrycks.myopenid.com (from livejournal.com)
What do you plan on working on next?

Date: 2010-03-26 09:16 pm (UTC)
From: [identity profile] xiphmont.livejournal.com
My development schedule is booked out for the next six months at least. Things subject to change, but...

1) A docuemtnation fest, concentrating on Ogg and Ogg best practices. There's been some amount of outside sniping about the Ogg container by a few folks who haven't honestly spent any time figuring out how the system actually works. The best way to combat that is much better documentation than we have.

2) Resume development of the Ghost sinusoid discriminator-- the one key piece of Ghost tech that doesn't really exist in a servicable form today. Although there are lots of unknowns in 'gluing the pieces togather', all other aspects of the Ghost design could be made of off-the-shelf techniques if need be. The discriminator that I need has not ever been made practically fast enough. So I'll be working on that.

3) AoTuV merge; this *is* useful to the Ghost work because Aoyumi's work explores parts of the solution space I never had time to look at. Although Ghost and Vorbis don't really share much in the way of high level design, AoTuV still counts as basic informative research that could prove illuminating.

Date: 2010-03-27 01:50 am (UTC)
From: (Anonymous)
Does Aoyumi work with the Xiph team at all, or is his work completely independent of Xiph?

Date: 2010-03-28 05:45 am (UTC)
From: [identity profile] xiphmont.livejournal.com
I asked several years ago, and Aoyumi said at the time that he wanted to remain completely independent.

Date: 2010-03-26 08:28 pm (UTC)
From: (Anonymous)
New releases, Woohoo!!

Profile

xiphmont: (Default)
xiphmont

Most Popular Tags