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: oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new (Read 39833 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

oggdropXPd V1.8.7, oggenc2.8 and oggdec V1.9.2 released  2005-12-08.

All the above version updates are to handle multi-channel input and output correctly in relation to WAVEFORMATEXTENSIBLE conforming input and the channel mapping as defined in the Vorbis I Specification. The decoders handle channel mapping correctly for output to file, and for playback, creating WAVEFORMATEXTENSIBLE conforming output. The decoders also offer the option to downmix multi-channel audio, conforming to the Vorbis I Specification, to stereo. These versions are based on libogg 1.1.3 and libvorbis 1.1.2/aoTuVb4.51.

All flavours are at Rarewares now.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #1
Thank you very much indeed, appreciated.
WavPack 5.7.0 -b384hx6cmv / qaac64 2.80 -V 100

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #2
Nice.  Updated the recommended encoder thread with the new versions.  Also updated the static linux binaries of vorbisgain and oggenc to aoTuV beta 4.51.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #3
Sorry I think I missed something...

libvorbis is now 1.1.2 ? how does it relate to aoTuVb4.51 ?

 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #4
Quote
Sorry I think I missed something...

libvorbis is now 1.1.2 ? how does it relate to aoTuVb4.51 ?
[a href="index.php?act=findpost&pid=348770"][{POST_SNAPBACK}][/a]


libvorbis 1.1.2 is the official Vorbis library coming out from Xiph.Org that is mostly based on the old aoTuV beta 2.  aoTuV beta 4.5 is Aoyumi's tuned version of libvorbis (based on libvorbis 1.1.1).

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #5
It don´t have any important improvement in quality, I check the changelog and it mostly fix one bug...

Code: [Select]
libvorbis 1.1.2 (2005-11-27) -- "Xiph.Org libVorbis I 20050304"
* fix a serious encoder bug with gcc 4 optimized builds
* documentation and spec fixes
* updated VS2003 and XCode builds
* new draft RTP encapsulation spec

In fact... the libvorbis 1.1.2 has the same signature that the 1.1.1 "Xiph.Org libVorbis I 20050304".... I really want to know what the Xiph guys are doing... If Aoyumi don´t release his great Aotuv, vorbis can´t compete with AAC. Even LAME has evolved a lot more...
JorSol
aoTuVb5 -q4

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #6
Quote
Quote
Sorry I think I missed something...

libvorbis is now 1.1.2 ? how does it relate to aoTuVb4.51 ?
[a href="index.php?act=findpost&pid=348770"][{POST_SNAPBACK}][/a]


libvorbis 1.1.2 is the official Vorbis library coming out from Xiph.Org that is mostly based on the old aoTuV beta 2.  aoTuV beta 4.5 is Aoyumi's tuned version of libvorbis (based on libvorbis 1.1.1).
[a href="index.php?act=findpost&pid=348793"][{POST_SNAPBACK}][/a]

IIRC, aoTuVb4.51 was actually based on the then current SVN version, ie., post 1.1.1, and did include the bug fix referred to in the release notes.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #7
This versions support 5.1 channel coupling? or is just the correct way to output each channels in the correct order?
JorSol
aoTuVb5 -q4

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #8
 Sooooo...  let me get this straight:

Xiph 1.1.2 is a bugfix of Xiph 1.1.1 which incorporates aoTuVb2.

aoTuVb4.51 is a bugfix of aoTuVb4.5 which is an improvement of aoTuVb4 which -ultimately- is based on Xiph 1.1.1.

aoTuVb4.51 already incorporates the bugfixes of Xiph 1.1.2.

So in conclusion: I should be using the aoTuVb4.51.

Am I reading this correctly? 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #9
Quote
This versions support 5.1 channel coupling? or is just the correct way to output each channels in the correct order?
[a href="index.php?act=findpost&pid=349774"][{POST_SNAPBACK}][/a]

No channel coupling, they just maps channels in the correct order when encoding and decoding.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #10
Quote
Sooooo...  let me get this straight:

Xiph 1.1.2 is a bugfix of Xiph 1.1.1 which incorporates aoTuVb2.

aoTuVb4.51 is a bugfix of aoTuVb4.5 which is an improvement of aoTuVb4 which -ultimately- is based on Xiph 1.1.1.

aoTuVb4.51 already incorporates the bugfixes of Xiph 1.1.2.

So in conclusion: I should be using the aoTuVb4.51.

Am I reading this correctly? 
[a href="index.php?act=findpost&pid=349813"][{POST_SNAPBACK}][/a]

Yes and yes, if I understand you you correctly!!

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #11
I think this has definitely been asked before, but I'd like to know if anyone could tell what the main differences are between the available 3 versions:
- Oggenc2.8 using libVorbis v1.1.2
- Oggenc2.8 using libVorbis v1.1.2 with IMPULSE_TRIGGER_PROFILE Option
- Oggenc2.8 using aoTuVb4.51

Recently I made some samples @ Q4 (128Kbps) > the libVorbis produced me 116Kbps (3.180.453 bytes) file, and the aoTuVb produced me a 118Kbps (3.232.446 bytes) file.
I didn't notice any soundquality differences though...and I also noticed QuantumKnot recommends the aoTuVb version in his Recommended Encoder Versions and Settings thread...Why? What makes this version so special above the libVorbis version?

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #12
Quote
and I also noticed QuantumKnot recommends the aoTuVb version in his Recommended Encoder Versions and Settings thread...Why? What makes this version so special above the libVorbis version?
[a href="index.php?act=findpost&pid=350099"][{POST_SNAPBACK}][/a]

Haven't you noticed QuantumKnot's explanation in the same thread?

Quote
aoTuV beta 4 Now the recommended encoder

Developed by Aoyumi and based on libvorbis 1.1.1, many people have reported this encoder to give better quality at low to medium bitrates. It includes a -q -2 option for the lowest bitrate. According to guruboolez' latest listening test on classical music, aoTuV beta 4 performed magnificently well at -q 6!!
Wavpack Hybrid: one encoder for all scenarios
WavPack -c4.5hx6 (44100Hz & 48000Hz) ≈ 390 kbps + correction file
WavPack -c4hx6 (96000Hz) ≈ 768 kbps + correction file
WavPack -h (SACD & DSD) ≈ 2400 kbps at 2.8224 MHz

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #13
Quote
Haven't you noticed QuantumKnot's explanation in the same thread?

Quote
aoTuV beta 4 Now the recommended encoder

Developed by Aoyumi and based on libvorbis 1.1.1, many people have reported this encoder to give better quality at low to medium bitrates. It includes a -q -2 option for the lowest bitrate. According to guruboolez' latest listening test on classical music, aoTuV beta 4 performed magnificently well at -q 6!!

[a href="index.php?act=findpost&pid=350105"][{POST_SNAPBACK}][/a]


Ah... it bears your name... that must be the reason 

Hehe j/k. Lighten up! 

Peace 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #14
Quote
So in conclusion: I should be using the aoTuVb4.51.
Am I reading this correctly? 
[{POST_SNAPBACK}][/a]


No, latest [a href="http://homepage3.nifty.com/blacksword/index_e.htm]Lancer[/url]

sarcastic note: those 'yellows' (Japaneses) are great ! 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #15
Quote
Quote
So in conclusion: I should be using the aoTuVb4.51.
Am I reading this correctly? 
[{POST_SNAPBACK}][/a]


No, latest [a href="http://homepage3.nifty.com/blacksword/index_e.htm]Lancer[/url]

sarcastic note: those 'yellows' (Japaneses) are great ! 
[a href="index.php?act=findpost&pid=350756"][{POST_SNAPBACK}][/a]

Wow! This Lancer built is well above 40x encoding here. Never tried it before.
I somewhere read it "may" produce different results due to its optimisations. Is there a degraded example documented?
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #16
Quote
I somewhere read it "may" produce different results due to its optimisations. Is there a degraded example documented?
[a href="index.php?act=findpost&pid=350768"][{POST_SNAPBACK}][/a]

If you're unsure about the result, do the following:

a) choose a sample and encode it with oggenc (let's call it sample X);
b) encode that sample with lancer (sample Y);
c) open both of them with a sound editor;
d) flip/invert one of them;
e) mix them (by this operation, you subtract X from Y, or vice versa — depending on which one you've flipped; the result will be identical);
f) see if there is something left (if the aforementioned samples are identical, there shouldn't).

Cheers.

edit: gr.
Infrasonic Quartet + Sennheiser HD650 + Microlab Solo 2 mk3. 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #17
Quote
Quote
I somewhere read it "may" produce different results due to its optimisations. Is there a degraded example documented?
[a href="index.php?act=findpost&pid=350768"][{POST_SNAPBACK}][/a]

If you're unsure about the result, do the following:

a) choose a sample and encode it with oggenc (let's call it sample A);
b) encode that sample with lancer (sample B);
c) open both of them with a sound editor;
d) flip/invert one of them;
e) mix them (by this operation, you subtract A form B, or vice versa depending on which one you've flipped; the result will be identical);
f) see if there is something left (there shouldn't; if both encodings are identical).

Cheers.
[a href="index.php?act=findpost&pid=350838"][{POST_SNAPBACK}][/a]

All compiles deliver different results. So does the Standard, AMD/P3 or the P4 compile. It is no wonder the Lancer does a bit different also.
I just asked if there is a documented "problem" about the Lancer build just cause of its optimizations in the code.
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #18
Ah, sorry, I somehow misread your post.
Well, as for now, there weren't any documented and/or well-known problems with Lancer, AFAIK.
Infrasonic Quartet + Sennheiser HD650 + Microlab Solo 2 mk3. 

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #19
I also hinted in another thread that the optimized code might affect quality. But I am going to retract that notion and venture toward the hunch that different compilers have different ways to derive equations with math, then results (in the case of perceptual audio) are approximately the same.

Actually I have no idea what the hell I'm talking about

Thanks: john33, Aoyumi, the Blacksword guys and all the testers ..and Xiph people
[span style='font-size:8pt;line-height:100%'](I use the latest encoder music excerpts at [geocities slash feedthedead slash palehalf] and, no, this is not plug- just sharing[/span]
"Something bothering you, Mister Spock?"

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #20
Ah this question I had asked previously in this thread.

Basically, the answer is like this:

Lancer uses SSE, and this rounds off floating point numbers differently than the, um, plain aoTuVb4.51.

However, despite the differences, I have tried them both and to my ears they sound the same.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #21
Quote
Ah this question I had asked previously in this thread.

Basically, the answer is like this:

Lancer uses SSE, and this rounds off floating point numbers differently than the, um, plain aoTuVb4.51.

However, despite the differences, I have tried them both and to my ears they sound the same.
[a href="index.php?act=findpost&pid=351106"][{POST_SNAPBACK}][/a]

So i think it is safe. There once were discussions about small differences in lame´s output due to compiler optimisations. No one ever reported a sound problem cause of this. The differences are just to small.
Thanks for your input.
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #22
Dunno if anyone tests these in Win x64, but I tried both aoyumidrop and lancerdrop; they both began promisingly encoding about half of the dozen FLACs, but then the fish stopped and the drop ability was gone. Those files which had been encoded were fine. It seems to me that these Oggdrops also borked MediaCoder.
I wound up doing a System Restore and all is well again.  But I'm sticking with MediaCoder pointed to Lancer's oggenc2.exe .

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #23
Looking at the xiph bugtrac I see there are some ticket with problems and patches for OggDropXP.
I don't know if they are yet valid, in this case they should be closed.

oggdropXPd V1.8.7, oggenc2.8, oggdec V1.9.2 - new

Reply #24
Quote
Lancer uses SSE, and this rounds off floating point numbers differently than the, um, plain aoTuVb4.51.

However, despite the differences, I have tried them both and to my ears they sound the same.


That's the general consensus that I am came to and what I have written down on the page in the wiki.  I have read about SSE instructions in the past, but it's been a while.
budding I.T professional