This one works on little chain now. Just got it new . Think it is not so much required there as that one is using Pi400. So, here I am feeding DacMagic 200 via USB or via Hifiberry Tos. This one a testshot for USB. No reclocking. Just Jitter lowering. Guess more interesting for pre 4 Pis? Just had to restart Pi 400 for HQP seeing NAA again. Thatsās all JitterBug FMJ Ā· AudioQuest // Alpha Audio - Review Audioquest Jitterbug FMJ
++Edit, yes, I think that was a next step for little chain +++ take a look at the links below before buyingā¦
Did move this topic to here about Apple Camera Connection Kit and Jitter in general as I guess in this thread a better fit for this. Maybe others can share experience on this too? Pls. take a look at the discussion link posted there about bit perfect tests and jitter.Still have to read it myself.
Camera Connection Kit itself doesnāt have anything audio-specific. It is just a dongle to make USB port from iPhone/iPad available through Lightning connector.
Bit-perfectness then depends on the application and iOS/iPadOS CoreAudio stack.
my concerns are more about jitterā¦ when you click, there is a link to a discussion about bit perfect tests and jitterā¦this is what i have to understand better, if relevantā¦
hm. Audioquest claims at Cobalt manual the following. So, if it is not Jitter related and bit perfectā¦Why there should be any diferenceā¦
ā Note: In our tests, Appleās Lightning-to-USB 3 Camera Adapter (with charging port) sounds better and is more reliable than Appleās less expensive Lightning-to-USB Adapter, while also providing the ability to charge during playback.ā
This,is confusing. I am learning to understand your argumentation. It is logic, what you are telling. Anyway, for upgrading my ābigā chain, I believe I will only invest in something, where someone capable has done measurememts. But first myself has to learn about how to read those measurements. Thank you again Jussi. It is super important to me, what you are saying!
I have both dongle variants, but from this point of view thereās no difference.
Since the USB in this case is not used to connect a DAC, just transport data between two devices, I donāt see how it could affect the sound. Thereās no audio clock being transmitted or such.
This goes to same category as worrying about jitter on internet when streaming Qobuz.
Logic what you are sayingā¦ However Audioquest not just a unknown companyā¦lolā¦therefore i decided, want to see measuremens before putting serious money into somethingā¦(not in regards to this 2 USD China Apple stuff of courseā¦)
Edit: ā Since the USB in this case is not used to connect a DAC, just transport data between two devices, ā + Yep
I donāt need to look at what Audioquest say because Iāve talked to some of the best D to A designers on the planet and they say what Jussi has just said.
Anyway weāre off topic here, Iāll stop at this
I didānt find anything with these words using Ctrl-F -technique (people probably use screenshots instead of text), so:
Iām trying to boot into NAA, but I constantly get stuck on this error on boot:
āA start job is running for Wait for udev to complete device initializationā
Another part of that error (it loops between the above error and this):
āA start job is running for Wait for Network to be configuredā
Every 20th boot or so goes through and I donāt change anything between the boots. Iāve created the usb stick using multiple different versions of NAA and I always get the same result: most of the boots are stuck in this loop but sometimes it goes through. Iāve also tried different usb sticks and two different computers (NUC and Lenovo X1 Carbon). Same thing. Iāve tried all imaginable BIOS configurations and settings in my Router (Asus ZenWifi), same thing. Iām using direct ethernet cable (yes, tried different cables). I have also tried completely disconnecting the power cable for like 60s to make sure that NUC doesnāt keep any kind of state between boots in ram or something (not sure it those traces would survive that though ).
Iām starting to think that there is something wrong in the NAA images. Iāve never had similar problems and Iāve fiddled with probably 30 different linux distros in the past. The only thing that I can come up with that is special to my setup that has stayed constant is the router and that Iām using intel CPU. However the boot shouldnāt be dependent on that.
There is something going on in the boot that to me looks like this: it creates several asynchronous tasks, but itās dependent on in which order they are executed. Most of the time they come out in wrong order and thus it fails. Sometimes however the critical tasks takes a bit longer and the things that itās dependent on manage to get themselves done in time. However debugging this goes beyond where Iām willing to go. Unfortunately in itās current form NAA is unusable as getting it up and running takes always like 15-20minutes of booting, waiting, trying and swearing. When I do get it working it seems to work great and be stable though.
If this is a known problem, I would be more than grateful if someone could point out what settings I have to have enabled somewhere to get things working.
I have it running for example on the UP Gateway and never had issues. And this is first report of such issue Iāve seen.
When such happen, first suspect is multiple ethernet interfaces on the machine. The rule set says that all ethernet interfaces must become configured through DHCP for the boot process to complete.
You can also try to use HQPlayer OS image for NAA. It has different network configuration and bridges all interfaces (creates a software switch) and is happy once DHCP succeeds on the bridge interface, meaning on any of the ethernet interfaces.
You can turn HQPlayer OS image into plain NAA, by disabling HQPlayer Embedded there and you can also change itās hostname to for example ānaaā.
Indeed at least NUC has only one ethernet port. I even physically detached the WiFi card exactly for this kind of reasons, to make sure that it didnāt intervene anything. With Lenovo naturally itās not that simpleā¦
And thanks for the tip on HQPlayer OS. Is there some guide on how to do the disabling and changing the hostname? I will do that next time I have problems. Right now I got it to boot after resetting the factory settings of NUC (not sure if these are related) so I dare not to touch anything
P.S. Itās probably not a bad idea to include similar kind of bridging also to NAA. It may well be that some customers (or worse, potential customers) have had similar problems and just dropped it without reaching to you.
Bridging has small CPU hit because of the software switch. And NAA OS wantās to be 100% optimized single purpose image. This is one reason thereās NAA functionality is also on HQPlayer OS instead, so you can get the NAA functionality working with bridging in case you have more CPU power.
Other alternatives is to install minimal Ubuntu Server, Fedora Minimal (from Server installer), or minimal Debian and then install networkaudiod package there.
Intel NUCs should certainly work fine. It is of course good to check that you have latest BIOS. But not sure what could be the issue here.
Thanks for the support! Iāll keep this for the future in case I have further problems. For now it seems that resetting to the factory settings of NUC seemed the solve the problem. It was a nasty problem as it sometimes worked and sometimes not, which directed me to think there is something problematic in the software (especially as I had the same problem with my laptop). What made it even harder to debug was that I needed to open UDP ports from my other computerās firewall where I had hqplayer running. Sometimes it hit the range I had open already and sometimes it couldnāt connect. This acted more as a unrelated distraction, but after some hard hours the mind starts to fly wildā¦
I just wanted to leave this for others that come after me. If you have problems with NUC, reset factory settings from BIOS! And those who canāt connect to NAA, disable your firewall from your computer where you have the HQPlayer and restart HQPlayer to see that this is not the problem (especially on linux where you generally donāt allow applications in firewall, but ports/port ranges for TCP/UDP).
. Think it is not so much required there as that one is using Pi400. So, here I am feeding DacMagic 200 via USB or via Hifiberry Tos. This one a testshot for USB. No reclocking. Just Jitter lowering. Guess more interesting for pre 4 Pis? Just had to restart Pi 400 for HQP seeing NAA again. Thatsās all 
+++ take a look at the links below before buyingā¦
)
