Log in

View Full Version : CoreAAC updated!!!


Avish
23rd May 2006, 10:55
CoreAAC updated!!! Here is the link:
http://ffdshow.faireal.net/mirror/Misc/CoreAAC-1.2.0.575.exe

So What's New?:)

videomixer9
23rd May 2006, 12:11
New is that it crashes and doesn't solve the issues there were before with some files that some people already mentioned in the ffdshow thread as problematic. I wonder where celtic_druid took the sources from though as it seems to be svn revision tagged, only source I know is CVS only.

Avish
23rd May 2006, 15:48
New is that it crashes and doesn't solve the issues there were before with some files that some people already mentioned in the ffdshow thread as problematic. I wonder where celtic_druid took the sources from though as it seems to be svn revision tagged, only source I know is CVS only.
Hmmm.
Well... It haven't crashed on my pc yet!!

videomixer9
23rd May 2006, 17:00
Oh I meant that it crashes on the problem file. Try it yourself.

http://rapidshare.de/files/21190777/crash_coreaac.mkv.html

shon3i
23rd May 2006, 17:09
@videomixer9 can you upload somewhere else, because this fu**ing rapidshare have some restrictions, please, i want to what is problem because on my system this coreaac works fine in any case

videomixer9
23rd May 2006, 17:46
what's with all this people with shitty isps ... http://www.filepoint.de/download/4765-dl-crash_coreaac_mkv

however it crashed only due to reclock, however it still sounds borken.

clsid
23rd May 2006, 18:10
I get a nice bluescreen on my Win2k box when I play that file.

Happens with the new CoreAAC 1.2.0.575 and the older 1.2.0.573 and also with libfaad2 from ffdshow. No ReClock installed.

videomixer9
23rd May 2006, 18:19
you sure your soundhardware handles 96khz properly? after uninstalling reclock ffdshow played the sample fine unlike coreaac. mpc internal was also okay.

unmei
23rd May 2006, 18:44
is it even 96kHz? because both in the old 1.0b9 and this new coreAAC it plays for me without crash, but very slow.

It is signaled as A_AAC/MPEG2/LC/SBR in matroska with an output samplerate of 96kHz (up from 48) - but if i demux it to an AAC both winamp and foobar *as well as coreAAC* report it not as SBR, play it at 48kHz and it sounds perfect.

My guess is, the muxer wrongly muxed it as SBR. He might just have checked the SBR checkbox in mkvmegre gui without checking wether the file actually is SBR.

videomixer9
23rd May 2006, 19:02
Guess the automatic fixing of many others make CoreAAC fall into a trap here then.

Doom9
23rd May 2006, 19:29
@mods, how can I change thread title?Edit your post, change the title.. it'll update the thread title as well.

BetaBoy
23rd May 2006, 21:08
Sorry for the issues but dont point the fingers this way, as this is not an 'OFFICIAL' CoreAAC/CoreCodec release... in that if you browse our SVN nobody has commited any changes and Toff has not changed anything to the 1.xx code base recently. However this does not mean there has not been any libfaad changes made... and someone decided to do an unofficial release... if thats the case then, there you go ;-)

btw... We are finishing up work on CoreAAC V2.0 now with HE/SBR/LC support and hope to bundle it with CoreAVC Professional as soon as we QA it.

shon3i
23rd May 2006, 22:10
what's with all this people with shitty isps ... http://www.filepoint.de/download/4765-dl-crash_coreaac_mkv

however it crashed only due to reclock, however it still sounds borken.
This file on my machine sounds normaly without any error,about ip's i have firewall, proxy etc...

videomixer9
23rd May 2006, 22:32
so you create problems yourself just to bitch about it later and want the world to adjust to your self-crippling? even my university has no problems with rapidshare and they got firewall, packet filters installed etc. ...

SeeMoreDigital
23rd May 2006, 22:34
btw... We are finishing up work on CoreAAC V2.0 now with HE/SBR/LC support and hope to bundle it with CoreAVC Professional as soon as we QA it.Now that sounds more like a plan :)

shon3i
23rd May 2006, 22:43
so you create problems yourself just to bitch about it later and want the world to adjust to your self-crippling? even my university has no problems with rapidshare and they got firewall, packet filters installed etc. ...
Yes but i have proxy, because of this i have same ip and thousand other ppl's who have same provider like me, and rapid share not love proxy or same ip

videomixer9
23rd May 2006, 22:53
don't use the proxy? if it's forced the isp is not worth a cent, never heard of such an ISP though as customers would be prolly banned all around cause there is always someone getting IPs banned for some reason ... only thing may be lousy internet via umts/ev-do services.

CoreAAC 2.0 will be probably nice because libfaad2 seems to be kinda abondoned. Better include some error resistance though, the strategy with being doing exactly what upstream filters say seem to be not that good working.

shon3i
23rd May 2006, 23:09
don't use the proxy? if it's forced the isp is not worth a cent, never heard of such an ISP though as customers would be prolly banned all around cause there is always someone getting IPs banned for some reason ... only thing may be lousy internet via umts/ev-do services.Yes i know but i must use proxy because no proxy brandboard connection in my contry cost's 60% expensive than with proxy, and i alredy have problem with ban on HA.org forum. Someone is banned and i can't access to forum, and who know how many ppl's are banned.

CoreAAC 2.0 will be probably nice because libfaad2 seems to be kinda abondoned. Better include some error resistance though, the strategy with being doing exactly what upstream filters say seem to be not that good working.It will bi nice when come out

Kurth
24th May 2006, 05:58
Sorry for the issues but dont point the fingers this way, as this is not an 'OFFICIAL' CoreAAC/CoreCodec release... in that if you browse our SVN nobody has commited any changes and Toff has not changed anything to the 1.xx code base recently. However this does not mean there has not been any libfaad changes made... and someone decided to do an unofficial release... if thats the case then, there you go ;-)

btw... We are finishing up work on CoreAAC V2.0 now with HE/SBR/LC support and hope to bundle it with CoreAVC Professional as soon as we QA it.

Soo that means if I want to use CoreAAC 2.0 I have to buy the CoreAVC software ?

BetaBoy
24th May 2006, 06:18
At first yes.... in a few weeks we will offer it as a stand alone purchase as well as bundled with our upcoming 'Core Media!' directshow bundle.

celtic_druid
24th May 2006, 09:12
FILEVERSION 1,2,0,575
PRODUCTVERSION 1,2,0,575

http://corecodec.org/scm/cvsweb.php/CoreAAC/CoreAAC.rc?rev=1.6&contenttype=text/x-cvsweb-markup&cvsroot=coreaac
There were indeed some changes to faad.
http://faac.cvs.sourceforge.net/faac/faad2/libfaad/?sortby=date

So the reason I compiled it was to have a release with the latest libfaad. Plus I noticed that I had only 573 up, not 575.

I wonder if the next klite codec pack will all of a sudden contain 1.2.0.575?

bond
25th May 2006, 19:18
New is that it crashes and doesn't solve the issues there were before with some files that some people already mentioned in the ffdshow thread as problematic. I wonder where celtic_druid took the sources from though as it seems to be svn revision tagged, only source I know is CVS only.if you have found a bug in faad2 i am sure menno (the dev) would like to be informed about it (eg via the bug tracker on the faad2 sourceforge page or via hydrogenaudio)

Skelsgard
25th May 2006, 23:02
What about +6 channels decoding support (as in transcoding DTS-ES or decoded Dolby EX streams) in the new CoreAAC?

Adub
24th June 2006, 20:27
Is it just me, or does CoreAAC have trouble decoding aac audio in an Mkv container? The nonmuxed source plays perfectly, but when it is muxed with Megui or MKVmerge, it plays slightly faster than it should.

the older version played it supper slow, about 6fps, it sounded cool, but it wasn't really help full. I have tried changing the SBC/HE-AAC/AAC+ flag, and it doesn't change a thing. Anyone else have this problem? Anyone know how to fix it?

dk75
24th June 2006, 21:36
It's a probably problem with faad code. Use another decoder (like ffdshow but with RealAAC decoding routine).