Aoyumi, thanks a lot

Yatta!

Especially arigatō for pre-echo tunings in this release.

Thank you for this release, Aoyumi

Thank you so much Aoyumi!

Great Man!!!

Unofficial retranslation of Japanese changelog:

Expanded/extended noise control in impulse blocks. This affects samples with outstanding pre-echo.

Applied pre-echo reduction code to lower bitrates (q -1/-2).

Noise normalization bug fixed. And code was revised.

In addition to the changes/additions above, various parts were retuned.

Compiles now available at Rarewares.

Thnx too, John ... your compile is much faster on my Computer

Thank you very much, Aoyumi and John.

Vorbis is my favourite audio codec.


Best regards

akapuma

Thank YYYYYOOOOOUUUUUUUU

Thanks Aoyumi! Vorbis rulez!

Great work Aoyumi! Thanks a lot. :c)

/Kef

Though I'm not a vorbis user I admire your great work, Aoyumi.
Just tried your new version at -q4 with regular music and some problem samples. Wonderful quality!

Thx Aoyumi!!! Pre-echo is real less.
Why this wonderful news is not on the main HA page???

That is great news indeed. Just can't wait to get LANCER version of "aoTuV" beta5.5

I couldn't agree more ...

/Kef

Thank you very much for the new release. Been using Vorbis for all my portable use for quite a while now thanks to your tunings.

Thank you very much for the release, Aoyumi!

Charles

Thank You Aoyumi and John

I too await LANCER version of "aoTuV" beta5.5

+1- I hope BlackSword is still going to do Lancer builds

Is he on these forums?

Anyway, thanks very much for your hard work Aoyumi. It puts all the hot air over MP3 beta 5 and 6 and final 3.98 never coming out to shame when one guy can simply finetune an encoder himself and get on with it.

- Spike

Aoyumi you did it finally

Thanks for all.

I see a lot of happy faces, hehe you made ".ogg vorbis" fans happy again.

Thanks again

Many many thanks!

Thanks for your hard work, Aoyumi, and thanks for hosting so many goodies for us, john33!

Also thanks alot from me, I think without your work I wouldn't use Vorbis as of today, it's nice to see someone actively improving one of my favorite codecs

Sugoi!
Otsukaresama deshita!
The first thing I encoded was a conversation exercise CD that came with a Japanese language text.
The Oggdrop XPd functions of converting to mono and down-sampling are a huge help for making great-sounding tiny files. ( I wish those functions, especially the new resampler, were in FLACdrop.)
Aoyumi-san was in large part responsible for my resolve to learn Japanese.
Gambarimasho!

This makes a fine birthday present. I'm glad you put this together. As an individual and on behalf of the community, I thank you.


ckjnigel: The impetus to learn Japanese came from Aoyumi-san, eh? That's awesome... XD

You know what else is awesome...? For the first time, I'm unable to consistently abx some of my music at -q0 (lowpass 18).

Are there any noticeable improvements when using q -5 between the previous beta and the current one?

Also, are there noticeable differences between using Auyumi's tuned-up build and Xiph.org's latest build at q -5?

Thanks for your hard work, Auyumi!

Im kind of interested about the first question aswell.
Is there anyone who did any advance tests on the new built?

Thanks

Audible improvements at q5? If a5 was transparent to you before, there's no "audible improvement" possible, no matter what build you use.

But what about the pre-echo problems at high bitrates that some people mention on the previous beta? Is there any pre-echo reduction at q5 on the new beta?

Does anybody else have problems with this beta 5.5 release? I encoded a few albums at -q0 for my portable player (iRiver S10) and even though the files plays in foobar, I only get 2-4 seconds of each song on my portable and then it tries to play the next song which is also about 4 seconds long and so on and so on... It even says the songs are 4 seconds long!

Aoyumi, did you change something in the bit-stream?

/Kef

AFAIK, aoTuV beta5.5 uses official Vorbis 1.2.0 as its base. Previous versions use Vorbis 1.1.x.
Try Vorbis 1.2.0 (Xiph.Org libVorbis I 20070622) and you'll see if this matters.

Anyway, my Samsung YP-U3 plays such files (aoTuV beta 5.5, q0) without problems.

Ah, good catch, that might be it... I'll check

You where right, it's not aoTuV beta5.5, it is Vorbis 1.2.0 that causes the problem.

Good catch. Thanks! (off to iRiver to ask for a firmware-update)

/Kef

But that's not the whole story though... oggdrop works just fine with both beta5.5 and Vorbis 1.2.0, but not with foobar and either command line encoder... Strange!

Which command line encoders are you referring to? oggenc2 output should match oggdropXPd output and if there is some fatal difference, I need to look into it.

I'm referring to oggenc2.



I can send you the files, if you like, but ... I would probably be the next target of RIAA...

What command line are you using from foobar and what options are you specifying in oggdropXPd? Sorry to be a pain, but I need to know whether foobar is doing something different.

I'm just using default settings and -q0.

oggenc2 and oggdropXPd downloaded from rarewares

No tagging at all?

Ehum... I usually don't use tags but I checked the source (reference libFLAC 1.1.2 20050205) files and yes they are tagged.



Maybe it would be a good idea to use wav's to eliminate any tagging problem?

<edit>
I tested with a wav file and it worked perfectly, when I use the flac file it doesn't (using foobar2000 for both). Seems like some tagging problem to me.
</edit>

<edit2>
I removed the tags from the ogg file and still no luck
</edit2>

So, if I understand this correctly, the ogg files created from the FLAC files using foobar, with tags copied from the FLAC files, fail in your portable.

The ogg files created from the FLAC files using oggdropXPd are read fine in the portable, but do they contain tags, or not?

The fact that removing the tags from the ogg files doesn't solve the problem may suggest that the tagging routines in foobar are behaving in a way that is not quite standard, or if the oggdropXPd generated files aren't created with tags, then there is something about tagging that the iRiver doesn't like.

Edit: Sorry, thinking about it, the comment about foobar tagging routines is probably complete nonsense since it will presumably just feed the tagging routines in oggenc2!

Correct

They don't contain any tags.


Yeah, that's the question isn't it?

Anyway, I'm glad to find out it probably isn't a bit-stream problem. This is the first time I have encountered this problem and I have done a lot of conversions with both foobar and oggdropXPd. But as a previous poster suggested, it might have something to do with the new 1.2.0 libvorbis. I haven't used 1.2.0 until now (there was no reason to) and since aoTuVb5.5 is using 1.2.0 that might indeed be the problem. Luckily, there are workarounds for me.

<edit>
I'll test with libvorbis 1.2.0 later today and let you know if the problem is still there.
</edit>

foobar2000 calls oggenc.exe with commandline like that:

So fb2k don't rely on codecs when tagging.

Try a conversion using oggdropXPd and set the option to copy the FLAC tags. If that causes a problem, then the tags would seem to be the problem.

Slightly more confusing is that the tagging routines in the library appear unchanged relative to the previous version.

I did convert using oggdropXpd and copying the tags. It worked perfectly.

In which case, the problem must lie on the foobar tagging! Which, in the context of lvqcl's post, certainly seems a possibility. Mal-formed tags, I would guess, although somewhat unexpected.

I don't discover the cause of the problem. However, I know that a problem gets up by the state of the comment header at a low bit rate depending on DAP.

I think that it is not a problem of the library. Because the reason is because the problem does not depend on the version of the library.

I suppose that padding domain of the Vorbis comment or the size of the Vorbis comment domain influences it.

Are you still interested in material that provokes artefacts, to tune your psycho acoustics further? Or may I possibly add some "Advanced Encoder Options" here to test for you if they improve the result?
__

Listening to Ogg Vorbis audio with a Home Cinema set was in general satisfying for me. Most of my CDs sound well even when compressed with just Quality 3/10.

Some time ago I bought a pocket audio player which supports Ogg Vorbis files (Samsung YP-...), and I am in general satisfied too. Until I heard a remarkable exception. So I compared several oggenc2 versions (usually I prefer the aoTuV variants, the song I heard was encoded with aoTuV-b4), and even with the current b5.5 "release", I still get "twitting" noise at quality 3 with:

The Prodigy: 04. Your Love [Remix] (Experience, 1992)

for the synth percussion at the time 01:12-01:14, and even more at the time 03:29-03:31. I understand that this sound is possibly very provoking, it has sharp attacks and some flat "pappy" noise afterwards.

I can send you some material if required (e.g. short cuts around these positions).

I understand the cause of the problem. But, I don't find an efficient solution for the moment.
Probably the basic solution is not possible in "Advanced Encoder Options".

...
When somebody finds the good method, I am glad.

Thanks for this new release, Aoyumi! The low bitrates keep getting better and better.

Also, I just asked in the Vorbis 1.2.0 release thread whether they included any of your tunings (beyond what was put in the Vorbis 1.1.0 release). But looking here, I see I don't need to worry, since you already integrated Vorbis 1.2.0 into your latest release.

I second making a news thread.