I agree, that in the sense that while OpenHome is not supported by MC it will not function with an OpenHome only renderer.
You missed the point. OpenHome and by implication the Auralic are wrongly claiming to support UPNP:AVTransport (which is the part of UPNP that MC connects to). JRiver fulfills it’s side of the bargain. OpenHome does not.
Tried both methods, neither reveal the AURALiC
Device Spy, which is part of this suite of tools sees the AURALiC:
That is actually quite interesting.
Device Spy does a wildcard search “*” for all possible types of UPNP devices (the UPNP specs cover all kinds of home automation equipment like printers, routers, security cameras, lights, thermostat etc.) On the other hand the DMRA and MC do a specific search for just one specific class of UPNP device “MediaRenderer”.
So the Device Spy result shows that the Auralic is advertising itself as SOME kind of UPNP device, but it is not advertising itself (properly) as a MediaRenderer.
Furthermore, the fact that the Auralic uses the word MediaRenderer in some of its description texts, make me suspect that it is TRYING to advertise itself as a media renderer but failing (probably due to wrong syntax). So the general wildcard search succeeds, but the specific search for a media renderer fails.
This is clearly a problem with the Auralic / OpenHome device. And NOT MC.