02-05-2021, 06:26 PM
(02-05-2021, 12:08 PM)Zigzag Wrote: 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 pulled out my shelved moode v6.7.1 uSD card to test Audirvana. The ver of upmpdcli used is 1.4.12 with linupnpp 0.19.1. Audirvana in Windows 10 streamed music from the decoded and buffered Qobuz 24-bit/192kHz FLAC music without problem. If I use moode v7.0.1, upmpdcli v1.5.1 and libupnpp 0.20.0, I will hear loud white noise randomly if 96k and above streamed music from Qobuz. Audirvana will create a temporary wav file for the decoded "FLAC encoded music" then send the location of its local file to UPNP renderer. The Android App BubbleUPNP will forward the URL to the UPNP renderer instead. Therefore, I will go back to moode v6.7.1.
