nostromo
Nov 5 2005, 04:55
There is a new aoTuv beta release(4.5) out.
Changelog:
QUOTE
aoTuV Beta4.5 [beta4 >> beta4.5]
# Reexamination of a low bit rate region, the addition of the code accompanying it, and tuning. Influence has this change below quality3. Probably, in the especially low bit rate, it will be effective.
http://www.geocities.jp/aoyoume/aotuv/index.html
Let's call together: Gu-ru-boo-lez!!!
rjamorim
Nov 5 2005, 05:24
QUOTE(de Mon @ Nov 5 2005, 09:09 AM)
Let's call together: Gu-ru-boo-lez!!!

Erm.. as if Guru had big interest in low bitrate testing
Gabriel
Nov 5 2005, 05:24
QUOTE
Let's call together: Gu-ru-boo-lez!!!
Come on people! This is low bitrates area, you could test it yourself...
manuelator
Nov 5 2005, 05:59
Thanks, i tried it...but sounds like metallic, the switch used is:
"-q-2" the nominal bitrate whas 32.
Any vorbis can encode at 20-25? (at 44 and stereo)
QUOTE(manuelator @ Nov 5 2005, 03:59 AM)
Thanks, i tried it...but sounds like metallic, the switch used is:
"-q-2" the nominal bitrate whas 32.
Any vorbis can encode at 20-25? (at 44 and stereo)
Did you compare it to aoTuV b4?
Is the encoding at high quality affected by this? I encoded a file at -q6 with both b4 and b4.5 and decoded again (with the same decoder), and the content of the decoded files differs (as shown by a quick md5 hashing).
MedO
QUOTE(MedO @ Nov 5 2005, 05:29 AM)
Is the encoding at high quality affected by this? I encoded a file at -q6 with both b4 and b4.5 and decoded again (with the same decoder), and the content of the decoded files differs (as shown by a quick md5 hashing).
MedO
Can you find out 'audio difference' between them in some audio editor? How much differs the size of encoded files?
Sebastian Mares
Nov 5 2005, 08:27
QUOTE(de Mon @ Nov 5 2005, 01:09 PM)
Let's call together: Gu-ru-boo-lez!!!

He's already busy with Nero AAC.
madoka@ex-sounds
Nov 5 2005, 09:21
wow, nice works
kotrtim
Nov 5 2005, 10:02
QUOTE
Is the encoding at high quality affected by this? I encoded a file at -q6 with both b4 and b4.5 and decoded again (with the same decoder), and the content of the decoded files differs (as shown by a quick md5 hashing).
I've tried -q 4 , they can be considered bit identical
Beta4 = 3,489,542 bytes
Beta4.5 = 3,489,535 bytes
-q 2
Beta4 = 2,768,456 bytes
Beta4.5 = 2,805,795 bytes
The slight difference in -q4 might be bacause of the beta4 I used is P4 optimised, Optimised version might produce a file that has slight differences from non-optimised version.....this causes discrepencies in MD5, but it terms of perception quality, it is the same.
Lets wait a bit, maybe
Aoyumi will give some explanations about this version and what we should expect from it. If it is OK, it would be wonderful if
john33 compiles an OggDropXPd with this thingy inside. Is it possible, John ?
Saoshyant
Nov 5 2005, 10:26
I will be testing this new release as well. I have high expectations about it, but aside the tuning at very low bitrates I don't suppose it's a major release, probably why it's numbered 4.5 and not 5.0

Aoyumi-san domo arigato
Ah, I wonder if one day you will try making the first known implementation of Bitrate Peeling. I know I would be happy about just better tuning at the higher bitrates, so that Vorbis could finally beat Musepack.
Squeller
Nov 5 2005, 10:39
I use -q-2 sometimes on classical stuff for some reason. I have a symphony of 63 Minutes, which encodes @ 13.960.454 Bytes. With 32 kbps it does sound incredible!
Now I encoded it again with ao4.5.
I could not hear any differences/improvements at the problematic parts.
BUT theres a significant improvement in size:
aotuv4: 13.960.454 Bytes
aotuv4.5: 13.080.681 Bytes
Rotareneg
Nov 5 2005, 11:48
Cool, I'll give this a try this evening since I use Vorbis at -q2.25 on my iFP-895 (with a hacked firmware to play Vorbis files that average less than 96 kbs.)
Benjamin Lebsanft
Nov 5 2005, 12:56
QUOTE(Rotareneg @ Nov 5 2005, 06:48 PM)
Cool, I'll give this a try this evening since I use Vorbis at -q2.25 on my iFP-895 (with a hacked firmware to play Vorbis files that average less than 96 kbs.)
Where can we find the firmware ?
Rotareneg
Nov 5 2005, 14:35
QUOTE(Benjamin Lebsanft @ Nov 5 2005, 12:56 PM)
QUOTE(Rotareneg @ Nov 5 2005, 06:48 PM)
Cool, I'll give this a try this evening since I use Vorbis at -q2.25 on my iFP-895 (with a hacked firmware to play Vorbis files that average less than 96 kbs.)
Where can we find the firmware ?
http://www.misticriver.net/showthread.php?t=24020
QUOTE
Any vorbis can encode at 20-25? (at 44 and stereo)
For the moment, it is impossible.
QUOTE
Lets wait a bit, maybe Aoyumi will give some explanations about this version and what we should expect from it.
Please hear and judge in person.
I downloaded this and compiled it. After unpacking the .tar.gz I had to do chmod +x on the configure and install-sh scripts before building and installing it. Other than that, no problems.
I encoded a few files and in general they are free of artifacts, except one: The encoder seems to have a strong preference for removing high frequencies at low quality settings. The encoded files sound as if they were downsampled or a low-pass filter was used. This effect diminishes with higher quality settings, and above -q7 I can't tell the difference anymore. At lower settings I can distinguish the vorbis file from the original because of the relatively increased bass and decreased treble.
I am just curious if this was intentional in the design of the encoder? I do think it is less annoying than other types of artifacts, so maybe it's not such a bad trade-off.
I canīt really hear the diference, is hard to say that is a big improvement, ok I only made one test (at -q 0), so I canīt really say that is not effective and I donīt have a "extreme hear" so it just only my opinion.
QUOTE(Leo 69 @ Nov 5 2005, 04:10 PM)
Lets wait a bit, maybe
Aoyumi will give some explanations about this version and what we should expect from it. If it is OK, it would be wonderful if
john33 compiles an OggDropXPd with this thingy inside. Is it possible, John ?

Yes, it's possible now I have the source, which wasn't available when I first looked.
Extract from one of the text files included:
QUOTE
aoTuV beta4.5 technical information
The differences from the aoTuV beta 4...
1. M4 code of beta3 was deleted. M5 is added as what is replaced with it. The advantage of this method is that the result stabilized more is obtained. Instead, the change width of the bit rate becomes large rather than before. [32/44.1/48kHz only]
2. New M4 was added. There is this for the same purpose as M1. However, it is tuned up only in the low bit rate region according to work and individual parameters. [32/44.1/48kHz only]
3. M2 code was extended. This decreases a specific noise problem. [32/44.1/48kHz only]
...and I mainly tune up tone/noise masking and noise normalization parameters.
The above change is applied below quality3.
2005/11/05
Aoyumi
----------------------------------------------------------------------------
QUOTE(Nayru @ Nov 6 2005, 06:45 AM)
I downloaded this and compiled it. After unpacking the .tar.gz I had to do chmod +x on the configure and install-sh scripts before building and installing it. Other than that, no problems.
Hi, n00b here. Downloaded, chmod'ed, configured & compiled... no errors.
But where is the executable ? Or do I miss something here ?
EDIT: Yes I did
It was libvorbis source. Oggenc source downloadpage gives me Error 404.
QUOTE(suur13 @ Nov 6 2005, 05:16 AM)
EDIT: Yes I did <_<
It was libvorbis source. Oggenc source downloadpage gives me Error 404.
Here is what I did:
Download libogg-1.1.2.tar.gz and vorbis-tools-1.1.1.tar.gz from
http://www.xiph.org/downloads/Download libvorbis-aotuv_b4.5.tar.gz.tgz from
http://www.geocities.jp/aoyoume/aotuv/Unpack everything.
cd libogg-1.1.2
./configure
make
make install
cd ../aotuv-b4.5_20051105
chmod +x configure
chmod +x install-sh
./configure
make
make install
cd ../vorbis-tools-1.1.1
./configure
make
Run oggenc/oggenc
QUOTE(jorsol @ Nov 5 2005, 10:46 PM)
I canīt really hear the diference, is hard to say that is a big improvement, ok I only made one test (at -q 0), so I canīt really say that is not effective and I donīt have a "extreme hear" so it just only my opinion.
Which file was bigger? aoTuV b4 or aoTuV 4.5? May be this improvment affects size while keeping quality same?
By the way, did you use one of the famous 'hard samples' or any randomly chosen 'easy sample'?
QUOTE(Aoyumi @ Nov 5 2005, 08:51 PM)
QUOTE
Any vorbis can encode at 20-25? (at 44 and stereo)
For the moment, it is impossible.
I know this is not reccomended, but with oggdropXPd (and I think also with other programs) is possible to go down to 12 Kbps @ 44.1 KHz stereo using ABR with:
Min. Bitrate = 0
Nom. Bitrate = 12
Max. Bitrate = 0
I think Min. Bitrate and Max. Bitrate = 0 means there is no limit, thus give a higer quality than CBR @ 12 Kbps.
QUOTE(fpi @ Nov 6 2005, 08:57 AM)
QUOTE(Aoyumi @ Nov 5 2005, 08:51 PM)
QUOTE
Any vorbis can encode at 20-25? (at 44 and stereo)
For the moment, it is impossible.
I know this is not reccomended, but with oggdropXPd (and I think also with other programs) is possible to go down to 12 Kbps @ 44.1 KHz stereo using ABR with:
Min. Bitrate = 0
Nom. Bitrate = 12
Max. Bitrate = 0
I think Min. Bitrate and Max. Bitrate = 0 means there is no limit, thus give a higer quality than CBR @ 12 Kbps.
Sorry, I just found that ABR @ 12 Kbps with oggdropXPd is automatically resampled to 8 KHz, while ABR @ 32 Kbps is resampled to 24 KHz.
QUOTE(Leo 69 @ Nov 5 2005, 04:10 PM)
Lets wait a bit, maybe
Aoyumi will give some explanations about this version and what we should expect from it. If it is OK, it would be wonderful if
john33 compiles an OggDropXPd with this thingy inside. Is it possible, John ?

Generic, P3 and P4 compiles of oggdropXPd now at Rarewares.
kurtnoise
Nov 6 2005, 13:09
Thanks John...
Could you update also libvorbis.dll with this new Aoyumi stuff ?
QUOTE(kurtnoise @ Nov 6 2005, 07:09 PM)
Thanks John...
Could you update also libvorbis.dll with this new Aoyumi stuff ?
Surely, but do people want the full range of compiles, or is this considered somewhat experimental at this stage?
Mo0zOoH
Nov 6 2005, 14:12
I didn't test it thoroughly, but it seems to me that the most important point was to increase the effectiveness of encoder by making same samples sound the same at lower bitrate. For example, I cannot distinguish one sample @ -q2 from another, but the one created with b4.5 is smaller. That's all I can say for now.
I really think that we must gather and do a couple of short tests just to show that b4.5 is better than 1.1, and then make it the recommended version. Aoyumi's work deserves it.
QUOTE(de Mon @ Nov 6 2005, 07:43 AM)
QUOTE(jorsol @ Nov 5 2005, 10:46 PM)
I canīt really hear the diference, is hard to say that is a big improvment, ok I only made one test (at -q 0), so I canīt really say that is not effective and I donīt have a "extreme hear" so it just only my opinion.
Which file was bigger? aoTuV b4 or aoTuV 4.5? May be this improvment affects size while keeping quality same?
By the way, did you use one of the famous 'hard samples' or any randomly chosen 'easy sample'?
Ok, the file created by 4.5 is smaller by a few kbytes, probably this is the improvment, same quality in smaller size... and not is not one of the famous hard samples, is a sample that I choose and probably an easy one...
Anyway great job Aoyumi, all Vorbis fans apreciate your hard work, I imagine that if wasnīt for you, we are still using the 1.0.1 version (or probablily 1.0.2

) I think that the Xiph boys are busy in other things... like Theora...
Tried it on two samples - harpsicord and Prodigy "You'll Be Under My Wheels" (both of them require high bitrates with b4 q6. 1st one q6 average is 237 and second q6 average bitrate is 300!)
I tested them on -q -2, q 0, -q 1. b4 vs b4.5. I can't say I found out any difference. May be, JUST MAY BE, b 4.5 preserves high frequencies better but I can't be sure.
Also I tested each version against original file on -q 0 and -q 1. And it was slightly more difficult to ABX between b4.5 and original than b4 and original due mentioned possible better high freq preservation.
P. S. Harpsicord sample is not the sample others use. It is just from my collection.
QUOTE(de Mon @ Nov 7 2005, 12:04 AM)
And it was slightly more difficult to ABX between b4.5 and original than b4 and original due mentioned possible better high freq preservation.
I tried to ABX b4 to original and b4.5 to original in a pop sample at -q0, and I think it was harder with b4.5 when concentrating on the distortions in the main voice only. However, it was still easy when listening for a different artifact (close-to-noise parts of the sound being replaced by real noise... don't know if that makes any sense to you, I just don't know the right terminology) that is present in both.
MedO
QUOTE(MedO @ Nov 7 2005, 01:42 AM)
I tried to ABX b4 to original and b4.5 to original in a pop sample at -q0, and I think it was harder with b4.5 when concentrating on the distortions in the main voice only.
MedO
Just a quick question here: after comparing b4 to the original and b4.5 to the original but not b4 to b4.5, is it really correct to draw any conclusions about the quality improvements from b4 to b4.5? I would call the method above a sighted test, and would only use that when the differences are very obvious... Were there obvious differences in your files between b4 and b4.5?
QUOTE(ErikS @ Nov 6 2005, 04:11 PM)
QUOTE(MedO @ Nov 7 2005, 01:42 AM)
I tried to ABX b4 to original and b4.5 to original in a pop sample at -q0, and I think it was harder with b4.5 when concentrating on the distortions in the main voice only.
MedO
Just a quick question here: after comparing b4 to the original and b4.5 to the original but not b4 to b4.5, is it really correct to draw any conclusions about the quality improvements from b4 to b4.5? I would call the method above a sighted test, and would only use that when the differences are very obvious... Were there obvious differences in your files between b4 and b4.5?
In my test the difference was subtle. I think if we want reliable test, a listener first has to find such -q meaning (with potentially weaker encoder version) at which ABXing becomes VERY DIFFICULT. Then use the new version and encode a file which is about the same size as 1st encoding. If there are any improvements - the second encoding will not be possible to ABX. The main difficulty is an ABXer has to find a proper -q meaning for each sample. The second difficulty are improvements which affect quality at lowest bitrates and ABXing from the original becomes very easy. So maybe we should use 'very easy samples'?
QUOTE(de Mon @ Nov 7 2005, 03:27 AM)
[...] So maybe we should use 'very easy samples'?
The obvious thing to do is a blind test between two encoded files, A=v4.0 and B=v4.5, which have comparable filesizes. It doesn't matter what kind of samples you use. If you can hear a difference between the two versions, then go ahead and rate which one you find more pleasing...
QUOTE(Leo 69 @ Nov 6 2005, 12:10 AM)
Lets wait a bit, maybe
Aoyumi will give some explanations about this version and what we should expect from it. If it is OK, it would be wonderful if
john33 compiles an OggDropXPd with this thingy inside. Is it possible, John ?

And John please compile oggenc2.6 and ogg vorbis dlls using aoTuV b4.5 as well.
wow, this is amazing at q0, makes me with i had an vorbis portable, i am stuck with using q25 wma...
QUOTE(ErikS @ Nov 6 2005, 08:33 PM)
The obvious thing to do is a blind test between two encoded files, A=v4.0 and B=v4.5, which have comparable filesizes. It doesn't matter what kind of samples you use. If you can hear a difference between the two versions, then go ahead and rate which one you find more pleasing...
As I said before the difference between b4 and b4.5 is very small and I can't decide which one is better at such a low bitrate .
I hope others would.
QUOTE(john33 @ Nov 6 2005, 08:29 AM)
QUOTE(Leo 69 @ Nov 5 2005, 04:10 PM)
Lets wait a bit, maybe
Aoyumi will give some explanations about this version and what we should expect from it. If it is OK, it would be wonderful if
john33 compiles an OggDropXPd with this thingy inside. Is it possible, John ?

Generic, P3 and P4 compiles of oggdropXPd now at Rarewares.

Сool ! Thanks mate!
BTW
Aoyumi, are you going to make tunings for high bitrate in the future versions ? Thanks for your great work.
Cheers
Mo0zOoH
Nov 7 2005, 17:06
QUOTE(de Mon @ Nov 7 2005, 04:22 PM)
As I said before the difference between b4 and b4.5 is very small and I can't decide which one is better at such a low bitrate .
I think the question is which one makes the file smaller.
kurtnoise
Nov 8 2005, 03:22
QUOTE(john33 @ Nov 6 2005, 09:03 PM)
Surely, but do people want the full range of compiles, or is this considered somewhat experimental at this stage?
well...just libvorbis.dll is enough for testing I think. Not the full range of compiles.
I asked this because I'm not able to compile myself this library (only vorbisenc/vorbisfile/vorbis in fact w/o optimizations).
QUOTE(Mo0zOoH @ Nov 7 2005, 03:06 PM)
QUOTE(de Mon @ Nov 7 2005, 04:22 PM)
As I said before the difference between b4 and b4.5 is very small and I can't decide which one is better at such a low bitrate .
I think the question is which one makes the file smaller.

With my samples sizes are almost identical.
PatchWorKs
Nov 8 2005, 05:53
Uhm, waiting for a new Lancer !
B-1B Lancer info page
QUOTE(Nayru @ Nov 6 2005, 04:13 PM)
Download libogg-1.1.2.tar.gz and vorbis-tools-1.1.1.tar.gz from
http://www.xiph.org/downloads/Download libvorbis-aotuv_b4.5.tar.gz.tgz from
http://www.geocities.jp/aoyoume/aotuv/Unpack everything.
cd libogg-1.1.2
./configure
make
make install
cd ../aotuv-b4.5_20051105
chmod +x configure
chmod +x install-sh
./configure
make
make install
cd ../vorbis-tools-1.1.1
./configure
make
Run oggenc/oggenc
And when you are using oggenc from vorbis-tools 1.1.1, how does this use aotuv4.5 ?
Linux Zealot Troll
Nov 8 2005, 11:15
QUOTE(suur13 @ Nov 8 2005, 05:54 PM)
And when you are using oggenc from vorbis-tools 1.1.1, how does this use aotuv4.5 ?
Because oggenc uses the libvorbisenc/libvorbisfile libraries to do the encoding. So as long as you replace this library you should get the new encoding functionality.
You can also test it without installing and breaking packages:
CODE
cd aotuv-b4.5_20051105/
./configure
make
export LD_LIBRARY_PATH=./lib/.libs/
oggenc will now temporarily link against the new libraries and will encode with aotuv:
CODE
$>ldd /usr/bin/oggenc
libvorbisenc.so.2 => ./lib/.libs/libvorbisenc.so.2 (0xb7eea000)
libvorbis.so.0 => ./lib/.libs/libvorbis.so.0 (0xb7ec0000)
libOggFLAC.so.1 => /usr/lib/libOggFLAC.so.1 (0xb7ea1000)
libFLAC.so.6 => /usr/lib/libFLAC.so.6 (0xb7e6d000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7e4c000)
libogg.so.0 => /usr/lib/libogg.so.0 (0xb7e47000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7d1a000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7feb000)
xmixahlx
Nov 8 2005, 15:48
QUOTE(Linux Zealot Troll @ Nov 8 2005, 10:15 AM)
Because oggenc uses the libvorbisenc/libvorbisfile libraries to do the encoding. So as long as you replace this library you should get the new encoding functionality.
yeah

it's pretty handy for packaging
from RareWares/Debian:
CODE
$ ldd /usr/bin/oggenc-aotuv
linux-gate.so.1 => (0xffffe000)
libvorbisenc.so.2 => /usr/lib/libvorbis-aotuv/libvorbisenc.so.2 (0xb7ead000)
libvorbis.so.0 => /usr/lib/libvorbis-aotuv/libvorbis.so.0 (0xb7e83000)
libOggFLAC.so.1 => /usr/lib/libOggFLAC.so.1 (0xb7e59000)
libFLAC.so.6 => /usr/lib/libFLAC.so.6 (0xb7e1c000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7df7000)
libogg.so.0 => /usr/lib/libogg.so.0 (0xb7df1000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7cb9000)
/lib/ld-linux.so.2 (0xb7fad000)
btw, aotuv 4.5 is at RW/Debian now
later
I think aotuv beta 4.5 is safe to use.
my logic: new Aoyumi releaze is BETA 4.5, not new TEST version.
Mekatype
Nov 9 2005, 18:40
So, b4.5 is supposed to perform better than b4 @ q3 and below, but what about @ q3 and better?
HotshotGG
Nov 9 2005, 19:05
QUOTE
So, b4.5 is supposed to perform better than b4 @ q3 and below, but what about @ q3 and better?
Sounds fine to me

. 4 and 5 were transparent to me long before all of the tweaking with the psychoacoustics. The only major thing that really needed to corrected was some of the noise normalization issues, which are still being addressed and have been fixed. How much better can you make it possible? Aoyumi has been at it for a while now and has done a great job.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.