I'm guessing here but to me this sounds like Audirvana isn't compatible with the OpenHome protocol and instead depends on bog-standard UPnP A/V.... This probably wouldn't have surfaced as an issue in versions of Moode up until I think v7.0.1, as it featured earlier incarnations of upmpdcli which some how could combine the two protocols (OpenHome + UPnP A/V) into a single service. But this approach apparently had issues with BubbleUPNP for android, hence with new builds of upmpdcli there is now one service for OpenHome and another one UPnP A/V.
I don't know if this has already been attempted, or makes any difference. My suggestion is that upmpdcli's UPnP A/V service is activated and perhaps even its OpenHome service switched off - this can easily be done via the UPNP config page on Moode's ui. Oh and do make sure that Audirvana can pass through the firewall on Windows.
Upmpdcli continues to evolve, at some speed, and its developer provides really good support, so if there's no joy with this or anything else on this thread, I would urge you to report this issue to him - https://framagit.org/medoc92/upmpdcli/-/issues.
I don't know if this has already been attempted, or makes any difference. My suggestion is that upmpdcli's UPnP A/V service is activated and perhaps even its OpenHome service switched off - this can easily be done via the UPNP config page on Moode's ui. Oh and do make sure that Audirvana can pass through the firewall on Windows.
Upmpdcli continues to evolve, at some speed, and its developer provides really good support, so if there's no joy with this or anything else on this thread, I would urge you to report this issue to him - https://framagit.org/medoc92/upmpdcli/-/issues.
