If they don’t give you another free trial next time, you don’t need to subscribe for a full year. You can subscribe for a month, and try it. It costs only a few backs. That’s what I did.
Before doing it, just ask the support or @Antoine if the MicroRendu bug was fixed.
Yeah, or @Antoine could just respond to the question.
What I find hard to understand is the fact that I have stable transmission between my UPnP streamer whilst using either JRiver or BubbleUPnP/Minimserver/Linn Kazoo, yet untold problems whilst using AS.
Wouldn’t this point to the fact that the UPnP implementation problem lies with AS?
1 Like
Hell, I’m using a three-year-old version of this thing, and it works better than anything this company has released since!
Still, it couldn’t possibly be an issue with the one software that won’t work with UPnP for innumerable users, right?!
Nothing surprising there.
A new application is not necessarily better than an old one. I never rush to upgrade my apps and the OS of my computers as soon as there is a new version.
There is an expression in French “essuyer les plâtres”. I leave that to other, impatient, users.
AS also works in a different way than these applications.
Still, it doesn’t make it easy to solve this for the Audirvana Team without having the cause clear. Apparently in the conditions they are testing in there is no problem.
Hi @Jacob
So AS DOESN’T use the standard UPnP protocol?
Or would it be the other 2 scenarios I’ve tried and that work that do it differently?
Audirvana is not a classical UPnP server like JRiver, Minim and others. It just uses UPnP protocol to play to UPnP compatible endpoints.
1 Like
With the newest version of AS, my first impression is that UPnP has improved considerably. No hang ups, sort of works quite well. What doesn’t hold up is AS remote. Still, the old problem here that the progress bar often gets stuck. When trying to proceed to the next track, sometimes AS gets entirely blocked.
All in all better, but still problems.
Roon is rock stable in this respect, but it uses its own protocol (RAAT). JRiver also works flawlessly with UPnP.
I see. Thanks @bitracer 
I suppose the elephant in the room then is the term ‘compatible’, in that there would appear to be fewer compatible devices when using AS as opposed to other UPnP solutions?
Same here.
The old remote of 3.5 worked better.
Well, that’s true, but it’s mostly due to incomplete or erroneous implementation of the specification. Most manufacturers test against traditional UPnP servers, hence the compatibility gap.
This will change with time, since we’re witnessing the rise of endpoints popularised by Roon RAAT, Chromecast, Airplay.
I wonder, would there be a reason why Audirvana doesn’t follow the same model as JRiver (as an example) by introducing it’s own ‘server’ within the software, feeding files TO the renderer, as opposed to the renderer PULLING the files from the software?
Honestly, I don’t know enough about UPnP so I’m sure there’s a very good reason. But to me there certainly appears to be an issue with regard to the way AS presents the files over the network.
I don’t think that it has to do with having a built-in server.
I have a few other upnp players that do not have a built-in server, and who stream very well to Linux distributions with which Studio fails to work.
The reason is complexity. UPnP is very broad standard, supporting many media types including audio video and photo. If you look at JRiver, most of improvements and fixes are related to video.
Audirvana on the other hand focuses solely on audio.
1 Like
@Cloclo, I waited well over six months, before even attempting to use AS, after being burned when I purchased version 3.5 and the disaster that turned out to be. Štüdîø is not exactly brand new to the market. I erroneously assumed that would be an adequate grace period, for @Damien to work out the kinks.
You’re using AS, are you not?
Frankly, it’s pretty hard to imagine that my use case or setup is that unique, among this community.
Also, it’s incredibly difficult to imagine that Audirvana couldn’t ask for a current version of the MicroRendu, since there’s obviously enough of a partnership/ relationship there for Audirvana to be mentioned by name within the SonicOrbiter software preferences. Perhaps they could have avoided issues with a setup like mine, if they’d simply written SonicOrbiter an email, requesting the latest version of their devices, on which to test their new software…?
Doesn’t seem like the most thoughtful, inclusive, forward-thinking, intelligent, or anticipatory beta testing, to me…
Hello @GaseousClay,
I’ve been patient with you so should be more patient with me but apparently your are not at all. There are thing that takes time and personally I’m really done with you.
You can share your opinion but the way you are doing it it’s not what I would say very “intelligent” to quote you. There are things we can’t control on our hand and I am here to do the best I can to fix them but saying this:
This is enough and for all of the work we done in the last year, I can’t let you saying this. Mark my words, I will close this thread If you keep spamming the same thing over and over again. It’s my first and only warning. I think in this thread you have said numerous time what your issue is so stop spam about it, you are going in circle over and over again.
Oh and by the way, If you really want this extra trial, you will have to wait a bit because I’m waiting for a response from SonciOrbiter about this to know if they can reproduce your issue on their side.
1 Like
You haven’t solved the issue, @Antoine, so why mark it as solved? Seems more than a little disingenuous to me.
Also, if my issue still isn’t solved, and I have less than a week of “trial” time left. What else can I do? I haven’t actually been able to trial the software, because bugs have prevented me from doing so.
It’s only for everyone, including you, to see the status of the post since there is now more than 200 response on it.