- are these options required for movies audio? --rate keep, --adts, --no-delay, --no-optimize (I even saw a --limiter?)
- when is --ignorelength - used? Whith piped .WAV input?
options are they different to encode stereo, 5.1, downmix stereo, etc channels? Or from different types of DTS (ES, HDMA, etc)?
Fix: Was failing encoding mono AAC to AAC. Support Wavpack v5 interface (with large file support) Wavpack version 5 is still in alpha state, and DLL is not officially provided. If you want to try it, you have to build it yourself from the source code.This version of qaac supports both of old and new Wavpack DLL (they are binary compatible). When new functions provided in version 5 library are detected, qaac will use them.
Just out of curiosity:Why is qaac's output directed to stderr when you supply --check as parameter?(other messages like help screen goes to stdout...)
qaac 2>&1 | more
First converting the FLAC file to a tag-less WAV, and then again to an AAC file with tags given on the command line works, but is a slower, two-stage process. I imagine it would be easy to add an option to ignore any tags in the source file and only use those provided on the command line.Is there an easy way to do this in qaac?
@nu774:According to QAAC's wiki it is save to use --normalize with aac/mp4, although that may result in samples above 0dbFS.Did I understand that correctly? Or is an additional --limiter recommended? And how much is "near 0dbFS", where the limiter is activated?edit: Just did a quick test (with 4 mp3 files being concatenated to one mp4 file) with --normalize alone and together with --limiter.Both mp4 files had peaks above 0dbFS (1.044) when checked with foobar's replaygain scanner...
Changed 7.1ch rear channel layout in favor of Apple QuickTime.qaac was using 3 front + 2 side + 2 back for 7.1ch rear output. However, it turned out that Apple QuickTime cannot handle this, and only recognizes 3 front + 4 back.
Channel(s) : 8 channelsChannel positions : Front: L C R, Side: L R, Back: L R, LFE
Channel(s) : 8 channelsChannel positions : Front: L C R, Side: 4, LFE
In my PC, MediaInfo reports like this for 2.60:Code: [Select]Channel(s) : 8 channelsChannel positions : Front: L C R, Side: 4, LFE
What is diffrent (in 2.60) is how channel layout is described in the AAC program config element, where channels are described in a completely different manner compared to WAV's channel mask.
[qaac] release 2.61posted 16 minutes ago by nu 774Fix 7.1ch PCE: was incorrectly writing object_type(2) instead of profile(1). AFAIK, this doesn't seem to actually affect decoders because decoders are only interested in channel layouts in PCE, but still it was incorrect, and should be fixed.
Encoding a wav FL,FR,FC,LF,BL,BR,SL,SR to .aac with qaac 2.60 and decoded by itself we obtain a wav FC,FL,FR,FC,SL,SR,BL,BR,LFOthers decoders have also problems with qaac 2.60: http://forum.doom9.org/showthread.php?p=1782018#post1782018
Thanks, I noticed one issue in 7.1ch PCE and released 2.61 just now. However, this release wouldn't fix your problem.
Because of complexity and too much of flexibility in the PCE based channel configuration, poor handling in the decoder side is to be expected, and there's nothing I can do for it.