Connect the DAC to the M1 Via Ethernet? Why?
I’m streaming from the M1 to a Naim SuperUniti over UPNP.
It’s not a ram issue, my other iMac has 32gb and I get the same issue sporadically.
Appreciate the help, I’ll keep tinkering as I love the audirvana interface too much to give it up.
Is the Naim Superuniti connected to your wireless system over wifi, or have you connected it to your wireless router with an ethernet cable. I occasionally had issues with wireless UPnP with some KEF speakers a while ago and solved it by connecting the speakers to the wireless router with an ethernet cable.
Testing UPnP using a direct ethernet connection will identify where your problem may exist in your network… If UPnP works with the Mac M1 connected with an Ethernet cable, then you can eliminate Audirvana Studio as the source of the drop-outs that are causing the loss of synchronization of the digital signal flow and the DAC…
If the drop-outs persist when connected directly with an ethernet cable and you have lowered your pre-load buffer allowcation to allow the system to run Audirvana efficiently, then you can have reasonable insights to draw a conclusion from…
The maximum RAM that you can allocate will depend on the bit-depth and sample-rate of the files you are playing… these factors determine how much pre-load buffer you will require for uninterrupted playback… The more playback buffer you allocate, this reduces the RAM available for the macOS system, no matter the CPU speed… From what I have seen in the M1 chip architecture, there is no dedicated RAM cache on the chip to handle the level of audio playback caching needed for playback pre-loading…
The minimum RAM needed to run general macOS 12 applications is approximately 4GB… the speed of the platform has nothing to do with it… However in a networked scenario, the M1 should be more than capable of managing these audio signals across the network… But the available RAM on the platform will restrict these capabilities, as the system demands memory in support of any given operational scenario.
I solved this similar issue by selecting " do not send raw PCM " …
I currently have the same setting but the issue continues. My observation is that there are quite few people who are having this problem and there doesn’t seem to be any proper solution offered for it so far. Sorry to say that as much as I really like Audirvana, It is quite annoying that no one from the support team seems to be properly addressing this issue and I have been quite disappointed by how they have handled this so far.
Yep still happening for me, despite one member stating that a brand new M1 iMac is not powerful enough to stream a single 16/44.1 song when my old iPhone and DAP manage fine. This is an issue with Audirvana and UPNP, @Damien any ideas on this?
Tried: 1) increasing/decreasing buffer 2) not sending raw PCM
I stated nothing of the kind…
My statements:
Secondly, you are misconstruing my statement regarding the ‘on chip’ RAM cache:
Have you tried this test of your network?
Don’t get upset. I was paraphrasing, you’re essentially saying that a 2022, $1795 iMac is not capable of streaming an audio file, which is nonsense regardless of the RAM requirements of Audirvana or OS.
UPNP works fine over wifi or wired with zero blasts of white noise using Roon, BubbleUPNP/mconnect, come to think of it neither does this happen when using minimserver on a NAS drive over UPNP.
Seems like I am not the only user who suffers from this so I think we can all agree the problem or bug lies with Audirvana.
No… You did not paraphrase anything from my statements… I am not saying anything of the kind, and you are posing a ‘straw man’…
You must also consider those users that are distributing audio via Audirvana, using Ethernet based UPnP on M1 Mac’s that are not having the same problem that you seem to be having, with no playback issues…
Lol don’t cry about it. To quote you directly:
“You are taxing the system capabilities”.
By streaming an audio file, you’re out of your mind!
I have always been wired via Ethernet on the iMac and the Naim Superuniti, never said otherwise.
…
This is what I stated that you are misconstruing and attaching a ‘straw man’ to:
Depending on your playback demands and audio file sample-rates and the number of clients on the network, you may be taxing the system RAM requirements to manage application and network demands… Of course, in a simple system with a direct Ethernet connection to the DAC and 16/44.14kHz playback this will never tax your system…
(Edit:)
I personally, have 11.4GB buffer and 11,710 MB pre-load memory (MacBook Pro 2016 2.7 GHz Quad-Core Intel Core i7 16 GB 2133 MHz LPDDR3, running Audirvana Studio, using USB 3.1 via the Thunderbolt 3 bus…)
(Edit:)
Getting back to your original post…
The reason you are getting “hash” at the start of playback sometimes, is because the DAC is losing synchronization with the signal delivered by the Host platform that is managing signal flow across the Ethernet bus…
Because you cannot consistently reproduce the issue, this points to something else affecting the signal synchronization… If Audirvana were the source of the loss of sync, you would be able to reproduce the loss of synchronization anomaly with repetitive consistency,
Good afternoon, I have my subscription to AS, since October. i play audirvana on a 2012 mac mini over network to a marantz pm7000n. I’ve been having noise problems for a month when trying to play a file, whether it’s from my library or Tidal. I have the same problem as my colleagues. I have bought a roon subscription, to be able to listen to music. and with them this does not happen. Let’s see if you can please review this. Thank you
I have that also sometimes but not always when starting first song of the day…
static noise, but not a burst that can blow speakers. Origin on Ventura beta, was there also on Monterey or Big Sur, Mac mini 2018.
I’ve been up sampling to DSD 64 for the past few days, haven’t noticed the issue since. No idea why this could could prevent the white noise or if this is somehow detrimental in some other way…
Update still havent had the issue since ive been upsampling…
Hi. I encountered this today. I was playing from Audirvana to one of my endpoints from Qobuz. The first track started ok then I got a very very loud blast of horrible noise. Unfortunately I was using headphones and I got such a terrible fright and it was physically painful. Now I can’t listen to anything without trepidation, I have been trying out Audirvana and all had been going well until this. I’m stopping now. I should not have to trouble shoot things like this to listen to my music, fearful of another blast in my ears. Happened twice now and had enough.
I wouldn’t bother posting here, there is no solution other than someone talking about a straw man and implicating that a 2022 mid range iMac is not powerful enough to stream an audio file.
I switched to Roon a month ago and have not looked back.
You can try enabling mute during sample rate changes.
The reality is that we all must trouble-shoot our own unique system configurations…
What you are experiencing is a ‘loss of synchronization’ of the data being transmitted from of the host computer and Audirvana to your DAC, somewhere along the transmission path… What is causing this loss of synchronization can be precipitated by multiple elements along the digital-audio signal path from the storage device, through the host computer hardware platform and software-player interfaces and out-through the transmission bus and interface controllers subsequently delivered by the electronic and electro-mechanical means of connection to your DAC …
The place to start is to get back to a basic connection to your DAC… If this does not exhibit the problem, you have to look beyond this and into your network distribution scheme… If the issue persists in the simple configuration, then other questions crop-up regarding computer platform configurations and Audirvana configurations and DAC firmware, that may be precipitating your loss of synchronization problem…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.