CLLDR 0 Posted 4 hours ago Posted 4 hours ago (edited) I came across this thread while troubleshooting the same issue with my NVIDIA Shield Pro and LG OLED, and although I didn’t find a solution here, it helped me think through what might be happening. My setup: NVIDIA Shield Pro Onkyo AV receiver LG C2 OLED Shield connected to Onkyo, with Onkyo HDMI output connected to the TV. Playback of file with Dolby Vision and TrueHD 7.1 Atmos I have the Shield connected directly to the Onkyo receiver and the receiver connected to the TV (not using eARC). The issue was that the Dolby Vision notification would randomly keep appearing in the top-right corner of the TV during playback. The picture itself never flickered, dropped out or went black. The TV remained in Dolby Vision picture mode, and playback statistics showed no change. I tried various things, including changing the Shield’s Dolby Audio Processing and Low Latency Dolby Vision settings, clearing the cache and investigating the HDMI connection none of this provided a permanent solution. I may have finally found something that works. On the LG TV, I changed: Settings → Sound → Advanced Settings → Select HDMI Input Audio Format I selected the HDMI input connected to my Onkyo receiver and changed it from Bitstream to PCM. The result: Dolby Vision continues working. The Onkyo still reports Dolby TrueHD 7.1 Atmos. The Onkyo continues decoding and playing Atmos through my speakers. The repeated Dolby Vision notification stops appearing. I also tested switching the setting back to Bitstream, and the notification returned. Switching back to PCM stopped it again. My theory is that the Onkyo is passing audio signalling through its HDMI output to the TV, even though I have no need for the TV to receive a bitstream audio signal. Changing the LG’s HDMI input audio format to PCM appears to avoid whatever interaction is causing the repeated Dolby Vision notifications. I haven’t established the exact technical cause which may still be an LG specific issue, but the PCM/Bitstream comparison has been reproducible in my setup. Hopefully this helps someone else experiencing the same issue! I’d be interested to hear whether anyone using a similar setup can reproduce this fix. Edited 4 hours ago by CLLDR
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now