For random reasons, I had a Pi 5 in a Flirc case with Ropieee installed. I coupled it with a Topping HS02 USB isolator to drive a Holo May KTE in DSD256. Without having a fancy streamer to compare with at hand, this modest NAA endpoint sounds really good (meaning, it sounds as if is not there 
)
2 Likes
It har certainly been up before, but, is there a kind soul who can tell me if there is a real audible difference between NAA image and NAA image ramfs. Any drawbacks or limitations?
No audible difference. Main difference is that with the ramfs one you can always completely safely just pull the power plug and it is fine. In addition you can remove the boot media after booting up and it continues to work. Downside of ramfs image is much larger memory footprint because there’s a lot of redundant and never used data being held in RAM, and that you cannot store any setting changes that would survive reboots. Also the regular images contain more utilities for advanced use because many of those would be useless on ramfs. It is very unlikely though that the regular one would get broken if you just pull the plug with those, thanks to modern journaling filesystem.
1 Like
Hello,
Here is an error report.
I let RopieeeXL do its upgrade today and HQPlayer Embedded on Ubuntu will no longer play PCM 384kHz to it. After reading some similar issues from back in November, I then upgraded to the latest version of HQPlayer embedded for Ubuntu, but still receive the same error.
The version of NAA on RopieeeXL is 5.1.3.
The error in the log is:
NAA output requested format not available!
NAA output clNetEngine::PushPCM(): engine not ready
clHQPlayerEngine::Execute(): push to FIFO failed
This is when sending PCM at 384kHz. Sending DSD 256 on the same streamer to my other DAC works fine.
I have another streamer running NAA 5.0.2, and it still works fine sending both 384kHz PCM and DSD256 using the latest version of HQPlayer Embedded.
Maybe you have already fixed this issue with a later version of NAA. If so I will send a note to the Ropieee developer to hopefully have the version updated in the next release.
I’ve saved off the entire log if you need it.
Thanks
Sorry, but I think you’d need to ask RopieeeXL people. It is not not among my supported OS and thus the support is up to the entity providing the OS.
I’d like to make a USB stick with NAA 5.13. I can’t get the .img file to work with Balena Etcher. I’ve tried the 2 images (normal and RAMFS), reloaded the files several times but still the same thing.I’ve also tried several USB sticks.
I tried it with Rufus and it works!
1 Like
Yes, on Windows Rufus is a good option. Sometimes balenaEtcher fails in mysterious ways. Rufus is more reliable, but it is Windows-only.
On Linux and macOS of course “dd” always works, but it is a dangerous and command line only.