Difference between libvorbis and aoTuVb?, Was: Q:What's 'em different? [TOS #6] |
![]() ![]() |
Difference between libvorbis and aoTuVb?, Was: Q:What's 'em different? [TOS #6] |
Jan 13 2008, 06:09
Post
#1
|
|
|
Group: Members Posts: 50 Joined: 19-November 06 From: China-Asia Member No.: 37789 |
http://www.rarewares.org/ogg-oggenc.php
I see Oggenc2.84 using libVorbis v1.2.0 and Oggenc2.84 using aoTuVb5. what's the different are libvorbis and aoTuVb? -------------------- I like foobar2000 like I luv 2pac.
|
|
|
|
Jan 13 2008, 08:35
Post
#2
|
|
![]() Group: Members Posts: 6 Joined: 16-April 06 From: Austin, Texas Member No.: 29614 |
http://www.rarewares.org/ogg-oggenc.php I see Oggenc2.84 using libVorbis v1.2.0 and Oggenc2.84 using aoTuVb5. what's the different are libvorbis and aoTuVb? libVorbis 1.2.0 is the "official" release from Xiph.org. aoTuVb5 is a modified version which aims to improve performance. Many people here report it produces better results when encoding at low quality settings (q<=1.0). See the wiki: HA Wiki: AoTuV |
|
|
|
Jan 13 2008, 11:16
Post
#3
|
|
![]() Group: Members Posts: 432 Joined: 1-January 07 From: Luebeck, DE Member No.: 39196 |
I wondered about the differences between the two... but never looked myself.
This post has been edited by SamHain86: Jan 14 2008, 15:00 -------------------- OP can't edit initial post when a solution is determined :'-(
|
|
|
|
Jan 14 2008, 10:41
Post
#4
|
|
|
Group: Members Posts: 236 Joined: 14-January 04 From: Kanto, Japan Member No.: 11215 |
I see Oggenc2.84 using libVorbis v1.2.0 and Oggenc2.84 using aoTuVb5. About the aoTuVb5(aoTuV beta5), please look at this page. what's the different are libvorbis and aoTuVb? |
|
|
|
Jan 15 2008, 07:49
Post
#5
|
|
![]() Group: Members Posts: 101 Joined: 16-September 03 Member No.: 8871 |
Excepting Rockbox as an aftermarket upgrade, are there compatibility issues with portable music players (that natively support Vorbis) if using aoTuV builds over "official" Xiph ones? I am not encoding my stuff at the ultra-low rates (usually quality between 4 and 7), anyway.
|
|
|
|
Jan 15 2008, 08:03
Post
#6
|
|
|
Group: Members Posts: 44 Joined: 13-October 06 Member No.: 36310 |
If I am not mistaken, there are no compatibility issues between them.
My Iriver H120 plays AoTuV encoded Vorbis files just fine both with Rockbox and also with the original firmware. (I do not use very low bitrates, either. -q 4,5 and -q 5) |
|
|
|
Jan 23 2008, 22:08
Post
#7
|
|
![]() Group: Members Posts: 83 Joined: 8-April 07 Member No.: 42314 |
I noticed that those wiki's haven't been updated in awhile as they don't include the libVorbis 1.2.0 release.
I may be misinformed, but libVorbis 1.2.0 is now newer then aoTuVb5. While you can download version of oggenc using libVorbis with the aoTuVb5 tunings patched in, which is actually better now, the default tunings(newer) or the aoTuVb5 tunings? Anyone done any tests? |
|
|
|
Jan 24 2008, 11:59
Post
#8
|
|
|
Group: Members Posts: 44 Joined: 13-October 06 Member No.: 36310 |
Since libvorbis 1.2.0 did not contain any quality improvements - see changelog at http://svn.xiph.org/trunk/vorbis/CHANGES - its release did not change the situation regarding which encoder is better (or best). Therefore aoTuV beta 5 is still to be regarded as best (producing the best quality) encoder.
|
|
|
|
Jan 25 2008, 02:23
Post
#9
|
|
![]() Group: Members Posts: 83 Joined: 8-April 07 Member No.: 42314 |
Ah interesting. May they will finally incorporate aoTuV tunings in the next official build. Vorbis development seems to be extremely slow, which could be a sign of stability, or a lack of interested developers. It is too bad, with a more active team it could be alot bigger then it is now. Whereas Lame, on the other hand, seems more active in comparison.
This post has been edited by Useless Warrior: Jan 25 2008, 02:24 |
|
|
|
Jan 27 2008, 17:32
Post
#10
|
|
|
Group: Members Posts: 100 Joined: 6-March 07 Member No.: 41226 |
libVorbis 1.2.0 is the "official" release from Xiph.org. aoTuVb5 is a modified version which aims to improve performance. Quality, not performance. The Lancer builds are performance driven. So: aoTuV = aims at quality, Lancer = aims at speed with possible quality loss. This post has been edited by Nikaki: Jan 27 2008, 17:32 |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 23rd May 2013 - 21:28 |