Monday, 15 December 2014

DSD - Is DST Compression Really Lossless?

The SACD format was built around DSD right from the start.  Since DSD takes up about four times the amount of disk space of a 16/44.1 equivalent this meant that a new physical disc format with more capacity than a CD was going to be required.  Additionally, SACD was specified to deliver multi-channel content, which increases the storage requirement by another factor of 3 or more, depending on how many channels you want to support.  The only high-capacity disc format that was on the horizon at the time was the one eventually used for DVD, and even this was going to be inadequate for the full multi-channel capability envisaged for SACD.

The solution was to adopt a lossless data compression protocol to reduce the size of a multi-channel DSD master file so that it would fit.  The protocol chosen is called DST, and is an elaborate DSP-based method derived from the way MP3 works.  Essentially, you store a bunch of numbers that represent the actual data as a mathematical function which you can later use to try to re-create the original data.  You then store a bunch of additional numbers which represent the differences between the actual data and the attempted recreation.  If you do this properly, the mathematical function numbers, plus the difference data, takes up less space than the original data.  On a SACD the compression achieved is about 50%, which is pretty good, and permits a lot of content to be stored.

Given that DST compression is lossless, it is interesting that the SACD format allows discs to be mastered with your choice of compressed or non-compressed data.  And, taking a good look at a significant sample of SACDs, it appears that a substantial proportion of those discs do not use compression.  Additionally, if you look closely, you will see that almost all of the serious audiophile remasters released on SACD are all uncompressed.  So the question I have been asking is - is there any reason to believe that DST-compressed SACDs might sound worse than uncompressed ones?

First of all, let me be clear on one thing.  The DST compression algorithm is lossless.  This means that the reconstructed waveform is bit-for-bit identical to the original uncompressed waveform.  This is not at issue here.  Nor is the notion that compressing and decompressing the bits somehow stresses them so that they don’t sound so relaxed on playback.  I don’t buy mumbo jumbo.  The real answer is both simpler than you would imagine (although technically quite complicated), and at the same time typical of an industry which has been known to upsample CD content and sell it for twice the price on a SACD disc.

To understand this, we need to take a closer look at how the DSD format works.  I have written at length about how DSD makes use of a combination of massive oversampling and noise shaping to encode a complex waveform in a 1-bit format.  In a Sigma-Delta Modulator (SDM) the quantization noise is pushed out of the audio band and up into the vast reaches of the ultrasonic bandwidth which dominates the DSD encoding space.  The audio signal only occupies the frequency space below 20kHz (to choose a number that most people will agree on).  But DSD is sampled at 2,822kHz, so there is a vast amount of bandwidth between 20kHz and 2,822kHz available, into which the quantization noise can be swept.

One of the key attributes of a good clean audio signal is that it have low noise in the audio band.  In general, the higher quality the audio signal, the lower the noise it will exhibit.  The best microphones can capture sounds that cannot be fully encoded using 16-bit PCM.  However, 24-bit PCM can capture anything that the best microphones will put out.  Therefore if DSD is to deliver the very highest in audio performance standards it needs to be able to sustain a noise floor better than that of 16-bit audio, and approaching that of 24-bit audio.

The term “Noise Shaping” is a good one.  Because quantization noise cannot be eliminated, all you can hope to do is to take it from one frequency band where you don’t want it, and move it into another where you don’t mind it - and in the 1-bit world of DSD there is an awful lot of quantization noise.  This is the job of an SDM.  The design of the SDM determines how much noise is removed from the audio frequency band, and where it gets put.  Mathematically, DSD is capable of encoding a staggeringly low noise floor in the audio band.  Something down in the region of -180dB to -200dB has been demonstrated.  What good DSD recordings achieve is nearer to -120dB, and the difference is partly due to that fact that practical real-world SDM designs seriously underperform their theoretical capabilities.  But it also arises because better performance requires a higher-order SDM design, and beyond a certain limit high-order SDMs are simply unstable.  A workmanlike SDM would be a 5th-order design, but the best performance today is achieved with 8th or 9th order SDMs.  Higher than that, and they cannot be made to work.

So how does a higher-order SDM achieve superior performance?  The answer is that it packs more and more of the quantization noise into the upper reaches of the ultrasonic frequency space.  So a higher-performance higher-order SDM will tend to encode progressively more high-frequency noise into the bitstream.  A theoretically perfect SDM will create a Bit Stream whose high frequency content is virtually indistinguishable from full-scale white noise.

This is where DST compression comes in.  Recall that DST compression works by storing a set of numbers that enable you to reconstruct a close approximation of the original data, plus all of the differences between the reconstructed bit stream and the original bit stream.  Obviously the size of the compressed (DST-encoded) file will be governed to a large degree by how much data is needed to store the difference signal.  It turns out that the set of numbers that reconstruct the ‘close approximation’ do a relatively good job of encoding the low frequency data, but a relatively poor job of encoding the high frequency data.  Therefore, the more high frequency data is present, the more additional data will be needed to encode the difference signal.  And the larger the difference signal, the larger the compressed file will be.  In the extreme, the difference signal can be so large that you will not be able to achieve much compression at all.

This is the situation we are in with today’s technology.  We can produce the highest quality DSD signal and be unable to compress it effectively, or we can accept a reduction in quality and achieve a useful degree of (lossless) compression.

So what happens when we have a nice high-resolution DSD recording all ready to be sent to the SACD mastering plant?  What happens if the DSD content is too large to fit onto a SACD, and cannot be compressed enough so that it does?  The answer will disappoint you.  What happens is that the high quality DSD master tape is remodulated using a modest 5th-order SDM, in the process producing a new DSD version which can now be efficiently compressed using DST compression.  Most listeners agree that a 5th order SDM produces audibly inferior sound to a good 8th order SDM, but with real music recordings it is essentially impossible to inspect a DSD data file and determine unambiguously what order of SDM was used to encode it.  So it is easy enough to get away with.

How do you tell if a SACD is compressed or not?  Well, if you have the underground tools necessary, you can rip it and analyze it definitively.  For the rest of us there is no sure method except for one.  You simply add up the total duration of the music on the disc, and calculate 2,822,400 bits of data per second, per channel.  If the answer amounts to more than 4.7GB then the data must be compressed.  If it adds up to less, there is no guarantee that it won’t be DST-compressed, but the chances are pretty good that it is not.  After all, if the record company wants to compress it, they’d have to pay someone to do that, and that probably ain’t gonna happen.  The other simple guideline is that if it is multi-channel it is probably compressed, but if it is stereo it probably is not.

Of course, none of this need apply to downloaded DSD files.  If produced by reputable studios these will have been produced using the best quality modulators they can afford, and since DST encoding is not used on commercial DSF and DFF* files this whole issue need not arise.  However, if the downloaded files are derived from a SACD (as many files are which are not distributed by the original producers), then the possibility does exist that you are receiving an inferior 5th-order remodulated version.  The take-away is that not all DSD is created equal.  Yet another thing for us to have to bear in mind!

[* Actually, the DFF file format does allow for the DSD content to be DST compressed, because this format is used by the mastering house to provide the final distribution-ready content to the SACD disc manufacturing plant.  However, for commercial use, I don’t think anybody employs DST compression.]

Saturday, 13 December 2014

BitPerfect 2.0.2 Released

Today, BitPerfect 2.0.2 has been released to the App Store.  It may take up to 48hrs before it shows up in all regions.  V2.0.2 contains several minor bug fixes, plus some minor enhancements to the audio engine to improve stability.

BitPerfect 2.0.2 is a free upgrade for existing BitPerfect users.

Monday, 24 November 2014

24-Bits Of Christmas

Once again LINN Records are announcing a "24-Bits Of Christmas" promotion, where they are offering a free high-resolution download every day from December 1st through Christmas.  The doors are opening early this year, and the first track is already available.  Check it out!

A Fix for the Yosemite Console Log Problem

BitPerfect user Stefan Leckel has come up with a useful solution to the Yosemite Console Log problem.  In case you are unaware, under Yosemite, when you use BitPerfect, iTunes fills the Console Log with a stream of entries - several per second - which rapidly fills the Console Log to capacity.  At that point, the oldest messages are deleted.  In effect, this renders the Console Log pretty useless as a diagnostic tool.

Stefan's ingenious solution is a simple script file which, in effect, sets up the Console App so that it ignores these specific messages.  However, because the script works at the system level, using it requires a level of comfort with working on OS X using tools that are capable of wreaking havoc, although hopefully the instructions below are easy enough for most people to use with a degree of comfort.  As with anything that involves tinkering at the system level, YOU USE THIS TOOL ENTIRELY AT YOUR OWN RISK, AND WITH NO EXPRESS OR IMPLIED WARRANTY.  If in doubt, channel Nancy Reagan, and "Just Say No":)

First, you need to download a special script file which you can download by clicking here.  This will download a file called  It doesn't matter where you place this file.  Your downloads folder would do fine.  If you are concerned about the authenticity of this file, or what it might be doing to your Mac, the contents are reproduced below for you to inspect and compare.

To use the script file, you need to first open a Terminal window.  Inside the terminal window type the following: "sudo bash " - don't type the quote marks, and be sure to leave a space after the bash - and DON'T press the ENTER key.  Next, drag and drop the file that you just downloaded into the Terminal window.  This action will complete the "sudo bash " line with the full path of the file.  Now you can press ENTER.  You will be prompted to enter your system password.  Enter it (nothing will show in the Terminal as you type), and hit ENTER.

That's it.  The Console Log should now work fine.  If you want to reset it back to how it was, just re-run the same sequence.  The same command is designed to toggle the modification on and off.

Thank you Stefan!

Below, for reference, I have reproduced the content of in full (lines shown in green are wrapped from the end of the previous line):

# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# use at your own risk, no warranty
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# checks if asl.conf is already modified
set -x
cat /etc/asl.conf|grep -F "? [= Facility] [=
Sender BitPerfect] [S= Message] ignore" > /dev/null

if [ $? -eq 0 ]
    echo "removing bitperfect modification from /etc/asl.conf file"
    cat /etc/asl.conf|grep -v -F "? [= Facility] [= Sender BitPerfect] [S= Message] ignore" > /etc/asl.bitperfect
    echo "adding bitperfect modifications to /etc/asl.conf file"
    echo "? [= Facility] [= Sender BitPerfect]
[S= Message] ignore" > /etc/asl.bitperfect
    cat /etc/asl.conf >> /etc/asl.bitperfect

echo "backup /etc/asl.conf to /etc/asl.conf.bitperfect"
cp /etc/asl.conf /etc/asl.conf.bitperfect

echo "activating new config"
mv /etc/asl.bitperfect /etc/asl.conf

echo "restarting syslogd daemon"
killall syslogd

echo "done."

Friday, 21 November 2014

The Importance Of Being Roger

Roger has been somewhat shunted unceremoniously to one side in the modern world.  We seem to have forgotten why he was ever there in the first place, and the important role he used to play.  Without Roger, our world today is a less friendly place, one in which misunderstandings are easy to come by.  Personally, I miss him, but then again I suppose I am just another old fart.

In the early day of person-to-person radio communications, Roger played a critically important role.  If you are flying an aeroplane, and you want to announce to the control tower that you’re commencing your takeoff roll, you want to be sure that the control tower is aware of that, otherwise all sorts of unpredictable outcomes could potentially result, some of them dire.  That’s where Roger comes in.  The control tower responds “Roger” and now you know your message has been received and, by extension, that the control tower knows you are rolling.  It is part of what we today recognize as a handshaking protocol, something that ensures the effectiveness of a two-way communication.  Handshaking is a tool to ensure that a message has been received, that it has been understood, and that both parties know either who is expected to speak next, or that they are agreed that the conversation is over.

When speaking to someone face-to-face, or over the telephone, there are implied cues to which we tend to adhere in order to provide this handshaking element.  These can be turns of phrase, vocal inflections, gestures, and the like.  They often vary among cultures.  How we communicate with a person has important ramifications as to how the other person perceives us, and how we in turn perceive the other person.  We may perceive that person to be brusque, friendly, rude, gregarious, or to have any of a number of attributes.  If, as a person, your inter-personal communications cause others in the world to perceive you wrongly, it is well-understood that you could have problems in your life.

Generally, it is important in our day-to-day inter-personal communications that we understand how the subtext of our communication is being received.  If you ask someone if they want to have a beer with you after work, there is world of difference between “No” and “Gee, I’m sorry, but my daughter has soccer practice”.  Most of us, when we speak with someone face-to-face or on the telephone, understand the subtext, even as we recognize that the understanding itself is sometimes in error.

Roger’s absence first became a problem with the widespread introduction of e-mail into mostly business correspondence.  If I send an e-mail inviting a colleague out for dinner when I’m in town next week, many people will find it acceptable to reply “No” in an e-mail when they really mean “Gee, I’m sorry, but I’m out of town that day”, even when they would never dream of responding with the terse “No” in a face-to-face situation.  It is part of a complex issue, one on which I don’t propose to write a treatise, but a major contributory factor is that, for most of us, it takes far longer to compose an e-mail message that properly encapsulates the subtext with which we wish to endow our response, and often we just don’t feel we have that time.  Personally, I find that excuse to be a lazy one, and if not, then disrespectful towards the recipient.

In today’s world, for many people the text message has replaced the e-mail, particularly for one-on-one conversations.  Partly by their nature, and partly due to the hardware typically used to send them, text messages tend to be terse by default.  Additionally, text message conversations tend to replace telephone conversations for many people.  They want to multi-task.  They will fit your text conversation in as they find time during the course of their day.  And so will you.  Consequently, the alternative of a phone call takes on something of the aura of an intrusion.  Which is rather frustrating, since, in the grand scheme of things, a phone conversation is always many, many times more effective.  But that too is another discussion.

This is where Roger comes in.  The lingua franca of texting is the curt message.  I don’t know about you, but I really feel the need to know that a message has been received and understood.  If I send a text that says something to the effect of “I need to see your report by the end of the day”, I feel unhappy if I don’t get a response.  It’s like if I said the same thing to that person in my office, and he just walked out without responding.  It is very clear to me how I would interpret such an action.  And shortly thereafter it would be equally clear to the other person.  What is missing is Roger.  All you need is a text response that says “Will do”.  Or even “K”, if that’s your thing.  Sadly, and frustratingly, I am finding that Roger is very much the exception rather than the rule these days.

I said earlier that inter-personal “handshaking” protocols are to a large degree cultural, and maybe that’s what’s going on here.  A texting culture is arising - or has arisen - in which subtext is no longer being conveyed at all - even emoticons, as best as I can tell, are en route to being passé.  If so, that is a counter-productive development.  I do converse with a few people routinely whose preferred mode of communication is the test message, and have done for some time.  I still find it a frustrating medium, and mainly because I dearly miss Roger, which I still give, but rarely receive.

Thursday, 13 November 2014

The PS Audio DirectStream DAC - Part IV.

It has been several months now since I concluded my review of the PS Audio DirectStream DAC, and a pretty positive review it was.  Since that time the unit has continued to very gradually break in, and there have also been a couple of firmware updates (all of which are available on PS Audio’s web site at no charge), each an improvement, but not sufficient to justify adding substantially to the gist of my review.  But recently there has been a major firmware update - version 1.2.1 is its designation - which is a sufficient game-changer that it warrants a whole update of its own.

So why should something as perfunctory as firmware change the sound of a DAC?  Normally when we think of firmware updates we think of functionality rather than performance.  And indeed there are functionality issues which are addressed here - the DirectStream now fully supports 24/352.8 PCM, which it did not do with the original firmware.  But in a DAC in particular, a large part of what it does performance-wise lies in the processing of the incoming data in the digital domain, and those processes are often under the control of the firmware.  Particularly in the DirectStream, where all that processing happens on in-house PS Audio firmware rather than within the proprietary workings of a third-party chipset.  What goes on under the aegis of its firmware is to a large degree the heart and soul of what the DirectStream is all about.

I have communicated at length with Ted Smith, designer of the DirectStream, about the nature and effect of the changes he has made.  I’m not sure how open those discussion were intended to be, and so I will not share them in detail with you, but there are two areas in which his attention has been primarily focussed.  The first is on the digital filters, and how their optimal implementation is found to affect jitter, something which initially surprised me.  The second is on the Delta-Sigma Modulators which generate the single-bit output stage, always an area ripe for improvement, in which Ted has reined in the attack dogs which stand guard to protect against the onslaught of instabilities.  Together, the effect of these significant updates has been transformative, and that is not a word I use lightly.

The simple description of the sound of the 1.2.1 firmware update is that it has opened up the sound.  Everything has more space and air around it.  Sonic textures have acquired a more tactile quality.  The music just communicates more freely.  It would be easy to sit back and characterize the sound as more “Analog-” or “Tube-” like.  These are words the audiophile community likes to use as currency for sound that is quite simply easy to listen to.  It is interesting that we audiophiles admire and value attributes such as sonic transparency, detailed resolving power, and dynamic response, and yet how often is it that when we are able to bring them together the result is painfully unlistenable?  It is these Yin and Yang elements that are foremost in my mind as I listen to the 1.2.1 version of the DirectStream.

So, without further ado, what am I listening to, and how is it sounding?

First up is “Bending New Corners” by the French jazz trumpeter Erik Truffaz.  This is a curious infusion of early-‘70s Miles Davis, ambient groove jazz, and trip-hop, which brings to mind the sort of music that might have deafened you in the über-trendy restaurant scene of the 1990’s.  I first heard it on LP at the Montreal high-end dealer Coup de Foudre, and today I’m playing the CD version.  The mix is a relatively simple one involving trumpet, bass, keyboards and drums, plus the occasional vocal stylings of a rapper called ‘Nya’.  The music is set in an atmospheric ambient, and is quite simple in its sonic palette, but nevertheless I have always had trouble separating out the individual instruments.  I was keen to know what the additional resolving power of the 1.2.1 DS would make of it.

What the additional clarity brought was the realization that I have been hearing the limits of this recording all along.  The trumpet has a very rich spectrum of harmonics which overlay most of the audio spectrum, and when it plays as a prominent solo instrument those harmonics can intermodulate with the sounds of many other instruments, making it difficult to hear through the trumpet and follow the rest of the mix.  If the intermodulation is baked into the recording, then no degree of fidelity in the playback chain is going to solve that problem.  This is what I am plainly hearing with the 1.2.1 DS.  This recording, far from being a clean and atmospheric gem waiting for an extraordinary DAC to liberate its charms, is a bit of a digital creation.  The extraordinary DAC instead reveals its ambience as a digital artifact.  The lead trumpet and vocals can be heard to have a processed presence about them.

Once you have heard something, you can never “un-hear” it again.  It’s a bit like skiing, in that once you’ve mastered it, it becomes impossible to ski like you did when you were still learning.  At best, all you’ll manage is a caricature of a person skiing like a novice.  I can now go back to the CD of “Bending New Corners” on a lesser system and will recognize its flaws for what they are, even though previously I would have interpreted what I was hearing differently.

My experience with Bending New Corners was to be repeated many times.  As I type, I am listening to Ravel’s Bolero with the Minnesota Orchestra conducted by Eiji Oue on Reference Recordings, ripped from CD.  It begins with a pianissimo snare drum some 20 feet behind the speakers and slightly to the right of center.  This recording has always been one of which I have thought highly.  The solo pianissimo snare is a good test for system imaging.  However, I now hear the snare as living in a slightly smeared space.  I perceive its sonic texture differently - more plausibly accurate if you will (a layer of sonic mush hovering around the instrument itself has evaporated away like the early mist on a spring morning) - but I somehow cannot place the image more accurately than a few feet.  I surmise that, because my brain is more confident that it is hearing the sound of a pianissimo snare drum, it therefore also expects to hear that sound more accurately localized in space.  But it is unable to do that.  As a consequence, although I never previously thought that the stereo image was wanting, I now appreciate that in fact it is, and I wonder how a higher-resolution version of this recording would compare.

Here is a song my wife likes.  It is “Hollow Talk” from the CD “This is for the White in your Eyes” by the Danish band Choir of Young Believers.  My wife had me track it down because it is the theme tune on a Danish/Swedish TV show we have been watching on Netflix called The Bridge (Bron/Broen).  It is another example of how the DS 1.2.1 can render a studio’s clumsy machinations clearly manifest.  The echo applied to the vocal adds atmospherics but is just unnatural.  As the track proceeds, the production gets layered on and layered on - and then layered on some more.  The effect is all very nice when heard on TV, but on my reference system driven by the DS 1.2.1 it just calls out for a lighter touch.  For example, at the beginning I heard a faint sound off to the left like someone getting into or out of a car and closing the door.  I don’t see why they wanted to include that - I can’t imagine it is particularly audible unless you have a highly resolving system such as a DS 1.2.1, one which makes clear the dog’s breakfast nature of the recording.

Next up is another old favourite of mine, “Unorthodox Behaviour” by 1970’s fusion combo Brand X.  I saw the band live at Ronnie Scott’s club in London back in 1975 (or thereabouts) and bought the album on LP as soon as it came out.  Today, I’m playing a 24/96 needle-drop.  I just love the opening track, Nuclear Burn.  Percy Jones’ bass lick is original and memorable, and extremely demanding of technique.  DirectStream 1.2.1 lets me hear the bass line more clearly than I have ever heard it before.  I had always thought it to have a slightly muddy texture - not surprising, given that playing it would tie most people’s fingers into inextricable knots - but now I hear just how extraordinarily skilled Jones’ bass chops really were.  And below it, Phil Collins’ kick drum has acquired real weight.  Not that it sounds any louder, or deeper.  It is more like the pedal mechanism has had an extra 5lb of lead affixed to it.

Now to a lonely corner of your local music store, where the Jazz, Folk, and Country aisles peter out.  This is where you’ll find Bill Frisell’s 2000 CD “Ghost Town”, a finely recorded ensemble of mostly acoustic guitar and banjo music with Frisell playing all the instruments.  Despite the album’s soulful and contemplative mood, due at least in part to the sparse arrangements and absence of a drum track, I keep expecting it to break out suddenly into 'Duelling Banjos'.  The track list comprises mostly Frisell original compositions together with a handful of well-chosen covers.  Apart from enjoying the music, the idea here is to play Spot The Guitar.  On a rudimentary system this involves telling which are the guitars and which the banjos.  As the system gets better, you start to be able to tell how many different models of each instrument are being played.  With the DS 1.2.1 I suspect you could go further and identify the brands (Klein, Anderson, Martin, etc.).  Me, I’m not a guitar head, and can’t do that (although, back in the day, I used to be able to reliably tell a Strat from a Les Paul, even on the most rudimentary systems), but I do hear the different tonalities and sonorities very clearly.

Gil Scott-Heron is credited in some circles as being the father of rap.  He was a soulful yet extremely cerebral poet-musician with a strong sense of a social message.  His 1994 CD “Spirits” was a bit of a swan song, and contains a track “Work for Peace” which is a political rant against the 'military and the monetary', who 'get together whenever it’s necessary'.  I kinda like it - it is, I imagine, great doper music … yeah, man.  But the mostly spoken voice is very soulfully and plausibly captured.  You can imagine the man himself, in the room with you.  I would just love to hear the original master tape transferred to DSD.

I Remember Miles” is a 1998 CD from Shirley Horn.  It’s a terrific recording, and won the Grammy for Best Jazz Vocal Performance.  But really, it is an all-round wonderful album.  And the standout track is an absolute classic 10-minute workout of Gershwin’s “My Man’s Gone Now” from Porgy and Bess.  It begins with Ron Carter’s stunning, ripely textured, ostinato-like bass riff which underpins the track.  It has always sounded to me like two basses - one electric and one acoustic - but with the latest DS 1.2.1 the electric bass tones now sound more and more like an expertly played and finely recorded acoustic bass, and in addition I’m beginning to think there’s just the one bass - perhaps even double-tracked.  I’d love to know what you think.  Aside from the tasty bass, the rest of the recording is revealed to have a smooth but slightly congested, slightly coloured sound, a bit like what I hear when I listen to SETs played through horn speakers (I know, I know, heresy.  Kill me now.).  The immediacy and sheer presence of a fine DSD recording is just not there.  Unfortunately, this has not been released on SACD either.  Perhaps a DSD remaster will finally put the bass conundrum to bed?

Which brings me to the nub of this review.  Finally, the DirectStream is delivering on its huge promise as a DSD reference.  With the 1.2.1 firmware, it is opening up a clear gap between its performance with DSD and PCM source material, along the exact same lines as my previous experience with the Light Harmonic Da Vinci Dual DAC.  The DSD playback just adds that extra edge of organic reality to the sound.  It just sounds that little bit more like the actual performer in the room with you.  Sure, CD sounds great on it - probably as good as I’ve ever heard it sound - but the DS 1.2.1 consistently shows CD at its limits.  Great sound requires more than CD can deliver across the board, and in my view the DS 1.2.1 - through its excellent performance - makes this about as clear as it’s ever going to be.

In Part II of my review I mentioned the CD of Acoustic Live by Nils Lofgren.  I recently came across a SACD of music from the TV series “The Sopranos”, and it contains “Black Books” from the Lofgren album.  The CD is a pretty special recording, but the DSD ripped from the SACD just blows it clean out of the water, if you can imagine such a thing.  The vocal has incredible in-the-room-in-front-of-you presence.  All of the acoustics, which were already pretty open, really open up.  The pair of tom-toms I mentioned take on individual tonality, texture, and weight.  And the guitar work, which I previously characterized as being 'aggressively picked' comes across with a much more natural and plausible sound.  You just cannot go back to the CD and hear it the same way.  DAMN!  Someone needs to release this whole album on SACD, and preferably as a DSD download.

Another great SACD is MFSL’s remastering of Stevie Ray Vaughan’s “Couldn’t Stand The Weather”, with its perennial audiophile favourite “Tin Pan Alley”.  Beginning with a solid kick drum thwack, it launches into a cool, laid-back, 12-bar blues.  Vaughan’s guitar has just the right combination of restraint and blistering finger work, and his vocal is very present and stable, just to the left of centre.  The rhythm section lays down a fine metronomic beat, playing the appropriate foundational role upon which SRV builds his performance.  By contrast, in their uncomplicated take on Hendrix’s “Voodoo Chile”, the drums are given full rein to pound out a tight and impactful rhythm, and SRV gives his guitar hero chops a good airing.  If you’re unfamiliar with SRV and want to know what the man was about, this would be the place to start.  It is a fantastic recording, and one that has been expertly transferred to SACD.

The Japanese Universal Music Group has remastered and released many classic albums in their SHM-SACD series, all of which are both hard to come by outside of Japan, and ruinously expensive.  Their work on Dire Straits’ “Brothers in Arms” is interesting.  To the best of my knowledge the original recording was on 20-bit 44.1kHz digital tape (but there are people around that know more than me about those things).  Anyway, the fact is that there is no obvious reason why a remastered SACD should sound significantly better than the original CD, unless, of course, the latter was not well mastered.  However, the conventional wisdom is that Mark Knopfler was particularly anal about the recording and mastering quality, and so maybe that argument doesn’t hold water.  Additionally, the Universal SHM-SACD can be compared with a contemporary remastering by MFSL, and both can be compared to the original CD.

Right away, both SACDs come across as superior to the CD in all the important ways.  The title track, Brothers in Arms, is one of my all-time go-to tracks.  On both remasterings, with the DS 1.2.1 the vocal has that signature SACD presence, and Knofler’s guitar work sounds more organic, more like a real instrument in the room with you - just like with the Nils Lofgren.  I puzzled over how and why two SACD remasters from impeccable digital sources could sound different.  But they do, and maybe someone could enlighten me about that.  The two remasters sound almost stereotypical (there’s gotta be a pun in there somewhere) of how we think of Japanese and American musical tastes.  The Japanese SHM-SACD is massively detailed, but with slightly flat tonal and spatial perspectives compared to the American MFSL.  The latter’s tonal bloom fills the acoustic space in a more immediately appealing manner, but at the apparent cost of some of that delicious detail.  If one is right, then the other must be wrong, so they say.  You pays your money, and you takes your choice.  But the bottom-line is that with a DAC of the resolving power of the DS 1.2.1 considerations such as these are going to weigh more heavily than might otherwise be the case.

So there you have it.  The 1.2.1 firmware update will transform your DirectStream from a great product into a game-changing product.  I concluded my last review by comparing the DirectStream, with its original firmware, to my all-time reference, the Light Harmonic Da Vinci Dual DAC.  I felt that, based on my aural memory, since I no longer have the Da Vinci to hand, that the DirectStream was not quite up to the latter’s lofty standards.  With the 1.2.1 firmware I am no longer so sure about that.  I would need to have both DACs side-by-side in order to be certain.  But this time around my aural memory tells me that the DirectStream in its 1.2.1 incarnation could very well give the Da Vinci a good run for its money.  And in some areas, such as its bass performance, I even wonder if the DirectStream might not come out on top.  Let's bear in mind the price difference - $6k vs $31k.  That’s an extraordinary achievement.

Tuesday, 11 November 2014

The Promised AirPlay Update

Now that Tim’s Vermeer is out of the way, here, finally, is my promised AirPlay update.  You will recall that, following my system-wide upgrade to Yosemite and iTunes 12.x, when I set about evaluating BitPerfect’s AirPlay behaviour under that configuration it started out looking very bleak.  Nothing seemed to want to work, and there seemed to be a number of different and quite independent failure modes.  At the same time I was running short of patience with my AppleTV for non-audio reasons, and eventually discovered that it was one of a number of early ATV3 units which was eligible for free replacement under an Apple program.  With the AppleTV removed from my network, AirPlay suddenly started working very well, very predictably, and very stably.  Now that I have my replacement ATV3 from Apple, the question is what would happen when I re-installed it?

The answer is good news.  It has had no adverse impact whatsoever on my AirPlay setup.  So I set about devising a torture test, one I have never tried before.  I have three Macs in my test network, all running Yosemite and iTunes 12 - the first is a 2013 Mac Mini, the second a 2014 RMBP, and the third a 2009 MBP.  I also have three AirPlay devices in my network - the first is my
Classé CP-800 (which has an ethernet-connected AirPlay interface built in) which is connected to my main reference system, the second is an Airport Express connected to a set of computer speakers, and the third is my new AppleTV3, connected to a TV set.

All three Macs are running BitPerfect 2.0.1 straight from the App Store, and all three are playing through AirPlay.  The Mac Mini is playing Sade’s “Diamond Life” to the CP-800, the MBP is playing Laura Mvula’s “Live with Metropole Orkest” to the AirPort Express, and the RMBP is playing AC/DC’s “Back in Black” to the AppleTV.  All three are playing music quite happily, simultaneously, and the music choices are ones which my brain can at least separate out from the cacophony.  There have been no dropouts or other problems as far as I can tell (it is not easy listening to three systems simultaneously!).  So what had the potential to be a metaphorical headache is now instead a physical one, but for the time being I am not too unhappy about it :)

Next, I decided to stress the system to breaking point.  Although BitPerfect “hogs” its audio output device, thereby preventing other Apps - including OS X itself - from accessing it, this is not so simple with AirPlay.  BitPerfect can only hog AirPlay’s standard audio interface, but OS X does not control AirPlay through the standard audio interface.  So, even while BitPerfect is hogging it, you can still access the AirPlay subsystem via OS X’s Audio Midi setup.  So what would happen if I messed with the AirPlay settings in Audio Midi Setup while BitPerfect was busy playing through it?  And suppose I did that simultaneously with all three systems, while each one was busy playing?  Ugh.

So, on my Mac Mini I changed the AirPlay device in Audio Midi Setup from the CP-800 to the AppleTV.  Nothing happened.  BitPerfect continued playing to the CP-800, and the RMBP continued playing to the AppleTV.  So then I changed the RMBP’s AirPlay device from AppleTV to Airport Express, and the MBP’s from AirPort Express to CP-800.  Now, each of my Macs has its AirPlay device set to a different one from the one which BitPerfect is playing through, but BitPerfect’s playback has continued unchanged.  It is as though BitPerfect’s “hog” on the AirPlay device seems to have a lot more teeth to it that was previously the case under Mavericks and Mountain Lion.  This is a good thing, although the net result would be seriously confusing to someone who came in off the street right now and set about inspecting my setup.

Finally, the playlist playing on each of the systems has moved on to the next album in the queue.  In each case I have selected a 24/176.4 album so that (i) BitPerfect is doing some extra work to downsample the incoming signal, and (ii) the WiFi network is now being more seriously challenged.  The Wi-Fi network now has to stream 24/176.4 music into two of the three computers (the audio files live on a NAS), and then stream a 16/44.1 AirPlay stream out of the computers and then into the AirPlay devices.  That’s two 24/176.4 streams and four 16/44.1 streams simultaneously.  The third computer, and the third AirPlay device, are both connected via ethernet.  Everything continues to play just fine.  Credit here, to be fair, must go to my trusty Cisco E4200 router.

And still my headache continues.  Eric Clapton’s “Slowhand”, Deep Purple’s “Machine Head”, and Arkady Volodos reciting Chopin, now permeate the soundscape.  Excuse me while I take a couple of Tylenol….