Jump to content
IGNORED

HQPlayer's Network Audio Adapter


Recommended Posts

3 hours ago, jdubs said:

Thanks Miska.  Curious what you would consider a better solution to both serve as an unraid server AND (simultaneously) something that can run HQPlayer?  That's what I want to do.

 

Install HQPlayer directly on it? Although that is likely not the best base platform to run media things in first place...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
  • 2 weeks later...
7 minutes ago, Sigi said:

I would like to ask if NAD will be able to connect to the Hapi, didn’t try jet. I know that Merging has developed a Linux based driver, but they seem to give it only to definite player developers due to the fact that specific properties had to be introduced in dependency of the player. So player developers like you are will need to contact Merging directly in order to get support. Are you planning to extend your Linux HQPlayer Version to be used with Ravenna ?

 

On Windows and macOS it should work through ASIO and CoreAudio respectively.

 

On Linux, you need the driver, but then it should work. I have the driver, but I cannot test it since I don't have any Ravenna hardware. Merging would need to test it and give me permission to distribute it. But this has been pending for about four months now...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
On 11/3/2018 at 2:54 PM, Sigi said:

I have tried now, unfortunately it doesn’t work under windows. When I start the bat file there is no response from the Asio driver.

Am I doing something wrong? I used the latest version of NAD

 

It doesn't do anything immediately, only once HQPlayer starts talking to it. Do you get anything listed at HQPlayer side?

 

networkaudiod passes null window handle to the ASIO driver, so there may be some drivers that actually care about it. But usually it shouldn't get used for anything else than ASIO Control Panel, which is not used by networkaudiod anyway.

 

Quote

I have the Hardware, could try to test the Linux driver! For that I will have to install HQPlayer for Linux. What do you think about it?

 

If you get the driver from Merging, you could try it out...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
40 minutes ago, Sigi said:

Hi Miska,

When I start the latest version of NAD I get:

api-ms-Win-core-libraryloader-I1-2-1.dll missing.

If I start version 3.5.0.0 I get:

[c:\NAD.exer] (1996) discovery from [ : :fff:169.254.93.126%12]:49185

 

It is strange, IP address of the Hapi is 169.254.1.165

cheers

Sigi

 

Maybe you are missing this one?

https://support.microsoft.com/en-gb/kb/2999226

Or the VS2017 runtime from here?

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

 

You would never see address of Hapi there. That is autoconfig address of the HQPlayer machine...

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
16 hours ago, Sigi said:

I managed to connect with 3.5.0.0 , but streaming is still making problem. 

Wanted to use the latest version of NAD, but still the problem with api-ms-Win-core- libraryloader-I1-2-1.dll missing. VS 2017 installed, same Problem. All updates of win 2012 R2, apart from security updates ( am mainly not in the internet ), same problem.

Do you have any idea what I could try?

 

Stock Win10 Pro? ;)

 

But overall, I'd recommend to forget about Windows and for example try my bootable image instead...

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
1 hour ago, semente said:

I installed your cuboxnaa-355-cubox-i.7z image but I can't get HQP desktop to connect with it.

I never could use your images with the Raspberry Pi either, always had to use a Linux image...

The BT router doesn't show that the cubox is connected.

Running arp -a on the terminal only shows the router, the NAS and two 224.0.0.XXX addresses...

Be gentle because I am an ignorant in these matters.

 

P.S. there's also a (198.168.1.255) at (incomplete) on en0 ifscope {ethernet}

 

DHCP is for some reason failing on the ethernet interface? Does running "ifconfig" show you a proper IP on the Ethernet interface?

 

Still IPv6 auto-config should come up with something functional (not very helpful though if you have HQPlayer on a Mac).

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
29 minutes ago, semente said:

Could be the British Telecom router, I don't know...

 

I presumend you wanted me to run ifconfig on the Terminal:

 

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 ::1 prefixlen 128
    inet 127.0.0.1 netmask 0xff000000
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
    nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
    ether a8:20:66:36:7d:ef
    inet6 fe80::aa20:66ff:fe36:7def%en0 prefixlen 64 scopeid 0x4
    inet 192.168.1.118 netmask 0xffffff00 broadcast 192.168.1.255
    nd6 options=1<PERFORMNUD>
    media: autoselect (1000baseT <full-duplex>)
    status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
    ether 5c:96:9d:70:95:5b
    nd6 options=1<PERFORMNUD>
    media: autoselect (<unknown type>)
    status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
    options=60<TSO4,TSO6>
    ether d2:00:1a:34:98:c0
    media: autoselect <full-duplex>
    status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
    lladdr a8:20:66:ff:fe:a3:49:8c
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
    ether 0e:96:9d:70:95:5b
    media: autoselect
    status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
    ether fe:9a:71:e9:12:af
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=63<RXCSUM,TXCSUM,TSO4,TSO6>
    ether aa:20:66:63:38:00
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en2 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 6 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: <unknown type>
    status: inactive

 

What hardware is this and what is it running?

 

en0 has IP 192.168.1.118 and also IPv6 address (and of course loopback adapter), but everything else is empty. I don't immediately see a problem here, although there's a bridge and the IP should be (maybe) on the bridge instead of en0.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
8 minutes ago, semente said:

HQ Player on MBP running 10.11

Router is a BT Home Hub 4 https://www.manualslib.com/manual/967428/Bt-Home-Hub-4.html

NAA on Cubox i4p with your image

 

Would it help if I connect everything to a switch, and this to a router?

 

OK, but I'd like to see that output from the CuBox-i4Pro side...

 

Using a separate switch may or may not help depending on what the BT router is doing, but usually the LAN side ports on such are attached to internal switch.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
5 minutes ago, semente said:

Don't worry, you've wasted too much time already.

I'll try to install Stretch tommorow... Is this version OK and will I be able to ssh the Cubox from the MBP?

 

https://www.armbian.com/cubox-i/

 

armbian is a different thing. I've been using official Debian.

 

I think I've been using this one:

http://ftp.nl.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
4 hours ago, jabbr said:

So ... Cubox hardware is ancient but if you aren’t using Wi-Fi then @Miska s images are awesome ... for WiFi I’d use Ambian (and do)

 

I think I have WiFi driver included, but not wpa_supplicant. I could maybe build some new NAA images... I ordered the new CuBox in something like March this year, still haven't seen it. And they don't respond to my bugging about it anymore either. I have some other similar new hardware, but it is still total PITA to deal with...

 

I didn't include WiFi things before because I considered the images configuration free which cannot be the case with WiFi...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
19 minutes ago, semente said:

I can change to static IPs on the laptop and NAS but I can't access the Cubox with ssh because I'm using Miska's image. I think I'll have to install Armbian but need to borrow a keyboard...

 

There are couple of ways to check things with my image:

 - You can use serial console on it, if you have a laptop (normal microUSB cable and 115200,8N1 no hardware flow control as serial parameters)

 - IIRC, HDMI out + USB keyboard also works.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
  • 4 weeks later...
25 minutes ago, semente said:

I think I must have fried my Cubox because the ethernet connection doesn't light up on the switch and the TV HDMI input gives a no signal indication.

It's back to the Raspberry for the time being...

 

How did that happen? Input is 5V DC, but other than that it shouldn't be too sensitive...

 

Have you tried with another PSU? There's usually some current peak at power up, so some PSUs could run into protection.

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment

The original wall-wart for CuBox-i4Pro is 5V 3A. So that is a good starting point. Usually the device takes most power when booting up. Sometimes if the PSU cannot give enough peak current, device goes into reboot loop.

 

I have so much 5V DC barrel power connector hardware that nowadays I just have 5V 6A power brick at hand all the time.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment

If you have HQPlayer on Windows or Linux, I recommend trying with the "Network Audio IPv6" backend, it usually works better.

 

You can login as "root" to the image and run "ifconfig" to see if it has got IP address from DHCP. For IPv6 that doesn't even matter since it automatically sets up local IP.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
9 hours ago, semente said:

Would it help if I were to use a router instead of a switch?

 

Usual topology would have a switch connected to a router. And router would have DHCP server providing IPv4 addresses. So like a normal home network where router is providing internet connectivity and DHCP service. NAA doesn't need internet connectivity as such, but the router usually provides the basic network infrastructure.

 

Routers also have a built-in switch, but not necessarily a great one. Using a separate switch keeps NAA traffic away from router since packets travel only between the switch ports.

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
4 minutes ago, semente said:

I've run ifconfig

 

IMG_20181213_210402494_HDR.thumb.jpg.932fc6f1fca0b2676b15bf6633df7941.jpg

 

Local autogenerated IPv6 address, but no IPv4 address... NAA is not reaching your DHCP server.

 

Do you have NAA connected to your ordinary home network, the same you use for internet access?

 

Quote

This network will only serve the NAS, laptop and NUC so I thought it would make sense to keep it as simple as possible and reduce the amount of SMPSs. I'll try adding the router this evening, and will take home a keyboard to log into the cubox.

 

No need to worry about SMPS or such on a network...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
  • 2 weeks later...
1 minute ago, Em2016 said:

Hi @Miska

 

Is your RPi NAA image only for RPi USB audio output?

 

I tried it with an Allo DiGiOne HAT but couldn't get it to work.

 

Happy Holidays to you!

 

Happy Holidays!

 

It works with USB audio devices (not very recommended due to hardware design) and with HifiBerry things DAC+ and Digi+ and other components compatible with these. To enable I2S devices like HifiBerry DAC+ you need the edit the bootloader configuration as documented by HifiBerry. This can be done for example using regular Windows computer.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
  • 2 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...