In my case often “stop” doesn’t work and I have to pause instead. And yes, selecting another tack (especially with menu/play now) often helps more. Otherwise my slow response got a little better now.
New product release accompaniment aside of marketing has been better here in the past. The product matures at the customer as always (at least for non Roon use). Anyway sound wise I’m very happy,
I made more tests. DSD256, which is playable with unchecked Bitstreaming only, sounds worse than the same DSD128 track with it checked. So forget DSD256 on the Airlens at least with Jriver, makes no sense.
On Friday I will check Roon against Jriver once more. My assumption: I plays everything (as Jriver with unchecked Bitstreamng), but sounds worse again than each option on Jriver, but let’s see.
1 Like
I have more modest equipment. Like you I concluded that what sounds best is the way to go.
I acquired a Parasound Halo P6 which integrates the DAC with the Preamp for my bedroom system. It is capable of 4xDSD. I use Windows 11 mini towers with JRiver MC28. The plug & play WASAPI driver is limited to 2xDSD via DoP. I downloaded the ASIO driver from Parasound’s website and was able to play 4xDSD but this combo sounded lousy. Until Parasound releases an updated ASIO driver that works well with Win11, I’ll happily live with 2xDSD via DoP.
In my living room my Bryston BDA3 with Bryston’s ASIO driver works very well with 4xDSD. I worked with Bryston to have them update the driver to work with Win11.
Yes, I’m quite puzzled what difference SW (here Jriver is generally among the leading) and even certain settings can make. A can of worms.
But on very high end setups, some might not know what they loose when they didn’t experiment with all that. The best DAC doesn’t give back such loss.
I have not experienced this specifically.
However, like the mysterious loss of a handshake between networked kit, I have found software and firmware to benefit from a reboot.
If you have not already tried, I suggest you make sure all of your software updates “took”. Then I would reboot all of the devices, including your JRMC host device and the JRMC program itself.
IOW, close out the JRMC program and power down all related, networked kit in your signal chain. Then reboot everything starting with the router forward to the DAC and back to the computer.
This rain dance has proven to be effective for me under similar circumstances over the years.
FWIW/good luck.
1 Like
Thanks Scotte1,
I wound up rebooting everything including the rooter, and this seems to have cleared up the issue. JRiver is seeing the Airlens again. Recommend this to all if you have this problem.
2 Likes
I’ve asked this before in another thread and didn’t receive an answer. Does the mkii indicate if it’s getting DSD via DoPE. Regardless of the bitstream setting I use in JRiver, in my setup, the mkii shows DSD64 (don’t own any higher rate DSD files). In other words, I’m not sure if my mkii is seeing DSD direct or DoPE.
Sure wish we had access to a full mkii display map in the owners manual.
I don’t count on PSA to further care about Jriver or provide any information, so I tried a few things to fix my kind of network delayed touch/play response in playing tracks over JRemote/Jriver/Airlens (while this wasn’t a problem in Roon with Airlens or Jriver with Bridge II, so not really seems to be a network problem).
I think it got better after I set „ignore transport events“ in DLNA controller settings. Would be interesting if also helps others who might have this issue.
Thanks Jazznut - I would like to try this to see if it helps. Where is this setting configured?
Right click on Airlens in the play now screen, then DLNA controller options and there it is.
Thanks- giving this a try
Steve Arentzoff
I just finished experimenting with this on my setup, and it doesn’t seem to make any difference for me.
1 Like
I do not have Air Lens just the DS DAC with the original Bridge and JRiver Media Center since version 19 (currently on JRMC 31). I’ve found that selecting both Ignore Transport Event and Disable SetNext Support results in trouble-free behavior.
As I said this may not apply to the Ait Lens but it’s worth a shot.
1 Like
You are right…both of those old Bridge settings still seem to be necessary for the Airlens. In my case all performance issues seem to be gon until further notice.
Edit: at least much better most of the time, sometimes still a little slow.
Also before in some phases the reaction time was normal and the suddenly worse again, but without network problems, as Airlens/Roon was always fast as was Jriver/Bridge II.
2 Likes
The interaction between some of these programs (JRiver and Foobar2000 in my case) and the hardware can be really idiosyncratic at times. I’m not a particularly patient person and getting them to run reasonably well has surely proven that.
I’m not sure what possessed me to say “trouble-free.” Sorry about that misleading statement.
Meanwhile I recognized that the second setting disables gapless in several cases but prevents other bugs during play now actions, so I’ll see what to keep. Delays in click/play response from JRemote are just 50% of the time present and I didn’t find out the reason yet. Usually such problems were solved by firmware upgrades in case of Bridge II at the time…I honestly didn’t expect those things were fixed from start, tested with Jriver or recommended settings known this time. But I have a status I can live with…sound wise great.
Sometimes these things are just a plain mystery to me. Comcast sent me a new modem/router. It’s smaller and about 10% faster on downloads which is nice but now every time I try to access JRiver or Foobar2000 from my Oppo 105D I lose the connection before the music even starts. Nothing else has changed and I can still push the music files to the 105D but I can no longer pull them from the Oppo’s end. The DS DAC continues to work as it was since the files are being pushed to the Bridge.
Sigh.
The experiences with Bridge II, the never fixed bugs, the use of the converse module again and the friendly but missing PSA support on the long run due to their perceived non responsibility for the involved 3rd party products and modules nearly kept me from buying the Airlens…but I still did and even waited for 7 years. Happy with most of it but not everything yet.
Agreed on the airlens. Really happy with the sound improvement it delivered, but the Wi-Fi, tidal and jriver code is wonky. Hoping this gets resolved with code updates shortly
Steve Arentzoff
Are you sure?
I finally observed that both settings checked has still mostly slow reaction of playing tracks after touching a track but no hang ups, but unfortunately the enabled second setting causes non gapless play.
Disabling the second setting enables gapless but causes frequent delays or hang ups when touching a track on Jremote.
Roon always reacts fast (different protocol).
To me it seems the AirLens still has bugs in connection with uPnP/DLNA. Bridge II worked regarding instant reaction (better than AirLens), but until the end had partly gapless problems, too…
Unfortunately PSA didn’t seem to test thoroughly with Jriver and still seems to be very little interested to find out or fix things. I hope this changes soon and I assume it doesn’t just affect Jriver/Jremote but also other uPnP/DLNA based SW.