Old 8th July 2004, 14:05   #1
gaekwad2
Foorum King
 
gaekwad2's Avatar
 
Join Date: Jul 2003
Location: bar2000
Posts: 11,423
Vorbis 1.1 RC1

Quote:
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 detail:

1) Adoption of AoTuV tunings

The AoTuV encoder substantially improves the basic tunings of the
1.0.1 encoder for 32,44.1 and 48 kbps input samples. This 1.1 release
merges the AoTuV tunings into the mainline Xiph codebase along with
other tuning tweaks. The AoTuV tunings are unchanged from the AoTuV
encoder with the following exceptions:

a) bugfix to AoTuV code section 'M1'; after discussion with Aoyumi,
we agree that the second tuning case both triggered relatively
seldomly and did not produce the intended results when it did trigger.
The predominating first case ('partial masking') is now used for all
samples. This should address some minor pure tone instability issues
in the AoTuV encoder.

b) Changes to book construction, training, and on-the-fly adjustment
to allow the AoTuV tunings to work properly with bitrate management.

c) AoTuV introduced quality ranges down to -2; the 1.1 Xiph
libvorbisenc implements the same modes but maps them down to -1 as in
previous Xiph releases. The bitrate of quality -1 in 1.1 is similar
to quality -1 in 1.0.1 but the quality of the output is improved.

2) New bitrate management code

After use case analysis, I concluded that the 'sliding window'
approach to bitrate bounding and management in previous encoders was
not usefully more featureful than the more standard 'bit reservoir'
approach used in the rest of the industry. In addition, the bit
reservoir approach uses substantially less memory in the encoder. For
these reasons, the 1.1 libvorbisenc moves to implementing bitrate bounding
and management by using a bit reservoir.

The bit reservoir is also conceptually easier to understand; the
encoder has a fixed bucket size for 'slop space' in encoding. When a
frame is smaller than the desired rate, the unused bits go into the
reservoir so that they may be used by future frames. When a frame is
larger than target bitrate, it draws 'banked' bits out of the
reservoir. Encoding is managed so that the reservoir never goes
negative or fills beyond a fixed limit.

The 1.1 libvorbisenc allows setting the fixed reservoir size (in bits,
defaulting to two seconds worth of requested bitrate) and 'hoarding'
behavior (whether the encoder tends to keep the bit reservoir more
full or more empty) as well as the other encoding heuristics available
through the API of 1.0.1.

3) bugfixes

See SVN for a more details; I'll collect a list for the full release.

There are vorbisenc API additions to handle the new bit reservoir
configuration; I will describe those in more detail tomorrow. The
binary API is undisturbed; deprecated calls are are all mapped to the
new infrastructure. I *believe* oggenc is already updated to the new
API.

Have at, have fun, report bugs.

Monty
Discussion and links to binaries here.
gaekwad2 is offline   Reply With Quote
Old 8th July 2004, 15:59   #2
Rocker
Hiding in plain sight (mod)
 
Join Date: Jun 2000
Location: Melbourne, Australia
Posts: 9,907
great news
Rocker is offline   Reply With Quote
Old 9th July 2004, 12:30   #3
ilikedirtthe2nd
Junior Member
 
Join Date: Feb 2001
Posts: 28
icl binaries for rc1 are available here:

http://rarewares.org/ogg.html
ilikedirtthe2nd is offline   Reply With Quote
Old 11th July 2004, 15:53   #4
STanger
Senior Member
 
STanger's Avatar
 
Join Date: Jun 2004
Location: Memphis TN
Posts: 399
Send a message via AIM to STanger Send a message via Yahoo to STanger
no Wa5 encoding/ripping plugin based from 1.1rc1? or do those usually surface after 1.1 goes gold?
STanger is offline   Reply With Quote
Old 11th July 2004, 16:28   #5
gaekwad2
Foorum King
 
gaekwad2's Avatar
 
Join Date: Jul 2003
Location: bar2000
Posts: 11,423
I don't think there's an API available for 3rd party enc plugin developers, so it all depends on someone from Nullsoft updating their unofficial vorbis encoder (which is still based on 1.0.0).
gaekwad2 is offline   Reply With Quote
Old 11th July 2004, 17:09   #6
STanger
Senior Member
 
STanger's Avatar
 
Join Date: Jun 2004
Location: Memphis TN
Posts: 399
Send a message via AIM to STanger Send a message via Yahoo to STanger
45kbps

I had to use CDex with the Vorbis 1.1 RC1 ..since there isn't a enocding plugin available yet but even at -1.00 (45kbps avg) quality setting it still sounds really really really good imho

D

STanger is offline   Reply With Quote
Old 11th July 2004, 17:11   #7
STanger
Senior Member
 
STanger's Avatar
 
Join Date: Jun 2004
Location: Memphis TN
Posts: 399
Send a message via AIM to STanger Send a message via Yahoo to STanger
ogg vorbis 1.1 rc1 in wa5 ML

http://www.nunzioweb.com/daz/temp/st..._ogg1.1RC1.JPG
hope this works

just wanted to show the relation b/t filesize and bitrate at -1.00 (45kbps avg)..

Last edited by STanger; 11th July 2004 at 17:40.
STanger is offline   Reply With Quote
Old 11th July 2004, 20:44   #8
lostonline
Where am I?
(Major Dude)
 
lostonline's Avatar
 
Join Date: Feb 2004
Location: Yorkshire, UK
Posts: 680
That's good, I might do a couple of encodes with it and do some listening tests but I won't use a RC for archive encodes.

Kids, you tried your best and you failed miserably. The lesson is, never try.
--
Homer Simpson
lostonline is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Community Center > Breaking News

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump