Posts by 2re

Quote from The Coolest

2re

That doesn't mean anything. What matters is the type of LCD (or OLED) panel used.

All TVs that support DV have 12 bit pathways. I think some high-end Sony TVs are even 14 bit in that respect. I have one that supports DV, but the panel is 8bit + dithering, which helps a bit with banding, but it's still a 8bit+ TV. As long as the panel itself is limited to 10 bits, all that is pretty negligible.

I'm not saying your wrong, but as long as the manufacture's don't advertise the actual bit size of the display, but only the supported bit size I'ts hard to tell, but I found some reports on several test done an newer high-brand TV's and It stated several of them actually were 10 and 12 bit displays. Unfortunately I can find the source But if I do, I'll post them

Quote from The Coolest

2re I'd like to see a source for that.

I normally keep tabs with new display tech, and I have heard nothing about 12 bit TV panels (be it 10+dithering or 12 bit native), especially from Samsung.

Well, as I said, normally it's not in the spec. But if you insist...

Norwegian usermanual:

NOR_KTMDVBEUL-3.0.7_180111.1.pdf

Quote from matt77303

brilliant, thanks bud. Much simpler than I thought.

Matt

... and simplicity turned to complexity

Quote from The Coolest

But do you see it switching from 8 bits in SDR to 10 bits in HDR?

HDR10 is just 10 bits, also all TVs are only 10 bits.

Only Dolby Vision currently is 12 bits, but since displays are physically still 10 bits, there's no real benefit to it.

Most of Samsungs newer displays are 12bit, but it's never specified in the spec.

Quote from Tim_Taylor

Bits are also reportet by AVR - but I never saw 12 bits

And what version of LE are you running?

One mustn't mix bits & HDR. I you set your GUI to 720p and disable rate change, than play a 4k HDR movie your TV will report 720p HDR. But this has nothing to to with the amount of bit used for colors.

Quote from Tim_Taylor

Yes - AVR reports YcbCr 444 or 422

TV reports SDR/HDR

And 8/10/12 bits also is also reported?

Quote from Tim_Taylor

Either I´m stupid or lucky.

Checked a few min ago.

Recorded TV 720p(SDR) - OK

Recorded TV 1080p(SDR) - OK

4k 10Bit HDR - OK

My combination box-AVR-TV is working well - TV switching from SDR to HDR and back to SDR, also 420/422/444 depending on video file

Maybe some combinations are not working (my TV is from 2017, my AVR from 2016)

Display More

Dose your AVR/TV actually say YcbCr 444:30bit (3*10bit) or is it just the HD/UHD(HDR) that changes?

Nope, no auto-switching on bits on my boxes. It sticks to what's in "/sys/class/amhdmitx/amhdmitx0/attr".

But it do switch from 444, 422 and 420 depending on values in disp_cap. So the trick questing here is, Can one also define Bits in disp_cap?

Anyone??

Quote from Tim_Taylor

I do nothing - colour space changes automatic to 444,10Bit playing video

Doesn't work on my boxes, I'do some tests;)

Quote from Tim_Taylor

I use automatic color space - Why should I change it manual

Can you explain what you mean by "automatic", and how you selected that?

For normal HD TV use 444,8bit. If you have a UHD TV, use 444,10bit

Quote from djnice

The h265 version is not from the original Spears & Munsil disc. The reencoding affects the chroma subsampling.

That may be so, but the h265 is my own reencoding from the original.

I have a h265 version off this file, and that one works ok, But the h264 is "bad".

"echo 1 > /sys/module/di/parameters/bypass_all" seems to fix the problem, but might cause new ones.

Quote from satello

i have same problem on some streaming, but i don't have the deinterlace option under display settings. weird. i

These setting are only for advance user, which I think, you are not!

Do you have any custom settings in autostart.sh?

If I select "Disable deinterlacing" in System->Display setting then I get the same problem, so if you have it selected, you should deselect it and reboot.

Just a new observation regarding AAC 2.0.

Starting playback of a video with AC3 2.0, makes AAC 2.0 work. If I play something with DTS , than it's broken. Starting a new playback with AC3 2.0, and it works again.