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: qtaacenc: a command-line QuickTime AAC encoder for Windows (Read 409093 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #227 –
Read post #1 for the link.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #231 –
There was a DNS update mistake on the hosting server. Wait for a few days until the update is reflected in your DNS server or try different DNS servers (at least google DNS should work).

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #232 –
Hi,

I wonder it can add encode settings into AAC Tag?

Like lame mp3:
Quote
Audio
Format                          : MPEG Audio
Format version                  : Version 1
Format profile                  : Layer 3
Mode                            : Joint stereo
Duration                        : 1mn 9s
Bit rate mode                    : Variable
Bit rate                        : 234 Kbps
Minimum bit rate                : 32.0 Kbps
Channel(s)                      : 2 channels
Sampling rate                    : 48.0 KHz
Compression mode                : Lossy
Stream size                      : 1.94 MiB (100%)
Writing library                  : LAME3.98r
Encoding settings                : -m j -V 4 -q 0 -lowpass 17.5 --vbr-new -b 32


I tried "--compilation" in qtaacenc, but it seems not work
Quote
Audio
ID                              : 1
Format                          : AAC
Format/Info                      : Advanced Audio Codec
Format profile                  : LC
Codec ID                        : 40
Duration                        : 1mn 9s
Bit rate mode                    : Variable
Bit rate                        : 159 Kbps
Maximum bit rate                : 177 Kbps
Channel(s)                      : 2 channels
Channel positions                : Front: L R
Sampling rate                    : 48.0 KHz
Compression mode                : Lossy
Stream size                      : 1.32 MiB (98%)
Language                        : English
Encoded date                    : UTC 2011-04-18 05:01:44
Tagged date                      : UTC 2011-04-18 05:01:45


Is it the AAC's limitation?
Excuse me for my poor English...

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #233 –
Quote from: upyzl on
I wonder it can add encode settings into AAC Tag?

Is it the AAC's limitation?


AAC has no tagging capability. The tags are in the MP4 container. So whatever you are using to read out that file must support that.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #234 –
@Garf
Thank you.

I have to say that's a pity...
Excuse me for my poor English...

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #235 –
I was feeling a feeling a little paranoid recently that I was "missing something" by using qtaacenc with QT Lite, so I uninstalled QT Lite and installed the official QuickTime software. Then I upgraded to QuickTime Pro with an old serial I had around.

The output files for QT Lite [version 4.1.0], QuickTime, and QuickTime Pro [version 7.6.9] were exactly the same. Yes, I actually encoded from FLAC three times for several albums. This result was to be expected, but I had to make sure.

So if you want to use QT Lite instead, it does work. And the bonuses for using it are no start-up entries and it saves a little bit of hard drive space.
 

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #236 –
Channels have the wrong sequence.

http://rghost.ru/5662311

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #237 –
There is another project, qaac:

Quote
I found that in the recent version of QuickTime (at least for 7.6.9), QuickTime's channel mapping behavior seems to be BROKEN or at least CHANGED


http://sites.google.com/site/qaacpage/news...elaudioencoding
http://sites.google.com/site/qaacpage/news...ltichannelaudio
http://sites.google.com/site/qaacpage/news...channelmapping2
http://sites.google.com/site/qaacpage/news/aboutquicktime77

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #238 –
I was a bit slow in copying quotes from the qaac site. lvqcl already posted the essential content of my reply. 

However, here is my reply as I intended to post it. I hope someone will report the problem to Apple (assuming it is reproducible by using QuickTime Pro directly).
______________________________________________________

Quote from: CWP on
Channels have the wrong sequence. ...

The qaac developer has found the problem to be caused by a bug or change in QuickTime (qaac is a similar program to qtaacenc).

From http://sites.google.com/site/qaacpage/news
Quote
[qaac] Don't use for multi channel audio encoding
posted Jan 26, 2011 5:04 PM by nu 774  [ updated Jan 27, 2011 6:03 AM ]

I found that in the recent version of QuickTime (at least for 7.6.9), QuickTime's channel mapping behavior seems to be BROKEN or at least CHANGED, therefore qaac produces wrongly mapped output.

I'm sorry, but I don't know the exact QuickTime version which causes this. At least it worked properly on 7.6.5 and 7.6.6, and broken on 7.6.9. If you know something about this, please let me know.

For now, please don't encode multichannel sources with qaac, until this will be fixed, and unless you are using working version of QuickTime. Ordinary 2ch stereo encoding is OK.

Technically, when you feed multichannel source with standard MPEG order (like L R C LFE Ls Rs), qaac just pass it to QT encoder as it is, and just tell QuickTime the order (like kAudioChannelLayoutTag_MPEG_5_1_A). Then, QT AAC encoder nicely re-mapped it into AAC order (in this case, C L R Ls Rs LFE).

But now, this remapping feature by QT AAC encoder seems to be broken, or at least behaves differently.

[qaac] follow-up report about multichannel audio
posted Jan 28, 2011 11:29 AM by nu 774

I downloaded older version of QuickTime from oldapps.com, and tested each of them.

The result was, version up to 7.6.8 is OK. Only the newest version 7.6.9 is broken with AAC channel mapping. I have reported this to Apple with Apple BugReporter.

For now, I recommend you to use versions before 7.6.8, if multichannel encoding matters to you.

follow up about AAC channel mapping: 2
posted Jan 31, 2011 5:17 AM by nu 774  [ updated Feb 5, 2011 12:27 PM ]

I found the channel mapping problem was brought by CoreAudioToolbox.dll, version 7.9.4.

Strictly speaking, this is not a QuickTime component, but is one of "Apple Application Support" components, which is installed under "C:/Program Files/Common Files/Apple/Apple Application Support".

Upon QuickTime 7.6.9 installation, by simply replacing this dll with older version, channel mapping problem was fixed and everything seemed to be working properly (QuickTime 7.6.8 package contains CoreAudioToolBox version 7.9.3).
Though I don't recommend you to do this, if you don't know what you are doing.

I don't know if Apple is aware of the problem. I also don't know if using the older CoreAudioToolbox.dll file can affect the encoding quality or other properties of the resulting files anyhow.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #239 –
I just noticed the following in the above quote:
"I have reported this to Apple with Apple BugReporter."

I hope Apple will fix the problem soon.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #240 –
lvqcl, Alex B

Thanks...

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #241 –
I pass mono 16b 44KHz WAV to encoder but it produces stereo file. I don't see any option in command line help or elsewhere how to keep channel as is. Is there such possibility?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #242 –
Is it possible to make mono AAC file with iTunes or QuickTime player?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #243 –
If you are asking me, I have no idea as I don't need iTunes to run this encoder, and free version of QT does not allow me to check your question, so I'll assume that's not possible

But I might be wrong that way, as I remember that QT can export mono AIFF, but can't tell about MP4

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #244 –
Thanks for the qtaacenc!  I have a bunch of audio files that need to be encoded with QuickTime AAC encoder.  You just made my work a little easier!

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #245 –
After upgrading Quicktime to 7.7 qtaacenc crashes at the end of the encoding when output folder contains non-ascii characters (at least cyrillic).

My debug compile of qtaacenc stops at "QTNewDataReferenceFromFullPathCFString(outFile, kQTNativeDefaultPathStyle, 0, &outDataRef, &outDataRefType)" line in convertToMP4PathThrough() function.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #246 –
Thanks for the report. New version is available now.
I don't know why this happens, but as a workaround I've fixed it by using the temp directory.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #247 –
after upgrading to quicktime 7.7, I can't encode wav to aac in foobar2000.  cmd.exe works fine, but with the exact same options, fb2k fails.  this is qtaacenc version 20110806 and 20110414...

options (command line):
Code: [Select]
qtaacenc.exe --highest --ignorelength --quiet --tvbr 127 track01.cdda.wav track01.m4a

this works.

options (foobar2000):
Code: [Select]
--highest --ignorelength --quiet --tvbr 127 - %d

Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #248 –
Thanks nao, it works.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #249 –
I apparently just needed to restart foobar2000.

sorry for the erroneous report.