Welcome, Rob
It appears you have already cleared things up with respect to these fees/non-fees, but can you provide additional information as to how all of this works and fits together? Such as who controls what, where are fees generated, etc.
To be clear you are correct - but that only applies to ROON RAAT implementation.
RAAT is an endpoint in the Bridge, and we pay nothing to anyone for installing ROON, but that does not apply to MQA. ROON has their own deal with MQA which we are not privy to and I assume MQA processing is handled on the room server side, not the endpoint located in the Bridge.
Every Bridge II has both a ROON endpoint and an MQA decoder (the two are separate programs). We do not pay for the ROON endpoint but we do pay for the MQA decoder in each Bridge II. They are separate and not involved with each other.
When users stream an MQA encoded track from a service like Tidal it is decoded in the Bridge through the MQA decoder built inside.
When users use ROON as a server and the Bridge as the receiver, MQA decoding is handled by ROON, not us.
Paul, so…you have to pay Roon for their MQA implementation? Or - in your earlier statement:
“Paul McGowan said: Thanks. Makes perfect sense. Indeed, we too have to pay Roon every time a unit is sold. Just part of the fun of it all.”
…did you mean to write “MQA” instead of “Roon”?
Ahh, thanks Mark. I fixed it.
Sorry, Paul - fixed what?
He edited post 5449 (where that quote appears) to change Roon to MQA.
Thanks Steve - I was just trying to sort out the answer to Rob Darlings post/question from this thread yesterday.
Is “Post 5449” some sort of absolute address, or is it the 5,449th post in some other thread?
See, here
Thanks, Elk. Thought I remembered that one, just didn’t know where from. “5449” refers to the number of posts Paul had done here in the Forums, correct?
Yes, this is Paul’s current post count. The reference to this number confused me for a moment as well.
I’m glad Rob chimed in. I read Paul’s post, knew what he meant, and never noticed the typo. Others may well have been confused/mislead by the original post.
Brain fart on my part. It was post 130 in this thread (page 3). Just looked to darn fast.
A bit late, but just wanted to share that I am very very happy with the latest Bridge update! Especially the addition of Spotify is greatly appreciated by my dachten 
What a huge surprise… Thank you, PS Audio!
BigAlMc saidI might have a display issue after all.
Noticed this immediately after the Bridge II firmware update but it’s now happened three times.
The artwork doesn’t display. Though this has been an intermittent issue the whole time I’ve had the Directstream.
The difference now is that once it stops displaying it stays that way or seems to, on the tracks after. Previously it skipped the occasional track and then the artwork showed up on the next one.
The other issue is that the progress bar (not sure what you call it - but the timer bar under Input & Rate that shows the progress of the track) seems to stop working.
That’s three times now I’ve noticed this and after power cycling the DS off and on again it immediately resolves for a while. But then I notice it again.
Is anyone else seeing this?
Any thoughts on how I can try to resolve this or is it a bug?
Thanks,
Alan
BigAlMc saidPS that photo is of a track that’s playing mid way but the status bar shows 0:00 for the entire time the track is playing.
Fairly trivial and the music still sounds great but be good to know if this is a defect in the new BII code or something more local to my setup.
Hi All,
Is anyone else seeing this because mine has done it 5 times now. Cover Art and the Track Progress bar just stop working altogether. And as an experiment I left it playing overnight to see if it remedied itself. It did not. But power cycling the Directstream resolves it immediately. Until the next time that is.
Is this just me or any others having this issue?
Many Thanks,
Alan
I also am having problems with the DAC Display “locking up” on the progress bar and not loading album art as well. It seems to happen only after playing MQA files for a while and unfortunately seems very repeatable. Cylcing power is the only way to correct it and as long as only WAV files are being played, the issue does not return… It seems there is too much information passing through the SD card when playing MQA files because album art updates much slower when playing MQA files, so I think there is a correlation there… Hopefully a bug that PSA will uncover and correct soon. I also notice that your DAC display is “ghosting” below the progress and volume bars like mine as well. This is something that PSA knows is an issue and can be replaced under warranty.
I know this is a Roon thread; however, I assume my problems, using JRiver, and those reported here using Roon have a common cause in the DLNA implementation of Bridge II.
Haven’t noticed the progress bar lock up problem; however, I do have new problems with album art loading and skipping songs in a playlist when the resolution changes. For reference, album art has been rock solid on my system for a long time. I have had some problems with sudden track changes (skips the last second or two of the previous song).
The Bridge II update has changed things for the worse. I play songs from a long favorites list often. When a song list has a change in resolution, 16/44.1 to 24/96, album art will not load and the following song will play for a second or two then skip to the next song. This is repeatable. On my system album art eventually loads properly after a two songs with the same data rate.
I use JRiver 23.0.87 64 bit. I have not experimented with deselecting SetNext and some of the various tricks JRiver employs to solve faulty renderer problems. I hesitated to report on the issue since I haven’t experimented much. Also, JRiver just made several major changes to their DLNA code issued as version 23.0.91. I haven’t experimented with that version yet.
MarkG-Michigan saidI also notice that your DAC display is “ghosting” below the progress and volume bars like mine as well. This is something that PSA knows is an issue and can be replaced under warranty.
Haha - I assumed that was by design and didn’t occur to me it was defect. Thought that was the style!
Good to know it can be fixed. But initial thoughts are that it doesn’t matter much in the greater scheme of things.
Thanks tho Mark.
Cheers,
Alan
I just verified that the issue I described above remains even with the new JRiver 23.0.91 update. Selecting or deselecting IgnoreSetNext in JRiver has no effect. Skipping HD tracks in a playlist is a Bridge II upgrade software issue. This is a problem that was long ago slayed and has returned. Very disappointing to go backwards. I have the ability to go back to previous Bridge II software versions and will be doing so. This issue is much more important to me than any newly available features.
I see in other threads that some Bridge II issues have been acknowledged. Hope this one doesn’t get lost.
I installed RedCloud and the Bridge II update today. I have observed the same MQA anomaly where tracks that should be showing 24 bits are showing 192/16. Also that it flashes 24 for a split second occasionally. I have tried with and without the volume control disabled in Roon. Unlike what one member reported it made no difference.
I can add one additional data point which may help debugging. Playing the Stories album by Jan Gunnar Hoff (a 2L recording) via Tidal Roon says 44.1.24 2ch MQA 352.8 - my DSD says 176.4/18. I understanding unfolding to 352.8 is beyond the spec of the Bridge II however the 18 bits obviously is showing some data in the lower 8.
In my system album covers works. It flashes off between tracks and then comes back on. I believe it was working this way before the update as well.
Karl Salnoske saidcymbop said 4) If a janky free app like Mconnect can designate MQA albums with a little M on the cover art, why can't Roon pull this off? When I see three different versions of the same album, I have to play each file to see how it displays to find out which is which.Probably a comment that should be posted to the Roon forum, as there is nothing PSA can do about this. However, one approach I’ve used to work around the issue is that I browse the Masters list periodically in the Tidal app (which has no filtering or sorting capability once you get into the Masters - major Fail!) and I mark those albums I’m interested in as Favorites. Then from Roon, I can pull them up as Favorites and know without an icon that they are MQA versions.
Karl, thanks for your informative post. I was able to follow your technique up until the step of marking the selected MQA albums as favorites in TIDAL. I cannot find the right button to push to do this.I also may have trouble pulling them up as favorites in Roon. If you could enlighten me on these two steps I would be very grateful.
Simply click on the star icon, which is the icon for Favorites and the album will be added to the MyMusic in Tidal. Then in Roon menu, select Tidal and then select Favorites and all of your albums will be there.
However, I recently noticed that the Roon version of the Tidal interface is now showing the ability to view all the Masters just like you can in the Tidal native app, so you can probably skip my whole process going forward and just use Roon/Tidal/Masters.