2014-05-06, 15:24
2014-05-06, 15:24
Onkyos have a "Postprocessing Setting" which needs to be turned off.
Here is a testimage:
or
Is black black? Do you see all rows in the last one? (It's okay, when you don't see the top most three squares), but if a full line is missing - something is wrong.
Here is a testimage:
or
Is black black? Do you see all rows in the last one? (It's okay, when you don't see the top most three squares), but if a full line is missing - something is wrong.
2014-05-06, 19:23
@fritsch
Question regarding the second blacklevel test image:
Although all my movie files seem now correct black level wise, i noticed that the above test image (i used the second one) looks correct while looking at the thumbnail in the file overview. (almost all squares are visible separately)
As soon as i launch the image to fullscreen, the image looks too dark. Is it possible that pictures are somehow rendered/processed differently hard-/software-wise than movies, so the image isn't correctly displayed while in fullscreen mode?
Question regarding the second blacklevel test image:
Although all my movie files seem now correct black level wise, i noticed that the above test image (i used the second one) looks correct while looking at the thumbnail in the file overview. (almost all squares are visible separately)
As soon as i launch the image to fullscreen, the image looks too dark. Is it possible that pictures are somehow rendered/processed differently hard-/software-wise than movies, so the image isn't correctly displayed while in fullscreen mode?
2014-05-06, 19:29
What does mean "too dark"? Make a photo of your TV, please :-)
Also verify that black is black.
Also verify that black is black.
2014-05-06, 19:49
I tried - not that easy to take good meaningful pictures:
Black seems black. It's just badly crushed so many squares are missing in fullscreen.
Black seems black. It's just badly crushed so many squares are missing in fullscreen.
2014-05-06, 19:50
Enable the Option "Use Limited Range" - what happens now? Is black still black?
Provide: DISPLAY=:0 xrandr --verbose | pastebinit
Provide: DISPLAY=:0 xrandr --verbose | pastebinit
2014-05-06, 20:00
Man - provide debuglogs, nobody knows what you are running, what OS nothing ... that is annyoing.
2014-05-06, 20:07
I test with a "limited rgb range only" lcd-tv
autostart.sh
combined with
activated in settings.
Video-files look perfect black-level wise.
BTW: I have a slight memory that i already noticed some time ago that image files seemed to be processed differently than video files. Didn't gave too much thought in it since it was a old nightly and i didn't use pictures at that time.
DISPLAY=:0 xrandr --verbose (4.0 nightly r18348 from 2014.05.05, i can upgrade to 4.0 stable but i doubt that this changes something in this case)
autostart.sh
Code:
xrandr --output HDMI1 --set "Broadcast RGB" "Full"
Code:
Use limited color range (16-235)
Video-files look perfect black-level wise.
BTW: I have a slight memory that i already noticed some time ago that image files seemed to be processed differently than video files. Didn't gave too much thought in it since it was a old nightly and i didn't use pictures at that time.
DISPLAY=:0 xrandr --verbose (4.0 nightly r18348 from 2014.05.05, i can upgrade to 4.0 stable but i doubt that this changes something in this case)
Code:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 connected 1920x1080+0+0 (0x48) normal (normal left inverted right x axis y axis) 708mm x 398mm
Identifier: 0x43
Timestamp: -763203693
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC: 0
CRTCs: 0 1 2
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff005262050100000000
0011010380693b780a0dc9a057479827
12484c20000001010101010101010101
010101010101023a80d072382d40102c
4580c48e2100001e8c0ad09020403120
0c405500c48e21000018000000fc0054
4f53484942412d54560a2020000000fd
00173d0f440f000a202020202020013b
02033571529f14131216111510050403
070206012021222c097f070d17071507
503d06c0831f00006c030c001100a82d
c029293333011d80d0721c1620102c25
80c48e2100009e011d00bc52d01e20b8
285540c48e2100001e023a801871382d
40582c4500c48e2100001e011d801871
1c1620582c2500c48e2100009e0000b5
Broadcast RGB: Full
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
1920x1080 (0x48) 148.500MHz +HSync +VSync *current +preferred
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz
1920x1080 (0xa7) 148.500MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz
1920x1080 (0xa8) 148.352MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz
v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz
1920x1080i (0xa9) 74.250MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.75KHz
v: height 1080 start 1084 end 1094 total 1125 clock 60.00Hz
1920x1080i (0xaa) 74.250MHz +HSync +VSync Interlace
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.12KHz
v: height 1080 start 1084 end 1094 total 1125 clock 50.00Hz
1920x1080 (0xab) 74.250MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.75KHz
v: height 1080 start 1084 end 1089 total 1125 clock 30.00Hz
1920x1080 (0xac) 74.250MHz +HSync +VSync
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.12KHz
v: height 1080 start 1084 end 1089 total 1125 clock 25.00Hz
1920x1080 (0xad) 74.250MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.00KHz
v: height 1080 start 1084 end 1089 total 1125 clock 24.00Hz
1920x1080i (0xae) 74.176MHz +HSync +VSync Interlace
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.72KHz
v: height 1080 start 1084 end 1094 total 1125 clock 59.94Hz
1920x1080 (0xaf) 74.176MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.72KHz
v: height 1080 start 1084 end 1089 total 1125 clock 29.97Hz
1920x1080 (0xb0) 74.176MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 26.97KHz
v: height 1080 start 1084 end 1089 total 1125 clock 23.98Hz
1280x720 (0xb1) 74.250MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.00KHz
v: height 720 start 725 end 730 total 750 clock 60.00Hz
1280x720 (0xb2) 74.250MHz +HSync +VSync
h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.50KHz
v: height 720 start 725 end 730 total 750 clock 50.00Hz
1280x720 (0xb3) 74.176MHz +HSync +VSync
h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 44.96KHz
v: height 720 start 725 end 730 total 750 clock 59.94Hz
1440x576i (0xb4) 27.000MHz -HSync -VSync Interlace
h: width 1440 start 1464 end 1590 total 1728 skew 0 clock 15.62KHz
v: height 576 start 580 end 586 total 625 clock 50.00Hz
1440x480i (0xb5) 27.027MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.75KHz
v: height 480 start 488 end 494 total 525 clock 60.00Hz
1440x480i (0xb6) 27.000MHz -HSync -VSync Interlace
h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.73KHz
v: height 480 start 488 end 494 total 525 clock 59.94Hz
720x576 (0xb7) 27.000MHz -HSync -VSync
h: width 720 start 732 end 796 total 864 skew 0 clock 31.25KHz
v: height 576 start 581 end 586 total 625 clock 50.00Hz
720x480 (0xb8) 27.027MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.50KHz
v: height 480 start 489 end 495 total 525 clock 60.00Hz
720x480 (0xb9) 27.000MHz -HSync -VSync
h: width 720 start 736 end 798 total 858 skew 0 clock 31.47KHz
v: height 480 start 489 end 495 total 525 clock 59.94Hz
640x480 (0xba) 25.200MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.50KHz
v: height 480 start 490 end 492 total 525 clock 60.00Hz
640x480 (0xbb) 25.175MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz
v: height 480 start 490 end 492 total 525 clock 59.94Hz
DP1 disconnected (normal left inverted right x axis y axis)
Identifier: 0x44
Timestamp: -763203693
Subpixel: unknown
Clones: HDMI2
CRTCs: 0 1 2
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
HDMI2 disconnected (normal left inverted right x axis y axis)
Identifier: 0x45
Timestamp: -763203693
Subpixel: unknown
Clones: DP1
CRTCs: 0 1 2
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Identifier: 0x46
Timestamp: -763203693
Subpixel: no subpixels
Clones:
CRTCs: 3
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
2014-05-07, 02:56
(2014-05-06, 06:45)macmus Wrote: I have issues with Netflix APP for windows 8 when using Dolby 5.1. The whole movie slow downs and it becomes unteachable.
This is a known bug that Intel has not yet responded to, but there's a workaround: "While the Netflix app is running on the TV and a 5.1 DD+ audio track selected (i.e., with no sound output and skipping most video frames), go into the Speaker Setup configuration (right click on the Speakers icon, Playback Devices, select Intel Display Audio device, and click on Configure). Choose Stereo option and click Next a couple of times, followed by Finished." You'll get an error popup, but it will work.
Go on the Intel communities forum and complain. Most of us who have been bringing this up for months (since December) have given up.
2014-05-07, 07:21
(2014-05-07, 02:56)Taxcheat Wrote: Go on the Intel communities forum and complain. Most of us who have been bringing this up for months (since December) have given up.
Thanks!
Why this is intel bug ? netflix cannot address that ?
I like addon for XBMC but this one does not have dolby
Oh well .. i will have to keep chromcast for some time ..
2014-05-07, 07:50
Wait, there's still the audio bug in Intel drivers? I thought this was only for BayTrail and not in Haswell.
2014-05-07, 09:22
(2014-05-06, 19:23)axbmcuser Wrote: @fritsch
Question regarding the second blacklevel test image:
Although all my movie files seem now correct black level wise, i noticed that the above test image (i used the second one) looks correct while looking at the thumbnail in the file overview. (almost all squares are visible separately)
As soon as i launch the image to fullscreen, the image looks too dark. Is it possible that pictures are somehow rendered/processed differently hard-/software-wise than movies, so the image isn't correctly displayed while in fullscreen mode?
Just to confirm axbmcuser's observation, the test images look totally different in thumbnail (OK) and full screen (crushed blacks), which makes them a little difficult to use as test images! xbmc seems to be messing with the luminance when displaying pictures full screen, is this a known feature? This is with the sensible NUC RGB settings, i.e. X11 driver full RGB, xbmc setting 16-235, TV expecting limited range.
2014-05-07, 09:25
It does not. Could be a known feature by your TV ... "optimizing Contrast" or something. Try xbmc Limited option unset and keep your hdmi on limited (remove the xrandr hack) and compare.
2014-05-07, 09:45
(2014-05-07, 09:25)fritsch Wrote: It does not. Could be a known feature by your TV ... "optimizing Contrast" or something. Try xbmc Limited option unset and keep your hdmi on limited (remove the xrandr hack) and compare.
Good point fritsch, as you say it's probably the TV. Mine's a recent Panasonic LCD, what's yours xbmcuser? I'll experiment with xbmc full RGB, X11 limited RGB (though this will presumably mean it's doing the nasty stretch-then-shrink luminance operations), as well as TV settings, and report back if I discover anything that might be of use to anyone else. Though we're really splitting hairs here, basically the image looks lovely and everything is working great since the kernel XHCI bug was patched.