Audirvana problem

@kacomess 

Keith- for what it is worth, I've found the user forum there to be faster than starting a "support ticket" (or whatever Audirvana calls it). You post in a new thread with a descriptive title and often, other experienced users will chime in quickly with fixes.

I searched the Audirvana Forum/Blog for the answer and, as I didn't see a similar problem there, I wrote to Support. This is the first issue I've had with their "legacy" software but, if I have another, I'll follow your advice and post a question on the Forum first. Anyway, I'm sure the company's support site is inundated with questions so I was happy to get a response...and it seems to have worked.

Thanks,

Keith

Same problem here.  I entered the text "defaults delete com.audirvana.Audirvana" into the Terminal app in MacOs Mojave, but nothing happened.

After I executed the terminal script Audirvana sent, the software ran for a time and then I started once again receiving the "file playback" error. I deleted the entire software package, reinstalled it, re-ran the script and...no luck.

I wrote to Audirvana a couple of weeks ago and after several days elapsed, I received a request from the company for the software log files and a IP address check which I provided. No reply so far.

I think Audirvana is tepid about continued support of the non-subscription version (i.e., the package you paid a "one time fee" to purchase) and is tacitly communicating that. I may try to build a Raspberry Pi with Moode or Volumio instead.

Anyway, I’m both stuck and disappointed...but, that’s the way it goes. If I get a helpful response, I’ll post it here.

Keith

Just today, after several weeks time lapse, I received this clarifying response from Audirvana:

Hello,

We are aware of an issue with Tidal in the Audirvāna 3.5 version and we are actively trying to find what is going on with Tidal directly. We are in contact of their project coordinator and they will come back to us as soon as possible on this subject as this issue seems to happen to some of our users but not all of our users.

This is why we suspected in the first place that it would may be an issue related to public IP that have been banned or something like this on Tidal side. For the moment this supposition has not been confirmed by them but we are waiting for Tidal to give you an explanation about what is going on.

We know this has been around for a long time but we are dedicated to tackle this with Tidal and we will reach you back as soon as they have something to share on the state of this issue.