next time try disable streamer and re-enable. (unless that was part of the usual fixes). I find that this is almost as good as a factory but faster.
1 Like
With latest SW and playing Roon, connection to the streamer is sometimes lost.
Remedy is to activate the streamer again. I have no clue as to why it was deactivated.
Also, I wish that changing āinput deviceā (e.g. from Roon to Qobuz) is made easier.
I find that when there are network outages, this happens. One of my network devices locked up and this happened. seems that when it looses network connectivity for a while (not idea what while is) getting back needs a streamer reset. I think I even see green light but its not really on network, but an off and then on with the streamer seems to fix
1 Like
what do you mean by this??? coax vs streamer vs AES?
1 Like
I edited my response and added an example. 
Disable/re-enable streamer
Switch to another input then back
Power-cycle DAC
Disconnect/reconnect Wi-Fi (that didnāt work)
Factory reset (that worked)
wow thats strange. I do not use qobuz connect. did some testing with it, but do not need. So either it or the dac would not let go of it no matter what you did.
One other thing IF it happens again. In Qobuz connect change it to output to a different device inside it. see if that forces it to let go. Hopfully it wont happen again, but it does try that. if that does not work you know for sure its on the DAC side. the connection became sticky.
2 Likes
Hmmm, I didnāt try that, but I did close the Qobuz app on both iDevices before launching JPlay, though. My past experience has shown that, following a Qobuz session, if I exit the Qobuz app before launching JPlay all is well. If I donāt exit Qobuz (or change its output device, as you suggest, though I havenāt done that), JPlay can still see the 512 but canāt play music through the streamer. This was a different kettle of fish altogether, as the 512 apparently was no longer broadcasting its availability as a UPnP renderer.
ā Chris
BTW I was told the releasing of the Qobuz was fixed. Could be on the app side if they changed something PSA does not know about. I am pretty sure it sounds like the two are not communicating perfectly.
Oh, interesting. Iāve not experimented to see if that was the case since Iāve had no reason to think that it was, until what youāve just said. I can certainly imagine how that might be accomplished from a systems perspective. Perhaps itās an inherent functionality in the new MPD rendering software that replaced the old gmediarender stuff, which wouldnāt really be a surprise since that old software was such an abomination.
Iāll check it out shortly!
ā Chris
Yeah hit that bug early on and from what I tested it was fixed. But you are dealing with software on iOS thatās fairly new and itās going to get frequent updates. If they changed the flag on how it shuts down or anything and the PMG does not detect it remains held by it. Would like to see a way to release that hold in a menu in dac.
1 Like
I had no problems until last week when I turned off my system to do some recabling. I had a bit of a problem with the PMG DAC not finding Roon, but after several reboots of everything Roon came back. The real problem was that the static snaps also came back in the right speaker. This was fixed several updates ago. I emailed Delia but no reply as yet. VERY FRUSTRATING.
1 Like
I am following this thread for a while, and these streamer problems reminds me of the difficulties I always had to keep more than one endpoint protocol active at the same time on a Linux-based machine. Especially when trying to implement the flaky UPNP standard.
Since the streamer is based on a OrangePi compute module, the same problems may be occurring. The only work around I have found when using an intel nuc or a raspberry pi, was to stop one service before starting another, that is, to stop upnp before activating roon raat, or hqplayer naa, or squeeze light.
That is the same solution sonore always used on their modules, where using a web interface you activate a specific protocol for use, to avoid multiple protocols active at the same time.
In the past, Psaudio did not have this problem because the bridge was based on a conversdigital unit, that was specific built for these protocols, and not a general purpose compute module. I donāt know the hardware configuration of the airlens.
Hope this helps.
6 Likes
This makes sense! Thanks for sharing your knowledge of these types of systems.
1 Like
The AirLens uses a Converse Digital module, donāt know the specific model, but a more up to date version than the Bridge. Works good for me! Like some other folks Iām not rushing into the PMG DAC until the āexcitementā subsides ā¦
2 Likes
Indeed the PMG series was an all-in movement (EDITED) in a totally different direction of PSAudio product development.
Again, my experience with keeping all protocols alive at the same time was never successful. Especially upnp via rygel applet in Linux.
Maybe psaudio could consider reaching out to sonore or small green computer to use their OS (Sonicorbiter if I recall correctly) that already has a web interface builtin to allow the user to select the active protocol, or considering allowing a ssh tunnel into the streamer for the end user to activate or deactivate the desired protocol, via a simple systemctl command (I am assuming a standard Linux distro is being used in the OrangePi module).
Stepping away from dedicated hardware has its many challenges.
I wouldnāt call it that. Glitches aside, the reports are that SQ is on another level and as evidenced by comments here on this forum most folks have elected to deal with the technical shortcomings (which have been or are being addressed by PS Audio) specifically due to the amazing upgrade in sound quality. Iāve been a critic in many of my posts about the QC issues of the early PMG units as reported here, but I have also acknowledged the efforts of the company to fix those issues. So, instead of nose dive Iād say perhaps a turbulent takeoff, but they are reaching altitude with smoother air and the destination is sublime.
7 Likes
IMO, if you are a Roon user, it is Production Ready. No need to wait.
3 Likes
Being a non-English speaker, I believe I got lost in translation. My bad. My intention was to say an āall-in movementā, and not something that could indicate any movement to a worse position/product
Sorry about the misunderstanding
3 Likes
Oh, that makes sense. I lived in a foreign country for 10 years and made those kinds of errors in language all the time. There are so many nuances and idioms that native speakers can get confused too. All is well, seems like we are on the same page.
2 Likes