PS Audio AirLens

Get the AD. As I’ve gotten older I’ve come to the conclusion that even in this whack-a-nutty hobby we’re in, any unnecessary complexity (yes, that’s subjective, I know :wink:) just winds up taking precious minutes off your life. I went from a Classic III to an Avenger Plus, then replaced the belt drive with a BLDC rim drive (whereupon the boxes needed multiplied by two), then came to see - it’s taking up just too much of my audio life! In comes the AD and “boom!”, all that time wasted on adjusting, tweaking, experimenting with various bits and bobs, goo-gawing the motors and displays, all gone. Now I just drop the needle and listen, and guess what it sounds great!

Back to the AirLens discussion…

3 Likes

So, how can we feed it? Is there no app at all?

Exactly. If the AirLens doesn’t do Ethernet In → I2S out of at least DSD512, with the ability to support additional user interfaces beyond Roon, then at least for me it’s a tough sell.

1 Like

Thanks and, perhaps over time as we near launch, we’ll get more into the details and particulars.

The main benefits of the AirLens are two fold: its complete galvanic isolation as well as Digital Lens outputting jitter free data.

Think of it in the same way we first demonstrated with the PWT how perfecting the CD transport’s clock changed forever the way we think about what’s possible.

For those that do not remember, let me give a brief recap. Whenever a DAC decodes the incoming digital data into analog, the clock it uses as a reference comes from the source. In the case of a CD transport, it is the transport that supplies the master clock. Which is why up until the introduction of the PWT’s Digital Lens, all transports sounded so remarkably different. Their data was identical in all cases. What differed was the jitter and noise levels of their master clocks driving the DAC.

The PWT partially solved this problem by building in a large FIFO (First in first out) buffer using a precision low jitter fixed clock. Thus, whether the incoming data from the spinning CD came in fast or slow didn’t matter. It collected up in the FIFO and then output perfectly to control the DAC. The sonic impact was huge.

When we stream digital audio data the same is true with clocks, only, unlike a transport, there is no clock information contained in the streaming digital data. That clock is later supplied by the streamer. So, step one is to have a Digital Lens buffer built in to the streamer.

Check.

Next, noise and unwanted artifacts found on the incoming data connection (whether Ethernet, USB, or WiFi conversion) are the second biggest culprits to bad sound next to the master clock problem. Fiber optic cables solve this problem but, unfortunately, since consumer audio got the short shaft with TOSLINK’s inability to pass high sample rate data (and ATT optical connectors are no longer supplied on gear), we’re stuck with physical connections for incoming data.

Which means we’re injecting all that wonderful noise and crap from the outside world. What’s needed is what we refer to as galvanic isolation. No physical or electrical connection between the outside world and the incoming DAC. Galvanic isolation. Not even the grounds are connected and power supplies are separate. Galvanic isolation solves the second biggest problem in data delivery. That’s in the core of the AirLens.

Check.

So, now add them up. Incoming data is fully buffered and output separately via our own low jitter fixed clock Digital Lens. That data is sent over “the air” (hence the name Air Lens) to the DAC.

AirLens = perfect, jitter free data without any electrical connection to the outside world.

Which is why you’re in for a treat when you hear how many problems you have now will vanish with the Lens.

11 Likes

There is no app at all. You can feed it with Roon, using it as an end point. You can feed it anything using UPnP/DLNA. You can feed it with AirPlay.

5 Likes

Thanks for clarifying, Paul. Now about the I2S out and the DSD capability…… :thinking:

Having a BlueSound Node 2i, I think you have a valid point. It is a rather effortless streamer in search of a better sound. The Node 2i is great for causal listening and exploring new releases, but an improved sound would be most welcome. The Innuos Zenith Mk III with a Phoenix re-clocker gets at it in a more complex package being that it is a server/streamer. Innuos Tidal integration needs work, but I have no regrets concerning its sound.

It certainly has I2S out. While on the road I saw a cool little device that extracts the signal from HDMI out of something like an Oppo or other player and goes to I2S. https://m.aliexpress.com/item/32961686980.html but I bet it’s on Amazon.

2 Likes

I don’t get DSD512. It’s a higher data rate than DSD recording, there are very limited options for sending it from storage to a streamer, you can’t get DSD online and frankly only bats might be able to hear it. You must also like the ridiculously small amount of material available. Octave Records are only released in DSD64.

Excellent summary of the advantages of the Digitals Lens and proper implementation of Galvanic Isolation.

A Jitter Primer

1 Like

Steve, see Paul’s note in the Octave thread. As to DSD512, what you’re saying is true… for today. But when the Bridge II came out it was already behind what was available from online sources like Blue Coast and others. Two things - if products from China can do it, a company like PS Audio should be able to do better than them. Secondly, and more importantly, PSA should be at the lead or ahead of the curve, not behind it. If the music is going to be out there, PSA should give us the gear to hear it.

Deal me in. I need a streamer / Roon end point for a new small system that will be going together later this year.

1 Like

With respect to Paul, systems controlled by external clocks were around for more than a decade before the PWT. dCS designed a reclocker/transport system for Bob Ludwig to master the first SACDs over 20 years ago. Lots of people use fibre optic, I’ve used it for years, and lots of units have extensive galvanic isolation. Reclocking comes in all shapes and sizes, the first one I had was a Wyred Remedy about 7 years ago, my current system includes a very good reclocking bridge/streamer, a major hardware upgrade in 2017 from the processor first released in 2010, with no need for an external clock. There are reasonably priced products that allow you to set the clock according to the incoming data rate.

Streaming is very mature and I don’t see anything new. What is interesting is how these known technologies can be produced in a neat, effective and competitively priced package.

dCS have always lead on this, they developed most of this digital processing for SACD, DSD, upsampling, they were doing DXD in 2000. Their proprietary DAC goes back to the 1980s. These ultra-high data formats can cause more problems than they solve. Some of us don’t bother with DSD data files at all.

Obviously dCS products come at a price, but they are more affordable now and other companies are packaging these technologies at more affordable prices.

The DSD DAC is a good example, it’s got better over the years through software upgrades and has proven a good investment for many, but very few people actually invent anything new and those that do are normally doing it in the professional/commercial sector rather than consumer sector, with research budgets to match.

A Pi can sound as good as you want. People consider a pi “cheap” so building a $1000+ streamer around them is a hard sell but it’s perfectly doable (and there are a few out there). Use the Pi itself for compute and memory and then send the I2S to the output. This is no different than any other streamer or digital transport out there. It’s all I2S to the output stage. You can even power the output stage independent of the Pi board (Allo has a board setup this way). So, yes, there are shortcomings of the Pi itself but using it as the “brain” only is a nice design. The new Zen Stream from iFi is similar design. It doesn’t use a Pi but an off the shelf SBC wrapped around various bits of iFi tech. I expect more manufacturers take this path as industrial SBCs become cheaper over time.

There is not a ton of 4K video content yet either, but would you buy a tv today that didn’t support 4K?

This is a bit of an oversimplification of the Roon architecture.

Roon Core is the server and in the Roon architecture the Core handles most of the heavy work of library, DSP including sample rate conversion, file access (local or network), etc.

The “streamer” in Roon is an endpoint and endpoints are fed from Core only. For an internet stream it hits core is then sent to endpoint. This commonly includes a container conversion (but not payload conversion as Roon is bit-perfect). All Roon “app” (called Remote) interaction is between the app and the Core. The core then controls the endpoints.

This is correct. The endpoint software, called Roon Bridge, is part of Core. Hooking a DAC directly to Core allows access to local Bridge and the Core now runs double-duty as Core and Bridge (server and streamer). It’s not recommended to run this way for various reasons.

As it relates to Roon, it needs to run the Roon Bridge software or one of the the other protocols supported in Roon. But Roon Bridge is preferred as it’s bit-perfect and supplies additional feedback which can be seen in the Signal Path.

There are plenty of 4K transmissions and they come as part of my satellite service. I tried DSD in 2016, decided I didn’t want to use it, and bought a machine without it. Still have it 6 years later. The big difference is that if you want DSD, you have to pay extra per file. The other difference is that most people can tell the difference between HD and 4K, but very few between PCM and DSD. I can’t. Finally, a decent 4K TV can be found for $1,000.

What’s this, the Roon police? I have a lifetime sub and have been running it for 3 years off an Innuos and a QNAP and I think I know how it works. For two years I used it both as a server (I currently have 7 zones) and direct to a DAC by usb. It worked perfectly.

Where you have the Core, the database has to be on that machine or have direct access (eg SSD by usb). That’s what I mean by direct access. Some of my zones are Roon Ready and others are connected by Airplay. They are still endpoints, but work differently.

Putting aside all the Roon terminology, which confuses more than it explains, you basically need a fast processor for the Core with storage for the core database and that is always on. Hence the Roon Nucleus. Makes Roon a breeze. The places you send it may have Roon endpoint software onboard (Roon Ready) or be able to receive from Roon by Airplay or a wired connection to the Core.

Plus you login to qobuz or Tidal in the core and it sends streams wherever, which probably annoys qobuz as their license limits to playing on one device at a time.

There is a ton of 4K content. There just is not a lot bandwidth provided for high refresh rates when streaming. It is 8K content of which there is not a lot. Bought my first DSD128 files recently. The price was only a bit more than DSD64 and a good bit less than DSD256. So I could not compare with DSD64. But I brought in a teenager to confirm that I could tell the difference between the DSD128 and a FLAC 24-96 conversion, both playing over USB to the PSA DAC. So I am happy with DSD128.

1 Like