OK a new problem with Isengard version from 1004
After wakeup from suspend there is no picture. After power off and on the nuc there is a picture. With version from 0923 there was no problem
http://xbmclogs.com/pd9jintns
Kernel issue - most likely introduced when updating to 4.1.10 ... I will upgrade to 4.3 the very moment it is out ... Braswell and 4.1.x is meh anyways.
(2015-10-08, 12:43)fritsch Wrote: [ -> ]Kernel issue - most likely introduced when updating to 4.1.10 ... I will upgrade to 4.3 the very moment it is out ... Braswell and 4.1.x is meh anyways.
When 4.3 is out then we, who use your patched kernel 4.2, should also upgrade to 4.3, on Braswell?
Is the kernel still the reason I have the strange "need to go to system setting at first start issue" based on the logs I posted?
@gurabli: No idea - this thread is about testing VideoPlayer and VAAPI implementations - helping with kernels is just done - cause I felt like helping - but as that stuff is taking too much time - I will concentrate on the basics again. As you are a selfhacker and can easily install a 4.3-rcX kernel - you could tell us after you tried it, right?
Thanks for your help on kernels, it is really appreciated. I'm no way any expert with all this, just trying to catch up with things here. I didn't even know or spotted the problems with the unpatched 4.2 kernel until you pointed out.
Just curios, anything in the logs I posted that would help to figure out why I need to enter into system settings on first start to have proper refresh rate change?
(2015-10-08, 01:29)Sunflux Wrote: [ -> ]What projector are you using? If dithering is having such an impact, then it sounds like you aren't actually outputting limited via the new passthrough option (I haven't seen dithering do anything visible in Passthrough mode, but it definitely has an effect in Full mode, which is less ideal).
I am using a Viewsonic Pro8200 projector.
So to test your theory, I loaded up the black bars and increased the brightness on my projector. I see bars below 15. Does that mean Full is getting passed? FYI, my projector is set to Limited.
Code:
OpenELEC:~ # xrandr --verbose
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
HDMI1 connected 1920x1080+0+0 (0x47) normal (normal left inverted right x axis y axis) 520mm x 290mm
Identifier: 0x42
Timestamp: 1230566513
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:
00ffffffffffff0011ee400001010101
00180103800000780a9abb9f60519c23
0e4d59ffef80a9409500904081806159
455901010101023a801871382d40582c
450000000000001e000000ff00533846
3132343130303431300a000000fc0044
454e4f4e2d41565248440a20000000fd
00325a0f6410000a20202020202001f9
020336f14f90050403071f1413121601
0f241e26350f7f071507503d1ec04d02
005706015f7e01677e01835f00006703
0c002500882d023a801871382d40582c
450008222100001e023a80d072382d40
102c458008222100001e011d8018711c
1620582c250008222100009e011d0072
51d01e206e28550008222100001e0091
aspect ratio: Automatic
supported: Automatic, 4:3, 16:9
Broadcast RGB: Video 16:235 pass-through
supported: Automatic, Full, Limited 16:235, Video 16:235 pass-through
That image isn't working.
What the new "Video 16:235 pass-through" option is, is the old Full mode, but with the proper tagging to tell your device that it's receiving a limited signal (note that you need to be running the latest Isengard build for this to work). Previously, you would manually switch to Full mode, set Kodi to Limited, and then manually force your display device to treat it as a limited range signal (which not every display can do). This avoids the video driver doing any range compression/expansion, which is what causes all the banding in the first place.
When your display device is working correctly, you should NOT see anything darker than bar 16. If you are, then it isn't treating it as a limited range signal, and everything will look washed out. Seeing brighter than 235 is fine.
(2015-10-09, 03:08)Sunflux Wrote: [ -> ]That image isn't working.
What the new "Video 16:235 pass-through" option is, is the old Full mode, but with the proper tagging to tell your device that it's receiving a limited signal (note that you need to be running the latest Isengard build for this to work). Previously, you would manually switch to Full mode, set Kodi to Limited, and then manually force your display device to treat it as a limited range signal (which not every display can do). This avoids the video driver doing any range comparession/expansion, which is what causes all the banding in the first place.
When your display device is working correctly, you should NOT see anything darker than bar 16. If you are, then it isn't treating it as a limited range signal, and everything will look washed out. Seeing brighter than 235 is fine.
Okay.. so should I set it to Full in the driver since that seems to be what my projector wants to accept anyway?
You mention your projector is in "limited" mode. How are you doing this? Is there an auto option?
If you simply can't get your projector to accept a limited range signal correctly (and the same thing happens if you force the "Limited 16:235" option, which should result in your blacks being grey), then yes, use xrandr to manually set full mode, set Kodi to full with dithering, and then leave your projector on full. When you do this, you should only see greyshades between 16 and 235.
(2015-10-09, 05:20)Sunflux Wrote: [ -> ]You mention your projector is in "limited" mode. How are you doing this? Is there an auto option?
If you simply can't get your projector to accept a limited range signal correctly (and the same thing happens if you force the "Limited 16:235" option, which should result in your blacks being grey), then yes, use xrandr to manually set full mode, set Kodi to full with dithering, and then leave your projector on full. When you do this, you should only see greyshades between 16 and 235.
Thanks for the help so far. Also, I fixed the link to the picture in my post above. You can see the black bars below 16.
So my projector's color setting is misleading or broken. It's supposed to be "Auto", "RGB", or "YCrBr". I've always taken that to mean RGB = 0-255 and YCrBr = 16-235. However, after trying every combination of xrandr, kodi, and PJ colorspace setting, I've proven that the PJ setting doesn't actually do anything. I leave the PJ on RGB for now, but like I said, it doesn't really matter.
So without PJ options, I have tried all of the combinations on the software side, and I'm more confused than ever. I am running the Oct 6 Jarvis build. Here is what I've found:
Code:
xrandr kodi lowest banding comments
black
----------------------------------------------------------------
full limited 12 high blacks look okay, but bars below 17 flash. bad banding in greyscale ramp
full full 30 high black crush. no detail in shadows, bad banding
limited limited 0 low washed out, black bars flash all the way to 0
limited full 17 low looks good, less banding
pass limited 0 low washed out, black bars flash all the way to 0
pass full 17 low looks good, less banding
From this, I suppose I should run passthrough with full set in Kodi, but that is counter intuitive, isn't it?
Here is a picture of the banding from passthrough and kodi set to full. Dithering off. I can eliminate the banding with dithering set to 6.
Yes, RGB / YCrCB are totally different things. Kodi only operates in RGB, but most cable boxes and BD players can run in component, which how videos are originally encoded. At any rate, RGB can be either limited or full, and component is always assumed to be limited.
Are you using a photo or video test pattern to count bars? Your last 2 results make no sense to me, because in passthrough mode the Kodi full/limited setting does not affect video processing and only changes the GUI rendering.
EDIT: remember with Jarvis you have to add the lines to autostart.sh that switches the video output off and on again in order for Passthrough to work correctly.
I am using a video test pattern to count bars. It's pretty easy to see the different because they are either flashing or not.
I have nothing in my autostart.sh.. what should I be using?