Dolby Vision Profile 5 File plays in Green/Purple

Help and Support Vero V
1

Only happens with the new Season of Reacher (S04E01) but with all 3 Episodes on a Sony Bravia 9. Other Files from Netflix/Appletv etc working fine with Profile 5 i also downloaded it myself again and i still have the issue so its not the File itself. What makes it more strange the converted 8.1 Version works without any Problem in Dolby Vision.

Mediainfo of both Files:

https://paste.osmc.tv/reputiluja.coffee

Log:

https://paste.osmc.tv/dekamopaco

Sample File:

@Tee77 maybe you can test it if you have time? You also have a Sony TV :slight_smile:

2

This is a Sony issue since the latest Sony FW update, I have it as well. Stop playing the file, restart the TV and start the file again, then it will play fine. Sony is aware and they are fixing it now. Very very annoying bug.

3

The Problem is that this is the firmware from October 2025 i didnt update it yet because of the Dolby Vision problems with the new firmware. Also Reboot didnt help. Very Strange but i also have the white flashing bug (very annoying).

4

FWIW, your sample plays fine on Philips TV.

5

Yeah sadly still not working on my end :frowning: even cutting of the power for 15 minutes didn’t fix it :frowning: any ideas/solutions?

6

I’ll test this when I get time over next day or two.

7

It should play OK if you disable DV. Settings→Player→Video→HDR processing→HDR.

8

Tested on Sony A95L and also see purple/ green colours. Same on my Mac using VLC.

9

Then i lose Dolby Vision :smiley: @Tee77 VLC cant tonemap Dolby Vision so it makes sense but if its also on the Sony A95L something is wrong :confused: Maybe Vero V and the Sony TVs have handshake issues or something? I just find it strange that it only happens with Files from Amazon but not from others. Also if i convert it to 8.1 it works which makes zero sense.

Edit @Tee77 can you test the internal player? For some strange reason it plays the file without a problem.

10

It is a Sony FW problem, seemingly also existent in very old FW. It worked great on my Bravia 9 before the latest FW update.

11

Yeah but how can it be fixed? If I update to the latest firmware they are handshake issues all over the place :smiley: if I don’t I have green/purple picture even after power reset.

Just frustrating.

12

I think this is the same problem others have reported but with different symptoms. Please try the fix posted here.

13

I will try strange question but the ui interface with Profile 5 files is bright blue (the seeking bar) and with 8.1 files dark blue, why is that so?

14

As a fellow Sony A95L owner, I’ve also noticed that since the June firmware update, the TV no longer automatically switches to Dolby Vision. Sony is aware of the issue, but it looks like we will unfortunately have to wait for the next quarterly update for an official fix.

In the meantime, there is a quick and easy workaround for the latest firmware: when a Dolby Vision video starts playing, simply press the ‘HOME’ button and then the ‘TV’ button on your remote to force the television back to the HDMI port. It works perfectly every time and only takes a couple of seconds.

Ref. Post Vero V Dolby vision broken

15

Is the sample file working on your A95?

16

I tested the sample video you provided on my Sony A95L with the latest firmware (v114.602.080.1).

Although it was recognized as Dolby Vision, it played with distorted purple and green colors, which I haven’t encountered before.

17

Yeah so its not the Firmware its something else. I first thought its the File but it happens to all 3 episodes so yeah

18

Did some research its the DV Profile

Amazon is using Dolby Vision, Version 1.0, Profile 5, dvhe.05.01, BL+RPU, no metadata compression

which is incorrect.

Correct is: Dolby Vision, Version 1.0, Profile 5, dvhe.05.06, BL+RPU, no metadata compression

But Sony seems like the only TV Brand which can’t play it every other brand has no issues with it.

19

Brand new LG G5 has the same issue, so I took my Ugoos AMB6+ and to my surprise the issue is gone. So it’s definitely a Vero V issue.

20

Yeah and solved with this patch which will be in the stable build soon: