I don’t think it makes any sonic difference. I’m using 7054 with my DAC200 and 7055-C with my HA200. For those USB3 isolators I would strongly recommend to use USB3 port and a proper USB3 cable (with the big blue B-side connector).
There’s now also the new USB2 7055-B isolator that is in same chassis as the USB3 models.
I have placed the 7054 sideways in the equipment rack, behind other devices, so it is not visible.
Thank you very much for the information…
Hi 
everyone!
On this matter we kindly request your “vote” to help resolve this issue by clicking this link and voting for the request:
https://community.roonlabs.com/t/hqplayer-mobile-path-text-display-fix/301562
We already fixed the non DSD signal path, just need the DSD signal path to show correctly!
Many thanks!
@jussi_laako Hello, I heard from IFI Audio they asked you the NAA 6.x version package to install on their Zen Stream platform.
I have the ZenStream2, do you think possible to upgrade to NAA 6 or at least 5, since the current installed version is a 4.x ?
Yes, sure, but it requires updating the OS as well. The original first gen Zen Stream I have is still on NAA 3.x.
@jussi_laako I wonder if latest NAA could support DAC-50, as It does DAC-60 now. Don’t have it yet though. Many thanks 
Well I was too curious and bought the 7055-C. They’re rarely available second hand.
But it didn’t work between my LHY RPI Pro (Rpi 4 based streamer) and DAC200. It worked normally between my Windows laptop and DAC200 though. So I contacted Intona and they told me that they can fix it so I sent it to Germany. I got it back today and now it works. The version number sticker at the bottom of the unit now says v2.0.6 (it was v2.0.3 before). Maybe they updated the firmware or something? Anyway, it works well now. I also ordered their USB 3.0 cable to test on the dirty side of the unit against my Intona USB 2.0 Premium cable. On the clean side I’ll keep the 2.0 Premium cable.
I think they’ve updated some of their FPGA code to fix the compatibility issue. Good to know it is now solved, so likely any new device purchased from them will be compatible!
It is one of their “legacy” cards with AK4490. If it works with the existing support, then it is good. But if it doesn’t, someone who has it would need to extract some information from it and then do some testing. So it could be supported, but it is not as straightforward as I don’t have it. I have only DAC-60.
Hi,
I’m currently evaluating switching from Ropieee to NAA OS as a NAA endpoint on a Raspberry Pi 4.
One cool feature of Ropieee is the ability to auto-suspend the USB DAC. This is very helpful as my Topping E30 II can then switch automatically to the Toslink connection when I turn on my TV.
Is it something that could be implemented in NAA OS ?
I don’t know about this “auto-suspend”, but you can just try if it behaves the way you like.
It doesn’t behave the way I want, thus my question. Please let me rephrase.
My DAC goes in a standby mode when there is no signal on a given input. When that’s the case and I start for example my TV, it senses a signal on the optical input and switches to it.
This isn’t possible on NAA OS because your system maintain a signal to the DAC even when nothing is playing.
Ropieee has implemented a feature where it cuts the signal to the DAC when nothing is playing for a given amount of time.
The problem I have with Ropieee is that the sound is worse than on NAA OS.
So I’m asking you if you could implement such a feature in NAA OS.
How about sending the data from TV through HQPlayer?
But generally this is not in scope of NAA OS or HQPlayer OS. Which are pretty much assumed to be part of the DAC and nothing ever bypassing it.
My TV is on the optical input. HQPlayer isn’t wanted here because I want minimal latency for gaming.
The Raspberry Pi is on the USB input. I use it strictly as a NAA endpoint when I want to do serious listening.
The two inputs are used for completely separate use cases that don’t interfere with each other.
I guess the easiest and least expensive solution is to get another E30 II. It costs about the same as 1 - 2 hours of my development time.
I am trying to deploy NAA 6.1.2 daemon and have been able to copy the file my home directory but because the NAA doesn’t have dpkg, apt or even sudo so I can’t deploy the new software as again my limited Linux knowledge is letting me down. So what’s the process for updating the NAA?
If you are using NAA OS, the process to update is to reflash new version of the OS image. It is intended to be like a firmware, a monolithic all-inclusive block.
OK. I was looking in the wrong place and picked up the deb file. I can see the image files for 6.1.2 so will re-flash. Thank you.
For example Raspberry Pi4 and also for example Intel Atom and Nxxx devices.
For example RPi4 can be both input and output at the same time. For example USB or S/PDIF input to HQPlayer and then output from HQPlayer to your DAC through USB.