Wednesday, July 15, 2020

Avoid Jumping to False Conclusions

To get the 140 Hz crossover producing a decent RTA, I had added a 7dB boost at 174 Hz in the sub response.  I figured this was "OK" because of the 140 Hz crossover, certainly by 174 Hz the crossover was already applying more than 7dB of attenuation, this was just providing a bit of boost in this region where the sub itself was starting to roll off, but not hugely rolled off yet.

But when I was listening to the Saturday night program featuring local concert performances called Performance Saturday on KPAC, announcer Nathan Cone's voice seemed to have a lot of added upper bass delayed resonance.  The kind you might imagine, say, from a 1930's large cabinet radio.

OK, I immediately figured this had to do with the boost.  So I dialed back the boost, and re-listened to the radio program I had recorded digitally from my FM radio onto my Marantz state recorder.  (Pity me having to listen to the preceding 5 minutes of music over and over for these tests--marvelous music--but anything gets tiring in a situation like this.)

I thought it sounded better, but the upper bass resonance had NOT entirely gone away.

I tried it with the boost again.  I thought it was worse again, but now it was getting really hard to tell. That's the way it goes, for me, with A/B audio tests.  If I even listen to B at all, I start getting confused, and by the time I've listened to A/B/A, I am really confused.

When I just want to move forwards with something I know is an objective improvement, I don't bother trying to do an A/B test at all.  I just set up B--which often takes awhile--and start listening to it.  Days later, if there's clearly something wrong with B, I may go back to A or try to move on to some further refinement of B which is C.  And so on.

I find listening tests so inconclusive I don't put much faith in them.  I'd also hate to predjudice my judgement against what is likely to be a step forwards with a quick but possibly false snap judgement against it.  But I've known people who take the opposite stance, intended to do A/B/A  test, but finding B so much clearly better they don't need to go back.  Just forwards.  I find that very suspicious actually.  Strong result claims need better, not lesser, validation.

Anyway, as I was dialing back the A, I noticed something.  As part of the previous day's testing, I had never re-enabled the midrange EQ on one channel.  It was bypassed.  I completed the A/B/A test sequence anyway, which I felt had some internal validity even if the conditions were way off.

Then I went back to re-enable the midrange EQ, and I noticed something else.  I had never restored the 140 Hz crossover for the subwoofer, I had left it with the 300 Hz crossover I had dialed in for testing purposes.

It was THAT which had distorted the sound of Nathan Cone's voice the most.

What may be happening in the subwoofer as the frequency rises above 160 Hz or so, the subwoofer's 13 inch cone starts becoming directional.  It measures fairly flat to 300 Hz...but only on-axis.  Of axis, the increasing directionality means that midbass in that region is less radiated toward the listening position, but more towards a wall reflection.

Well, that's another theory I have but not really well established yet.

But concluding the boost was THE problem was wrong.  It's even hard to know how much it was a factor.  I generally don't like to boost anyway, but it's unclear how much bad this experience shows it to be a problem.  I could have just been mistaken.

I have often found longstanding "conclusions" to have been caused by some mistake, exactly like this, but sometimes long after.

For that reason, things would need to be tested and retested for firm conclusions.  I avoid that problem by resisting firm conclusions generally, especially in things that don't make sense to me.


Saturday, July 11, 2020

Emotiva Stealth DC-1

I bought three more of these Emotiva DACs after I found that my first one measured far better than all my dual differential 1704 based DACs.  As I recall, it measured 0.0003% distortion, which is identical or better than my Juli@ measurement card itself in loopback, so the Emotiva might even be better than that.  I needed 4 identical DACs with AES inputs and Balanced outputs and level control, so these inexpensive Emotiva DACs fit the ticket at a reasonable price.  They have always sounded sweet and pure to me.

I was shocked to see bad things written about this DAC after that.

  But now I go back to the original ASR review, and in fact it's pretty actually pretty good, beats the highly touted original Topping DX7 in THD but not linearity.  It would get a 2dB better SINAD score than the DX7.  It has other unimportant issues, like an -104dB idle tone at 17kHz with USB input playing J-Test.  Amir rightfully dismisses this as audibly unimportant, though not a good sign.

Elsewhere, and possibly at ASR,  I read something worrisome about a grounding issue and running rather hot.  I had to cancel a ground loop by plugging the Emotiva into the same circuit as my Amplifier...suggesting it IS grounded, but may lack isolation through the AES input which a professional unit should have.

Because of heat, I avoid stacking them, and in the one case I do, I use 3 rubber feet to separate them.

There are complains of failures at ASR, but I have had my original unit over 5 years, and no problems.

I continue to think about upgrading to the latest Topping, a D90 would be unequivocally better (unlike the DX7) but it hardly seems worth it for likely inaudible improvements, and I have more important things to think about.


Friday, July 10, 2020

Looking at individual drivers

I had reached the conclusion the dips in the left channel midbass response starting at 180 Hz are occurring because the subwoofer doesn't have flat response to there.  Measurements below show I was mostly correct, but as usual, the story is a bit more complicated.  The panels do also have a bit of relative difference, with the right channel actually peaking at 180 Hz, cancelling some of the sub dip there.  It does appear like the subs might have enough response to work more or less OK at 140 Hz with a steeper crossover like LR48, which I am pondering.  Whereas if I move the crossover any lower, I might expose the panel cancellation at 110 Hz, which a 140 Hz crossover mostly but not entirely suppresses.

The measurements I made today are not necessarily the quietest.  It is 106F outside and my air conditioner is running near its top speeds.  I decided to leave it running, and just accept that as a given.  The rough range of the subwoofer response should be apparent anyway.  There are some slightly audible tonalities in the operation of the air conditioner, but they do not appear to introduce any notable spikes in a background noise measurement.



Here is the left channel sub (and supertweeter) without any EQ.  Notice the large dip below 140 Hz, and especially at 180 Hz.



Here is the left sub with all the current EQ dialed in.  Notably I have significantly suppressed but not eliminated the dip.  This is with 5.5dB of boost at 174 Hz, and I wouldn't feel safe dialing much more in.  The dip at 225 followed by a huge peak just above is very tricky to fix with EQ, though I could probably suppress the peak without making the dip too much lower.


The right channel subwoofer with EQ is similar at low frequencies but does not have the boost at 180 Hz, therefore 180 Hz is down but about 40% less than in the left channel without EQ.  This seems to explain some but not all of the difference at 180 Hz the combined responses of both channels.  Note also it has no peak at 225, only higher at 260.


Some of the remaining difference might be caused by the Acoustat response.  Here is the left channel Acoustat response, with EQ, with the super tweeters turned off, but no crossovers (which does not make an easily visible difference at high frequencies).  There is just a tiny dip at 180 Hz compared to the surrounding frequencies, though in the midst of the second highest plateau.



With the current panel EQ turned back on, there is very little difference there but you can tell the unmitigated peak at 4kHz right where Linkwitz calls for a dip.  I think this could be the error that kept the Acoustat from becoming a market leader, instead of being displaced by Martin Logan and Sanders.  This is somewhat tuneable with the HF level control, but not without making it less flat higher up.  I keep the HF level control nearly perfectly centered.  The Absolute Sound had the temerity to criticize the sound of the Acoustat 2+2, which could still be considered a feat of modern engineering, that perhaps lowlifes like me dare not criticize--it's far more amazing as a total package than anything I have come up with, and probably ever will.  But, there may have been some truth in TAS whining.  If Strickland could just have been persuaded to make it just a bit better sounding somehow, with a little nicer tuning of the response.  The speaker sounds "coarse" like sandpaper playing pink noise without EQ, with EQ it sounds smooth despite the slighly more irregular looking response curve.  The excess output with no EQ is centered right at the 6kHz "metallic" range.  I concede my "smoothing" may not yet be perfected...and perhaps it's even "too smooth" sounding, once again proving you can't naively judge sound from the response curve picture.



Here is the right channel channel Acoustat with EQ.  Notice there is actually a slight peak at 180 Hz, helping reduce the dip in the combined response on the right.


Here is the right channel Acoustat response with no EQ.  Notice again the peaking from 4-8 kHz which I have imperfectly (but simply) reduced with EQ above.


The New Crossover Frequency

In the last episode, I determined that the 100 Hz crossover frequency between the SVS subwoofers and the Acoustat panels was too low, because front wall cancellation reflections appear to be centered around 110 Hz or so.  (One friend wants me to investigate the reflections further, from multiple angles, etc., but I'm satisfied my story is essentially correct.  100 Hz can't and won't work.)

Early indications were a crossover frequency of 140 Hz might work.  I first set up a highpass at 147, but a lowpass remaining at 100 because it seemed to have an approximate 140 Hz acoustic rolloff anyway.

I was troubled by that assymmetry for various reasons.  When I ultimately go to linear phase crossovers, such an approach might not work at all.  And even more immediately, it seemed that I was still suffering a depression around 100 Hz anyway, just like before.

I was thinking of setting up my fancier measurement rig with calibrated microphone and ARTA to first do a full analysis of the subwoofer response, and the panel response, and find the exact best crossover frequency from that.

But instead, after a day of distraction, I decided to go ahead and try setting both sides to 140 Hz, with normal 24dB/octave, and see how that worked.

And of course, once I had done that, I couldn't help but keep fiddling with parametric EQ's on the subwoofer side to get it straightened out.

(Plot spoiler: I looks indeed like I will have to go back and determine the actual Subwoofer response after all, because it seems to be a factor in how the 140 Hz crossover works.  There is considerable weakness around 180 Hz which may be caused by subwoofer already starting to roll off where the crossover is still expecting some output from the sub side.  Curiously this only seems to happen in the left channel.  I'm thinking the left subwoofer, which is very hard to get behind, may have some sort of internal crossover enabled which is interfering with my attempt to do a good 140 Hz crossover.  This needs to be checked by playing the sub with a much higher crossover like 300 Hz.  In past experience, it's not good to play pink noise full range into my SVS without any subwoofer.  That generates scary sounding noises that make you wonder if the subwoofer isn't going to self destruct.  So it needs some crossover, or some other way of ensuring that all testing is below about 300 Hz.)

After first setting up 140 Hz for both the panels and the subs in my miniDSP OpenDRC's I measured what looked like much higher bass than before:




My first impression was that the subwoofer level was too high.  (I had long suspected this.)  But I quickly took a look at the sub response by itself,  but with the 140 Hz crossover enabled).  That looked like this:




That looked like there might be some peaking at 140 Hz, but not enough to explain the huge bulge at 140 Hz.  So I turned the sub level down and down.  From -3dB to -13dB.  That looked a little flatter, but there was still that peak at 140 Hz!  If I remembered correctly, I already had a big cut there.  At that point, not remembering that I had an hour earlier turned down all the PEQ's above 90 Hz on the principle this would be a whole new EQ game because of the new crossover, and I'd best start from scratch.  As a result of that memory failure, I started with a huge sub level change rather than first restoring the old EQ's.  With a 10dB reduction, the last LF plateau around 32 Hz was clearly lower than the 18kHz peak on top, and generally I like those more-or-less at the same level, intuitively and otherwise (though the true HF response is not revealed by these or any other measurements I have yet done, and on ARTA with my calibrated mike the HF peak appears to be about 15dB higher, which I think partly has to do with my cal microphone's lack of omnidirectionality at those frequencies, or some such factor, even perhaps the way the software works.  I think for an RTA long term average type response, it's hard to beat the iPhone running the  RTA app I have, and the iPhone simulates a true omnidirectional microphone response with two microphones and sophisticated internal processing.)

Finally I realized I had previously zeroed out the 125 Hz notch and even a 105 Hz notch I had zeroed out last week or before, but left in the PEQ list set to 0dB.  I actually took the time to run the oscillator and retune all 3 points.  And then back to the RTA and back to the oscillator.  I slowly raised the subwoofer level as seemed to work best, but not back to the original -3dB which may indeed have been too high.

(Having the sub level too high, or a substantial "room curve," is very destructive to transparency across the audio range, and also limits dynamic range.  You can't turn the level up too far without everything in your house rattling, or even the sub itself sounding off, on very bassy music.  You can sort of make a too high level work by having deep notches at the room modes.  Or you can lower the sub level and use less-deep notches.  It's never exactly clear where the optimal point is between deeper notches vs lower sub level.)

Finally, after endless adjustment, I got to this:


The deepest bass up to just pass 125 Hz is as flatter and nicer than it has ever been.  There is zero notch at 100 Hz, though a slight depression that includes 90 Hz.  But look, now there are some too-large depressions starting at 160 Hz, and also just above 250 Hz, that I didn't recall from before.  I tried fixing the lower one with as much as 7dB boost at 170 Hz without much success.  If I remember correctly, the measurement above is the one with the boost already added, it looked even worse before.  I figure the boost is OK because at 140 Hz response is already rolled off by 6dB by the 140 Hz crossover, and the fairly high q peak I'm adding at 170 Hz doesn't much extend that low.  I generally have more headroom in the bass too, meanwhile the midrange headroom is deliberately limited so as not to waste digital dynamic range and "information"...it's always playing close to 0dB.
(This kind of tradeoff is called "gain structure.")

Still, even with the boost, I'm not happy with this response as it looks.  I think it sounds OK, with much punchier bass than before, and the pair of lower midrange depressions aren't immediately obvious to me.  On oscillator sweeps they don't sound so much like the null at 110 Hz I was aiming to eliminate with these changes, they sweep better than they look in the RTA.

Tuesday, July 7, 2020

Opening more cans of worms

At the end of my last week-long session of Time Alignment using ARTA, I made a list of future improvements to put ahead of expriments with linear phase crossovers.

During that "Time Alignment" I also made some adjustments to the bass in the left channel, using only ARTA as a tool.  Now ARTA is very good in many ways, but relying only on one kind of measurement to make important adjustments is like trying to map a mountain from one picture window view.

It disturbed me since than that I had probably reduced the bass too much to make it look flat in the ARTA measurement.  This seemed to be confirmed when I did my first new iPhone measurements on Sunday July 5.  But then I realized I had the weighting switched to A.  I switched it to C to make this measurement (though it's actually better if I use "Flat" which is an option in this app, and I remembered to use Flat for all measurements after this one):

Left Channel, as last adjusted using ARTA

The bass below 63 Hz was rolled off more than it appears here.  I brought out my oscillator and resumed doing hand sweeps.  It was clear the left channel was audibly lower at 30 Hz and below especially, which seemed to almost disappear.

That was relatively easy to correct simply by dialing back a little the cuts I had made when using ARTA.  I experimented with changing the position of the wide 3/4 octave cut, there really seem to be two separate resonances involved in addition to a broad area of excess (without EQ).  But I finally left the low EQ frequency more-or-less unchanged, because if I set it precisely to the center of the lower resonance, it tends to cut the lowest frequencies too much.  So it's at a compromise frequency that works for both resonances AND the whole area pretty well, as currently adjusted.

But I became more and more bothered by the apparent notch at 100 Hz in the 6th octave RTA.  I'd "worked" that a little bit before and it seemed fairly intractible.  I tried, tried, and tried some more.

I reduced and even eliminated the numerous EQ cuts below and above 100 Hz.  That didn't remove the problem, though with a bunch of EQ changes it seemed to be a bit better.  Here I was using both hand sweeping the oscillator, AND the RTA app.)  Sometimes.  It was sounding nearly OK on the hand sweeps.  But not really enough better on the RTA, in fact making the surrounding regions more level with more finely tuned EQ seemed to make the notch at 100 Hz look worse.

Left Channel, after raising low bass and fine tuning EQ's around 100 Hz


Clearly something bad is going on right around 100 Hz, which is also the crossover frequency.  And clearly it has nothing to do with the EQ's I am applying nearby.

I first tried to get a handle on this by looking just at the bass response, which I figured was a factor:


There is a very little tiny dip around 100Hz, though it's hard to pay much attention to that when other things are not looking good.  (BTW, the I left the supertweeters on for these measurements.)  For one thing, the crossover doesn't seem to be really crossing over at 100 Hz, more like 140 Hz, and that's with two big notches dialed in to the subwoofer response above 100 Hz already.

I tried to do some more adjustments to fix the 100 Hz dip anyway, but nothing did much good.  I began to determine that the 100 Hz dip in the sub response is caused by a room mode.  When I've dialed in the frequency at maximum notch cancellation, I can walk around the room and the response varies enormously, going from way too much to just the little dip shown here at the listening position.

That's significant, but really not that bad.  A bigger problem must be elsewhere, notably in the Acoustat response (as rolled off by my crossovers and EQ adjusted, but with the supertweeter left on as before):


This doesn't look like it rolls off as much as it should, but the electrical signal as shown by the RTA on my Behringer 2496 DEQ shows the bass rolloff exactly as you would expect from 24dB/octave Linkwitz Riley.  The rolloff is flattened acoustically mainly by the high level of ambient noise.  So just ignore that.  The main feature here is the very large notch at both 100 Hz and 112 Hz.  Those notches would look even worse if the ambient noise (from air conditioner and stuff) were removed.

Interestingly enough, I had dialed in a 100 Hz cut in the Acoustats, which I determined necessary from the Right channel on which I spent more time EQ'ing in the recent past.  I had that same cut in the Left channel where it makes things worse, primarily because I had only done "stereo link" EQ's for the Acoustats previously.  Right here I decided to change that, and removed the 100 Hz cut from the Left channel, but it made little difference (IIRC, I had removed the 100Hz cut just before I took the above measurment.  Prior to that, 100 Hz and 112 Hz were more level.)

After playing around with this for far longer than should have been necessary, it finally began to occur to me that this 100-112 Hz notch was being caused by rear wall reflection and cancellation.

Somehow, my intuition had always been that the rear wall reflections would be a factor only at much higher frequencies, such as 220 Hz, or 160 Hz, where they had troubled me long ago.

After continuing to think wrongly about this problem, I finally figured out the right answer.  The rear side emission of a dipole radiator is already out of polarity with the front side.  Because of that, it has to make an entire wavelength (or none at all) of travel to have a cancellation effect.  So the distance from the wall is 1/2 of the wavelength of the cancelled frequency.  And not 1/4 of the wavelength, as it would be for a box speaker.

But calculating from the wall distance of the closest point of the speaker doesn't suggest 112 Hz at all.  The minimum distance perpendicular to the wall is 40 inches, and at the center of the 2+2 panel it rises to 45 inches.  Taking 45 inches as the distance, that would cause cancellation at 146 Hz.

Wavelength = Speed-of-Sound / Frequency
Frequency = Speed-of-Sound / Wavelength
(1100 * 12) / 90
146

But what's happening here is that not all the sound travels that minimum distance.  The dipole radiates in the back as the front across a 90 degree arc.  Nearly all of the reflected rear wave travels considerably more than 90 inches.  90 inches in the bare minimum, most of the reflected rear wave travels more like 120 inches before it reaches the plane of the speaker, and that is what corresponds to the cancellation at roughly 112 Hz.

Several times last year I moved my electrostats further from the wall to mitigate the cancellation notches.  When I reached the current distance, the notch seemed to completely go away in the right channel.  In fact I had added an additional cut around 100 Hz because there was too much energy there.  I hadn't paid much attention to the left speaker.

I should have paid more attention to the left speaker, which shows the cancellation notch much more clearly, and NO amount of EQ can get rid of it.  Even increasing the subwoofer output at 100 Hz doesn't help much because it is also a room mode for the monopole subwoofer.

I further confirmed the cancellation nature of the 100-112 notch in the panel response by measuring all around the room.  Unlike the room mode caused by the subwoofer, the larger notch in the panel response is only a little affected in magnitude by listening position.  There is no place where it gets louder instead of softer.  The notch pretty well sucks out all the signal everywhere.  But the center frequency of the notch shifts a bit, possibly because it also interacts with the room mode, OR because the angle from the speaker determines the rear wave travel distance.  At the listening position, the notch seems centered around 106 Hz, and on the side further back, it seems to center around 120 Hz.




So I had two problems not amenable to solution with EQ: a room mode (for monopole subwoofer), AND a rear wall cancellation notch.  But both are amenable to other solutions.

I was shocked at how much difference moving the listening position a mere 10 inches forwards made in the bass response from the subwoofer only.  There is no shortage of 100 Hz from the sub at that position, which I've decided to make permanent at least temporarily.  But this may mean way more readjustments of things like the speaker angles.  But I've decided to take on that challenge anyway.  Actually, the closer position might be better for stereo width anyway.

Fixing the panel response is done by opening another can of worms.  But it only makes sense that if a speaker has problems in the 100 Hz range, I should not be using that frequency as my crossover frequency.  I should cross over the panels higher then 100 Hz to push the rear wall cancellation effect way below the crossover frequency for the dipoles, not just above it!

Actually, however, I first though of this solution just from the fact that even with the existing crossovers and EQ's dialed in, the subwoofer response seems to naturally roll off around 140 Hz.  So, I decided that would be a good place to start, and I then adjusted the panel crossover to have a 140 Hz acoustic crossover frequency, or what looks like one on my RTA.

All my fine-tunings now need to be fine tuned all over again, given that I've changed both the listening position and the crossover frequency.  But it looks now like this is the only way to go forwards.  What I was doing before doesn't make sense.

Even without additional fine tuning, just crudely readjusting the listening position and the crossover frequency has made the sound much punchier and yet clearer at the same time.







Monday, June 29, 2020

Revealing the Denon DVD-9000 HDCD bug, in pictures

[For background, see the preceeding post Curiouser and Curiouser.]

To prove the DVD-9000 HDCD bug, I first played a track on the Mephisto and Co. HDCD, which has been ripped onto my harddrive library.  It plays on the DVD-9000 operating as a coaxial SPDIF DAC (selected by front panel switch), fed coaxial SPDIF from a Sonos ZP80, being fed through the Roon streaming software.

With the gain on my Emotiva XSP-1 preamp set to -5dB, the level peaked considerably above a normal CD, as shown by the LED's on my Lavry AD10 converter.  -1dB to be exact.  That corresponds to nearly 4V output on the Denon (because the Lavry is set for 0db at 3.88V, and the Emotiva doubles the voltage of single ended inputs at its balanced output).



Next, I played a track from  non-HDCD, the album Out of Sight by Pancho Sanchez.  This was also showing -1dB output, same as the HDCD, which should not be happening.



Next, I played a special CD I had burned years ago, with a 0dB recording of 1000 Hz.  This was created with Cool Edit Pro, and reaches the 0dB level precisely at peaks, but with no clipping.  I do not store this CD on my harddrive to avoid playing it by accident.



This showed a level of -7dB, indicating a normal 2V single ended output from the Denon.


Then, I switched the Denon back to Coaxial input, and played the same track from Out of Sight again.  Now, it's only reaching -6dB, like an ordinary CD (but 1dB higher than a 0dB fixed tone recording because of inter-sample-overs, which I may discuss in a future post).


So, to recap, playing the 0dB disc appears to have changed the DVD-9000 so it is back to normal, playing normal 44.1/16 PCM files at 2V output, instead of the 4V output it was reaching immediately after having played an HDCD with peak expansion.

Further tests indicated I could also "reset" the stuck Peak Expansion mode simply by flipping the Source switch on the front panel of the Denon from Coaxial to Disc and back.  And also that the bug does not occur when playing a CD disc after playing the HDCD disc, it only occurs while the DVD-9000 is being used purely as a SPDIF DAC.

Sunday, June 28, 2020

Curiouser and Curiouser

Yesterday seemed kind of a dud.  Mostly just writing up various things discernable and claimed about HDCD.  Was it a breakthrough, or a scam?  Well, I still don't know, probably a bit of both I'll concede, but I've discovered some amazing things.

For one thing, and here I may have the smallest scoop of all time, but it is actually most likely a scoop because I doubt anyone has reported this before:

The Denon DVD-9000, when used as a SPDIF DAC, has an HDCD bug.

If I play any track from Mephisto and Co., one of the most justifiably praised HDCD's ever, and something I've long used as demos and tests, while using the DVD-9000 as a DAC to decode it, which it seems to do better than any other DAC I've experienced, it apparently sets the Peak Expand state of HDCD, which is used throughout this disc according to ffmpeg.

THEN, if I play anything else, even if not using HDCD, it gets peak expanded also.  The peak expand mode stays set (or, perhaps it was because I didn't play Mephisto all the way through...not yet tested, just a few seconds is apparently sufficient to enable the peak expand bug I am describing).

So it's a bug in general, if you happen to be using the DVD-9000 as a DAC, which is probably a significant fraction of the small number of DVD-9000's still being used, and playing some fraction of HDCD's.  In that case you, as I once did, might consider the DVD-9000 one of the best DAC's ever, because it's cheating, applying peak expand to everything.

BUT, it's also a feature!  I can now apply peak expansion to basically anything.  It's like having Carver's famous (or infamous) Peak Unlimiter on tap.

And, I can tell you, it sometimes really ups the ante.  It really adds a lot to other albums, especially it seems, HDCD albums which don't actually use the Peak Expand feature.  Such as Mannheim Steamroller Fresh Aire II.  Or even non-HDCD albums, like Pancho Sanchez' Out of Sight.

This is a Damn Good peak expander function.  We can already hear how fine it sounds on Mephisto.  If you listen to that HDCD disc on a non-HDCD enabled player, it sounds perfectly fine and wonderful.  You would just never know you are listening to a disk with at least 4dB of compression.  Then, when you listen to it on an HDCD player, it knocks socks off.

But that's exactly how a GOOD compression scheme should work.  You don't want your socks knocked off while your driving down the freeway or on your bicycle.  You want your socks knocked off when you're seriously listening to your big rig, with the HDCD equipped player.

As I started to say in the last post, this is exactly how it should be, or should have been, to end the loudness wars.  FM stations and car drivers can play the compressed version, but turned up to a higher average level.

But if you want to turn the Peak Expand state off, you can simply turn the Source switch on the DVD-9000 back to Disc for a few seconds, and then back to Coaxial.  And by the same token, the bug does not appear to be triggered by playing the Mephisto disc, and then any other disc.  It seems to only occur if you are using the DVD-9000 as a SPDIF DAC.

Anyway, the story of how I discovered this and many things, was like falling down the Rabbit Hole.

It started with the delight of getting my Denon DVD-9000 back online as a DAC, so I can play HDCD albums on my hard drive through Roon with actual HDCD decoding, from the very best HDCD decoder I have ever experienced, the Denon DVD-9000.

The DVD-9000 is not just a 40 pound monster Statement Piece by Denon as the first foray into serious competitive DVD-Audio (this player DOES NOT support SACD, though some had believed a PCM conversion would be permitted, Sony was never willing to license it for this player, which has a the last and best PCM DAC chip, the Burr Brown 1704, used in it's best dual differential mode, much like the top Mark Levinson 360S DAC did for 10 years afterwards, and many other famous DACs of note).

It is also apparently the first generation HDCD product to not include a PMI digital filter chip.  It uses the second generation HDCD specification, which was never made into a chip, within a 32 bit digital filter system, which Denon called AL24.  And, the development of all this probably occurred before, or contemporanously with, Microsoft's purchase of HDCD from PMI.

If any DAC has the "transient filter" feature enabled, this might well be it.  Maybe it doesn't, maybe no HDMI players did, but I can state that this HDCD DAC sounds better to me than any other HDCD DAC I've ever heard, by a large measure, and it could be because of a Transient Filter feature, which I had always believed existed.

******

Just after setting up the Denon DVD-9000 with SPDIF input through a Roon enabled Sonos ZP80 Zoneplayer, I wanted to be sure this was actually working to correctly decode HDCD albums in my library (if not others).

It's damning that the DVD-9000 does not (usually) light the HDCD light when playing HDCD albums through the SPDIF input.  That bug had been observed by others.  It appears to only do so if you are playing an HDCD disc.  But it also appears, I have confirmed, to do the HDCD decoding for 16/44.1 SPDIF signals as well, if they are HDCD titles.  It just doesn't light the HDCD light.  (And, yet, sometimes it does light the HDCD light, but I have not been able to duplicate this occurance, a peculiar series of albums might cause it, or perhaps I incorrectly observed this when an HDCD disc was loaded.)

So, how does one confirm that the HDCD decoding is actually being done, in the absense of a reliable luminous HDCD indicator?

Well, before I knew of anything better, I could measure the output of the DVD-9000.  I do that automatically when I listen to the analog outputs, which are buffered and level adjusted transparently by my Emotiva XSP-1 preamp, and thence fed in balanced form to my Lavry AD10 analog to digital converter.  The resulting digital signal then feeds my digital crossovers and equalizers.

The Lavry has a wonderful array of LED's, with Peak Hold that stays held until you flip the reset switch.  Which means I can measure and/or compare any level within 1dB.

I've known for some time that HDCD's put out higher levels than regular CD's on the DVD-9000.  This was what the original HDCD license required, and the DVD-9000 implements it.  Later HDCD players tended to drop this feature, which reviewers and fans of other equipment (especially Sony equipment) tended to depricate.  Justifiably, non-fans of HDCD thought this was an unfair trick, and indeed, it was.

Many falsely claim that CD players were supposed to put out only 1V maximum for CD's, and 2V peak extended maximum for HDCD's.

What the Denon does is put out 2V for regular CD's, and up to 4V for HDCD's.  It's easy to see this difference on the Lavry LED's.

I generally try to adjust the gain on the Emotiva preamp so that the peak signal is -1dB on the Lavry indicator.  That way I'm sure there was no clipping.

However, as I was playing various HDCD and other files from my library on the DVD-9000 through SPDIF, it seemed I kept having to turn the level down on the Emotiva to stay away from the 0dB light.  Ultimately, it seemed, that if I set the Emotiva gain control to -5dB, I could do this effectively.  Playing regular CD's on the Oppo UDP 205 and other players, I can do this with the gain control set to -1dB or so.  So we can see there's at least 4dB difference in peak levels.  When I play LP's, I have to set the gain to +4dB to +7dB.

(I have set the Lavry input maximum input level to 3.88V, but the Emotiva automatically doubles the output voltage from the single ended Denon to the balanced outputs feeding the Emotiva.  So a single ended output reaching 2V would require a gain setting of about -1dB, as also with the Oppo balanced outputs reaching 4V.)

Anyway, I thought I could verify that the DVD-9000 was properly decoding the HDCD sent over SPDIF by playing an HDCD, and a CD, and comparing their levels shown on the Lavry.

I started with Mephisto and Co.  I couldn't actually remember the gain setting required for HDCD's with this setup, I remembered it seeming to differ from disc to disc, so I started with a gain setting of -3dB.  That didn't work, so I tried -4dB, and ultimately -5dB gain setting.  That eliminated hitting the 0dB indicator LED on the Lavry with this disc.

Wanting to be sure I had found the maximum, I also tried Fresh Aire II, and it was also hitting the -1dB LED more consistently.

I was sure a regular CD would not reach higher than -4dB or so, because of the level settings I've just described.  I was sure that I had already proven the Denon was playing HDCD's at an elevated output level.  So I didn't bother to compare the levels of regular CD's, so much as CD's I had always wondered might really be HDCD's, whose potential might previously have been untapped.

I somehow had this idea that Poncho Sanchez' Out of Nowhere might have been mastered in HDCD.  (Actually, I was confusing it with Arturo Sandoval's Hot House, I remembered later).  So I tested that, and it was hitting the -1dB Lavry LED even more frequently than the previous two discs.  So this had to also be an HDCD, despite not being marked as such.

This was a shock.  I knew that not all HDCD's were labeled as such, but exactly how many of my CD's are really HDCD's that haven't had their full potential revealed, I wondered.

I decided it was high time I use one of these programs, like Foobar2000, to test my files and see if they have HDCD features enabled.

That was a long trip into computer frustration.  The initial (and perhaps ultimately fatal) problem is that I use a Mac mostly, and Foobar2000 is solely a Windows program.  Well, I'll try it under the Wine emulator.

I was pleased that I managed to get Foobar2000 running.  And then I downloaded the HDCD plugin, and installed it, which required learning a lot about Foobar2000 and even a bit more about Wine.

Loading the HDCD plugin probably didn't work completely.  Either that, or it is broken on the current release.  It seemed to be installed, it shows up in black in the list of available plugins.  And I was able to add the HDCD reporting to the default display, as described on websites (the actual HDCD plugin has no documentation itself).

But every HDCD I played showed no HDCD features enabled.  I edited the default display so the contents of the HDCD variables are ALWAYS being shown, and they always show as ?.

It might have been that this was caused by an incomplete installation of the plugin.  When I pressed the INSTALL button, Foobar2000 was supposed to reboot itself with the new plugin.  It did not reboot, I had to restart it manually.  It's possible that Foobar2000 missed picking up the last bit of the HDCD plugin installation process.

Well, I figured, I'll just have to wait until tomorrow (it was already past my getting ready for bedtime time) and install it on my actual PC.  But this didn't keep me from another futile hour of futile fiddling with Foobar2000 on my Mac, all of which failed to reveal anything about any HDCD.

By the next morning, I decided to take a different path.  I happened to stumble upon the other recommended way of dealing with HDCD, ffmpeg.

Now, ffmpeg is definitely more of my kind of program! For one thing, it runs natively on Mac (and many other systems!).  It does all sorts of conversion tricks.  And there's no need to fiddle with plugins or recompiling (which I was afraid of at first) because HDCD is included in the standard Mac binary distribution!  (And if that isn't good enough, one can download the source code.)

And it runs from the command line also, another thing that I, a retired Unix programmer, really and truly like and appreciate.  That means I can easily roll shell wrappers and things (which I have already done--I created a script which simply examines files for their HDCD flags, deleting the pesky output files I don't want yet).

And, the results of ffmpeg were quite shocking.  I was shocked to see that neither Fresh Aire II, which is clearly marked HDCD and which I always believed was so much better on HDCD players as to not be worth playing on any other kind, uses no HDCD peak expansion or gain adjustment features!  It is fully embedded with the HDCD Transient Filter flags, which some claim to be ineffective, and that is all!

Out of Sight, a more recent addition to my library, showed no HDCD flags at all!  So how it the world was it reaching the nearly 4V output level when being played on my Denon DVD-9000 ???

Eventually, the theory I described at the top became clear to me.  The Denon must have a bug, I concluded.  And only then I set about systematically to prove it, as I shall show in the next post, with pictures!