my memory’s horrible, but I seem to recall testers commenting on the Stellar Phono stage during testing… even being asked to do so by PS Audio. But I could be wrong.
Sounded like they wanted to make sure they had no repeat of the MK2 process whereby non-Betas got onto the Beta thread and everything went public. Potentially not even using this forum tool this time around. Note: I do not know. I am off to yet another continent (not Europe or NorthAm this time) for a temp assignment and could not participate.
And now they are shipping to beta users. First step!
How long will the Beta be ?
My guess is because of all the snafus (muting, ticks/pops, noise, revving some units but not all, etc.) involved with the mk2 release and the headaches that it caused beta testers and which they freely commented about as they were encouraged to do, they want to avoid that situation again, but that’s only a guess - call it a clandestine beta : )
Curiosity makes me ask … is there significant software in the AirLens? The DS MkII has a lot of software, so an extensive beta was needed. The AirLens is much simpler and should require a quick beta, right? A while back it was mentioned, not sure if confirmed by PS Audio, that it uses a Converse module, similar to the old bridge. One would assume that is a known entity and shouldn’t need much, if any, testing, correct? There isn’t a PS Audio specific app either so no testing there. To me that really leaves Roon integration as the most important feature to beta. Am I missing anything here?
But it’s still a digital device that it’s taken them 4-5 years and counting to make, so I’m sure there’s nothing easy about it or it would have been done a long time ago, and when your testing program relies on your customers to actually do the work, well, that’s rife with pitfalls if it’s all out in the open
Well, I don’t agree with you. Most of the delay was due to features that were dropped, so we’ll just leave it that.
for those following, the Air Lens shows up as an available audio device in Roon. Funny but the mkii does not, only the mki (I assume since they’re not differentiated). I found it while re-configuring my signature rendu se for the new 2.9 software.
Aside, I found a crazy problem with 2.9 and DLNA, don’t use an apostrophe to name your device. The Rendu will not show up as a DLNA device…I tried a bunch of things before removing the apostrophe.
Hi, did 2.9 for the signature Rendu have any impact on SQ or functionality?
Thanks!
I think the second part of your sentence is certainly true, and it speaks very well for PS Audio, as they are very open to criticism and having problems be aired about their products. As for the first part, I think that’s a little harsh. I have been involved in several betas for PSA and also been part of the development and deployment of a decent number of products and rollouts in my professional life. It has been my experience that it is near-impossible to devise a testing regimen that stresses a system or product as much as or in the same way as will happen with end users in real life. Yes the Airlens is a fairly simple product and I have no clue why it has been delayed for so long or how long the beta is planned to run. But I would not advise them to skip this step.
None that I can tell.
Thank you for the response. I have ordered it so I was hoping it would yield something. My MK2 front ended with the SE at 2.8 sounds great already but always hoping to squeeze more out 
I use the mconnect control app on a Samsung G20 phone to stream Qobuz to a Bridge II card in a Directstream DAC MKI. The AirLens documentation says you connect to Qobuz through Roon. Does this mean I have to get Roon to stream Qubuz or can I continue to use mconnect? Also, if I am able to continue using mconnect, will I sacrifice anything with the quality of the sound?
I just looked at the technical information for AirLens and see what you are concerned about. I share the same concern, but I would hope using MConnect as you do and I used to do (upgraded to the DS Mk II) will still work with AirLens. As best I know the heart of the AirLens is a Converse Digital module, similar to the Bridge II. So MConnect is still a viable choice for controlling what is streamed to the AirLens. I should add that both Spotify and Tidal can be used direct, e.g., without Roon, MConnect, etc., since they have a “Connect” option. Qobuz for some idiotic reason thinks the “Connect” option is not needed. For what it’s worth, I found using MConnect for Qobuz clunky. I think we will hear a lot more of how AirLens works in the coming weeks. I can wait …
Just a guess, but the Airlens seems like an external Bridge II (III) manufactured by the same company. Probably has the same connectivity options.
I sure do admire PS Audio, its products and its people including this great and respectful community of users.
I think PSA should quickly abandon this Air Lens product so we forget it ever happened, sort of like Schiit and their Sol. I honestly believe that the Air Lens is nothing but a money pit of development, bug fixes and keeping up with all the advances in the streaming technology that PSA have no control over. Streamers are prevalent and there is no shortage of excellent products on the market and the market for streamers is not demanding something that much better.
I don’t want to see PSA suffer losses in time or money on a distraction like this because it will only slow development on devices that we all love and use and will continue to upgrade over the years as they make real strides. Streamers are just too resource intensive and dependent on third party technology.
I suggest wait and see. The product is inches from the finish line.
