And this is really difficult to fix, since it would require a full CD image file, and a scanner that can be told to check the beginning of the image file, before it seeks to the specified offset for the CUE sheet.
How many HDCD signal packets are encoded in the first track?
My component ignores any files with less than two consecutive packets.
Ah, my bad. It's not two consecutive chunks. It needs to still be enabled after a minimum of two chunks of audio and ten seconds.
Note that in a real HDCD player, after the requisite timer from a single packet counts down, the HDCD effect shuts off.
Gain is not applied globally. Gain is reported by every packet, and last I checked that album, it has a gain of -4 for about a second, then ramps up to 0 for the remainder of the album.
Clearly, the fade is shorter than the requisite 10 seconds my decoder needs to warm up. Maybe I should eliminate the warm up period, so we can get a lot more false positives.
As I said, it detects it at all, but it doesn't do any processing unless it detects it for a full 10 seconds and a minimum of two audio_chunks from the input.
(Why not let foo_hdcd observe a HDCD tag to be set to "yes"?)
1) No. ReplayGain is applied after this plugin decodes the signal.2) Dynamically applied metadata will reflect the HDCD mode and its properties.
Yeah, sure, I'll get right on that, as soon as there's a library for it that doesn't have an evil license. Last I checked, there's only one library, usually bundled with things like Tidal, and it requires that the audio go directly to a DAC, and not any digital output, or to any other process where the decoded data can be read or logged or processed further.