Thursday, November 25, 2021

Mysterious Problem Solved on Thanksgiving

[See Update 2 at bottom.  It appears a Sonos update the next day fixed this problem for now.]

[Nov 27 update I filled in some more steps in the testing.]

On the evening of Thanksgiving 2021, I was playing the living room system through the Sonos Connect known as "Living Room Sonos."  Or perhaps I should say...the Sonos Connect soon to be formerly known as "Living Room Sonos."

I wasn't playing THAT loud, I had the Tact level set to -10dB or so.

There was terrible breakup on a recording from Pipes Rhode Island, the Frank Chorale in B Minor.

I was using the Sonos Connect instead of the Oppo BDP-205 because I had previously been playing the Kitchen FM Tuner in the Living Room, and Sonos has analog inputs which let me do that (the reason I selected Sonos in 2005).

I tried other things before finally determining the Sonos Connect was at fault.  I was first afraid the speakers had an issue, very afraid.  But it was hard to test that...so instead I switched amplifiers to the Aragon 8008 BB.  I hadn't done that in awhile.  I figured it *could* be an amplifier problem, the Hafler has about half of the peak output current of the mighty Aragon--which has 1100VA transformers for each channel.  It was still breaking up.

I was getting more and more afraid that the speakers were indeed at fault.  So I did something I haven't done in many years.  I got out my Koss ESP-950 headphones and listened to the same song.   Electrostatic headphones are like an auditory microscope...you hear everything.  The Koss transformer box takes coax line inputs, so I fed it from the coax line outputs of the Emotiva Stealth Dac.  I got the same breaking up sound.

OK, so maybe it was the digital processing.  I was now fearing that my FIR based digital input filters might be introducing some kind of artifacts.  ("F" stands for finite...it's an approximation over finite time...that's how it can do so many amazing things...because it's not exact--in principle.  But audio is never exact anyways.)

So then I fed the headphones (which take line inputs to the transformer box) from the output of my Tact digital preamp.  It has analog outputs (using an optional high quality DAC on an internal card) which I don't normally use because I only use the XLR AES/EBU digital outputs...which feeds my chains of digital processors).

Same breaking up sounds. 

Then it occurred to me to try the Oppo, and while streaming the file through the Oppo it sounded fine (except for a few "ticks" which I hear so consistently, even on my dynamic speakers, I believe they are in the recording itself.  These ticks are nothing like the hashy breaking up sound I was getting on the Sonos Connect).

Wondering how I could check out the digital output of the Sonos Connect (I only use the digital outputs on most Sonos nodes)  I grabbed my Sencore digital meter.

The Sencore showed nicely low jitter (just over 200ps) and no errors or any other problems with the Sonos digital output.  And when I first checked the levels, and after turning off volume leveling on the Oppo (which I play through Roon, whereas in this discussion I'm playing the Sonos boxes through the Sonos S1 Controller), the levels were identical.  While doing these tests, I was not playing anything over the speakers because I had the digital signal piped into the Sencore instead.

But then later I was doing a test when the Oppo was playing through the speakers, but running the test meanwhile on the output of the Sonos.  And then I got a bogus level of -0dB where I shouldn't have (the peak level in the recording is -0.7dB).

I switched to the other nearby Sonos node I have been using the play HDCD's through the converter of the Denon DVD-9000 by sending the coax digital from that node to the Denon.  That Sonos node happened to be the earliest model, the ZP80, which I first bought 4 of in 2005.

The ZP80 did not have the breakup issue either, so THAT is now going to be the Sonos node I'm connecting to the living room stereo.  I have rarely used the HDCD path (which sends digital audio from Sonos to the Denon DVD-9000 for HDCD conversion) and I could always temporarily change the coax output of that Sonos ZP80 back to feeding the Denon if I do want to decode an HDCD that way, that takes little more time than just turning on the Denon 9000 and selecting coax input.

I really don't know that it was the fact I was playing music (possibly causing vibration or putting noise on the AC lines) that messed up the "Living Room Sonos."  It might have been something else.  When it first happened, I thought it was because I had just clicked mute and unmute in the Sonos controller.  I had been wondering if there was a bug in which, under some conditions, the Sonos Connect does digital amplification when it should not be doing so (such as when the level output is fixed).  I had thought I had seen such a bug before.  But the test examining the level from the Sonos where it, at first, exactly matched the Oppo, disabused me of that theory for awhile.

It could have even been that the coax connection to the Sonos Connect was slightly loose.

All I really know is for some reason, that one Sonos Connect was messing up it's digital output, sometimes.  It could be the fact it is also processing the tuner input for the rest of the house.

Maybe it's better to have one Sonos Connect to handle the FM tuner input, and a second Sonos node of one kind or another to feed the living room stereo anyway.  I also trust the ZP80's as much as, if not more now, than the Connects.  I tested the ZP80's extensively, as did John Atkinson.  I never actually tested the Connects, I just presumed they were an upgrade.  I can't remember when I first started having strange issues that seem like digital gain and clipping, was it when I got the Connects or before.  Also nothing stays the same because of Sonos software updates, which may be more important than whether a node is a ZP80 or Connect (which are almost identical in appearance and apparently identical in intended function).

And most of the time, I'll just be using the Oppo through Roon anyway to play music in the living room, which is my best digital pathway.  But...I had been using the Sonos Connect to run tests, and I very deliberately did not add the test files to the Roon list of music folders for that reason.

That calls into question some previous tests...including the test where I decided I had to lower the input of the midrange miniDSP by -6dB to prevent inter-sample-overs.  Perhaps the real issue was the bug in the Living Room Sonos Connect.

So from now on, what I'm going to do for some important tests is to temporarily add the test folders from Roon when doing tests, and that way  I can use the Oppo for doing tests, without fear of selecting test recordings at other times through Roon.  And then removing the test folders from Roon afterwards.

Because of worries about forgetting to turn such test folders off, perhaps I'll still use a Sonos node for most tests, but the ZP80 which hasn't yet shown any issues, instead of the Connect.  Until there is a weird issue (like the apparent inter-sample-overs on the miniDSP's) for which the ZP80 might be at fault, which I should have thought of when I encountered the apparent inter-sample-overs on the miniDSP's while using the Connect.

It's here I might also confess that the primary issue that made me quit using my Audio G_D DAC 17, which was the Krell FPB 300 shutting down, perhaps was never a problem with the DAC 17 at all.  It was only many months after that I traced the many shutdowns to a bad transistor in the Krell itself, at least by all appearances (I can see the hot spot in IR photos for example).  And ultimately it became impossible to use the Krell anymore because it would shut down before even coming fully on, and therefore before I could zap it with a big enough signal to stay on for awhile.

It was sad that I didn't imagine that it was principally the Krell at fault.  I also blamed the speakers and other things, perhaps wrongly in other cases too.  I spent many months trying to "fix" the speakers so they "wouldn't cause" the Krell to shut down.  I still need to re-test the DAC 17 and I might even use it in the future now that my system has fixed digital rates for each way...making it possible to do the time alignment for sources of any sampling rate even with different DACs...since all sources get converted to 48kHz or 96 Khz (for the tweeters) anyway.

The Franck Chorale is sufficiently complex that despite hearing it endlessly, it sounded different every single time.  This is the actual problem with subjective equipment tests...it's not so much that things don't sound different, but that you never actually hear the same thing anyway, and then you have to decide which differences (if any) are traceable to the change in equipment (which is pretty much determined by preconceptions).  And repeats especially sounded different at different levels.  With large level differences, it sound like a different composer.

Updates: I have tested reconnecting (and tightening) the digital cable from the Living Room Sonos Connect.  I still heard the breaking up.  I'm beginning to think this particular unit could be defective.   And the line inputs might be defective too.   About the same time as I replaced the original Living Room ZP80  with this Connect node I also noticed the line input from the tuner wasn't sounding as good.  According to all I've read just now, the only difference between ZP80 and Connect (same as ZP90) was a different and better radio.  If I remember correctly, I made this change last December, about a year ago, when I was incorporating the Marantz recorder and making other changes to improve the sound of FM, and it did sound much better in the living room, but not over Sonos, where it sounded worse.  I've had this theory that the better FM antenna, which reduced FM noise, was also making it sound more crispy.  But it sounded fine in the living room because I added the Musical Fidelity X10D to that path.  It merely sounded worse over Sonos.

Also the ability to control the line level input levels was removed from the computer software.  You must use the App (on a smartphone) to control this feature.  Or originally you could use the CR100's to control everything, including the line levels and the "Uncompressed" feature, but then CR100's were unsupported, which made me very angry and I still miss the convenience of the CR100's as compared to using a smartphone.  With the CR100 the pause and play buttons were always active, whereas with a smartphone you have to do a lot of fiddling to do anything.

My tests and those of John Atkinson showed the ZP80 to be bit perfect and it performed very will in the jitter test and other tests.  But neither I nor John Atkinson have tested the ZP90 aka "Connect."

I had been disappointed that Sonos never included high resolution into the original system (I believe it is available in the new S2 units) and went the direction of making midfi convenience speakers and such, rather than sticking to true hifi interconnection units (now called "streamers") and reasonably good amplifiers.

I see now that even my old "Connect" units cannot be used with the latest Sonos software.  I hardly care, if anything, I'd like to return to the original Sonos software of 2005, which did everything I needed it to very well.  I did later get a Logitech streamer, but it was such a hassle to use I never much did use the Logitech streamer, despite the fact it had high resolution.

But I can see the name of the game for many people is supporting all the different streaming services.  That is the excuse for the new incompatible S2 Sonos units and software.  I hardly care if Sonos keeps up with streaming services because I use Roon for that purpose, and for me it makes much more sense to me that interconnection units be dumb and the smarts be put into the central software as Roon is doing it.  I'd long hoped to roll my own dumb Pi3 interconnection units that were Roon Ready, until Roon started supporting Sonos, and then I had no excuse (other than modest monthly cost) not to get Roon and use with my existing Sonos network.  But Roon has never had any ability to use the Sonos Line Inputs.

Update 2:  This morning I googled "Sonos Uncompressed" and found you can set that feature (which defaults to "Automatic") using the app not on a node-by-node basis, but on a whole system basis.  Reportedly this feature only affects line-in playback, but the App doesn't say so.

I went to check the current setting in the app, but it wouldn't even let me view the current settings without updating my whole system.  I'm not sure when this update became available.  So I updated my system, and then it appeared that the option had already been set to "Uncompressed," as I now remembered doing sometime in the distant past (but possibly when this particular Connect node was offline or before I even bought it?).

I had already been testing the Sonos Line Input between the two different living room Sonos nodes.  I think they are identical.  But anyway I had moved the tuner output to the ZP80.

So now, with these two changes (updating Sonos, and moving the line input to the other node--which might be unimportant) the Living Room Sonos Connect sounds fine, no breakup playing the Franck chorus.

The best theory now is that somehow the Sonos Connect had a bug which was fixed by the update.  After the update, no more problem.  Though perhaps it wasn't even the update but a reboot caused by the update.

A related possibility is that Roon can fiddle with the Sonos level settings and left them in the wrong settings.  I sometimes play the Living Room Sonos Connect with Roon.  Roon has two relevant settings for each Sonos node, "fixed level" vs "device level" and then, when you select fixed level, you can set volume settings: min and max.  Last night I went through all my Sonos nodes in Roon and made sure all the ones that are supposed to be "fixed level" are set to "fixed level" in Roon.  I had never done that before.  Indeed the Living Room Connect was set to "Device Level," but Sonos S1 controller always showed it as "Fixed Level" anyway.  But I don't recall that changing this last night made any improvement in the sound.  Perhaps it required to update (and reboot?) to get it changed back correctly.  Perhaps the update makes sure the settings in Sonos are the ones in effect when you are doing playback in Sonos, regardless of what some other streaming software may have been doing previously with that node.

I still consider the Connect to be questionable enough that I'm going to use the ZP80 for living room playback, and either use the Connect for line input only, or in some other room where I'm not depending on the Fixed Level setting to remain in effect.  The bug has gone away for now, but there's no telling when it might come back.

Still testing the Sonos Connect, I moved the tuner connections to the inputs on this node again, and there is still no problem.

Both Sonos nodes are now working fine, but I'm still planning to switch the living room stereo to the ZP80 which may be better...though it's possible and perhaps even likely the problem was a software bug that just happened to the Connect based on how it had been used.  It may have been, for example, that I pressed the volume up button on it, and if Roon had told it to use Device Volume sometime in the past, that may have overridden the Sonos settings when using Sonos, though it shouldn't have.

But actually I'll run the FM tuner outputs to the Connect unit because it has a better radio in case one of the ethernet links goes down.  And it will interfere less with the ZP80 that will mainly be used for tests on the living room stereo (though I've never noticed any interference including in these tests).  And the Connect will feed the Denon for HDCD encoding, so if the bug occurs again it will be noticeable as the HDCD light won't light if the bits are tampered with.



Saturday, October 16, 2021

ISY-994i programming

I use an ISY-994i controller for my home automation.  It is very easily user programmable, and powerful.

However, the "Programs" for the ISY-994i have a particular weirdness that I've struggled with for a decade and now, thanks to discovering this informative post, I have a handle on.

https://forum.universal-devices.com/topic/4376-wrapping-my-head-around-how-the-isys-else-works/?tab=comments#comment-33946

It's not obvious what the "trigger" conditions for running a program are sometimes, and they have to be understood separately from the "condition" which determines whether the THEN or ELSE clause runs.

If a condition is something being switched, the program is only triggered when it is switched THAT way.  So if that is the only condition, the ELSE clause is never run.  A way around this is to add an "is not" clause because they must be evaluated for any change.

OTOH, if a clause is about the status of something being on or off, the program is run for ANY status change, and then the THEN or ELSE may apply.

A program is run if any of the conditions is triggered, so then the THEN or ELSE may apply.


Monday, September 13, 2021

Gain Structuring

 For complicated reasons I'll describe below, I decided to turn the gain up on all 3 Emotiva Stealth DC-1 DAC's I use in the living room system by 4dB.  The current levels are

Tweeters: +10dB

Subwoofers: -11dB

Panels: +2.5dB

It's actually become extremely convenient that these DAC's have 0.5dB resolution gain switching that goes way down and up to +12dB.  Functionally it's like getting a preamp with your DAC.  Though purists might rather have their own high end preamp, the gain here is provided by an impeccable LM4562 with a 2005 generation digital level control (that was when they got about as good as an LM4562).  If I ever switched to another DAC w/o gain, it might be difficult.  But now thanks to fixed digital rate of 48kHz from the miniDSP (and 96kHz for the tweeters) I can simply time align the DAC's (and the speakers) for these fixed rates and it's done.  (Previously, where the rates could vary from 44.1kHz to 96kHz...causing different delays in different DACs, it was impossible.)  So, I can fairly easily use different DACs on each way of the system...but few have the nice digital level controls of the Emotiva and with 12dB extra gain.

The actual tweeter (crossing in at 20kHz) levels are so low that boosting the gain there is never going to cause the DAC to overload...or the following amplifier.  The SVS subs are just very sensitive and I have their local level controls turned down also.  The DAC feeding the Hafler 9300 driving the panels had one time been at -6dB so I could set the higher gain Aragon to 0dB.  The Aragon is currently offline because the DAC feeding it now needs repair.  Just before this latest adjustment shown above, the DAC feeding the Hafler had been turned to -1.5dB.

Well I decided to do this after seeing that even turned all the way up, to no digital attenuation on my Tact, I was getting peak levels at -87dB C weighted.  That's not very loud.  But you'd think at "0dB" it would be.

But when I was setting up the miniDSP for the midrange, I detected clipping problems if I set it's input gain control above -4dB (so ultimately I chose -6dB to be on the safe side of no digital clipping).  This is because the miniDSP use a 48kHz ASRC input for the digital input.  Such asynchronous sampling can be pushed into clipping by "inter sample overs" because there can be (and are, on many pop recordings) peaks up to 6dB (theoretical maximum) higher than the nominal level.  This is another reason why units with SPDIF or AES digital input and digital output should use SYNCHRONOUS not ASYNCHRONOUS transmission.  Asynchronous should only be used, if at all, in a terminal DAC unit which does not output digital.  But totally unwarranted fear of JITTER has led to the near abandonment of synchronous digital receivers, despite the fact that the better ones did a nearly impeccable job with typical low jitter levels and considerably beyond.

The 1999 Tact RCS 2.0 did in fact have synchronous digital in and out, at rates from 44.1kHz to 96kHz.  My living room system uses this as source pre-selector (to the input of the home-controlled switch, which switches between FM and everything else, and from there on to a splitter to the 3 miniDSP's) and level controller.  I don't find the DSP in the Tact system meets my needs, with a trifle re-programming it could.  The Tact preserves the input rate--and timing--from input to output.  There might be some smoothing in the timing, I'm not sure of the details actually.  But if I were to build something, I'd have it like this.  I'm unsure if the synchronous receivers are made anymore.  Or updated to 192kHz, which I don't consider of much importance.  Actually my miniDSP's are limited to either 48kHz or 96kHz anyway.  So it would be useless to lust over a front end controller ("digital preamp") with more than 96kHz anyway.  And as I've many times stated, I think all that's needed is 96kHz, everything above that is a WOMBAT (Waste of Money, Brains, and Time).  Peter Aczel and the near entirety of "Objective" audiophiles would say 44.1kHz is enough and that nobody has "proven" otherwise in reproduced blind testing.  But I'm allowing margin over 44.1, for various reasons, though I recognize that 44.1kHz sampling can be damned good (and likewise 16 bits) and the vast majority of what I listen to is just that, and I'm still often (and pretty much always nowadays) wowed and so on.

So, the unfortunate loss of 6dB gain in my digital processing means I have to make up the gain somewhere.  If I were to increase the output of the Tact, I'd get actual digital clipping (not just intersample overs) at the miniDSP inputs.  So the only thing to do is to raise the output "after" the digital conversion.  Which I can conveniently do with my Emotiva Stealth DC-1's because in fact the level control can be increased to +12dB.

But what happens with a digital signal at 0dB with the Emotiva at +12dB.  Distortion rises from 0.0005% to 0.02% which doesn't matter audibly.  That's because the output circuitry of the Emotiva can actually drive 25.65dBu (14.85V RMS) !  (Well, that's into balanced...) The output with the control at 0dB is 14dB, or 3.88v RMS, into 4 ohms, which is a bit low for some high end power amps, but you can crank it up.

I got that information from this Pro review.  Pro's are interested in these sorts of things, which often don't get tested by audiophile reviewers.  (John Atkinson always tests maximum output level, but it seems Amir did not, he simply tested with the level control at 0dB which is not the maximum.)

In unbalanced I likely have half the output, or about 7.92V, which is still almost 11.95dB higher than the standard output of 2V with the level at 0dB.  So I can crank the level up to at least 11.5dB without concern basically (at least as far as the DAC is concerned), even if perchance there were a maximum digital level signal.  (Perhaps to allow for inter-sample overs in the DAC itself...it might not be a bad idea to keep the level below +6dB for ultimate fidelity.)  In my case, where the signal itself is deliberately -6 dB, I'm good with the 11.5dB level even before intersample overs become an issue.

The amplifier has "headroom" (above it's 1.1V rated input for full output) and besides such signals are way below the average level, due to both the mandatory -6dB processing reduction, and the crossover itself.  If the amplifier is working too hard, I will hear it, just like someone with an all analog setup.  What I strongly want to avoid is "invisible" digital clipping from ASRC for example.

Basically the signal is never going to go to the peak level (for one thing it can only go to -6dB on average) and the panels only get frequencies above 120 Hz, which also reduces the level.  If there ever is a transient peak (which is all it could be above the -6dB level because of my miniDSP attenuation) it won't stress the analog at all.

Well now that I've checked the Emotiva capabilities, I'm thinking of cranking up the DAC's another 2dB.


Monday, September 6, 2021

What to do with CD's after Ripping

 It seems that hardly anyone recognizes the ethical and legal issues regarding first ripping CD's, then selling or donating them.  Essentially two copies of music have been created, but only one was legally paid for.  This issue gets only a tiny bit of discussion (while being dissed everytime it comes up) in this thread.

Some keep their old CD's for this reason or other reasons, while others donate or sell.

I had been planning to keep all my old CD's.  But as I acquire more and more, this is looking untenable.

I was hoping someone had already "solved" this problem with "recycling" service for CD's.  You send boxes of CD's in, and they recycle the paper and plastic and return you a receipt for all the titles you have recycled, which you can then save as proof of ownership.

Short of that, I was thinking of taking photos of 100 or so CD's at a time laid out flat, then boxed, then trashed.

Though I suppose, old CD's are only the tip of the iceberg of my junk problem.




Sunday, August 29, 2021

Phono Frequency Response

I had a nagging to play vinyl on Saturday Night.  On top of some pile I can't remember buying I found Queen's Greatest Hits.  Having heard these same songs on digital, in some cases high resolution digital, this was different, having more presence, transparency, liquidity, and magic (and some noises).  But also, seemingly, less bass.

I think the less bass part is primarily a problem with this "Greatest Hits" pressing, which may not have the extended bass of the originals.  But also I suspected it could be my turntable system.  Often when there is less bass, we hear it as greater presence and transparency.

So I got out Hifi News and Record Review Analog Test LP, and played Track 7 Side 2 which is a sweep tone.  One of the very annoying things about this record is that each band is walled off from the others.  In order to play Track 7, you can't just cue to the space in between 6 and 7, because that just reverts back to 6.  You have to pass the wall at the beginning of Track 7, and cue precisely there.  It's hard to hit that point precisely, and when you do, the tonearm is still stabilizing at the beginning of the track.  That might, partly expaln the bass below 30 Hz in this recording shown here in Audacity.  There's also a matter of intermodulating with the tonearm and antiskate system resonances..



 The bump at the bottom where it more or less stabilizes is 30 Hz.  Up from there to the midrange level represents about a 1dB increase.  So it appears the bass below 100 Hz is gradually rolled off by 1dB at 30 Hz, then looks funky.  (The scale above is linear so it shows changes that look larger than they would on a logarithmic dB scale.)

I wouldn't think that 1dB loss would be that big a deal, I routinely make changes of that amount or more in the bass level, and in fact I tried adding 5dB (by changing the DAC output level from -15dB to -10dB) and the Greatest Hits recording still sounded like no bass, until the last track.

The instability below 30 Hz might be a problem, but possibly worse there is a peaky resonance just below 20khz which shouldn't be there.

Another measurement I made indirectly shows the instability below 30 Hz is not a matter of initial tonearm/table stabilization.  I happened to drop the needle at 30Hz instead of 20 Hz, and the reproduction is pretty clean, only showing the barest overlay of the needle drop stabilization, which disappears after 13 cycles of 30 Hz (just over 1/3 second).  That initial instability could also relate to the slight peak (small fraction of a dB) at 30Hz shown in the previous measurement.  This means that the instability shown above is caused by something else, presumably interaction with tonearm vertical and horizontal resonances that needs fixing for good bass below 30 Hz.  I'm showing higher magnification in the selected portion just after the needle drop (also shown) for clarity.


Digging through my files, I found a measurement with my Mitsubishi LT-3 linear tracking turntable, with damping added to tune the bass just as with the Linn (though it was an earlier job I didn't do as much or as well).  They both have a Dynavector 17D3 playing through an Emotive XSP-1.  I'm showing this somewhat aligned with the Linn result above.



The Mitsubishi is on top here.  I think it has slightly flatter bass below 120 Hz (perhaps 0.5dB loss down to 30 Hz vs 1.0dB for the Linn), it lacks a weird resonance in the Linn around 120 Hz, and the bass extends possibly a tad farther before it becomes unstable below 30 Hz--but they are so little different in that regard it's hard to tell, in both cases the bass becomes unstable just below 30 Hz.  They both seem to have a resonance just below 20kHz, I'm wondering if that's coming from the cartridge body or the screws.

I wonder if the resonance around 120 Hz in the Linn is the infamous flexible subchassis resonance and "flabby midbass."  From the day the LP12 was introduced people wondered why they were getting such a thin and flimsy subchassis with an expensive turntable, when even much cheaper turntables like the AR Turntable had very heavy gauge metal.  HP of Absolute Sound denounced both the subchassis resonance and the flabby midbass in his first review of the LP12.

Famously Linn doesn't have a subchassis upgrade except for the very expensive Cirkus bearing.  I figure this is because the original bearing has a noise that is absorbed by the flimsy subchassis.  The expensive Cirkus bearing eliminates that resonance, so you can even have specially cast and machined subchassis with it.  Such were never offered for the original bearing (except by outside vendors...and they were not universally loved).

The flimsy subchassis could have eliminated a bearing noise.  But the price may be that funny ripple in the frequency response around 120 Hz.  Remember the cartridges are the same model.

Although the Mitsubishi turntable yields better frequency response, I don't think it sounds as good.  It has larger and more undamped arm/cartridge resonances and/or motor and bearing noises.  The movement of the linear tracking tonearm subtly affects tonality.  I could possibly fix the larger arm/cartridge resonances, with the application of more damping material, and the electronic motor is probably due for a tune-up.  My Linn Valhalla board has been replaced at least twice, the Mitsubishi has it's original electronics and it's a wonder they're even still working.



Wednesday, August 25, 2021

Testing the M50

In May 2012, I decided to reward myself for something or other, and bought the M50 I have long planned to buy.

The Earthworks M50 is the king of measurement microphones nowadays, with calibrated (and quite flat) response to 50kHz.  It costs far less in real terms than the standards of old, such as B&K's with their custom amplifiers and such.

I think John Atkinson of Stereophile uses an M50, either that or an M25.

Until now, I've had no proof that my system even has frequency response above 20kHz or so, something I've invested thousands of dollars and endless fine tuning to achieve.  I have no idea what the proper calibration for my previous custom 25kHz calibrated Dayton Audio above 25kHz.  Given the different calibration curves for different angles, it's also hard to know which of several calibrations to use.  I didn't really trust it to 20kHz let alone 25kHz (but in fact I was wrong...it matches the M50 amazingly closely!  Perhaps I needn't have bothered.  Nah.  Anyway I plan to use my old mike for general purposes and the M50 for calibration and "final" measurements.)

For the measurements here, I recall I put the microphones straight forward.

Here is my system response with the 25kHz Dayton Audio microphone:



Here is the response with the M50, which I finally figured out how to calibrate correctly (the calibration they supply cuts off below 700 Hz..for ARTA I had to add in fake points at that exact same level).



The M50 shows a slightly cleaner HF peak at 22kHz, and about 3dB more output at 40khz, and that's about it.  If I had an accurate calibration above 22kHz for my Dayton I could probably make them match even better.

I think the speaker system response, shown in much higher resolution that you usually see above 100 Hz (and less below, thanks to FFT techniques) is pretty good.  It slopes nicely downward from 1kHz (though perhaps a bit too early and there is more loss than desirable above 8kHz or so.  The inaudible 22kHz peak merely restores the highest treble to the midrange level (and less than the deep bass), and also makes possible the response extension to 40kHz where there may still be more output than at 14kHz.  Many highly esteemed tweeters have much larger ultrasonic peaks from fancy construction.  My 21mm Dynaudio D21AF's have factory response curve showing flat from 1200Hz to 39kHz measured with close microphone but they don't account for a lot of variables here, including the polar response dilution of a cloth dome tweeter (which is good enough to even make 40kHz response possible--which can't be done with many materials including of course my electrostatic speakers).

Anyway, there clearly IS ultrasonic response at useable level at 40kHz, which has been my goal, and now proven with a top calibrated microphone.

Instead of huge peaks and valleys in the bass in the unequalized bass response, or where the wall bounce isn't properly corrected (I dodge that with my 4 foot wall spacing and crossing subs at 125hz with 8th order linear phase crossover) it's pretty flat 80-800 Hz (amazingly flat in my building and measuring experience), with just a soft rise below 80 Hz (which I may have reduced with subsequent adjustments as I'm writing this months after these measurements were recorded.)  It sounds natural.  1/6 octave omni measurements on my phone show less difference below and above 80Hz than these FFT measurements.

Some measurements last year were made before I figured out how to run the supertweeter miniDSP at 96kHz.  So it was running only at 48kHz like my other DSP's (the 48kHz plug in is more flexible than the 96kHz...but that flexibility is not an issue for my supertweeter...so I run only the supertweeter crossover at 96kHz where the highest sampling rate matters).  So measurements through the middle of last year showed a steep dive at 24kHz, the Nyquist Frequency of 48kHz sampling.  It took me awhile even to figure out that sampling rate was a problem, and until I did I greatly feared that I was basically getting zero response above 24kHz.  I remembered that fear into the present.  By that time I was thinking the microphone calibration explained the rolloff above 22kHz...but in fact the peak there, and the general response, shown by the Dayton...extending the highest calibration to all higher frequencies...is very close to that shown by the M50, with hard-to-see difference at 40kHz where useable response is ending with a precipitous roll off.  Also the Dayton curve shows a little notch where the calibration ends, whereas the M50 shows a smooth peak at 22kHz.




Sunday, June 20, 2021

Automating Music Reproduction

Entry Switchplate (Labeled)


After decades of thinking and dreaming about such things, I've finally automated my main audio system.  I think it's the best upgrade ever, and I'm still working on making it even better.

Automation, in the context of audio reproduction, means two things (and preferably both):

1) Powering up and making whatever other connections, protocols, or other actions are required for the system to begin to play music.


For a personal device system, this includes:
1) enabling device, getting past authentication
2) dealing with personal device issues necessary (upgrades, identity issues, expirations, selection menus, etc) to run app, and running music app.
3) Connecting headphones to device, and headphones to ears.

Good luck automating that.  This is also an illustration of why I have kept personal device centered audio, and even USB (which means some sort of authenticating computing environment) away from my living room system.  Computer based systems nowadays are designed to authenticate and then spy on you, while gaslighting you to gauge your preferences ever better.  The whole point is to keep you making choices through actions.  Being able to bypass all that crap and just press a single button to start the music would be antithetical to that primary point of such systems to their makers.

I want a realm if not an eternity away from the general issues of such devices, which are anything but relaxing and inviting in my opinion.

I deal with the much conceptually simpler situation of automating the powering up my living room audio system, which I can and do listen to from all other rooms in my house.  Especially from the Kitchen, which also serves as my home office, audio and video mastering center, as well as kitchen, dining room, and snack bar.  Nowadays it's the single room I spend the most waking hours within, so it's also where I listen to the most music in Background.

The kitchen has it's own fairly high end audio system, featuring Revel M20's plus a subwoofer, AND surround speakers.  It's a fine system for mastering or watching video.  But as Background Music, I find playing the living room stereo much much better.  It is of course fundamentally a better sounding system, because full range electrostats combined with subs and supertweeters and far more and better fine tuning.   I lose the stereo image from the Kitchen.  But for Background Music, having no stereo image makes it less distracting, and that's the key.  If it were more distracting, I couldn't tolerate it and get other things done.  Not only is there no stereo image, I do strongly get the feeling that the music venue is in an adjacent room.  Therefore it can't get in my way, but it can create an ambient vibe that helps me feel better, like being in your own private room at the club.

I consider background music just as important as serious listening.  Not because serious listening isn't a wonderful peak experience (when everything works and it clicks) but it's comparatively rare event in one's life, at least in my experience--I never had very much time for it.  Background music may ideally be something for nearly every waking hour, except when you need absolute silence for perfect concentration or talking to somebody.  But if it's not easy to start up your main system for this purpose, you might hardly ever enjoy it for such. 

If all you ever use your main system for is serious listening (and/or serious listening or other tests), then I suppose a fairly time consuming startup procedure may be tolerable, or even help prepare the mind.  Many audiophiles have startup procedures taking many minutes.  I've always wanted to make system startup as quick and easy as possible, in the hopes that this would get me actually listening to music more, and I started using home automation devices for this purpose inconsistently and with varying success since the 1980's.  Mostly, recently, I've had no automation whatever, and had to power up the amp and fiddle with preamp and other components before starting, and that almost always involved getting down on my knees to fiddle with the preamp buttons, often waiting to scroll through volume levels for an appropriate volume...

2) Selecting the music, playlist, or station to begin playing.

This is really the important thing, and I believe, ultimately the most difficult thing.  And I mean in merely selecting what to play next, though in some cases the mechanics of getting that thing playing may be considerable also, though I usually count those actions as part of step 1 above.

When I started on this article in January, I had no idea I was going to be able to construct an automatic playlist generator this year, if ever.  Having a computer program select the music seemed too far fetched an idea.

Partly it's because my dreams were too far fetched.  What if the computer, acting as your personal concierge, would sense you mood from moment to moment, and pick the perfect music to elevate your spirit?  Well, yes, that would be nice.  Closer to earth, algorithms in Pandora are supposed to select similar music, but in continuous varying mood, because that's supposed to be better.  Perhaps.

My own finding is that given the set of music I like as both background and partly as foreground, that is particularly to me music without words, or too much stress, which can be classical, jazz, electronic, or ambient, I can just mix it up at random--done properly without replacement to minimize repeats and let you hear everything in shortest order, and these simple playlists have revolutionized my music listening more than anything.

With the new playlist generator I am programming now, I can listen to automatically generated playlists designed to play so I hear everything in my music library with as few repeats as possible--that is until everything has been played (or at least auto-selected and possibly skipped).

Roon automatically loads my playlists.  For other programs, though I have not tested this for other audio programs yet,  I can also create virtual directories of soft links which take very little space, and works unless the audio folders are moved, which isn't an issue for a near daily playlist generator, and would be the case for a normal playlist also.

I haven't yet set this to automatically make a new playlist every every day.  But generally it takes very little action on my part, at least when the still under development playlist generating program is fully working despite yesterday's changes.  [As of June 2021, the playlist generator has a known bug when a too high percentage of albums has been played, which I haven't quite reached yet, but will require a major rewrite to fix.]

If I ever work this up for Rock music as well, I'l have to improve the customizeability.  In that case it might be more like the computer program making suggestions I can accept.  I think this approach is far better than the old logo what do you want to do today.   I don't know what music I want to play today.   It's great to have a program make suggestions if not the choices...and in many cases the choices themselves ...or perhaps the choices following a chosen scheme.  Making more choices is hard work.  Too hard to bother with in the course of daily living.  Let the computer do the choosing.  If I'm in the kitchen or phone I can skip an unwanted track or album in the Roon interface.

Automated System Start Up

This is something that seems of zero interest to any of my audiophile friends.  They've simply not responded to my self congratulation.  I've had great difficulty writing about it, because among other reasons I want to capture why I believe it is most important, yet others can't see why it would be necessary or even useful.

In the pursuit of audio perfection, many if not most audiophiles have the opposite of automation.  They have start up procedures that may take many minutes, perhaps even an hour or more for total warmup.  Of course they believe that all these steps they must take before playing music are absolutely necessary (though skeptics may wonder if they aren't superstitious rituals).  And while many of these audiophiles have been devotedly making the circuitry in their system components ever "simpler," through adept acquisition or modification or construction, this often means even more work in starting up each day.  Or switching from one source to another.  They may have to replug whole chains of equipment to switch from analog to digital sources (which I'm including in the "startup" part of the equation).

Many audiophiles also believe any attempt to make anything automatic must involve compromises at some level.  They would be utterly opposed, for example, to adding switch devices in any AC path.  I will have to explain why the switching I do is perfectly fine, at least in the living room system, yet I'm sure many audiophiles will never believe me.  However, I should note that I've been unable to add any kind of automated AC switching device in the kitchen, where due to multiple outside antenna grounds, AC grounds, and whole house network connections, and low power devices on micro switching supplies, is a virtual RF oven in the AC path of the power amp.  Anything but the most highly shielded AC cord introduces hum and noise.  But the living room has no such problems, despite 3 AC circuits, and network connections from the Kitchen.  This is an issue I hope to get fixed sometime possibly by moving some things around.)

Now you might think that turning on the stereo to play FM would be a fairly simple process taking about 5 seconds, as it once was for me, long ago, when I used a Marantz 2270 receiver (purchased in 1974).  To play FM, I would press the ON button and turn the selector switch to FM and possibly readjust the volume control, with all those controls being in one fairly convenient place.

But in fact it hasn't been that simple since the days when I had my Marantz 2270 right next to my bed, in my college dorm room, which was long ago and not for very long.  And of course for anything other than FM there was a matter of deciding what media object to play, obtaining said object, preparing it, mounting it on the playing device, and initiating playing.  So playing anything beyond a favored FM station can be a lot of work, which is impossible to have the time and energy to do, simply for background music.

Before long my Marantz receiver, and/or the Kenwood KT-7500 tuner I later plugged into it for better FM reception, was not right at hand, but typically across the room from my bed or chair.  I did that mostly by something like necessity, but often rued the day when I had to give up direct reach control of my system for "passive" line level switching and attenuation boxes.  (I denounced passive as lossy sometime around 1998 and stick to that now btw, but I was a passive fan from 1980-1998.)

By the early 1980's I owned a house with stereos in both living room and bedroom.  Partly because of inconvenience, and partly due to lack of free time, I didn't actually use either one very much.  The living room stereo had grown (and kept growing) into many components.  I once figured I spent far more time modifying audio equipment than actually using it.  I had become similar to what one friend calls a build-o-phile from 1980-1982 when I finally built my own tube preamp after having been a tube modifier for 5 years.  Well, so what, if I was having fun that way?  But it would have been nicer to run that show with music but in fact I rarely did.  One a handful of occasions by the late 1980's I had enjoyable audio parties.  But it was only on a small multiple of other occasions did I have time for extended serious listening.  And it almost never worth the bother to switch on my tri-amplified system of 1985 just to play background music on FM.  If I did switch to FM, it was only after already having played something else, and not being able to decide what to play next, I put on FM, which more often took more work than I wanted to bother with.  It should be the other way around, being easy to pop on FM at the spur of a moment, or perhaps the beginning of the day, and then switch to some collected music in higher fidelity form when time and energy permits and desire calls for it.

Some time around 1985, I set up my most beloved FM tuner, which was then a Fisher FM80R which always sounded marvelous (though in mono, I didn't care) atop the side table near my listening seat.  This was a marvelous innovation, as once again I could tune in different FM stations without having to get up.  And that was particularly important then as there were two fairly nice, if still far from perfect, FM stations, but between the two of them I could usually find something good to listen to.  But generally I didn't start my system to play FM.  If I started it to play a CD, and the CD ended, I have to walk across the room and fiddle with several controls to get it to play the FM tuner right next to my listening chair playing again.  Which I rarely did.  But at least I did that more often than switching on the system just to play FM.

I spent much time imagining a system which would let me switch from CD to tuner without having to get up, or maybe do anything at all.  I imagined a system which would sense that the music was not playing anymore, and then automatically switch to the FM tuner.  I figured I could simply add some relays somewhere, and I think I purchased a couple relays, but that was as far as this kind of automationproject ever got, until now, 35 years later.

But even with these early insights, I could begin to see the essential ingredients in effective automation:

1) It should be convenient, eliminating the need to get up and do things, such as with a push button reachable from where you are sitting without getting up.  It could be even more convenient, such as turning on music from a background source automatically when the primary source has stopped, or perhaps even when you get up in the morning, etc.

2) It should simplify, reduce, or eliminate the need to make decisions about what to play next.  Channels such as FM radio stations can do this, as do streaming channels or Pandora.  (One complication may be that FM stations are not always good to listen to and you may want to choose another FM station or source.  I am very fortunate in having a very good listener supported Classical Music FM radio station I love.  But it's not merely good fortune, because it's also something I've contributed to for about 30 years.  Some sort of personal contribution is probably necessary to make any such channel good.  Recently is the second time in 25 years I've been nagging them to clean up their sound, now they have a digital skipping problem which is apparent on both their analog and digital feeds.)

So the two essential ingredients are (1) reducing/eliminating need to do stuff, and (2) reducing/eliminating the need to make decisions.  Frankly I believe that it is the decision making that is the hardest of all.  Yet I've never heard other audiophiles even think about it.  Perhaps it's something that's uniquely hardest for me.

Enter Sonos

I may have thought about it the automatic music selection problem, but didn't do much until I learned about the Sonos system in 2006.  I quickly obtained a Sonos ZP80 and CR100 and a Windows XP machine to work as my Music Server.  Sonos didn't originally support Macs, and my Mac was ancient anyway.  These support uncompressed digital over wireless or ethernet, produce bit perfect (when no volume control or other features used) reproduction over their digital outputs, and have fairly decent 44.1 uncompressed digital analog to digital conversion for one analog input.  I wouldn't bother with their amplifiers, speakers, or other devices.  I have "high end" component audio systems in every room.

With Sonos, I could control everything (except turning my components on and off) with the convenient CR100 controller, which I kept on my bedside table.  Up until 2009, my primary audio system was the one in the bedroom.  The living room stereo was lower spec components I used only when playing the living room TV, which I only did for parties.  In 2009 I had a dental near death experience which opened me up to splurging on my dream system with electrostats and subs, as I imagined in 1992 when I bought the house.

Thanks to its combination of hard and soft buttons, the CR100 still represents a high water mark in semi-automated audio convenience.  I rued the day that Sonos no longer supported it.   Smartphones are not a very good substitute because you must do a lot of fiddling just to open the phone, select the Sonos app, and then get it to do some audio thing.  This is by necessity a two-handed operation which may even require putting your glasses on, and often results in failures and curses for an endless number of reasons, such as unsuccessful overnight smartphone update.  With the CR100 I could simply reach over and press the Play button to start when I woke up in the morning.  No securanoia.  And then press the Pause button when going back to bed.  Sonos occasionally did do updates, but back in the early days they went quickly and always succeeded.  No passwords or passcodes were ever required.

One of the reasons I bought Sonos devices was that I really lusted for the Random play mode, which Sonos had from the day I bought it.  I imagined this would finally solve the Selection problem, which had always been the key stumbling block to having music playing all the time, or even very often.  The other reason was line-in, which enabled me to play the FM tuner, which only worked decently on an indoor antenna in the living room, in the bedroom.  Running a cable between the two points was highly impractical.

I soon discovered it was very useful to organize my music files not just in one folder but in multiple folders.  When Sonos became available on the Mac, I created one folder for Classical and Ambient music suitable for background music in one folder, the original iTunes folder actually, and all the Rock and Jazz music which was too loud, jarring, or distracting for background music in another folder, which I called altTunes.  I imagined being able to play the background music randomly forever.

This seemed like a dream come true at first.  I also added an X10 Appliance Module* to start my power amplifier so I wouldn't need to get up from bed to turn it on.  The subwoofer plate amplifier has a music sensing auto switch.  

For a few years after 2005, X10 appliance modules were still working in my house.  But about then they started becoming more and more unreliable because they are sensitive to the noise created by DC power supplies, particularly things like cell phone chargers and computers.  The noise created by DC power supplies blocks X10 transmission.  There are various means of fixing this, such as using line filters and X10 signal extenders.  I clung to X10 for another 4 years accumulating all sorts of additional equipment like filters, extenders, and X10 signal vs noise meters.  Finally around 2014 or so I abandoned X10 for Insteon, which has been my chosen home automation device brand since then, working very reliably after being not-always-easy setup, and for which I also use a Universal Devices ISY994i controller, which is key to the way I do things in Home Automation now, and gets my highest recommendation of all.  It allows very flexible programming which I would not be happy without.  Universal Devices supports Insteon and some other automation device standards.

But back in the day, I could have done just about as much with simple X10 modules as with Insteon (or other systems) now,  if only X10 had just kept on working, using the fairly open computer programs and interfaces available.  Notably I do not at all believe Scenes are necessary, or in most cases even useful, except that certain things with Insteon (like full control of the lights on touchpads) require you to use Scenes.  The old Macros I used to cook up for X10 could have been about as useful as the combination of Programs and Scenes I use on Insteon now.  In my view, this is another area of geekdom where everyone says you must have this shiny new idea, but actually the old approach could have been made to work almost as well.  I think I would actually have hated Insteon because of all the more complex, but closed and ultimately more limited controllers made available from Insteon itself.  The magic piece is the ISY994i, which opens up the system to more capable programming.

I show the Living Room wall controller at the top.  This is right by the front door.  Most often I don't much bother to label the wall switches and mini controllers because I know which button does what (including a few choices that require 2 button presses).

Bedside Insteon 8 Button Module (unlabeled)



*****

But soon I found that simple "random" song playback as implemented by Sonos was unacceptable for various reasons.  Despite my using separate folders for different kinds of music, so I could have all classical/ambient music which is suitable background music in one folder, and loud talking music which demands your attention in others.  

Some of the reasons included:

1) The Sonos random play seemed always to start from a particularly tedious small file.  From this I concluded that Sonos implemented a deterministic randomization procedure.  It is much better for this purpose to seed the random number generator from a non-deterministic or at least less-deterministic source, such as clock time, or as exists in Unix and MacOs, the number of clock clicks since startup (which is a larger number and therefore better than the number of seconds since starting).  Then it should never start the same way or repeat the same random pattern.

2) Also the fact that Sonos random play started from the same song revealed another fault.  It implemented a simple with-replacement randomization strategy.  Thus no matter how many times a thing has been played before, it would still play as the first song at the beginning of a deterministic random play.  The with-replacement strategy also means you will hear other songs you had heard at the beginning of the last random play.  (They might have fixed this since then.)  A with-replacement strategy also has many other faults.  One is that there is no guarantee the same song won't be played twice in fairly close succession.  A Square Root of N Rule applies: you will hear a repeat about every square root of N times, where N is the number of songs in your library.  Finally, sometimes, without-replacement search rule is implemented, sometimes it may be lost every time there is a power cycle or power failure.  So then you're back to the same only forever heard songs.  Finally, the Square Root of N rule also has a dark side: as well as some songs being repeated over and over, there seem to be an endless number of songs which are never heard at all.

3) In my opinion anyway, whole album song play is better.  In other words, albums should be selected randomly, then all the songs in that album played in their correct order.  (If an album contains multiple Titles, it might be OK to play per title, so long as the titles are not too short.)

So while it seemed like Sonos random play ought to be the new millenium in automatic music, it wasn't.  I quickly grew tired of it.  (Cynically you might wonder if that wasn't the plan.)  Before long, I had subscribed to Pandora and quickly upgraded to Pandora Premium.  Pandora did a pretty good job of selecting new music to my taste and in different categories.  However, I would never use Pandora as a Featured source, it was just some level of MP3 compression.  I discovered a lot of new-to-me artists on Pandora.  But sadly, eventually even Pandora became tiresome as background music.

I haven't used Sonos Random Play in over a decade.  All services push Radio Stations which i haven't yet found acceptable in digital form.  I like my local classical radio station KPAC best broadcast in FM Stereo.

Just as my 1980's automated background music idea centered on FM radio, so did the beginning of my new one last year.

Actually, it started from an attempt to improve on the time shifting of my favorite program on KPAC, Performance Saturday.  Often I was at the Symphony itself, or doing something else on Saturday night.  So I recorded via in incredible path.  Starting from the indoor antenna in the magic spot for KPAC, to my Pioneer F-26 tuner, into the analog input of a Sonos Connect, through hardwired ethernet connections to my large DLink gigabit switch, on on the hardwired ethernet connections into the bedroom, through another Sonos Connect, and into my Nakamichi RX-505 and onto Chrome tape, with Dolby B.  This actually produced wonderful sounding recordings, I still say.  But I thought it could be better and simpler.

Plus, it would be useful to have a digital recorder deployed in the Living Room for making digital copies of LP records as well, and LP record tests (which is mainly what I have done so far, yielding hugh improvements in tonearm resonance control).  So, sometime in 2019 I purchased a Marantz PMD 580 recorder for the living room.  (Strangely, I was not happy with the digital recordings until many furthher changes.  Until now, maybe, it hadn't been as good as the previous system based on a Cassette recorder!)

But before I realized the PMD 580 had a crappy sounding analog to digital converter, even crappier than humble Sonos, I figured I was at the dawn of a new era in good sounding FM and recordings from it.  (Actually, I was at the bottom of a steep hill.)

While purchasing another impeccable Henry Engineering AES splitter from Markertek for splitting the digital from my Lavry AD 10 analog to digital converter off to the Marantz so I could use the better Lavry for making digital copies of Vinyl, and listen at the same time, I noticed another very interesting product from Henry Engineering.  A 3 way AES digital switch using relays.




This is a powered pushbutton switch.  You push one of the 3 buttons and it sets the relays for that particular input.  And the light on the button lights up (a very cool touch).

And, not only that, this 3-way switch can be controlled by the pins on a DE-9 connector.   That was the key ingredient to make automated background music from FM radio work.  Those pins work on contact closures which can be controlled by various means, but trivially easily from an Insteon home automation system using the marvelously flexible Insteon I/O module.  I use 3 of them (plugged into a  Hammond power strip connected to a non-audio AC circuit) for the 3 possible selections: Background Music (FM radio), Feature Music (Oppo), and Mute.






One absolutely essential thing for Automated Background Music is an independent volume control for the foreground and background sources.  You may have been listening to vinyl last night with the system cranked all the way up.  Or cd's.  The system has to set the volume for the background music source independently of that somehow to make automatic switching useful.

Modern Day Levinson preamplifiers feature something that would work.  You can assign relative and starting volume levels for different sources.  Sadly few other high end preamplifiers, or any preamplifiers, have such a feature.  My Tact digital preamplifier, just as costly as a Levinson when new, does not.

But using the Henry Engineering switch at the to switch the input to my miniDSP crossovers from the Tact to a new separate digital converter for the background music source, and I could use a Behringer DEQ 2496 to fine tune the digital level, aka volume, specifically for the FM tuner.

So that was the answer for me, with zero degradation, to switch the AES balanced digital stream (with relays) from one path to another.  I needed to create a new digital conversion path for the background music source, my Pioneer FM-26 tuner.

I had originally figured I'd use the Marantz PMD-580.  But by the time I'd purchased the Henry Engineering switch I'd already decided the PMD-580 conversion just didn't sound good enough.  I couldn't use my Lavry for this because if I were using the Lavry for something else, such as listening to Vinyl, then I couldn't just go to the FM signal at the push of one button.  Many changes would need to be made...changing the source input on the XSP-1 preamp, and changing the level.  I still can't automate that.

But in my closet I had a never-used-by-me nice looking (and it turns out, very nice sounding) Analog to digital converter.  It's a Black Lion Sparrow (now known as the Sparrow 1).  And in my testing it sounded even as nice as the Lavry on FM when buffered and stepped up slightly by minty Musical Fidelity X-10 V3.  The AES digital from the Sparrow then feeds a Behringer DEQ which trims the level.  Levels from -15dB to -6dB are useful, I generally like -12dB or so for background.  Sure I lose resolution by this attenuation, but only in the context of 24bit audio transmission.  Subtract 12dB from the 24 bit resolution of 144dB and there's still 116dB.

Sparrow ADC shown beneath Sonos Connect in crowded back of shelf

Marantz reccorder, Behringer EQ, and Musical Fidelity Buffer


The Fixed Output of the Pioneer F-26 FM Tuner goes to the Musical Fidelity X 10 V3 tube buffer.  The unbuffered output goes to a Sonos Connect, the buffered output goes to the Black Lion Sparrow Analog to Digital converter running at 48 Khz.  The AES digital output of the Sparrow goes to the Behringer, which fine tunes the output level in digital usually with about a 12 dB reduction.  The adjusted digital signal then goes out from the Behringer in AES balanced over mogami cable to the Henry Engineering 3 way AES switch.  The switch feeds an AES splitter which feeds the 3 miniDSP digital processors that make up my "crossover."  The Tact is completely bypassed when I'm listening to the tuner, and therefore the Tact digital level control has no effect on FM, only the "Feature" source.

The Optical Digital output of the Behringer is converted to coax by an adapter and fed to the Marantz PMD, which also accepts an balanced AES digital from the Lavry I used when digitizing vinyl through a Henry Engineering digital splitter (the other path is for my stereo itself).  In no case do I use the analog inputs (and therefore the analog to digital converters) of the PMD 580 which I consider inferior and grainy sounding.

This new pathway for the FM tuner, combined with now using an outdoor antenna run through the Kitchen have improved the sound of FM immensely.  This, and the electronically controllable an lossless audio signal switch, and the independent level control, were the essential ingredients of an automated background music switch.

But you'd still need to turn the power amp on and off.  I find, that on the living room circuit, and Insteon On/Off module works flawlessly, adds zero noise, grips the outlet and the plug very tightly, and has no detrimental sound quality impact.  This works perfectly with the Hafler 9300 which is well within the ratings of the device.  It did not work so well with the Aragon 8008 BB which has 2.2kW of primary power transformers.  The Insteon is rated at 1800W.  Strangely, however, in the radio frequency tunnel of my kitchen, the 2 inches of unshielded wire inside the Insteon On/Off module picks up noise big time, like you can't ignore it. That was true with unshielded power cords used there as well, on an otherwise equivalent Hafler 9300 I use for the Revel's in the Kitchen.




So now I can turn on the Living Room stereo to play the FM tuner, regardless of what it was playing just before, and even turn the amplifier on if needed through 3 wall keypads in my house and keypads by my kitchen chair and bedside.  And mute or turn it off too.  It turned out that when the Henry Engineering switch is set to an input with nothing conveniently, very conveniently the 3 miniDSP crossovers which are in line with it's output (through a Henry Engineering AES splitter) mute perfectly.  Even when the Hafler power amplifier is turned off the muting is important to keep the subwoofers and supertweeters from playing.

And then the third button (and corresponding Insteon I/O module) selects "everything else" other than the FM tuner.  I originally called the FM tuner input Background Music and the "everything else" input "Feature Music," thinking like a Featured artist is why you go to the concert, the Feature is what you must select, whereas the Background is preselected.

However it did not occur to me that the term Feature Music has the unfortunate initials FM, which could be confused for my FM tuner used as background music.

Anyway, the Feature Music designation itself is somewhat obsolete since now my "everything else" can be preselected by my computer program, not actually human selected/featured.

Now on the Living Room wall keypad, I've designated the two selections as FM (as in FM tuner) and DVD (as in my Oppo BDP-205, which serves as my high resolution disc player AND streamer with SPDIF 24 bit digital output to the Tact digital preamplifier) even though that would also be the selection for listening to Vinyl (with a different selection on the Tact).  It would be nice if I could control the Tact as nicely as I do then Henry Engineering source switch, with contact closures.  The Tact has a proprietary digital interface that its program on a 2000 era PC communicates with.  I very rarely use that since I do not use the Tact's room correction or even measurement anymore.

But it was still a bother to get up from the Kitchen to switch the Oppo in the living room on to listening to harddrive and streaming musing through the Oppo 205 digital output which feeds my Tact.  Those work best using the DC triggers.  So I have a pair of Insteon On/Off Modules which power regulated 12DC adapters which are connected to the trigger inputs of the Oppo 205 and the Emotive XSP-1.  The Oppo is automatically turned on whenever I select "DVD" in any of the wall switches and keypads in the house.  The Emotiva is best switched on by the ON button of the other On/Off module.  Both are automatically turned off for "bedtime" or when the mute button is pressed a third time.  (The first press is soft mute, which permits background music to come on in one hour, the second press is hard mute which keeps the music off indefinitely, and the third press is system off.)  The two Insteon modules are connected to an all metal noise reducing power strip which is connected to the "main" living room circuit and not any of the 3 dedicated audio circuits.  I bought that strip for reducing the pops in my stereo system created by switching the Tensor lamp for the turntable and other purposes, but it is also good for giving Insteon modules a true AC connection (not going through my Panamax) and not polluting my line audio devices with yet more DC power supplies.





My Playlist Generator for Roon (which is my current music program).  Sadly it seems you can't trust streaming services, or even subscriber-funded Roon it seems, to implement a decent playlist program.  Like everything else, Roon is always trying to sell you new music.  That's what Roon Radio does.  I find that when any program (except Pandora, which did it fairly well) tries to sell me new music, I hate nearly every song it selects.  Especially the first one.

But, fortunately, Roon does provide a way to import playlists, including from simple M3U files.  I've recently discovered what a powerful idea this is.

What needs to be created is a Daily Playlist.  That's not too often, I think just right.  Thanks to using an across-session without-replacement randomization strategy (based on a stored dot file listing all the files currently played) combined with automatic-replacement-reset-on-exhaustion, you can be sure that today's Daily Playlist won't repeat something on yesterday's, or in my case going way back, except in the rare case that still occurs right after a reset.  To overcome the reset problem, an additional reset window is applied for N/4.  For the first N/4 of random selection, nothing in the previous N/4 is permitted.

It is also critical to use an unbiased shuffling algorithm, like Knuth's (also given other names).  The  most intuitive shuffling algorithm is biased, meaning it can only reproduce a limited number of the possible shufflings.  I believe this can lead you to just feel what is coming up next, and make everything seem dull.

Roon applies a very nice level compensation on an album basis to keep the playlist at the same level without compromising the musical integrity of any album.  Roon also nicely stops and remembers its position when the Oppo is shut down through my automated system.  (I keep it going until I hit the sheets at bedtime.)  However, Roon does not restart the playlist when I restart the Oppo.  I wish it did that though I'd have it apply only to trigger-starts not front panel pushbutton starts.  Now I have to go into a Roon interface such as on my computer to restart the playlist playing, which is very easy since it brings it right back to the position when the Oppo was shut down.

Roon playing playlist generated by my program "mplay"

Roon doesn't list track numbers any  more, which is a misfeature in my opinion and others.  Track numbers have been replaced by "play" buttons.  Somehow I remember calling for visible play buttons in the past.  Perhaps I even said they could replace the "useless" track numbers.  Well now I find those track numbers are not at all useless to a serious music lover, for which we play a hefty fee.  If I asked for this, I was wrong, and I am sorry.  Somehow the track number should be made into a visible "play" button, combining both concepts.  Or just bring back the track numbers and have a Play dropdown menu if the combo I describe is impossible for some reason.