libvorbis 1.2.0 (2007-07-25) -- "Xiph.Org libVorbis I 20070622"
* new ov_fopen() convenience call that avoids the common
stdio conflicts with ov_open() and MSVC runtimes.
* libvorbisfile now handles multiplexed streams
* improve robustness to corrupt input streams
* fix a minor encoder bug
* updated RTP draft
* build system updates
* minor corrections to the specification
Ogg is unchanged.
so THAT's what has been going on in SVN
any aotuv merges?
thanks for the note, spoon.
later
I feel like saying "its about time there was an update"
although I don't know when the last one was. Good on them!
> Ogg Vorbis 1.2.0 is out
Nice. But no "official" announcement ?
Also "official" binaries (like FLAC and WAVPACK do have) would be good.
From the mailing list thread for 1.2.0 RC:
>> This does not incorporate any of the tunings from the aoTuV branch
> ...Yet. Before anyone asks, Monty will add the tunings on another
> release. There can't be just a blind merge. It has to be tested
> appropriately.
> -Ivo
Also "official" binaries (like FLAC and WAVPACK do have) would be good.
Paging John33.
The last vorbis update was early 2005! (off the top of my head)
We have updated dBpoweramp beta codecs (Flac and Ogg Vorbis( to 1.2.0.
-------
I think it might tie in with FLAC 1.2.0, the sudden jump to 1.2.0 was (atleast for me) unexpected for FLAC and Ogg Vorbis, perhaps Josh can shed some light, is there a big picture somewhere?
I think it might tie in with FLAC 1.2.0, the sudden jump to 1.2.0 was (atleast for me) unexpected for FLAC and Ogg Vorbis, perhaps Josh can shed some light, is there a big picture somewhere?
no, just coincidence!
[deleted]
Nice. But no "official" announcement ?
Also "official" binaries (like FLAC and WAVPACK do have) would be good.
That's no surprise at all. Xiph has been like that since Emmett left.
Paging John33.
Interestingly enough, John33 was the purveyor of official Vorbis binaries. I guess the Xiph guys lost his e-mail address or something
That's no surprise at all. Xiph has been like that since Emmett left.
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org (http://www.rarewares.org)
No new Vorbis 1.2.0 so far ...
Paging John33.
All libvorbis 1.1.2 based compiles now updated to 1.2.0.
So, to the question everyone is asking but no one can (?) answer:
Is it better than aoTuV b5?
Edit: Now that I actually read the first post, it seems this release doesn't touch audio quality. Am I right?
Yes!!
FIY, the new release includes multiplex stream support. What does that mean? If you have a bunch of stuff inside Ogg, like Theora, or strange mixes, the Vorbis part will still play on a Vorbis-only player.
Xiph has been like that since Emmett left.
Who?
Interestingly enough, John33 was the purveyor of official Vorbis binaries.
John33 does the OggDropXPd program for Windows, so what are you talking about?
Edit: Nevermind. Just noticed that rarewares carries compiled binaries.
But no "official" announcement ?
We made an official announcement. I think I'm missing the joke.
FIY, the new release includes multiplex stream support. What does that mean? If you have a bunch of stuff inside Ogg, like Theora, or strange mixes, the Vorbis part will still play on a Vorbis-only player.
Xiph has been like that since Emmett left.
Who?
Interestingly enough, John33 was the purveyor of official Vorbis binaries.
John33 does the OggDropXPd program for Windows, so what are you talking about?
But no "official" announcement ?
We made an official announcement. I think I'm missing the joke. Oh, nevermind.
Emmett Plant was the one-time CEO of Xiph.
At one time I also provided the 'official' win32 release compiles for Xiph, but that seems to have fallen by the wayside now.
Emmett Plant was the one-time CEO of Xiph.
I see. I suppose he's left way before I joined last year.
At one time I also provided the 'official' win32 release compiles for Xiph, but that seems to have fallen by the wayside now.
I just noticed that you replied to the Speex thread regarding Windows binaries. Would you mind if we mirrored your MSVC8 compiles on //xiph.org/downloads?
I think it might tie in with FLAC 1.2.0, the sudden jump to 1.2.0 was (atleast for me) unexpected for FLAC and Ogg Vorbis, perhaps Josh can shed some light, is there a big picture somewhere?
no, just coincidence!
Strangely enough, Speex also reaching the 1.2.0 stage. I actually thought it was intentional.
All libvorbis 1.1.2 based compiles now updated to 1.2.0.
Sure ?
EDITED: shot kicked since problem (partially) fixed, but © remained 2005 in OGGENC, OGGDEC not updated at all Saoshyant wrote:
FIY, the new release includes multiplex stream support. What does that mean? If you have a bunch of stuff inside Ogg, like Theora, or strange mixes, the Vorbis part will still play on a Vorbis-only player.
Thanks.
We made an official announcement. I think I'm missing the joke.
NO. The announcement didn't exist at the time I complained about "no announcement". And it was very hidden and tiny when you posted about the "joke". I extended it a bit
The XIPH's pages (xiph.org, vorbis.com, theora.org, ... etc. ) do leave some space for improvement IMHO
so speex, vorbis & flac all release 1.2.0 releases at the same time - and it wasn't planned?
At one time I also provided the 'official' win32 release compiles for Xiph, but that seems to have fallen by the wayside now.
I just noticed that you replied to the Speex thread regarding Windows binaries. Would you mind if we mirrored your MSVC8 compiles on //xiph.org/downloads?
Feel free, go ahead.
All libvorbis 1.1.2 based compiles now updated to 1.2.0.
Sure ?
I'll recompile and upload again shortly.
Edit: Just recompiled and uploaded again.
Just one more thing: there's also a new change on Vorbis, which developers may be interested. MIME Type has changed to audio/ogg per the MIME Type and File Extensions (http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions) proposal.
The Xiph's pages (xiph.org, vorbis.com, theora.org, ... etc. ) do leave some space for improvement IMHO
Indeed. We are looking for interested (and qualified) webmaster(s).
Feel free, go ahead.
Thanks.
Anyone care to explain the changes in plain English? I'm afraid my geek is weak today.
Just one more thing: there's also a new change on Vorbis, which developers may be interested. MIME Type has changed to audio/ogg per the MIME Type and File Extensions (http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions) proposal.
Just one more mystery: why are the binaries called OGGENC and OGGDEC, rather than VORBENC and VORBDEC ?
When I used oggdropXPd V.1.8.9 using libVorbis v1.2.0(Generic) shown in RAREWARES, I vomit Dr.Watson log with the end of the encoding, and oggdropXPd crashes.
アプリケーション例外が発生しました:
アプリケーション: (pid=1244)
発生時間: 2007/07/28 @ 06:18:02.457
例外番号: c0000005 (アクセス違反)
*----> システム情報 <----*
コンピュータ名:
ユーザー名:
プロセッサの数: 1
プロセッサの種類: x86 Family 6 Model 8 Stepping 10
Windows 2000 Version: 5.0
現在のビルド: 2195
Service Pack: 4
現在のタイプ: Uniprocessor Free
登録されている会社名:
登録されている所有者:
*----> タスク リスト <----*
0 Idle.exe
8 System.exe
140 smss.exe
168 csrss.exe
212 winlogon.exe
240 services.exe
252 lsass.exe
432 svchost.exe
456 spoolsv.exe
484 ccProxy.exe
496 ccSetMgr.exe
516 svchost.exe
556 Matrox.PowerDesk.Services.exe
604 mgabg.exe
616 navapsvc.exe
632 NPROTECT.exe
696 regsvc.exe
720 MSTask.exe
744 SNDSrvc.exe
808 NOPDB.exe
884 WinMgmt.exe
904 svchost.exe
920 ccEvtMgr.exe
1316 Explorer.exe
1384 SymTray.exe
1484 ccApp.exe
1524 kxmixer.exe
1516 Internat.exe
1528 MsnMsgr.exe
1244 oggdropXPd.exe
1308 drwtsn32.exe
0 _Total.exe
(00400000 - 00583000)
(77F80000 - 77FFC000)
(77520000 - 77550000)
(77DE0000 - 77E3F000)
(77E50000 - 77F33000)
(77F40000 - 77F7C000)
(79480000 - 794E5000)
(78780000 - 787EF000)
(73CC0000 - 73F06000)
(70A70000 - 70AD6000)
(78000000 - 78045000)
(71710000 - 71794000)
(7CFB0000 - 7D09F000)
(75DF0000 - 75E0A000)
(10000000 - 10030000)
(7C000000 - 7C054000)
(6CC90000 - 6CC96000)
(5EC20000 - 5EE97000)
(777D0000 - 777D7000)
(75940000 - 75946000)
(5EAE0000 - 5EB4B000)
(5EA80000 - 5EAC2000)
スレッド ID 0x138 のステート ダンプ
eax=00000000 ebx=00000000 ecx=0012ffb0 edx=00000000 esi=0012fee0 edi=77de55c4
eip=77e285c7 esp=0012fe98 ebp=0012feb8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
ファンクション: GetMenuItemRect
77e285ae b899110000 mov eax,0x1199
77e285b3 8d542404 lea edx,[esp+0x4] ss:01289d7f=????????
77e285b7 cd2e int 2e
77e285b9 c21000 ret 0x10
77e285bc b89a110000 mov eax,0x119a
77e285c1 8d542404 lea edx,[esp+0x4] ss:01289d7f=????????
77e285c5 cd2e int 2e
77e285c7 c21000 ret 0x10
*----> スタック バック トレース <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 ファンクション名
0012FEB8 00415440 0012FEE0 00000000 00000000 00000000 user32!GetMenuItemRect
77DE5B6C AAE80824 C2FFFFE7 4C8B0004 7EE80424 85FFFFE7 !<nosymbols>
74FF016A 00000000 00000000 00000000 00000000 00000000 <nosymbols>
*----> ロウ スタック ダンプ <----*
0012fe98 8f 69 de 77 e0 fe 12 00 - 00 00 00 00 00 00 00 00 .i.w............
0012fea8 00 00 00 00 00 00 00 00 - 11 69 de 77 c4 55 de 77 .........i.w.U.w
0012feb8 6c 5b de 77 40 54 41 00 - e0 fe 12 00 00 00 00 00 l[.w@TA.........
0012fec8 00 00 00 00 00 00 00 00 - 93 08 00 00 02 00 00 00 ................
0012fed8 c0 ff 12 00 01 00 00 00 - ee 00 20 00 0f 00 00 00 .......... .....
0012fee8 00 00 00 00 00 00 00 00 - cf 2b 37 02 91 02 00 00 .........+7.....
0012fef8 f0 00 00 00 30 00 00 00 - 03 00 00 00 70 40 41 00 ....0.......p@A.
0012ff08 00 00 00 00 00 00 00 00 - 00 00 40 00 eb 03 c7 01 ..........@.....
0012ff18 11 00 01 00 10 00 90 01 - 00 00 00 00 10 84 47 00 ..............G.
0012ff28 75 03 1f 01 a2 93 43 00 - 00 00 c8 42 00 00 00 00 u.....C....B....
0012ff38 cd 30 13 00 00 00 fa 47 - 03 bf 35 c0 c3 30 d7 30 .0.....G..5..0.0
0012ff48 5c 00 6f 00 00 f0 fd 7f - 44 00 00 00 90 3e 13 00 \.o.....D....>..
0012ff58 00 3b 13 00 40 3d 13 00 - 00 00 00 00 00 00 00 00 .;..@=..........
0012ff68 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012ff78 00 00 00 00 01 04 00 00 - 01 00 00 00 00 00 00 00 ................
0012ff88 00 00 00 00 01 00 01 00 - 00 00 00 00 bc ff 12 00 ................
0012ff98 00 00 00 00 05 00 00 00 - 00 00 00 00 c3 30 d7 30 .............0.0
0012ffa8 40 ff 12 00 4c 7f 0c c5 - e0 ff 12 00 80 b7 43 00 @...L.........C.
0012ffb8 fb 28 60 c0 01 00 00 00 - f0 ff 12 00 d5 89 e7 77 .(`............w
0012ffc8 c3 30 d7 30 5c 00 6f 00 - 00 f0 fd 7f 6f 00 70 00 .0.0\.o.....o.p.
スレッド ID 0x418 のステート ダンプ
eax=0003bfc0 ebx=00a80000 ecx=7ffdd000 edx=00a80608 esi=00f1f310 edi=00ee3350
eip=77fcd6ad esp=00f1e93c ebp=00f1e948 iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000283
ファンクション: RtlZeroHeap
77fcd692 56 push esi
77fcd693 8b750c mov esi,[ebp+0xc] ss:0207882e=????????
77fcd696 8b5d08 mov ebx,[ebp+0x8] ss:0207882e=????????
77fcd699 57 push edi
77fcd69a 8bfe mov edi,esi
77fcd69c 0fb74602 movzx eax,word ptr [esi+0x2] ds:020791f7=????
77fcd6a0 c1e003 shl eax,0x3
77fcd6a3 2bf8 sub edi,eax
77fcd6a5 3bfe cmp edi,esi
77fcd6a7 0f84cb010000 je RtlZeroHeap+0x702 (77fcd878)
フォールト ->77fcd6ad f6470501 test byte ptr [edi+0x5],0x1 ds:0203d236=??
77fcd6b1 0f85c1010000 jne RtlZeroHeap+0x702 (77fcd878)
77fcd6b7 0fb707 movzx eax,word ptr [edi] ds:00ee3350=????
77fcd6ba 8b4d10 mov ecx,[ebp+0x10] ss:0207882e=????????
77fcd6bd 0301 add eax,[ecx] ds:7ffdd000=00f1e9e4
77fcd6bf 3d00fe0000 cmp eax,0xfe00
77fcd6c4 0f87ae010000 jnbe RtlZeroHeap+0x702 (77fcd878)
77fcd6ca 807d1400 cmp byte ptr [ebp+0x14],0x0 ss:0207882e=??
77fcd6ce 0f84b7000000 je RtlZeroHeap+0x615 (77fcd78b)
77fcd6d4 56 push esi
77fcd6d5 53 push ebx
77fcd6d6 e814fdfcff call RtlIsValidIndexHandle+0x182f (77f9d3ef)
*----> スタック バック トレース <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 ファンクション名
00F1E948 77FCB80C 00A80000 00F1F310 00F1E9C0 00000000 ntdll!RtlZeroHeap
00F1E9F4 00435420 00A80000 00000000 00F1F318 C0D6AAF7 ntdll!RtlFreeHeap
00F1EA34 0040C89C 00F1F318 77E5B5AF 77E7B969 00000000 !<nosymbols>
00F1FFA0 0040CF34 77FB7E64 00134340 00F1FFEC 00000000 !<nosymbols>
77E77D0D 56530C45 6AFF3357 5B40A801 C38A0474 C4F637EB !<nosymbols>
8BEC8B55 00000000 00000000 00000000 00000000 00000000 <nosymbols>
*----> ロウ スタック ダンプ <----*
00f1e93c 00 00 a8 00 10 f3 f1 00 - 18 f3 f1 00 f4 e9 f1 00 ................
00f1e94c 0c b8 fc 77 00 00 a8 00 - 10 f3 f1 00 c0 e9 f1 00 ...w............
00f1e95c 00 00 00 00 02 00 00 00 - 18 f3 f1 00 44 ac 00 00 ............D...
00f1e96c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00f1e97c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00f1e98c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00f1e99c 00 00 00 00 00 00 00 00 - f8 01 a8 00 f8 01 a8 00 ................
00f1e9ac 02 00 00 00 01 00 00 00 - f8 01 a8 00 00 00 00 00 ................
00f1e9bc 00 00 a8 00 e0 7e 00 00 - 01 00 00 00 00 00 00 00 .....~..........
00f1e9cc 00 00 00 00 68 86 a8 00 - 01 00 00 00 00 00 00 00 ....h...........
00f1e9dc 60 e9 f1 00 88 e5 f1 00 - 24 ea f1 00 64 7e fb 77 `.......$...d~.w
00f1e9ec 78 16 f8 77 01 00 00 00 - 34 ea f1 00 20 54 43 00 x..w....4... TC.
00f1e9fc 00 00 a8 00 00 00 00 00 - 18 f3 f1 00 f7 aa d6 c0 ................
00f1ea0c 02 00 00 00 ec a7 59 00 - 44 ac 00 00 00 00 00 00 ......Y.D.......
00f1ea1c 08 ea f1 00 8c e5 f1 00 - dc ff f1 00 80 b7 43 00 ..............C.
00f1ea2c 3b 25 60 c0 fe ff ff ff - a0 ff f1 00 9c c8 40 00 ;%`...........@.
00f1ea3c 18 f3 f1 00 af b5 e5 77 - 69 b9 e7 77 00 00 00 00 .......wi..w....
00f1ea4c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00f1ea5c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00f1ea6c eb ec f1 00 00 00 00 00 - 09 f1 f1 00 00 00 00 00 ................
[!--sizeo:1--][span style=\"font-size:8pt;line-height:100%\"][!--/sizeo--]Mod edit: Codebox.[/size]
Just one more mystery: why are the binaries called OGGENC and OGGDEC, rather than VORBENC and VORBDEC ?
It's one of those things that wasn't meant to be, but ended up like that because the future is never clear. It's now kept for backwards reasons, but with some luck may change in the future*. It's also why Vorbis's extension is still .ogg even though it should be either .oga or even .vorbis
*either the name or the function; if all goes well, oggenc will in theory be able to encode OggPCM soon. What is OggPCM, you ask? Think of it like a much better WAV for audio editors.
Just one more mystery: why are the binaries called OGGENC and OGGDEC, rather than VORBENC and VORBDEC ?
It's one of those things that wasn't meant to be, but ended up like that because the future is never clear. It's now kept for backwards reasons, but with some luck may change in the future*. It's also why Vorbis's extension is still .ogg even though it should be either .oga or even .vorbis
*either the name or the function; if all goes well, oggenc will in theory be able to encode OggPCM soon. What is OggPCM, you ask? Think of it like a much better WAV for audio editors.
I second that too... I hate it when fb2k shows my ogg vids as audio file(ogg)
i searched the net for help, in the end i decided to use the .ogm extention for videos
i decided to use the .ogm extention for videos
You shouldn't for two reasons: 1) OGM is for MPEG 4 stuff like XviD inside Ogg, and 2) we are now recomending using .ogv video/ogg for video inside Ogg.
I need to get the bloody RFC done.
When I used oggdropXPd V.1.8.9 using libVorbis v1.2.0(Generic) shown in RAREWARES, I vomit Dr.Watson log with the end of the encoding, and oggdropXPd crashes.
Hmmm, all my testing is on XP Pro and all works fine. Anyone else running win2k that's seeing a problem? The baseline oggdropXPd code is unchanged and this is the first report I've had of a problem.
What is OggPCM, you ask? Think of it like a much better WAV for audio editors.
Another one?
Yes!!
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
Yes!!
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
I guess that comment was not too clear in terms of to what it was referring!!. libvorbis 1.2.0 has no quality improvements over 1.1.2 and, so, the answer to your question is that from a quality perspective, aoTuVb5 is considered to be better. 1.2.0 does address some other issues, but none that relate to audio quality. No doubt Aoyumi will merge b5 with 1.2.0 in due course.
so speex, vorbis & flac all release 1.2.0 releases at the same time - and it wasn't planned?
All I can say is that 1) I knew about Vorbis 1.2 about the day before the release and 2) Speex 1.2 won't be there for at least a few months.
i decided to use the .ogm extention for videos
You shouldn't for two reasons: 1) OGM is for MPEG 4 stuff like XviD inside Ogg, and 2) we are now recomending using .ogv video/ogg for video inside Ogg.
I need to get the bloody RFC done.
ok... will rename(again!)
but IMO, its better to use the standard .ogg extention for video and audio files, and .vrb for vorbis, .oga for audio only file and .ogv for video only files...
and I have a second question: is the container used for speex and flac the same as ogg or a stripped down version or completely different? because if its the same, I wouldn't mind using the .vrb extention for my ogg/vorbis music...
and I have a second question: is the container used for speex and flac the same as ogg or a stripped down version or completely different? because if its the same, I wouldn't mind using the .vrb extention for my vorbis music...
Speex uses Ogg. FLAC uses both Ogg and its own container; it depends of what the producer decides. The latter is more common, though -- it's rare for Ogg FLAC to show up on the wild.
You should read our recommendation for file extensions, if you care to follow the specification for file naming. .vrb for instance would not be allowed in such case. You are free to name your files whatever way you prefer, though.
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
From the mailing list thread for 1.2.0 RC:
>> This does not incorporate any of the tunings from the aoTuV branch
> ...Yet. Before anyone asks, Monty will add the tunings on another
> release. There can't be just a blind merge. It has to be tested
> appropriately.
> -Ivo
So, there is no ETA on that release ?
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
The patch (aotuvb5-libvorbis1.1.2.diff) applies almost cleanly to libvorbis-1.2.0. Only the libvorbis version has to be changed. Here's a patch upon the patch: http://pastebin.com/f79815e76 (http://pastebin.com/f79815e76)
The patch (aotuvb5-libvorbis1.1.2.diff) applies almost cleanly to libvorbis-1.2.0. Only the libvorbis version has to be changed. Here's a patch upon the patch: http://pastebin.com/f79815e76 (http://pastebin.com/f79815e76)
...and what about Lancer ?
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
I don't have the plan to merge beta5 and libvorbis 1.2.0.
It will happen by the upcoming version of aoTuV.
When I used oggdropXPd V.1.8.9 using libVorbis v1.2.0(Generic) shown in RAREWARES, I vomit Dr.Watson log with the end of the encoding, and oggdropXPd crashes.
Hmmm, all my testing is on XP Pro and all works fine. Anyone else running win2k that's seeing a problem? The baseline oggdropXPd code is unchanged and this is the first report I've had of a problem.
Same thing here. oggdropXPdV1.8.9-1.2.0-generic / Windows 2000 Professional Service Pack 4 (pt-BR)
Microsoft ® Windows 2000 ™ Versão 5.00 DrWtsn32
Copyright © 1985-1999 Microsoft Corp. Todos os direitos reservados.
Exceção de aplicativo:
Aplicativo: (pid=804)
Data e hora: 29/7/2007 às 18:20:04.286
Número da exceção: c0000005 (violação de acesso)
*----> Informação do sistema <----*
Nome do computador: K6
Nome de usuário: User
Número de processadores: 1
Tipo de processador: x86 Family 5 Model 8 Stepping 12
Versão do Windows 2000: 5.0
Versão atual: 2195
Service Pack: 4
Tipo atual: Uniprocessor Free
Empresa registrada: .
Proprietário registrado: User
*----> Lista de tarefas <----*
0 Idle.exe
8 System.exe
132 smss.exe
160 csrss.exe
180 WINLOGON.exe
208 SERVICES.exe
220 LSASS.exe
416 svchost.exe
468 svchost.exe
496 mstask.exe
528 winmgmt.exe
696 explorer.exe
800 GoogleToolbarNo.exe
288 NTVDM.exe
804 oggdropXPd.exe
752 drwtsn32.exe
0 _Total.exe
(00400000 - 00583000)
(78460000 - 784E0000)
(77550000 - 77581000)
(77E10000 - 77E79000)
(77F40000 - 77F7F000)
(79720000 - 797DA000)
(792D0000 - 79335000)
(77120000 - 77198000)
(7CF70000 - 7D1CB000)
(71710000 - 71794000)
(70BD0000 - 70C35000)
(78000000 - 78045000)
(7CE60000 - 7CF61000)
Despejo de estado para o identificador do segmento 0x128
eax=0012fb0c ebx=00000000 ecx=00000000 edx=00000000 esi=0012fee0 edi=77e41e49
eip=77e41eb3 esp=0012fe98 ebp=0012feb8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
função: DispatchMessageW
77e41e99 e8349dffff call GetFocus+0x50 (77e3bbd2)
77e41e9e e93effffff jmp GetWindowLongW+0x681 (77e41de1)
77e41ea3 90 nop
77e41ea4 90 nop
77e41ea5 90 nop
77e41ea6 90 nop
77e41ea7 90 nop
77e41ea8 b89a110000 mov eax,0x119a
77e41ead 8d542404 lea edx,[esp+0x4] ss:00ba9d7f=????????
77e41eb1 cd2e int 2e
77e41eb3 c21000 ret 0x10
77e41eb6 90 nop
77e41eb7 90 nop
77e41eb8 90 nop
77e41eb9 90 nop
77e41eba 90 nop
*----> Rastreamento regressivo da pilha<----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Nome da função
0012FEB8 00415440 0012FEE0 00000000 00000000 00000000 user32!DispatchMessageW
77E27ECB E9E80824 C200019D A4E80004 8500013C CB840FC0 !<nosymbols>
74FF016A 00000000 00000000 00000000 00000000 00000000 <nosymbols>
*----> Despejo simplificado da pilha<----*
0012fe98 7d 79 e2 77 e0 fe 12 00 - 00 00 00 00 00 00 00 00 }y.w............
0012fea8 00 00 00 00 00 00 00 00 - 3f 79 e2 77 49 1e e4 77 ........?y.wI..w
0012feb8 cb 7e e2 77 40 54 41 00 - e0 fe 12 00 00 00 00 00 .~.w@TA.........
0012fec8 00 00 00 00 00 00 00 00 - 93 08 00 00 02 00 00 00 ................
0012fed8 c0 ff 12 00 01 00 00 00 - 7c 00 1a 00 0f 00 00 00 ........|.......
0012fee8 00 00 00 00 00 00 00 00 - d0 a8 14 00 0b 02 00 00 ................
0012fef8 ac 01 00 00 30 00 00 00 - 03 00 00 00 70 40 41 00 ....0.......p@A.
0012ff08 00 00 00 00 00 00 00 00 - 00 00 40 00 cb 00 bd 01 ..........@.....
0012ff18 11 00 01 00 10 00 90 01 - 00 00 00 00 10 84 47 00 ..............G.
0012ff28 07 01 6e 00 a2 93 43 00 - 00 00 c8 42 00 00 00 00 ..n...C....B....
0012ff38 e8 2f 13 00 00 40 9c 47 - bf 23 ca 4b 6f 00 70 00 ./...@.G.#.Ko.p.
0012ff48 58 00 50 00 00 f0 fd 7f - 44 00 00 00 18 46 13 00 X.P.....D....F..
0012ff58 00 46 13 00 20 45 13 00 - 00 00 00 00 00 00 00 00 .F.. E..........
0012ff68 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012ff78 00 00 00 00 01 04 00 00 - 01 00 00 00 00 00 00 00 ................
0012ff88 00 00 00 00 01 00 01 00 - 00 00 00 00 bc ff 12 00 ................
0012ff98 00 00 00 00 05 00 00 00 - 00 00 00 00 6f 00 70 00 ............o.p.
0012ffa8 40 ff 12 00 f9 39 54 5b - e0 ff 12 00 80 b7 43 00 @....9T[......C.
0012ffb8 47 b4 9f 4b 01 00 00 00 - f0 ff 12 00 89 89 74 79 G..K..........ty
0012ffc8 6f 00 70 00 58 00 50 00 - 00 f0 fd 7f 65 00 00 00 o.p.X.P.....e...
Despejo de estado para o identificador do segmento 0x23c
eax=0003c230 ebx=009b0000 ecx=7ffdd000 edx=009b0608 esi=00abf310 edi=00a830e0
eip=784ad6ad esp=00abe93c ebp=00abe948 iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000283
função: RtlZeroHeap
784ad692 56 push esi
784ad693 8b750c mov esi,[ebp+0xc] ss:0153882e=????????
784ad696 8b5d08 mov ebx,[ebp+0x8] ss:0153882e=????????
784ad699 57 push edi
784ad69a 8bfe mov edi,esi
784ad69c 0fb74602 movzx eax,word ptr [esi+0x2] ds:015391f7=????
784ad6a0 c1e003 shl eax,0x3
784ad6a3 2bf8 sub edi,eax
784ad6a5 3bfe cmp edi,esi
784ad6a7 0f84cb010000 je RtlZeroHeap+0x702 (784ad878)
FALHA -> 784ad6ad f6470501 test byte ptr [edi+0x5],0x1 ds:014fcfc6=??
784ad6b1 0f85c1010000 jne RtlZeroHeap+0x702 (784ad878)
784ad6b7 0fb707 movzx eax,word ptr [edi] ds:00a830e0=????
784ad6ba 8b4d10 mov ecx,[ebp+0x10] ss:0153882e=????????
784ad6bd 0301 add eax,[ecx] ds:7ffdd000=00abe9e4
784ad6bf 3d00fe0000 cmp eax,0xfe00
784ad6c4 0f87ae010000 jnbe RtlZeroHeap+0x702 (784ad878)
784ad6ca 807d1400 cmp byte ptr [ebp+0x14],0x0 ss:0153882e=??
784ad6ce 0f84b7000000 je RtlZeroHeap+0x615 (784ad78b)
784ad6d4 56 push esi
784ad6d5 53 push ebx
784ad6d6 e814fdfcff call RtlIsValidIndexHandle+0x182f (7847d3ef)
*----> Rastreamento regressivo da pilha<----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Nome da função
00ABE948 784AB80C 009B0000 00ABF310 00ABE9C0 00000000 ntdll!RtlZeroHeap
00ABE9F4 00435420 009B0000 00000000 00ABF318 4B73364B ntdll!RtlFreeHeap
00ABEA34 0040C89C 00ABF318 7972B57B 7974B8F7 00000000 !<nosymbols>
00ABFFA0 0040CF34 00350034 00370036 00ABFFEC 00000000 !<nosymbols>
79747CC1 56530C45 6AFF3357 5B40A801 C38A0474 C4F637EB !<nosymbols>
8BEC8B55 00000000 00000000 00000000 00000000 00000000 <nosymbols>
*----> Despejo simplificado da pilha<----*
00abe93c 00 00 9b 00 10 f3 ab 00 - 18 f3 ab 00 f4 e9 ab 00 ................
00abe94c 0c b8 4a 78 00 00 9b 00 - 10 f3 ab 00 c0 e9 ab 00 ..Jx............
00abe95c 00 00 00 00 02 00 00 00 - 18 f3 ab 00 44 ac 00 00 ............D...
00abe96c e8 e9 ab 00 48 c0 bf 00 - 00 00 9b 00 d3 01 00 00 ....H...........
00abe97c 01 e9 ab 00 00 00 00 00 - c4 e9 ab 00 d0 69 9b 00 .............i..
00abe98c 01 16 46 78 ff ff ff ff - 18 e9 ab 00 3f 54 43 00 ..Fx........?TC.
00abe99c dc e9 ab 00 64 7e 49 78 - f8 01 9b 00 20 ab bf 00 ....d~Ix.... ...
00abe9ac 01 00 00 00 10 00 00 00 - f8 01 9b 00 00 00 00 00 ................
00abe9bc 00 00 9b 00 e0 7e 00 00 - 01 00 00 00 d8 69 9b 00 .....~.......i..
00abe9cc 0c 75 9b 00 60 89 9b 00 - 01 e9 ab 00 0c 31 42 00 .u..`........1B.
00abe9dc 60 e9 ab 00 88 e5 ab 00 - 24 ea ab 00 64 7e 49 78 `.......$...d~Ix
00abe9ec 78 16 46 78 01 00 00 00 - 34 ea ab 00 20 54 43 00 x.Fx....4... TC.
00abe9fc 00 00 9b 00 00 00 00 00 - 18 f3 ab 00 4b 36 73 4b ............K6sK
00abea0c 02 00 00 00 84 f9 06 00 - 44 ac 00 00 00 00 00 00 ........D.......
00abea1c 08 ea ab 00 8c e5 ab 00 - dc ff ab 00 80 b7 43 00 ..............C.
00abea2c 87 b9 9f 4b fe ff ff ff - a0 ff ab 00 9c c8 40 00 ...K..........@.
00abea3c 18 f3 ab 00 7b b5 72 79 - f7 b8 74 79 00 00 00 00 ....{.ry..ty....
00abea4c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00abea5c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00abea6c 0f ed ab 00 00 00 00 00 - 27 f1 ab 00 00 40 9c 47 ........'....@.G
EDIT: Ooops! Codebox...
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
I don't have the plan to merge beta5 and libvorbis 1.2.0.
It will happen by the upcoming version of aoTuV.
Kewl! I'll look forward to your newer version. I suspect Great Things are afoot!
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
I don't have the plan to merge beta5 and libvorbis 1.2.0.
It will happen by the upcoming version of aoTuV.
Kewl! I'll look forward to your newer version. I suspect Great Things are afoot!
and I also hope you make cymbals sound better Vorbis has only one noticable flaw and that is the way it handles a series of thrashing cymbals...
and I also hope you make cymbals sound better Vorbis has only one noticable flaw and that is the way it handles a series of thrashing cymbals...
Well, beating your head against the wall won't make anything any better. Are you participating in the 64 kbps listening test?
and I also hope you make cymbals sound better Vorbis has only one noticable flaw and that is the way it handles a series of thrashing cymbals...
Well, beating your head against the wall won't make anything any better. Are you participating in the 64 kbps listening test?
I got screwed by the program... used foobar to play 'em all instead
but vorbis did quite well, especially concidering the type of music was the one I like(METAL)... I chose that sample from metallica's wherever I may roam, the S&M version(sample#13).... lars ulrich's cymbals sounded quite natural to me. it was almost better than the aac 112 kbps version
but getting back to topic, I can't wait for still lower bitrates in vorbis like 16 to 20 kbps....
Merging of AoTuV b5 and Vorbis 1.2 wil be great.
is there a way to optimise aotuv so that it can convert mp3 to vorbis easily without much loss?
also, they say 448 kbps is the minimum bitrate required for transcoading... but what If I plan to use extremely low bitrates for output? say Vorbis AoTuV -q-2?(read minus two; 32 kbps)? will 128-192 kbps mp3 do?
is there a way to optimise aotuv so that it can convert mp3 to vorbis easily without much loss?
No. That's totally out of scope of what the aoTuV tunnings do.
also, they say 448 kbps is the minimum bitrate required for transcoading...
That would be an urban myth.
So, there is no ETA on that release ?
No.
I'm beginning to think of making a fundraise to hire developers to deal with delayed and/or dying Xiph projects. Getting people paid will very likely speed up things.
Holy smokes, I thought Vorbis was dead... really. Like Duke Nukem Forever dead. This is great news & I'm really happy, I love Vorbis but I really have to ask myself, is it even relevant anymore? I'm not trolling at all, I have legitimate curiosity since the furor and intensity of the Vorbis community has pretty much dropped off the face of the earth... I mean, remember how much of a big deal it was when Unreal Tourney came out w/ Vorbis as the audio?? Does Vorbis still have a future in this sense? I'd really love to know what people's thoughts and opinions are about this.
What's the point of the doom and gloom? It's doing marvelously amongst our collective: http://www.hydrogenaudio.org/forums/index....showtopic=51493 (http://www.hydrogenaudio.org/forums/index.php?showtopic=51493)
And the last third party tunings/builds came out less than a year ago.
One can't expect to move mountains without the capital possessed by the AAC backers and yet Vorbis is still pulling ahead of them according to at least our nonscientific poll.
is there a way to optimise aotuv so that it can convert mp3 to vorbis easily without much loss?
No. That's totally out of scope of what the aoTuV tunnings do.
also, they say 448 kbps is the minimum bitrate required for transcoading...
That would be an urban myth.
So, there is no ETA on that release ?
No.
I'm beginning to think of making a fundraise to hire developers to deal with delayed and/or dying Xiph projects. Getting people paid will very likely speed up things.
1) know it... it it was already done everyone would be using ogg vorbis... I asked if its possible
2) Then what is the correct answer?
========================================================================
========================================================================
anyway, when will OggDropXPed with Vorbis 1.2 be released?
.......
anyway, when will OggDropXPed with Vorbis 1.2 be released?
It's been on Rarewares since 27 July!!
.......
anyway, when will OggDropXPed with Vorbis 1.2 be released?
It's been on Rarewares since 27 July!!
Wow! Didn't Realise that I was ignoring the version number
and does it include multichannel support?
.......
anyway, when will OggDropXPed with Vorbis 1.2 be released?
It's been on Rarewares since 27 July!!
Wow! Didn't Realise that I was ignoring the version number
and does it include multichannel support?
oggdropXPd and oggenc2 have both had correct multi-channel support since March 2006. ie., a correctly formed multi-channel input file will be encoded into the correct channel order according to the vorbis spec, and oggdropXPD and my own oggdec (from Rarewares) will decode generating the correct channel order and wave header on output.
oggdropXPD and my own oggdec (from Rarewares) will decode generating the correct channel order and wave header on output.
Did we not use the correct channel order patch in our oggdec, as well? I cannot remember.
Did we not use the correct channel order patch in our oggdec, as well? I cannot remember.
The principle problem is that the output wave file does not contain a WAVEFORMATEXTENSIBLE header so that the channel order can only be assumed rather than known.
then is it possible to transcode AC3 to either another 5.1 or a 2.1 or a 2 channel or a mono?
then is it possible to transcode AC3 to either another 5.1 or a 2.1 or a 2 channel or a mono?
Yes.
Is it(Oggenc2.83 using libVorbis v1.2.0) better than aoTuV b5?
A bit different question: does someone be able to merge vorbis 1.2.0 with aoTuV b5 tunings ?
Aoyumi!
I don't have the plan to merge beta5 and libvorbis 1.2.0.
It will happen by the upcoming version of aoTuV.
A new version of aoTuV would be much bigger news to me than a new version of Vorbis