Signal Path Showing Incorrectly for USB-C Connected AirPods Max (ref#TIJ5GS)

[Ian_Blackburn]

What’s happening?

· Other

How can we help?

· None of the above

Other options

· I don't like how the product works

Describe the issue

Signal path is wrong for usb-c connected AirPods Max. AirPods Max now support lossless audio via USB-C connection however Roon shows this as a High Quality Bluetooth connection. If I turn off Bluetooth (which is inconvenient) then Roon shows a fully lossless path. I don't think AirPods Max can actually use Bluetooth when connected via USB-C so I think that Roon is reporting the Signal Path incorrectly

Describe your network setup

iPhone 16Pro. AirPods Max. Ios 18.4. Usb-C cable connection.

[Nepherte (Bart Verhoeven)]

The iPhone’s built in audio usb-c dac will resample everything to 48kHz.

You’ll need a dedicated usb-c dac / adapter in order to if you want anything other than 48kHz.

So with the info that was provided, I believe the signal path to be correct.

[Ian_Blackburn]

Yes that’s correct but not the point - I’m saying the signal path is displaying as Bluetooth which is clearly wrong

[Nepherte (Bart Verhoeven)]

Sorry, that part I missed.

Can you show a screenshot of settings > audio to see the various configured devices?

[Ian_Blackburn]

Here you go - let me know if you need anything else.

IOS is 18.4.1 and AirPods Max on 7E101 firmware

[daniel]

Hi @Ian_Blackburn,
Welcome to the Roon community. I’m sorry a problem is what brought you here for the first time. When @Nepherte asked for the audio settings they meant the page that shows all of the audio endpoints available to you. This is page that you enable audio zones one. Can you share a screenshot of that page?

[Ian_Blackburn]

OK - will those screenshots be publicly visible because it would contain some personal identifiable information.

[daniel]

If you need it to be private then you can send the screenshots to me as a direct message. That way only the support staff will see them.

[Ian_Blackburn]

Just sent

[benjamin]

Thanks @Ian_Blackburn - our team hasn’t been able to reproduce your issue yet, but we have a ticket in with development for further discussion.

We appreciate your patience in the meantime.