Why does HDCD encoder spend so much time on non-HDCD recordings?

[Porcus]

Not sure where to put this subject, chose the "beta" forum because of possible bug.

I have noticed that CD Ripper spends a lot of time at 0% encoding (and no, it doesn't then for sudden jump to say 40% ...). A bit of testing reveals that this is due to me having enabled the HDCD DSP -- turn that off, and the delay disappears.

But my CDs are not flagged as HDCD under "Track Technical"! I only have a very few of those, and yes I tried a few now I became aware of the delay.

So what is the issue? The HDCD DSP should not do anything to non-HDCDs. But nevertheless, it spends lots of time apparently doing some processing. For example, a certain 10 minute track took 35 seconds ripping (last on CD and in AR, quick), 55 seconds waiting at 0%, then 25 seconds completing encoding to FLAC. Another 12 minutes track spent > 2 minutes waiting at 0%, while only half a minute encoding. A third track confirms the pattern.

[Spoon]

Re: Why does HDCD encoder spend so much time on non-HDCD recordings?

For it to work a temporary wave file must be written, so encoding is done after (normal ripping will encode whilst ripping).

[Porcus]

Re: Why does HDCD encoder spend so much time on non-HDCD recordings?

For it to work a temporary wave file must be written

Wishlist: turn that off if there is no HDCD.

(normal ripping will encode whilst ripping).

... not in Ultra-Secure, right?

[Spoon]

Re: Why does HDCD encoder spend so much time on non-HDCD recordings?

Utrasecure uses memory rather than wav files.