Miska Posted August 31, 2020 Share Posted August 31, 2020 Does the networkaudiod output show display information about discovery messages from HQPlayer? If not, it is not receiving those messages. One possible reason is that HQPlayer computer has multiple active network interfaces and the discovery messages end up on wrong link. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted September 1, 2020 Share Posted September 1, 2020 Broadcast is privileged operation and also bad in general (and that's why IPv6 doesn't even support such). So NAA discovery uses multicast packets destined to local network (non-routable) scope. macOS doesn't like multicast bindings to fe80:: IPv6 automatic local addresses, this is why there is automatic IPv4 fallback. If you switch the IPv6 to use for example static IP's in fc00:: prefix it works. steven.y 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted September 5, 2020 Share Posted September 5, 2020 12 hours ago, steven.y said: I configured NAA machine's ipv6 network interface to "Unique local address", in my case, fd00:1::38f9:d349:f061 prefixlen 64. Unfortunately, it dose not work and end up "Can't assign requested address" error and "Socket failure, falling back to IPv4-only!". For me, fc00/64 prefix is working fine. But macOS is a bit painful and mysterious about IPv6. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now