I just installed version 2.246 successfully. I play via AirPlay from my PC. The audio is wonderfull, but it repeatedly stutters and stammers before interrupting a few seconds, then playing again before stuttering and interrupting again et cetera.
I suspect this could be a bug.
I am using a Meridian Explorer USB DAC and a Raspberry Pi 2. For playback I tried the DAC’s internal clock as well as the Pi’s clock. Wired does the same thing as wifi. I turned off BT in my home.
Welcome
I thought I saw it in the dropdown for the volume mixer, but I am now thinking I might have been hallucinating or something.
(Is Volumio supporting asynchroneous DACs?)
I see what you mean.
It’s a mixer naming used in XMOS which does not affect absolutely nothing. It’s not related to async transfer.
Async transfer is intrinsic of the USB receiver and there is no way to control it from software. So you just misunderstand it.
As you can see, it’s mentioned in the changelog:
Do not show XMOS Fake HW mixer
I’ve removed because it could have created confusion
When I visited the front end with my browser, it came up with a setup wizard, which I followed. My DAC was set appropriately (and showed “Meridian Explorer USB DAC” after the setup instead of just “USB DAC” like before). Then I connected via AirPlay and Volumio froze. So I restarted Volumio and connected via AirPlay and there was no sound. Then I selected another audio output, and then back to my USB DAC again. When connecting, Volumio froze again. Restarted, then there was music, but still pretty well ticking and stuttering unfortunately.
Maybe this makes any sense. Volumio is (I think) very complicated (as a former IT student and hobby programmer), so I have complete respect for your work. I am not in a hurry. I wish I could help, but I am getting old and tired and Linux is probably too complicated for me. (so I’m not bragging :mrgreen: )
I haven’t been able to use Volumio (and my set) for about three years now. I hope my issue gets addressed. Maybe I will sell my HiFi. (although that is the last option I think )
I believe, back in the time I bought the Explorer, they explained there are at least two methods of asynchronic transfer. The first is that the sender sends a send-request to the receiver, and the receiver accepts when it needs the next frame. The second is different: in this case the receiver requests a frame to the sender when it needs it. I believe the Explorer is the latter. Maybe you know what I mean.