Sony TA-AN-1000 Downsampling to 2.0 on macOS (ref#6UB5CU)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· I’m on macOS and I have a Sony TA-AN-1000 connected using exclusive mode. I use Roon with the TV off, if that matters (if on, the device is named differently, but both are configured the same). The system is a 5.2.2.

When I first set up the device in Roon I set it to 5.1., but now it is greyed out and I can only play 2.0 (downsampled from 5.1). After updating to macOS 27 I had to reconfigure the audio device in Roon and I was able to set it to 5.1. but now it is grey again.

I mostly listen to 2.0, but I want to have the choice of course.

From where is that limit coming from? I guess that shouldn’t happen, since the device and capabilities are known.

Thanks

Tell us about your home network

· Doesn‘t matter here.

If I play a FLAC with integrated DTS it works in 5.1 even though it shows 2.0 in Roon.

If I play 5.1 FLAC in Roon it switches to 2.0 even if I had 5.1 set and in Apple’s Audio-Midi-Setup it shows 5.1.2. as soon as RAAT takes over it set by RAATServer at only 2.0.

Even more concerning the Audio path still shows 6Ch, but only LPCM 2.0 is sent to the receiver.

The sample rate is correct though.

Hi @kitt,

Thanks for the extra detail, the note about DTS-in-FLAC working while 5.1 LPCM doesn’t turned out to be a useful clue.

Your logs give a clear answer, and nothing is wrong with your Roon settings.

What’s happening: the Sony appears on your Mac as an HDMI audio device, and macOS keeps changing what it says that device can do. Roon reads the channel count each time the device reappears, and over the past week it alternated between “8 channels” and “2 channels only”, about four readings in five came back as 2-channel. We can watch it happen in yesterday’s logs: at 13:22 the device reported 8 channels, you selected 5.1, and Roon genuinely opened the output at 96kHz/24-bit/6 channels. Ninety seconds later the device reported 2 channels again and the setting greyed out.

Why the audio path still showed 6Ch: macOS publishes two format lists for an HDMI output, a “virtual” one it will always accept, and a “physical” one describing what actually goes down the cable. On your Mac the virtual list claims 8 channels at all times, even while the physical link is stereo. When they disagree, macOS quietly folds 6 channels down to the 2-channel link, so Roon sees its stream accepted while your receiver only gets LPCM 2.0. We’re raising that mismatch internally.

Why your setting vanished: on 16 September the Mac changed the internal ID of that HDMI output. Roon treats a new ID as a new endpoint with default settings, which is why the 5.1 configuration didn’t carry over.

Worth knowing: with the TV off the output appears as SONY AVSYSTEM; with it on, as LG TV SSCR2. Those are two separate endpoints with independent settings, so the channel layout has to be set on each.

What to check: the root problem is HDMI-side, that output disconnects and reconnects 15–20 times a day in your logs, sometimes twice within ten seconds.

  1. With Roon idle, open Audio MIDI Setup and check the Sony’s format list. If it only offers 2ch there, the Mac isn’t seeing multichannel and Roon can only follow.
  2. Turn off Control for HDMI / Bravia Sync (CEC) on the TA-AN-1000 and let us know if the dropouts stop, CEC handshakes are the usual cause.
  3. Check the HDMI Signal Format setting (Enhanced vs Standard) on the input Roon uses.
  4. Failing that, try a different cable and input.

Once the output stops disappearing and reports 8 channels consistently, 5.1 should stay selectable, and the six channels will actually reach the receiver instead of being folded down on the way.

Let us know how the CEC test goes.

Hi benjamin,

I disabled CEC and set HDMI to standard (compatibility).

Still the same. What I found out is that it works if I don’t use the exclusive mode and the TV is on.

In all other cases, I can either only set 2.0 or Roon downsamples it to 2.0 or it says 5.1 but it isn’t.

I can always choose 8 channels in the Audio-Midi-Setup and the speakers work. If I set this manually, Roon sets this (normally) to 2.0. Can’t Roon just choose 8 channels when dealing with 5.1 or even always for that matter? If Roon chooses 2.0, it is clear to me it doesn’t work. If I could force Roon to always assume 5.1 capability it would likely fix the issue, right? My receiver always supports all formats and channels up to 7.1 or 5.1.2.

I just found out that when not using exclusive mode I can switch to 8 channels and if Roon is at 5.1 it works, if I set 2.0 (like Roon does always when in exclusive mode), then I only have 2.0 (while Roon still says 5.1). I can’t change it while Roon is using 2.0 exclusively, but I can still see the setting peaking at 8ch 24 Bit at 192 kHz in Audio-MIDI-Setup.

Since other software work properly I can see Roon having problems with the detection. This unfortunately makes Roon unreliable for me.

The internal speakers of the Mac are 2.0, maybe Roon is picking that up when it looses connection to the receiver? It may be that switching on the receiver leads to a short outage. I can see that Roon removes the target device for a few seconds.

The new setting on the 16th was likely because of the upgrade to macOS 27. So that is not a problem.

How would Dolby Atmos be handled? Is this a direct stream like with movies or DTS/TrueHd Atmos?

Thanks for your help.

Any update on this?

Hi @kitt,

Thanks for the added detail, especially the comparison between exclusive mode and non-exclusive mode, and the note about the receiver disappearing for a few seconds.

We have escalated your case to our development team for review, we’ll let you know once we hear back from them. Thank you in advance for your patience as the review is underway.

Hi @kitt,

Thanks for the added detail, especially the comparison between exclusive mode and non-exclusive mode, and the note about the receiver disappearing for a few seconds.

We are working on enabling some additional diagnostics in this area, but it will take a Roon release. Thank you for your patience as we work on adding more diagnostics here.