Sample rate conversion error Using the latest iOS software 18 on iPad/iPhone. Roon software is converting all high res audio above 44khz, MQA no longer works nor does DSD, everything in muse is disabled, I have ten Dac’s and all are doing the same thing down converting to 44khz. Using Qobuz without Roon everything is working fine.
I thought we would see the DAC in your signal path. Maybe not.
1 Like
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
6
I would have to agree with @Jim_F here, your signal path appears to show you using the iPad as the endpoint?
What DAC was being used in that screenshot?
Ifi Kensei
Dragonfly colbalt
Cambridge audio 200m
Doesn’t matter what dac I use same results
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
10
I’m afraid the signal path just shows your ipad as being the endpoint?
Is that not the case?
If the DAC is AFTER your ipad in the chain then I would think this is correct expected results.
Qobuz works fine, shows correct sample rate on Dac. iPad is capable of playing high res audio
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
14
Do you mean Qobuz app works fine but Qobuz inside of Roon does not?
If so then please check the max streaming rate of Qobuz inside of Roon in settings: service: Qobuz.
I can confirm, I have exactly the same odd behavior when using an external DAC connected to an iPad. Either Meridian USB DAC or Focal Bathys built in DAC.
Everything HiRes is downsampled to 44.1 and then sent to the DAC.
This behavior was introduced with iOS 18. With 17.6.1 everything was working as expected.
I’m experiencing a Sample Rate Conversion Error while using Roon ARC on my iPhone 15 with iOS 18. Despite trying multiple DACs, including the Mojo 2, iFi Hip DAC 3, and BTD600 aptX Adaptive dongle, the app continues to resample audio and fails to properly detect the connected DAC.
It seems that the Roon ARC application may need an update to ensure compatibility with iOS 18 and its audio management.
Could you please confirm if there are any updates in the pipeline or if there are additional troubleshooting steps I can take?