11
AAC / Re: QAAC on Windows 11
Last post by nu774 -Actually, I have both versions of the PDB files, so I disassembled them using dumpbin.exe and compared the machine code of the functions in both versions, but there were no differences.
On peak scanning, every sample is casted to double and then absolute value is computedBut that did not change from 2.83 to 2.84, or did it?
I think i may have found the problem. In advanced settings, Fast DSP reset when cycling tracks manually was checked. When changing songs now, every song has a ReplayGain DSP entry in the console and seems to be working correctly. I apologise for not being more thorough before reporting an issue.That is a good find and I apologise for not knowing it to cause this kind of behavior. I vaguely remember Peter explaining how the feature worked but it had slipped my mind.
I do still experiance several hundred milliseconds delay before each track is played. Im wondering if this could be due to Minibar scanning the waveform beforehand?Minibar scanning is performed in another thread so it doesn't delay the DSP processing. But over here Minibar scanning seems to introduce 1-6 millisecond delay for the DSP notification message based on quick tests. You have also lyrics stuff going on during track change, perhaps that causes a longer delay. If it works in main thread it probably causes a delay for the console message arrival, but again, it won't delay the DSP processing itself.
Is there a way (plugin/dsp or else) to apply a decent Replaygain value when using streams?If a stream uses a constant loudness level you should be able to manually configure appropriate ReplayGain values to it with foo_external_tags and possibly with the M-Tags component.
How did I "match" 7 other rips, but sometimes, get errors for that particular track? Is this some kind of copyright protection?More likely a flaw on the CD where the drive reads one area 2 or 3 different ways consistently. I've had several CDs like this.In addition, I'm still a little confused why some tracks have -12 offset. Does that mean my rip has SOME songs with 12 added bits of silence to them compared to most rips?
The CUETools result DOES NOT show any tracks with -12 offset. It does show you there's another pressing in the database that is offsetted by -12.
You're just misinterpreting the foobar2000 result. It is not telling you the track has an offset. It's telling you it found the highest confidence for a pressing that is offset from your rip by -12.