Well I've installed it and it appears to let you select VBR for any bitrate, not just 96-110 , 128-146 when encoding AAC using quicktime player. I can't really tell if it sounds any good though until my Etys get here.
Isn't there supposed to be a new version of iTunes in the Leopard preview as well?
Notice any differences? A major overhaul of iTunes (iTunes 7?) in a major overhaul of the underlying OS would be the ideal time to introduce things like HE-AAC support for instance...
Isn't there supposed to be a new version of iTunes in the Leopard preview as well?
Notice any differences? A major overhaul of iTunes (iTunes 7?) in a major overhaul of the underlying OS would be the ideal time to introduce things like HE-AAC support for instance...
If Apple are really serious about the iPhone they're going to have to support HE-AAC pretty soon for 3gpp support.
Isn't there supposed to be a new version of iTunes in the Leopard preview as well?
Notice any differences? A major overhaul of iTunes (iTunes 7?) in a major overhaul of the underlying OS would be the ideal time to introduce things like HE-AAC support for instance...
They usually don't update iTunes in tandem with OS updates, so the iTunes in Leopard is just the current one. QT is said to have received a rather major update though.
They usually don't update iTunes in tandem with OS updates, so the iTunes in Leopard is just the current one. QT is said to have received a rather major update though.
I know, usually. But now read this (http://www.hydrogenaudio.org/forums/index.php?showtopic=41278&st=28#).
For iTunes to play HE-AAC, Quicktime is the component that needs updating. You might see changes to iTunes to reflect the major changes in QT and you might not. That's why I'm asking.
They usually don't update iTunes in tandem with OS updates, so the iTunes in Leopard is just the current one. QT is said to have received a rather major update though.
I know, usually. But now read this (http://www.hydrogenaudio.org/forums/index.php?showtopic=41278&st=28#).
For iTunes to play HE-AAC, Quicktime is the component that needs updating. You might see changes to iTunes to reflect the major changes in QT and you might not. That's why I'm asking.
Well, as per online reports, Leopard includes iTunes 6.0.5 (current one). Whether or not the new QT includes HE-AAC I do not know. In any case, QT has often been updated with new features while iTunes hasn't. AAC VBR for instance, was long available in QT before they updated iTunes to take advantage of this. If the developer preview included HE-AAC I guess we'd hear about it by now. But it could of course be one of the new "secret" features
It'd be interesting if someone could post some new Leopard encodes of the problem sample you linked to though
It'd be interesting if someone could post some new Leopard encodes of the problem sample you linked to though
http://www.hydrogenaudio.org/forums/index....showtopic=47540 (http://www.hydrogenaudio.org/forums/index.php?showtopic=47540)
Also I just tested an HE-AAC file and it didn't seem to work...(played as 22khz, mono)
In any case, QT has often been updated with new features while iTunes hasn't. AAC VBR for instance, was long available in QT before they updated iTunes to take advantage of this.
Hhmm, I didn't know that.
Hmm, maybe I can clarify something.
First of all, Apple AAC codec along with other audio codecs are shipped as a component in Mac OS X, i.e., /System/Library/Components/AudioCodecs.component. Hence, its updates or releases are always tied up with those of Mac OS X. QuickTime and iTunes are just applications using the same AAC codec in Mac OS X. Their updates don't have a direct relationship with AAC codecs'. With the help of the SDK shipped with Mac OS X, everyone can develop his/her own applications using APIs to access Apple AAC codec, just like QuickTime or iTunes does. People can also use the command line tool, afconvert (built from /Developer/Examples/CoreAudio/Services/AudioFileTools/AudioFileTools.xcodeproj) to freely access the AudioCodecs (including AAC of course) to encode their favorite tracks.
A new AAC codec in Leopard (Mac OS X 10.5) is previewed in WWDC'06, as you have observed through QuickTime 7.2 (BTW, it's not 6.2). However, since it's just a preview, you can expect its performance, UI appearance in its applications or available features will be different in the final release whch is scheduled to due in the next spring.
You may also notice that FLAC (Free Lossless Audio Codec) also becomes available in the Leopard preview... not sure any application in the Leopard preview is using it though. However, you can certainly access it via APIs or the command line tool, afconvert.
Hope this helps.
You may also notice that FLAC (Free Lossless Audio Codec) also becomes available in the Leopard preview... not sure any application in the Leopard preview is using it though. However, you can certainly access it via APIs or the command line tool, afconvert.
Hope this helps.
FLAC support natively built into OS X? Am I reading this right? If so, it would be a boon to a lot of developers and users who have been seeking Macintosh FLAC supporting apps. Say it is so... Does Josh know about this? More info if you have it to confirm this feature please...
I heard that FLAC support in Quicktime was just demo'ed at WWDC.
Josh
That's great news Josh! I am so glad to see FLAC being recognized by larger companies (AOL wants FLAC natively in WinAmp, Apple now in Leopard, who's next Microsoft?). Keep up the good work Josh! FLAC 1.1.2 has been out now for almost 19 months (early Feb. 2005), and it has taken awhile, but the momentum is now building. Hopefully you can work with the WinAmp developers over their GPL issue to get FLAC included natively in WinAmp soon. Keep us updated on FLAC's progress please.
Is there anyway to run two instances of iTunes or Quicktime simultaneously?
Specifically I want to convert FLAC to iTunes AAC, but using two processes in order to make full use of my dual core CPU.
Is there anyway this can be done?
Is there anyway to run two instances of iTunes or Quicktime simultaneously?
Specifically I want to convert FLAC to iTunes AAC, but using two processes in order to make full use of my dual core CPU.
Is there anyway this can be done?
Use Max instead of iTunes to do the conversion. They both actually use Quicktime to do the conversion so are using the same codecs underneath. Max will automatically spawn as many encoding threads as they are processors in your machine. You can also set the number of threads manually if you wish I think.
http://sbooth.org/Max/ (http://sbooth.org/Max/)
Forgot to mention I'm on Windows...
Do you really need Apple AAC?
If not, try foobar with Nero AAC.
Do you really need Apple AAC?
If not, try foobar with Nero AAC.
I like using iTunes AAC, it seems to be pretty good quality.
From my testing, running two instances of NeroAAC via Foobar is about the same speed as one instance of iTunes AAC.
Well it is very marginally faster. I get about 20X real time running two instances of NeroAAC (10 times real time X 2 cores). Whereas iTunes AAC runs on my PC at around 18 - 19X.
Hence what I'd love is some way to run two instances of iTunes, so that I get 35 - 40 x real time.
Hopefully FLAC support will be integrated directly into iTunes, and the Quicktime encoder that iTunes calls will be modified in some way to be able to convert 2 songs at a time.
I mean rather than spending a heap of time optimising the encoder, it seems like a fast way to speed up the encoder is to simply let it create two instances to make use of dual core machines.
Forgot to mention I'm on Windows...
In that case you need Foobar 2000 and iTunesEncode (which is downloadable from rarewares).
Forgot to mention I'm on Windows...
In that case you need Foobar 2000 and iTunesEncode (which is downloadable from rarewares).
Since only one instance of iTunes can run at a time, it is impossible to get Foobar to encode more than one file at a time, which means it only makes use of one core.
In fact, I have found it necessary to set the affinity of Foobar2000 to one core, else Foobar tries to send two FLACs to iTunes, which results in an error. Something like "can not flush file"...
Guys, don't forget that this thread is about VBR AAC encoding with QuickTime 6.2 in Leopard (Mac OS X).
I suggest you post Foobar2000, NeroAAC, iTunesEncode and other Windows-application related support questions in a different thread!
Guys, don't forget that this thread is about VBR AAC encoding with QuickTime 6.2 in Leopard (Mac OS X).
I suggest you post Foobar2000, NeroAAC, iTunesEncode and other Windows-application related support questions in a different thread!
Since we're pseudo-modding anyway...
Could a mod perhaps change the topic title to state "Quicktime 7.2" instead of 6.2. Quicktime 7.2 is the version in Leopard while Quicktime 6.2 is over three years old.
Since only one instance of iTunes can run at a time, it is impossible to get Foobar to encode more than one file at a time, which means it only makes use of one core.
In fact, I have found it necessary to set the affinity of Foobar2000 to one core, else Foobar tries to send two FLACs to iTunes, which results in an error. Something like "can not flush file"...
Ah you want Windows and QuickTime AAC and SMP...you are out of luck them. On Mac OS Apple foot the licensing bill for the MPEG LA patents needed for MPEG Video and Audio encoding for all third party applications. Obviously Apple don't want to do this for Windows, therefore the codecs are only available to thirdparty applications on payment of a license fee to MPEG LA and receipt of a key from Apple to access the functionality.
This is why iTunesEncode was written in the first place as a gross hack to access the QuickTime AAC encoder without needing to pay a license fee to get at it via the QuickTime API. If you want to encode to AAC on Windows then the best route is probably the free Nero Digital encoder which is a standalone commandline executable of which you can run as many copies as you wish.
Presumably Ahead have paid the millions of dollars or whatever the extortionate fee is for a blanket license for all "shipped" copies of the encoder.
If you want to encode to AAC on Windows then the best route is probably the free Nero Digital encoder which is a standalone commandline executable of which you can run as many copies as you wish.
Presumably Ahead have payed the millions of dollars or whatever the extortionate fee is for a blanket license for all "shipped" copies of the encoder.
I believe they (Nero) have a blanket MPEG 4 patent license, and wrote the AAC code and MPEG video code the use themselves to avoid having to pay any additional royalties (other than the patent fees). Since Nero owns it owns code, it shouldn't have to pay someone else to use their copyrighted code for an encoder/decoder. At least that's what I believe, unless someone from Nero can correct me on this and edify us on their ownership of the AAC and MPEG 4 encoder/decoder code for audio and video.
Wow, great news on FLAC support in Leopard!
Since no one mentioned it, I assume no other Xiph format (like Vorbis and Theora) works under Leopard. Is my assumption right?
>I believe they (Nero) have a blanket MPEG 4 patent license, and wrote the AAC code and MPEG video
There is an upper cap for MPEG 4 royalties of $250,000, this allows Apple and Nero to effectively give encoders away for 'free'.
>I believe they (Nero) have a blanket MPEG 4 patent license, and wrote the AAC code and MPEG video
There is an upper cap for MPEG 4 royalties of $250,000, this allows Apple and Nero to effectively give encoders away for 'free'.
Is that
per year, or so long as they make a once off $250,000 payment then they never have to pay for MPEG4 royalties again?
It is per year.
If Apple are really serious about the iPhone they're going to have to support HE-AAC pretty soon for 3gpp support.
Quoting myself here - with the iPhone due in Q2, that would mean HE-AAC in Leopard/QT8/iTunes8 then?
I'd say it's likely HE-AAC is making its way to iTunes/iPod. Even without the iPhone there is a growing need because iTunes is losing more and more radiostations that switch to streaming with HE-AAC.
If Apple are really serious about the iPhone they're going to have to support HE-AAC pretty soon for 3gpp support.
Quoting myself here - with the iPhone due in Q2, that would mean HE-AAC in Leopard/QT8/iTunes8 then?
I really doubt it. HE-AAC support would be nice since the iPhone has capacities of 4GB and 8GB but I doubt Apple will add HE-AAC support. If they haven't already done it for the iPod mini, 1G iPod shuffle, 1G iPod nano, 2G iPod shuffle, or 2G iPod nano users, then I doubt Apple will ever add HE-AAC support. If the iPhone was 1GB or less then I can see the necessity of using this format. I guess it is harder for them to justify HE-AAC support (and the ability to encode to HE-AAC) when their iPhone supports 4GB (~1000 songs at 128kbps AAC) and 8GB (~2000 songs at 128kbps AAC).
I guess we all know by now that QT doesn't play FLAC files under Leopard, either.
What a surprise...
I guess we all know by now that QT doesn't play FLAC files under Leopard, either.
What a surprise...
Which gets all the more absurd as anno 2007, every $30 mobile phone now plays HE-AAC (as it's in the 3GP mobile video standard) while the most expensive phone on the market cannot play it. I guess Apple sent the whole Quicktime team on holiday in 2004, the last major improvement in Quicktime (H.264 support) was added with Panther.