New tuned encoder Options

[Garf]

Originally posted by jianxin yan
hi garf.
in rc2, if not a wavelet or wavelet package transform is used?

Nope. Wavelets aren't and won't be in Vorbis for a while.

Probably after 1.0 final release testing with them will begin.

--
GCP

[Garf]

Originally posted by PatchWorKs


YYYYYEEEEEESSSSSSSSSSS !!! I REALLY WANT IT
I need 32 kHz, 16 bit, mono please (bitrate: min 32 - max 48 - average 40 kbps)...

Tnx  

Sorry, I've only got a stereo mode for now

I'll compile an oggenc when I have time.

(btw. It's 45kbps now, I shaved off some. Going to 40kbps average is probably not going to be listenable with 32kHz stereo.)

--
GCP

[PatchWorKs]

Test this file (open with WinAmp CTRL+L) and tell me what you think about quality:

http://www.patchworks.it/stream.ogg

[encoded by Peter Pawlowski's Ogg Vorbis encoder plug-in v1.31 (libvorbis v1.0 RC2)]

[Garf]

Originally posted by PatchWorKs
Test this file (open with WinAmp CTRL+L) and tell me what you think about quality:

http://www.patchworks.it/stream.ogg

[encoded by Peter Pawlowski's Ogg Vorbis encoder plug-in v1.31 (libvorbis v1.0 RC2)]

Hard to tell. First impression is quite good, but the song is not very stressing. As soon as some more instruments kick in you see the bitrate go up too.

Feed it some metal

--
GCP

[PatchWorKs]

- ORIGINAL FILE CHARACTERISTICS -
Length (m:ss): 1:30
Size: 5.799.592
Frequency: 32000 Hz
Channels: 1
Artist: BirdFlesh (http://home.swipnet.se/~w-92019/)
----------------------------------------------------------------------


ENCODER = Ogg Vorbis encoder plug-in
File: test1
Location: http://www.patchworks.it/test1.ogg
Average Bitrate: 46 Kbps
Size: 532.091
Compression Ratio: 10 to 1 (9 %)

ENCODER = dBpowerAMP Music Converter
File: test2
Location: http://www.patchworks.it/test2.ogg
Average Bitrate: 43 Kbps
Size: 499.166
Compression Ratio: 11 to 1 (8 %)


Both encoders uses Xiphophorus libVorbis I 20010813


Listen and post your considerations...

[Volcano]

I have now tested your VBR mode on thewayitis.wav, fatboy.wav and short.wav (and compared it to LAME --r3mix / --dm-preset standard, using win32LAME 1.7). No ABX, just a quick-n-dirty test, but the difference was obvious enough.

It easily beats both LAME settings on short and fatboy, on thewayitis they all sounded transparent to me. I could still hear a difference to the original on fatboy and short, but both r3mix and dm-standard were so much worse. (Sorry Dibrom, I haven't tried your new settings yet, I don't know where to get my hands on a compile that includes them, can anybody tell me?)

I'm amazed - lower bitrates than r3mix (on normal music, that is - on those samples, the bitrate absolutely exploded), and FAR better quality. I think this has finally convinced me to switch over to OGG - hats off to you, Garf, this is just too great for words! (Take that from somebody who - until now - was 100% sure that --r3mix was the perfect quality/size compromise...)

And the 128k mode is also well tuned, is it? Fine, that might be enough to convince some friends to use it instead of LAME 128kbps without nspsytune...

The only thing that bothers me is the OGG tagging system, which I seriously dislike... firstly because of its structure and secondly because there are no batch taggers around that can handle it, but I guess there's a solution to that somewhere.

CU

A happy Dominic

[Garf]

Originally posted by Volcano

And the 128k mode is also well tuned, is it? Fine, that might be enough to convince some friends to use it instead of LAME 128kbps without nspsytune...

Well, no, it's not really tuned. The standard RC2 128kbps mode was 'ok' for me if it weren't for the stereo hiss. The tuned 128kbps just removes the stereo hiss, at the cost of some more bits, so it may average at a bit more than 128kbps (but it also contains a fix which brings bitrate down again, so maybe it'll even out). I think it will do badly on preecho-heavy samples, perhaps worse than a well-tuned MP3 encoder. For normal music, it should be pretty competitive.

The 128kbps mode that is in current CVS may do better than the 128kbps mode in my encoder.

The only thing that bothers me is the OGG tagging system, which I seriously dislike... firstly because of its structure

Not sure what you mean here...could you explain?

secondly because there are no batch taggers around that can handle it, but I guess there's a solution to that somewhere.

Most people on the vorbis lists use scripts to handle the tagging. I don't use tags myself.

Thanks for your feedback. I appreciate it.

--
GCP

[gnoshi]

There is one mass tagger for ogg files that I know of.

http://www.mediajukebox.com

Bit unstable, and not that easy to use, but it pretty much does the job.

gnoshi

btw... can't wait for rc3 =)
good work garf

[Volcano]

Media Jukebox does it? Cool, I'll try it when I get home.

Does it also batch-tag files according to the file name scheme?

CU

Dominic

[Volcano]

Problem solved - the answer is "Yes, it does batch-tagging". Works like a charm! I'm beginning to like Media Jukebox, although it's a bit bloated in some places...

Thanks, gnoshi, for the hint!

CU

Dominic

[Neo Neko]

I love the tagging system. It is supa-flexable! I did some audio captures of some of the funny dialog from the tick and it works great. With MP3 IDVx you just have to live with and work around the built in tagging sys. With Vorbis I can create my own like SHOW=The Tick, EPISODE=3, TITLE=Whatever I want. It could be confusing at first, but it allows for much better tagging. No more hard to read abreviations and trying to figure out what each lable reffers to. It is clear concise and there are even tools to edit them inside Windows Explorer!