I am running DietPi on my Roon Core NUC it is DietPi 9.1 and it runs kernel 6.1.76-1
Not sure if that is useful information or not
Just moved over from running Rock and very pleased so far.
I am running DietPi on my Roon Core NUC it is DietPi 9.1 and it runs kernel 6.1.76-1
Not sure if that is useful information or not
Just moved over from running Rock and very pleased so far.
Iâm happy to report another success for Mac users! In latest HQPlayer Desktop, I managed to figure out how to make automatic rate switching work on macOS with suitable input device.
As result, I can report that automatic input rate switching seems to be working with RME Digiface USB on macOS! On Windows, this is still partially broken due to a bug/issue with ASIO driver. But with macOS DriverKit driver, it seems to be working on macOS!
Nice
For people that donât know, That is US $600 and for feeding TOSLink sources into HQPlayer (only on Mac)
Tried Dietpi 9.1 (having NAA 4.6.0) and managed to connect my CM4 Pi as NAA input via WIFI to HQPE OS server machine.
However I still have dropouts althought the CM4 only use less than 2% CPU. Not sure if it is because of the way DietPi manages the Pi CM4 2.4GHz WIFI interface or the limitation of DietPi managing the NAA communcation.
Will try to test further to see if there is anything could be improved.
Good starting point is wired Ethernet with 802.3x active. Once that works fine, then next step you could try WiFi. WiFi is always unpredictable depending a lot on RF environment.
Ethernet works without issue, Jussi.
Will try to troubleshoot the WIFI further.
Power limitation through USB port is not an issue cause it faced the same WIFI issue when power by my separate 5VDC external power supply.
Finally got DietPi NAA input works smoothly via WIFI by switching to 5GHz instead of 2.4GHz!
Thank you all for the great suggestions and inputs!
Look much cleaner on the desk now.
Great ! I had a hunch DietPi would work
Like you, I of course have ethernet cable working fine with RPi4 but like you, less cable is better, as long as it works well.
Since NAA input is mostly <PCM192kHz , should be less prone to dropouts over WiFi.
NAA output at high rates of course can be an issue - best to have ethernet cable to avoid dropout.
DietPi WiFi is so easy to setup.
Wish NAA OS could have this kind of terminal screen - a bit like Raspi-Configâs wifi setup @jussi_laako ?
@Chipvn when you change sample rates, it switches correctly ? And no glitch or white noise coming up? Donât do fast switching but say after 5 seconds changing a playlist of alternating sample rates ? All good ?
I only have Tidal in Windows 10 which could not run in exclusive mode at this moment therefore cannot test the sampling rate switching. Will test when Tidal App for Windows 10 works well in exclusive mode again.
I mainly use this NAA input for Spotify App so it works well with fixed rate as of now.
Can confirm DietPi Bookworm on RPi4 running NAA 4.6 - auto sample rate switching works well
On WiFi !
For those of us with NAAâs in different rooms, some rooms it is nice to have WiFi, for practical reasons.
Some rooms I prefer ethernet cable.
Itâs nice to have the options.
I also already can see that WiFi (with ethernet disabled in DietPi Config) consumes less power than ethernet.
Ideally Iâd prefer NAA OS but with a WiFi setup screen like DietPi and Raspi-Config terminal screen thingy
With DietPi NAA i can still change my NAA name using same process:
This is cheap and the USB-C power in , is also USB slave. Which I assume means peripheral mode.
And comes in fanless case and is well supported by DietPi.
I have a thread somewhere with USB-to-WiFi adapters that work âout of the boxâ with DietPi. So can use the USB-A port for that. I know MT7612U chipset USB to wifi adapters work with DietPi because I tested.
I might give it a try, it is so cheap.
Can you explain a bit more what you mean?
I donât know the UI technical term but the way you configure Raspi-Config or Dietpi-Config is like in the video below.
Itâs not a bloated web GUI like ropieee but some terminal prompt looking thing.
From here you can very easily setup WiFi.
You can do it with HDMI and USB keyboard directly connected or if user enables SSH (like can choose to do with NAA OS) can do it over SSH
if NAA OS could do this , no need to use anything else. At least for now DietPi is nice and very minimalist. No bloat
That is ncurses-based text mode âGUIâ.
Low resources for NAA OS?
Something can add to NAA OS ?
I canât see anything to add to it other than WiFi setup
Iâm not planning to support WiFi on NAA OS, or manual IP configuration or such. WiFi is not plug-and-play, while wired ethernet is.
All good , DietPi has been a long favourite of mine for certain rooms where I needed WiFi. DietPi is Much less bloated than RoPieee in my opinion.
And DietPi is very well supported for a whole bunch of hardware.
In some rooms itâs nice to have this flexibility.
Will test NanoPi R2S and confirm if UAC2 input works well.
@jussi_laako Iâve seen your many comments on volume attenuation (digital vs analog), including some recent posts on headfi.
As it relates to this thread, what about using digital volume control on sources coming into HQ Player? For example, is there a risk using the digital volume control on a Bluesound or Wiim which feeds HQ Player? I ask because Iâm looking to build a living room system and ideally I would have a physical remote to work the volume for entire family to use.
Option 1: Use digital volume control on Bluesound/Wiim using Bluesound/Wiim remote which feeds HQ Player (-3db) with no analog preamp needed
Option 2: Have Bluesound/Wiim at full volume, feed HQ Player (-3db) and add analogue preamp (obviously more expensive)
Digital volume in those devices is not necessarily very good. It is not known whether they dither the output properly etc.
It is better to use HQPlayerâs volume control instead. And you can do that from the HQPlayer front-end, including traditional remote controls.
Oh I didnât even realize itâs possible to use HQPlayerâs volume control with traditional, physical remote! Do you have any more information on how to accomplish this? Ideally could have a physical remote control with volume up/down button that uses HQPlayer Desktop volume control on MacOS.