Thx for your explanation. I will keep the network connections as you proposed.
I will check tomorrow and get back with the result.
Yes it affects UPnP and Chromecast endpoints audio, TV etc. it does not affect Apple code such as airplay as this is trusted. Only applies to 3rd party applications
This is a known issue in macOS 15 and still exists in 15.2, Audirvana is aware of it. Same issue impacts some users of Roon using RAAT protocol and some other UPnP media players.
We await a solution either from Apple or a workaround from Audirvana (if possible)
today with method of @Djm1960 not a single problem AudirvÄna studio playing flawless! for now solved! hopefully apple come with a proper solution or audirvana with a workaround soon.
1 Like
What happens if you just use the ārefreshā button? 
@Djm1960 , Is it possible that when a new version of AudirvÄna is installed, that the āreferencedā security settings/permissions need to be refreshed by removing the AudirvÄna application in the permissions window and then re-adding it so to link properly in subsequent restarts? ā¦ Also if there is another version of AudirvÄna, like āAudirvÄna 3ā showing there, perhaps it will make a difference if the unused version is removed from the this security window?
For me I always conduct a clean install when updating the OS. As such after a re-install of all my software the issue has always occured so it is irrespective of whether it is a new install on a clean OS or an update of the OS as occurs for other people. The presence of Audirvana 3 entry does not impact the issue with the permissions service going AWOL.
The most interesting thing I have found is I have 4 app entries in local network, studio, wifi explorer, capture one and cyberduck. When access is forbidden in Studio I do not need to toggle off and on the studio entry, I can toggle off and on any of the applications and studio regains access to local network endpoints. This to my mind is proof that the issue is in the macOS subsystem, nothing to do with Audirvana.
My point is more specific to AudirvÄna when operating on a current macOS version and the AudirvÄna application is updated or revised while being hosted by the macOS. 
ā¦ Why would a ārefreshā instigated from AudirvÄna, not reveal/report that the local network security status of AudirvÄna requires reinstatement? Does refreshing the network connections status not show the DAC subsequent of this action?.. or does it show the DAC when instigating the refresh?
I have not observed any issue with updating AS. If access is granted prior to the update then once an update is completed AS has access. For me it only occurs after a shut down of macOS and restarting my computer
Sorry missed your question. After toggling off and on the Audirvana entry the UpnP devices are not detected until the user either a) restarts Audirvana or b) the device selection network section is refreshed using the circular arrows. Both actions forces Audirvana to re-scan the local network for devices. As the macOS permission has restarted the devices are then reinstated in the network device section
I apologize for not being clearerā¦ I am asking, when this condition appears, if you first ārefreshā the network connections in AudirvÄna, before doing anything else, to see if the DAC is recognized on the network connection and playback is possible.
No when the condition appears after a reboot, if you refresh the network in Audirvana the devices will not be found as access is forbidden by macOS. Only after toggling any of the entries in settings/privacy&security/local network off and on and then refreshing the network devices in Audirvana will the devices reappear.
Does this condition persist after renewing the DHCP Lease?
Yes
I wonder if any action is/will be taken towards Apple by AudirvÄna since when someone is in trial period for sure hĆ© will not subscribe to AS. And the word of jnstable / not working software will spread quickly and cost AudirvÄna new clients/ bad reviews.
@Antoine ?
In this case it isnāt the Audirvana software, but a bug that is in MacOS and which doesnāt affect everyone. So what would you expect them to do?
Still it will cost AudirvÄna customers.
Maybe. But the question still is: What do you expect Audirvana to do?
As @jmtennapel already said: It does not affect everyone. How do you expect the Audirvana team to repair a network bug in MacOS?
Bring It under attention of Apple.
Apple imo has knowledge how to fix this
Here you are: Feedback - macOS - Apple
It is already a known problem on Apple forums (Macrumors). Apple is well aware of it. The question is: will they (Apple) repair it (they might not see it as a priority) and how long will it take them?
I also see more and more complaints on Apple forums how buggy/breaking recent MacOS updates are. If it should cost someone customers it should be Apple and not Audirvana. But there is not much the Audirvana team can do about it.