Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Ogg Vorbis 1.1 Public Release Candidate 1 is ready (Read 17057 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

EDIT: I want to change the topic title to "Ogg Vorbis 1.1 Public Release Candidate 1 is ready!" since Monty have just tagged this release with "libvorbis 1.1 public release candidate 1".
Quote
r7047 | xiphmont | 2004-07-08 13:07:11 +0900 (Thu, 08 Jul 2004)

Tag 1.1 libvorbis release candidate 1; pending any last minute bugfixes;
this will be 1.1


I made a win32 binary of OggEnc (1.1rc1; MSVC2003) and Ogg Vorbis DLLs (1.1rc1; MSVC2003) for the memorial. Let's try and evaluate it for the upcoming stable release.
EDIT: Link changed.

Monty merged the mainline (trunk) of the svn repository in xiph.org with aoTuV tunings. Official Vorbis encoder with aoTuV tuning is now ready for testing according to Monty's svn log message:
Quote
r7037 | xiphmont | 2004-07-08 00:44:46 +0900 (Thu, 08 Jul 2004)

Put AoTuV tunings merge (along with bugfixes) on the mainline.  This
is ready for wider correctness testing; no substantial issues
expected.

"POST CVS" now represents aoTuV!  How wonderful!

EDIT: Deleted the link to the previous binary.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #1 –
Quote
Monty merged the mainline (trunk) of the svn repository in xiph.org with aoTuV tunings. Official Vorbis encoder with aoTuV tuning is now ready for testing according to Monty's svn log message:
Quote
r7037 | xiphmont | 2004-07-08 00:44:46 +0900 (Thu, 08 Jul 2004)

Put AoTuV tunings merge (along with bugfixes) on the mainline.  This
is ready for wider correctness testing; no substantial issues
expected.

"POST CVS" now represents aoTuV!  How wonderful!

I made a win32 binary of OggEnc (20040708 r7037; MSVC2003) for test purpose. Let's try and evaluate it for the upcoming release. 

So I gather it works on the quality modes, but not the bitrate managed modes?  Comparisons should be against aoTuV beta 2?

ff123

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #2 –
Quote
So I gather it works on the quality modes, but not the bitrate managed modes?  Comparisons should be against aoTuV beta 2?

The following log message says it's OK to use this development build with bitrate management.
Quote
r7031 | xiphmont | 2004-07-07 14:54:10 +0900 (Wed, 07 Jul 2004)

Merge and basic testing complete; AoTuV tunings fully active with
noew books, bitrate management fixed.

Thusfar, tests confirm the AoTuV tunings (along with a few quich
changes I've made apart fro AoTuV) is indeed considerably superior to
current mainline.  Merge with mainline will happen soon.

IMHO it's enough to check if there are big regressions from aoTuV beta2 or not. But comparisons with previous CVS version and MegaMix are also interesting for me. 

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #3 –
great!

1) does it offer channel coupling (for multichannel) too already?
edit: doesnt seem so

2) does the new New bitrate management code change vorbis' behaviour regarding the usage of variable number of samples/variable duration per frame?
I know, that I know nothing (Socrates)

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #4 –
Considering how well the aotuv tuned vorbis did in Roberto's test, this just seemed inevitable.  Bravo!


Any pre-echo tunings in thisnew vorbis?

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #6 –
Quote
Quote
I made a win32 binary of OggEnc (1.1rc1; MSVC2003)

Corrupted zip?
[{POST_SNAPBACK}][/a]

Ohhh! These files are broken after I download them with IE. (no problem with FireFox).    I don't know why this happens (maybe server problem). I uploaded these files in another web space:
[a href="http://homepage3.nifty.com/nyaochi/soft/dist/oggenc_1.1rc1.zip]OggEnc 1.1 RC1 (MSVC2003)[/url]
Vorbis DLLs 1.1 RC1

Sorry for the truble.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #7 –
Anyone have a fast ICL compile?

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #8 –
Quote
Anyone have a fast ICL compile?
[{POST_SNAPBACK}][/a]


Guess [a href="http://www.rarewares.org/ogg.html]where[/url]

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #9 –
Do you become connection at rarewares?
I'm not. 

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #10 –
Works fine here...

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #11 –
Quote
Quote
Anyone have a fast ICL compile?
[{POST_SNAPBACK}][/a]


Guess [a href="http://www.rarewares.org/ogg.html]where[/url]
[a href="index.php?act=findpost&pid=224179"][{POST_SNAPBACK}][/a]



Thanks Roberto.

I have to admit that there are so many different builds/variations of Ogg Vorbis that one must read through the page carefully.  It is a good thing it did not have teeth, because it might have bit me.

Perhaps a few will drop off the list when 1.1 goes stable.

It is this kind of cutting edge stuff that keeps me interested in HA.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #12 –
Quote
Thanks Roberto.

I have to admit that there are so many different builds/variations of Ogg Vorbis that one must read through the page carefully.  It is a good thing it did not have teeth, because it might have bit me.

Perhaps a few will drop off the list when 1.1 goes stable.

It is this kind of cutting edge stuff that keeps me interested in HA.
[a href="index.php?act=findpost&pid=224400"][{POST_SNAPBACK}][/a]


Oh definitely.  When 1.1 goes stable, then we won't need all these diferent variations.  If listening tests reveal at least no regression from aoTuV beta 2, then 1.1 will be the recommended encoder.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #13 –
Yeah that would be a good thing as I remember when I started I had no idea which encoder to use so I just picked up the official release not realising at the time that GT3b2 was better for -q6.  So it will be a good thing for those new people feeling adventurous and trying Vorbis for the first time.

I'm looking forward to 1.1 but for now I'm enjoying Megamix.  I honestly wasn't expecting that quick little merge to turn out so well.
Nero AAC 1.5.1.0: -q0.45

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #14 –
Quote
Quote

Thanks Roberto.

I have to admit that there are so many different builds/variations of Ogg Vorbis that one must read through the page carefully.  It is a good thing it did not have teeth, because it might have bit me.

Perhaps a few will drop off the list when 1.1 goes stable.

It is this kind of cutting edge stuff that keeps me interested in HA.
[a href="index.php?act=findpost&pid=224400"][{POST_SNAPBACK}][/a]


Oh definitely.  When 1.1 goes stable, then we won't need all these diferent variations.  If listening tests reveal at least no regression from aoTuV beta 2, then 1.1 will be the recommended encoder.
[a href="index.php?act=findpost&pid=224531"][{POST_SNAPBACK}][/a]


Why? It still lacks the pre-echo tuning that Garf and yourself did such a good job with. Shouldn't the recommended encoder be the one with the best quality? From the reports I have seen, the Megamix version has set a new standard in terms of being the best for the majority of -q settings.
flac > schiit modi > schiit magni > hd650

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #15 –
Small note that I've noticed that 1.1 RC1 files are slightly smaller than Megamix files at -q6, but at around 5-10kbps I'm not wanting to give up Megamix and all of the good preecho tunings.  It doesn't bother me that the bitrate spikes up to over 400kbps on the clapping at the beginning of Nirvana's Unplugged in New York and 1.1 RC1 only spikes to 350 or so 

About A Girl, the first track on that album had an average of 226 and RC1 had 207.  I guess it's just because Megamix is more aggressive due to the GT3b2 and QKTUne3.2 tunings in it.
Nero AAC 1.5.1.0: -q0.45

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #16 –
i think a better comment would be that the DIVIDE between the reference ogg vorbis codebase and needed improvements is drastically reduced.

3rd party advocates/testing/forks/improvements will always be welcome and needed for vorbis to improve...

the benefits will just be less evident now that the vanilla sources are actually of good quality (assuming the merge went well...)


later

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #17 –
Quote
(assuming the merge went well...)[a href="index.php?act=findpost&pid=224572"][{POST_SNAPBACK}][/a]

Speaking of which, ABX results, anyone?

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #18 –
Quote
Why? It still lacks the pre-echo tuning that Garf and yourself did such a good job with. Shouldn't the recommended encoder be the one with the best quality? From the reports I have seen, the Megamix version has set a new standard in terms of being the best for the majority of -q settings.
[a href="index.php?act=findpost&pid=224542"][{POST_SNAPBACK}][/a]


Oh, it just doesn't sit well with me that the merge was done blindly.  Plus, I'd like to see better ways of reducing pre-echo than to throw so many bits at it.

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #19 –
Quote
Why? It still lacks the pre-echo tuning that Garf and yourself did such a good job with. Shouldn't the recommended encoder be the one with the best quality? From the reports I have seen, the Megamix version has set a new standard in terms of being the best for the majority of -q settings.
[a href="index.php?act=findpost&pid=224542"][{POST_SNAPBACK}][/a]


Do we actually know if Monty hasn't done any tunings himself to this version?
 

Ogg Vorbis 1.1 Public Release Candidate 1 is ready

Reply #20 –
Quote
Quote
Why? It still lacks the pre-echo tuning that Garf and yourself did such a good job with. Shouldn't the recommended encoder be the one with the best quality? From the reports I have seen, the Megamix version has set a new standard in terms of being the best for the majority of -q settings.
[{POST_SNAPBACK}][/a]


Do we actually know if Monty hasn't done any tunings himself to this version?
[a href="index.php?act=findpost&pid=224938"][{POST_SNAPBACK}][/a]


I ask too! IMHO he makes only "bugfixes".

And somebody could update [a href="http://vorbis.com/news.psp]http://vorbis.com/news.psp[/url] !!!