As I said above, it works with other upnp players that I tried. So the problem is specific to Audirvana.
It’s primary in the interest of Audirvana to fix it. Volumio is a very big distribution with many free and paid users. Fixing it, may not be a top priority for them.
Maybe thay test against JRiver but not Audirvana. The 2 are not the same. One is full blown UPnP server and the other is just using the renderer functionality.
If it worked and it stopped working with the new release, whose fault is that?
Sticking religiously to the specification is the only way forward. I wouldn’t want to maintain a codebase that chases the implementation quirks if the others.
@bitracer ,
Volumio works also very well with Foobar and Mconnect, both are upnp players.
It doesn’t matter who’s to blame, and it’s not the point.
If Audirvana misses subscriptions to Studio from Volumio users, it misses business opportunities. If users of Studio don’t renew their subscription, because it does not work with Volumio, Audirvana will lose customers.
1 Like
Volumio also risks loosing customers. New distro for RPi is just a flash away. Some already have multiple SD cards at ready.
There’s a very strong competition, indeed, between the developers of the Linux distributions. And this competition is very good for the users, because they improve non-stop their software.
But the size of the communities of Audirvana and Volumio users are not comparables. Volumio is huge with more than 200K users if I’m not mistaken. Much bigger than Roon. I don’t know how many subscriptions Studio has, but it must be a small fraction of that.
I just checked on their site, they claim to have more than 433K active users!
Can’t you downgrade your MicroRendu software to make it compatible with Studio?
No. I’ve always run the same version of the software, since I bought the Rendu two years ago. I just reinstalled it, in hopes of getting this dysfunctional, subscription-based beta software to work with it.
Prior to my reinstalling the software, Štüdîø would hang at the end of every track. Now, it won’t play anything, except MQA files, and only those with loud bursts of noise at the beginning of every track.
In short, I wouldn’t even know where to download an old version of the MicroRendu software, nor would I have much confidence it would work with the MicroRendu 1.5, nor ANY confidence it would work with Štüdîø.
Maybe something went wrong when you reinstalled the software.
Did you try with another player (not an Audirvana player) to see if it works?
I’ve reinstalled it at least five times, at this point. Audirvana Plus, version 3.2.20, plays everything, EXCEPT MQA files, perfectly fine. It has always worked about as reliably as any music player/ library management software can, and all WITH a column browser!
My solution there will likely be to just get Štüdîø off of my computer completely and potentially try JRiver, if I can’t get 3.2.20 to work reliably for MQA files. At this point, I’ll try the recent Štüdîø update, when I get home, and, if it doesn’t play music reliably, in my setup, and allow me to drag songs within my play queue, I’ll simply give up on it. Nothing that is meant to facilitate a recreational pursuit should be this miserable.
If you boycott MQA, like I do, you can keep using happily your A+ 3.2. 
1 Like
Ha. I’m definitely not a fanatic, but there are many new masterings that have been released in Japan, since about 2020, that are well worth the money, not because they are MQA CD’s necessarily, but because the mastering is simply astounding. The MQA signal is just a nice, little extra.
Yes, though, if wiping Štüdîø from my computer and trashing/ restoring preferences don’t work to get MQA files playing on 3.2.20 again, I may very well just amend the file extensions, so they play as standard redbook files.
The latest update will not give better results. The Audirvana team has not found the underlying cause and there will therefore not be a solution. Endless testing and repeating does not change the fact that there is a problem in your situation. That won’t go away on its own.
Listen through another player or 3.2 until the problem is found.
And I am always in favor of a boycott of MQA.
1 Like
@Jacob, there is a problem in my situation that is extremely similar to a large number of other users’ situations. Like me, they are all attempting to use Audirvana’s much-touted “effortless” UPnP/ DLNA implementation.
And it does works for other users. If I understand Antoine correctly, they don’t know why it doesn’t work. Until then, they can’t fix it.
It’s a small company. They have only a few employees. So you have to be patient, and try Studio again in a few months.
1 Like
I’ll only be doing that, if @Antoine is willing to either extend my trial or offer me a new one, once these issues have been worked out. So far, it’s crickets, on that front.
I would never in my life pay to go through what I have during this “trial”, so without one or the other of the above options, I’m afraid Štüdîø will be a non-starter for me, once my trial is over. Not much of a trial, since I wasn’t even able to evaluate the software and only encountered bug after bug after bug, in an experience further diminished by a less functional interface than a version of the software that was last updated nearly three years ago. It’s been pretty hilarious.
Damien and Antoine have some real gall to be asking for money for this software. Åüdīrvãñâ Štüdîø is not ready for prime time, and I waited a fair number of months for them to work out the bugs, before trying it out.
There is a bug in the forum. I keep seeing the same messages endlessly.
1 Like
Don’t bother responding to them, in that case.