on 14-10-2021 18:27
Please can this be passed to engineering?
I have 360 box connected via hdmi to Sony 1080 av amp. The amp supports dolby atmos and is picking up dolby atmos support from the Netflix app on the stb. I know this as atmos appears on the av amp screen. The issue is thst when the programme starts or is paused, most occasions you get a large click through the speakers. A short sharp crackle. This is the kind of click that is familiar to when you used to power something on with speakers plugged in. It is very loud and will not be doing the speakers any good.
It only happens on atmos programmes. Can this please be investigated by engineering?
Thanks.
on 14-10-2021 19:24
on 17-10-2021 10:53
Hey @Gwizz27,
Welcome back to the community and thanks for getting in touch with us here on the forums.
I'm sorry to hear that you're having issues with your sound quality, are you able to check if this happens, when you use the TV's speakers?
Regards,
Steven_L
on 17-10-2021 18:12
Sorry for not making it clearer but models are as follows.
TV
Sony KD55XE9005
Av amp
Sony STR-DN1080
The 360 box is connected directly to the amp using hdmi. The amp is connected to the TV via hdmi to one of the 2 enhanced ports which can support hdr 4k 60hz. The issue only happens on dolby atmos. It is when the audio starts and stops and happens on Netflix and bt sport ultimate. They are the only times I have found anything thst uses dolby atmos.
No the issue doesn't occur when using the TV speakers.
on 19-10-2021 20:50
Thanks for getting back to us Gwizz27
I am guessing there is not an option to plug an optical cable between the 360 and your amp?
Regards
Lee
on 19-10-2021 21:17
Optical connection does not have the capacity to transmit atmos
on 20-10-2021 00:28
on 22-10-2021 07:27
Thanks for the replies.
It does indeed seem to be an issue Sony have acknowledged with their dn1080 amp.
I had no other source for Atmos to prove whether it was caused by amp or source and an initial Google search did not find the exact issue. Hopefully this will help others who may come in search of this issue. Looks like it will be patched in a future update to the amp firmware