It's one person (that I know of) that is member of this forum. But I suspect he's not alone working on the AAC encoder...... I bullied him already :B... He said he wouldn't mind including it in the encoder, but it doesn't depend only on him. It also depends on the QuickTime division, the iTunes division, the iPod division... For that reason, it'll probably only happen when a decision comes from above.
I have no idea who this person could be.
Multicore CPU is IMHO a very bad idea and direction. But CPU manufacturers had probably no other cheap solution on how to further increase power of their processors. If you want to use all cores at the same time in your encoder, you have to write it differently (much more complicated) compared to single thread encoder.
Does anyone have an idea of what Apple could have done wrong to cause an unlikely problem like this?
[...]I encoded one album (~1 hour long) with MP3 CBR 160 kbps:1 core: 3m 20s (= 200s)2 cores: 1m 57s (= 117s)The files have different comment tag, but identical audio content. With VBR, this isn't so:[...]
Some digging: http://developer.apple.com/quicktime/whatsnew.htm- "Multiprocessor (MP) Support" was added to QuickTime version 5- "VBR Sound Compression Support" was added in QuickTime version 6It's bad, that there seems to be no way to control the MP feature in QuickTime.
1 core 2 coresiTunes 184.108.40.206 135 137iTunes 220.127.116.11 194 119
Did that person say anything about which behavior is correct? I wouldn't be surprised if they would consider the single-core version broken and limit the amount of the bitrate variation.