Random Dolby Vision files only display black screen

Help and Support Vero V
2

Thanks for noticing Neal.

I also have recently observed an increasing number of 4K Dolby Vision (DV) titles exhibiting consistent playback issues. These complications appear to be independent of hardware age or manufacturer, as I have reproduced them on a fully updated Sony A95L and a Denon AVR.

To assist with the investigation, I have compiled a few more data points:

Timeline & Historical Context

  • Initial Discovery: This behavior was first identified in August 2025.
    Original Thread: Some DV files are Black in Vero V

  • Previous Critical Error: Historically, on my setup certain DV titles caused a full system reboot of my television within 10 seconds of playback. Following the November OSMC update, the rebooting issue was resolved; however, the black screen symptom persists.

  • Sample Data: A short video sample demonstrating the failure is available in provided thread, and I can provide it again upon request.

Observed Technical Behavior

When the issue occurs, the system exhibits the following symptoms:

  1. Video: The movie initializes with a black screen, though the file continues to play in the background.

  2. Audio: The AVR fails to handshake with the native high-bitrate format (e.g., Dolby Atmos) and reverts to a standard stereo output.

  3. Stability: The playback can be stopped without a TV reboot (thanks to the November update), and the UI remains responsive.

Workaround

Currently, there is a reliable method to bypass this issue:

  1. Exit the problematic title.

  2. Navigate to Settings > System > Player > Videos > Processing.

  3. Temporarily change the output setting from DV to Force HDR.

  4. Restart the movie.

Upon applying this change, the video renders correctly and the AVR successfully registers the original high-definition audio stream (Atmos, etc.). Just remember to revert this setting to “DV” after the session.

Impact

For me this has occurred across 9+ films and the series Fallout. And I’m watching a lot.

Therefore I assume the impact is currently very low.

Since we have a reliable workaround, there’s no urgent pressure, though a future fix would be appreciated. :wink: