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: QAAC: discussion, questions, feature requests, etc. (Read 592418 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: QAAC: discussion, questions, feature requests, etc.

Reply #1175 –
qtfiles(64), iTunes directory and Apple Application Support directory are prepended to PATH environment variable (in this order) in qaac process.
Other than that, DLL search order of qaac is pretty normal and like this:

  • Same folder as qaac64.exe (or qaac.exe).
  • Windows System32 (or SysWOW64) directory.
  • Windows directory.
  • qtfiles64(or qtfiles) directory next to qaac64.exe(or qaac.exe)
  • iTunes install directory specified in registry
  • Apple Application Support install directory specified in registry
  • Directories in PATH environment variable

Re: QAAC: discussion, questions, feature requests, etc.

Reply #1176 –
@for the developer

Hi,
i have a problem wich randomly happens to me with wich now i'm banging my head on, trying to solve (unsuccesfully).

I have an audio file wav (or flac no matter) 5.1 of lentgh 1:04:49.456.

When i compress with QAAC no matter what the options, i end up with a "pop / click" in the last part of the audio.
Opening in Audition i end up with a file of 1:04:49.485.
I've tried with a lenght of 1:04:49.478 and i end up again with a 1:04:49.485 (with pop click)

I'm pretty sure it's some problem regarding the length of the last audio frame.

Could you suggest me (while you analyze the problem) the right audio lenght to not make the "pop / clck" appear?

Here's the spectrum.

What's the problem?



Temporary Solution

Ok, as i was hypothizing it had to be a low level problem.
I remembered reading around in the discussion that QAAC uses a frame size of 1024,
so i thought that pheraps something in this particular file (remember the problem happens randomly)
was connected with the frame size that was giving problem with the encoding.

So, with delaycut i got the number of frames in the audio wav

186693888

I dived by 1024 and i got not an exact number (ha ha!).

186693888 / 1024  = 182318,25

With delaycut i calculated the exact frame count to give me an exact division

182319 * 1024 =    186694656

So my file had be of length of 186694656

The number of delay in delaycut that gave me that frame count was -16 ms

So i added -16ms to the wav, compress it with QAAC and voilà. No pop at the end.

So, having said so, could you implement a check and an (optional) autofixing to avoid the problem?
You could emit a warning before continuing encoding and an option to auto fix frame count
with anticipation or delaying.

Re: QAAC: discussion, questions, feature requests, etc.

Reply #1177 –
See here: https://developer.apple.com/library/archive/documentation/QuickTime/QTFF/QTFFAppenG/QTFFAppenG.html

From testing that I did, admittedly some time ago, it was apparent that most decoders do not cut the padding at the end of the aac data. The old Nero decoder was one that did perform correctly, from what I remember.

Re: QAAC: discussion, questions, feature requests, etc.

Reply #1178 –
Because of i cannot edit the post i give here the edit

Quote
So i added -16ms to the end of wav

Quote
an option to auto fix frame count
with adding or cutting at the end of file

@john33
Interesting informations thank you.