@Antoine, yes, I do have it enabled.
@Antoine, I tried updating the Rendu again, in the event that something went wrong last night. Once I restarted it, I once again got it to play one track, and then it froze at the beginning of the next track and wouldn’t play again.
If this can’t get resolved in the next day or so, this might be my exit. A music player that truly will not play music is a bridge too far for me.
Please let me know what else can be done here.
Thanks.
Are you still on a trial @GaseousClay?
If so, I would suggest to @Antoine that you be granted an extension to your trial period.
The Rendu is, after all, marketed as being ‘Audirvana Plus certified’ (although unfortuntaley NOT Audirvana Studio certified it would appear).
This may give any users hesitant in subscribing to Studio, as they see no apparent software fixes forthcoming, the comfort they may seek in taking the plunge if a solution can be found to the grief you’re currently going through.
Good idea, @Ironz. I am still in the trial period.
@Antoine, what do you say to the prospect of extending it?
At this point, I will likely have to switch back to 3.2.20, if I want to listen to music from my computer, since it is currently not possible, using Studio.
My microRendu will only stream from AS if I don’t have the Compatibility Mode box checked. Antoine, is it supposed to be checked or not, or does this vary between installations?
@Jud, I certainly didn’t have any luck with it checked, but the device didn’t even show up in Štüdîø, until I had checked that box. Once I reinstalled the software (MicroRendu version 2.8) I couldn’t play anything. I went from constant hangs, at the end of tracks, to maybe playing one track successfully, if I restarted DLNA on the MicroRendu, and/ or rebooted it, and then being unable to play anything after that. The player would just say it was initializing, loading, and then stop.
@Antoine, tonight, I had my nieces over, and they wanted to listen to something I had to stream on Tidal. Instead of playing, the player emitted a terrifyingly loud static sound. Everyone was horrified and had their ears hurt. I feared speaker damage. I had to stop the player. After that, I chose to just enjoy time with my family and use version 3.2.20. After resetting the MicroRendu again, I had no issues with the version of the software that was abandoned by @Damien in 2019. I’m not sure I’ll be going back to Štüdîø again, unless there is an update that is supposed to address all of these issues. This has been extremely unpleasant.
Currently, this just feels like I’m using beta software that should never have been released, or at least promoted for my use case. I can’t imagine for even a second that I would pay for the experience I’ve had for the past two weeks.
Please let me know if you have any further troubleshooting you would like to recommend. I remain happy to try it and report back.
If there is ever a version of this thing that works reliably with a DLNA renderer and allows the user to select and drag tracks, ideally with a column browser, with which to efficiently browse extensive, local music libraries, I’d love to try it.
Why you don’t try to start from scratch… nothing to lose 
big text, but fast to do…
**If you have Playlists that are important export them first to desktop and save them in a folder… when Audirvana is reset, you can re-import them back in one shot. Sadly to this day, the folders they were in if so, are not back, you have to do them again…
Now Studio has the backup and restore playlists option in preferences…
Apple hide the Home Folder in User Library at some time depending on OS System…
When you have clicked your Home Folder, and cannot see the Library Folder in there,
just do a ‘‘cmd J’’ to show the folder settings preferences and see at the bottom…
click Show Library Folder and then you’ll have access to the rest forever.
So, start by exporting your playlists if you have some, from Local tab in preferences.
Go in Audirvana preferences panel and remove your music folder(s) there
(all the folder(s) of music you have there) delete them with minus sign.
Close Audirvana.
Go to User… Home Folder… Library… Applications Support… Audirvana Folder…
Trash All the files in that folder (that is your database of music, back it up! or not)
AudirvanaDatabase.sqlite is for Studio, but remove the others, but don’t trash them like the AudirvanaPlus you might have there for 3.2 version (just put it back there when test is done). If you have old version of .sqlite there, Studio will want to convert them to a new one at first launch.
Go to User… Home Folder… Library… Preferences…
trash com.audirvana.Audirvana-Studio.plist in that folder
(those are Audirvana Studio software preferences, back them up or not).
Restart Mac.
Open Audirvana, (now you can decide if you follow what is under…)
Don’t do anything… cancel if ask for a music folder, then go in the preferences panel and check them all before adding music… For me, i decide to turn off both Musicbrainz preference and track ID… you decide. When trashing the preferences and starting new, the first preference of Musicbrainz is at ON by default… Just to be sure before adding music, close Studio and reopen it and go back to preferences if all is still off
Parano, yes
Now, add a Music folder, at first, it will sync in top middle of main window… then it will analyze all your files. Yes, even preferences off the Analyzing will be done… LET IT GO… you’ll see the progress bar going… Could be long the first time depending on how large your library is, and Mac is fast or not… go to sleep if it is too long
After, go to Local tab in preferences an restore your playlists if you exported some…
Then when finished, shut down Audirvana, yes close it before playing a song…
That way you will have your database from scratch saved without crashing.
Then copy the .sqlite file to somewhere else as a backup, then open Audirvana, and try to play a song. When all set, you can shut it down again… then you can copy the pref file for the software and back them up with the database .sqlite. If something going wrong… you just have to put the prefs in prefs folder and the database backup to replace to faulty one… it will reopen at the time of your last database backup… so do it regularly if you do often tags editing…
When you put a backup database .sqlite, you will lose all the play counts of music files that played
between the one you trash and the backup you put to replace… so i backup a lot the .sqlite file
2 Likes
Always great suggestions, @RunHomeSlow! Thank you.
I will give this a shot later today and let you know how it works out.
I tried everything you suggested, @RunHomeSlow.
Once again, I got a couple of tracks to play, after reloading everything and resetting DLNA, and then the player froze up again. I tried going back a track, and it again said it was initializing, then loading the first track, and then stopped. Currently, as before, that is all it will do: “Initializing…, Loading…”, stop. Over and over again.
@Antoine, once again, unless you or @Damien have other suggestions, this is my exit. If you’d like to offer me another free trial, once the many bugs are worked out of this product, I’ll be happy to give it another shot. Currently, as I have said many times in the past, Audirvana is not ready for prime time. Nothing that enables a recreational pursuit should engender this much headache or frustration.
1 Like
It appears that, in the process of chasing all of the issues, with Studio, I managed to somehow disable my MicroRendu, by messing around with its settings. Now, I can’t get it to play through 3.2.20, either.
I’m sure glad I took @Damien up on that “free” trial! It sure has been a trial. That’s about all I can say for it.
It seems that I’m able to play anything except MQA files, using the MicroRendu through 3.2.20, now. It worked previously.
Ok, @Antoine, because Audirvana 3.2.20 no longer works for me as it did, prior to this mess, I have gone back to the advice @RunHomeSlow gave, and have been trying to make it work with Štüdîø. I ensured that I was using the new .sqlite file I saved this morning. Rather surprisingly, the software indicated that it needed to complete syncing with my local drives, which it had previously indicated was complete.
Once it finished doing so, I reset and restarted DLNA and MPD, in the SonicOrbiter software and restarted Štüdîø. Hilariously, it seems Štüdîø will only play MQA files now, and 3.2.20 will only play non-MQA files, using the MicroRendu. This abject, crashing disaster has now carried over into the last version of Audirvana that actually did work for me, because I reinstalled the MicroRendu system software, apparently screwing everything up even more.
In summary, in Štüdîø, when I play an MQA album, it will play through without hanging, quitting, stopping, or freezing, albeit with strange bursts of noise at the beginning of every track. 3.2.20, on the other hand, will play everything except MQA files. When I try to play MQA in 3.2.20, the player does the whole “Initializing…, Loading…”, stop… song and dance. After that, it won’t play anything, until I reset and restart DLNA and MPD, on the MicroRendu. When I try to play non-MQA files, in Štüdîø, I get “Initializing…, Loading…”, stop…, all over again, and after that, the software won’t play anything until I reset and restart DLNA and MPD, on the MicroRendu.
Essentially, this whole debacle has now rendered both Štüdîø and 3.2.20 useless for me, in equal, opposite measure. Every time I think it couldn’t possibly get worse with this dumpster fire, it roars higher. Any help with troubleshooting would be greatly appreciated, especially since Audirvana’s unposted support office hours exclude weekends, and I will be traveling for work for the next week and a half, starting early next week.
I’ll also happily take suggestions for alternative, more competently designed music players that will actually work properly with a renderer.
I would advise to consider doing a clean install. The fact that only MQA works is an interesting indication. Have you installed some signal processing plug-in, something that could interfere with sound reproduction?
No, @bitracer, as I indicated to @Chris2, above, I tend to eschew filters, upsampling, etc. and am a bit of a purist. @RunHomeSlow gave advice to essentially perform a clean installation, which I did earlier.
As I previously indicated, I am now only able to continuously play MQA files in Stüdîø and everything else in version 3.2.20. I have been saving/ using .SQLite files for the appropriate version, when operating the two of them, so they are not occupying the Application Support folder at the same time. I’ve also tried trashing the preference files for both versions.
The 2 .sqlite can be in the same folder, they don’t have the same name. It was just for starting the new one in Studio, still that now it is done, they can be there at the same time…
You can also open to 2 applications at the same time, but only one can play 
1 Like
Still, something is up here that goes beyond Audirvana. The easiest way to fix it is to install fresh from scratch. Otherwise it’s blind guessing what might be wrong.
Way back when I was a second level computer support person (yeah, I was that guy), I had a couple of support calls that share some of the same elements / patterns as this issue. In most of those instances, there was a software driver installed by 3rd party or OEM legacy software (on Windows PCs) that ultimately was causing the issues, and updating (or uninstalling if not used) that legacy software resolved the issue. In most cases, anyway.
If a complete fresh install doesn’t work, I would suggest trying an install on another computer, if you have one. This would at least narrow down the issue to something installed on your main music computer, or perhaps intermittent hardware issues (another possible cause, especially RAM gone bad).
2 Likes
Thanks, @glen. I don’t disagree with you or @bitracer, but the two most important things to remember here, with regard to the current situation, are that, first of all, I was able to use version 3.2.20 without issue, prior to reinstalling the MicroRendu software, for all types of files, and it worked as intended. Second, I did essentially perform a reinstall, based on the advice @RunHomeSlow gave yesterday, and it changed nothing.
Finally, it is also worth remembering that, prior to reinstalling the MicroRendu software, the issue with Stüdîø was that it would hang up at the end of tracks and require user intervention, to tell it to play the next track. Further, prior to reinstalling the MicroRendu software, in hopes of fixing the hanging issue, with Stüdîø, version 3.2.20 worked fine and was free of issue. Since most of my music is not MQA format, I’ve chosen to use it, until something gets cleared up here.
I agree with both of you that there now seems to be something else entirely at work, with the MicroRendu and both versions of Audirvana, but the only reason I am now encountering this set of issues is that I reinstalled the software for the MicroRendu, in hopes of fixing the issues I was having with Stüdîø.
Thanks, @RunHomeSlow. I have been keeping them separate, because I wanted to eliminate any possibility that one could cause issues with the other.
@Antoine et al., if it makes any difference, both version 3.2.20 and Štüdîø are giving System Optimizer Error messages. The OSStatus error code is 22.
This never happened before yesterday. Once I tap OK, at least in version 3.2.20, the player starts working, as long as I’m attempting to play a non-MQA track. Of course, it’s exactly the opposite, in Stüdîø.