I can only imagine the total immersion, focus, and incredible hard work it takes to do what Ted does.
10 Likes
As some of you know I am a retired physicist ( Ph.D. ). I once had a doctor ( an MD ) tell me that anyone who gets a Ph.D. must be obsessive. I looked at at him in total disbelief. Yes, to get a Ph.D. in physics you must be very dedicate, focused and somewhat obsessive, however, the same thing is true of getting through medical school, years of internship and becoming a board certified MD. ( Talk about the pot calling the kettle black. ) Doing things like Ted does requires the same kind of dedication.
14 Likes
I was not aware Massive isn’t released yet…seems it’s just in beta…and still work to do.
It was mentioned but not very loudly. The update was (pre)released to try and solve a different problem but I have forgotten what that one was. 
To the folks having success with MControl finding the AirLens, were any of you using ethernet when it found the AirLens? I only had one day to hook mine up and test before going to my UP hideout. JRiver/JRemote found the AirLens quickly, but MControl could not find it. My only thought is I should try Wi-Fi when I get back home. I had a Bridge II for a long time and periodically had trouble with MControl, but it was solely connected via ethernet, so I thought not surprising I’m having trouble again, but need to confirm where the problem lies (moi? no, no, no).
Yes. My AL is connected to my network via Ethernet.
2 Likes
Yes, I use Ethernet exclusively. And, FWIW, I never had problems with mControl working with the Bridge II.
1 Like
I’ve no direct experience with the AL and MControl (I did use a Bridge II once upon a time) but, just a thought, when you say ‘solely connected’ do you mean with a fixed IP address? If so, maybe try DHCP?
1 Like
Hi, yes, the AirLens works well with mcontrol for me when the AirLens is connected via ethernet cable.
1 Like
I am running the Airlens via ethernet through a Netgear Powerline 1200 that indicates “Good signal < 80 Mbps” and controlling via iPad mini and McontrolHD. Qobuz and vTuner work fine.
1 Like
Thanks for the replies, looks like ethernet is not the issue, which is what I thought. I’ll be back home next week and will play with it some more to determine where the problem lies. Just to be clear, when I said “solely”, I meant no wi-fi, the Bridge never worked with wi-fi. I never tried a fixed IP address.
A new version of control was released for Android yesterday. It looks like bug fixes.
quick question for anyone who knows about this: I would have to use AirLens in wireless mode, but can’t use WPS because routers don’t support it. So can I configure AirLens with ethernet and then switch it to wireless and move it to where it will go in the audio rack? If not, is there any other workaround?
thanks!
BrosTrend AC1200 WiFi to Ethernet Adapter, 1200Mbps Dual Band Universal Wireless Bridge for Printer, Smart TV, Blu-Ray Player, PlayStation, Xbox, etc, WPS Easy Setup, Connect a Wired Device to Wi-Fi https://a.co/d/7QP33hC
Something like this should work
I’ve had the AirLens installed in my system for a few days now and just realized that I haven’t checked to see which version of the firmware I have installed. Do I need to know this? Does it update automatically?
I don’t think there has been a firmware update recently. In the manual, you will find the procedure to identify the firmware version installed. It’s a bit of a nuisance because it involves messing with the dip switches and counting flashing lights. An easier way is to use the mcontrol app which will tell you the firmware version under the device information screen. AFAIK, the firmware does not update automatically.
3 Likes
From this post over on the other thread where it probably should not be, sounds like you can avoid using the dip switches for firmware updates by connecting to the AirLens with the Mconnect app… even if you do not use it for playback. Do not know myself. But thought it funny. Kinda wondered if PS Audio even knew about this…
https://forum.psaudio.com/t/airlens-reviews/34864/129?u=carousel
2 Likes
Hi there Tony. I thought I’d see how the AirLens went with the mcontrol app as well as with Roon. I refreshed the mcontrol, which picked up the AirLens quite quickly.
When I went into the set up options for the AirLens I believe I was asked if I wanted to update the firmware. Sure…
I can’t see any detail of the different firmwares in play for the AirLens on PS Audio’s website, but know some people have had to update their system to whatever is current. I figured the mcontrol, being the native app for the Conversdigital 4140 card in the AirLens, was just doing its thing.
It appears to have gone into a device configuration mode and switched from firmware version psaudio_4s_mrstv_v4.3.59 to v4.3.67.
4 Likes
Your post inspired me to check out the AL interface via mconnect/mcontrol. I have it on my iPhone but I rarely use it.
I also had no problem syncing the AirLens with my subscriptions and JRiver Media Center.
FWIW, my AL firmware version noted in the “Device Information” on the mconnect/mcontrol app is 4.3.67.
Is there a consensus that 4.3.67 is the most recent firmware?
Cheers.
2 Likes
This is very useful to know, even if one doesn’t use Mcontrol as one’s regular app. I just looked in Mcontrol and found that under device information it identifies the current firmware, which is a lot easier than counting flashing lights. Then, as you say, under the setup section it would update the firmware (mine was already current).
4 Likes