[Milhouse]

By the way the SIGTERM fix is pretty straightforward.

[fritsch]

By the way the SIGTERM fix is pretty straightforward.

Thx - I was too lazy :-)

[fritsch]

SIGTERM fixed, mesa bump to 11.0.7 :-)

[smf007]

Can you upload the crashlog from your home directory?

I can't find one in /storage. Is there another place?

OK, I found it in ~/.kodi/temp:

http://sprunge.us/QXfS

I was able to reproduce this "crash" (the kodi process doesn't actually end, just the GUI disappears), and it is related to the refresh rate switching. Disabling refresh rate switching stops the "crash". If you need another set of logs I'm sure I can get some tomorrow for you.

[_Spook_]

Quick question:

3. Color Management
If your TV is limited range. Go to System -> Video Output and choose "Use Limited Range", disable Dithering.
If your TV is full range. Go to System -> Video Output and unselect "Use Limited Range" and enable Dithering with 8 bits.
If your projector is of low quality, use a dithering setting of 6 or 7 bits.

I have an LG 55EG960V 4k OLED TV. My guess would be that it is full range. Should I use option 2 here then?

[mbosner]

I have a similar LG TV and it depends on your TV setting. The LG does support limited and unlimited color range. Afaik the option is called deep black or something similar.

[fritsch]

Quick question:

3. Color Management
If your TV is limited range. Go to System -> Video Output and choose "Use Limited Range", disable Dithering.
If your TV is full range. Go to System -> Video Output and unselect "Use Limited Range" and enable Dithering with 8 bits.
If your projector is of low quality, use a dithering setting of 6 or 7 bits.

I have an LG 55EG960V 4k OLED TV. My guess would be that it is full range. Should I use option 2 here then?

Why do you guess? Just use the testing videos and find out:

Whites: https://dl.dropboxusercontent.com/u/5572...ipping.mp4
Blacks: https://dl.dropboxusercontent.com/u/5572...ipping.mp4

Also make sure that if it does not work - we need DISPLAY=:0 xrandr --verbose from you.

[fritsch]

@mbosner: http://www.lg.com/uk/tvs/lg-55EG960V <- this one or the non curved model?

[fritsch]

I can't find one in /storage. Is there another place?

OK, I found it in ~/.kodi/temp:

http://sprunge.us/QXfS

I was able to reproduce this "crash" (the kodi process doesn't actually end, just the GUI disappears), and it is related to the refresh rate switching. Disabling refresh rate switching stops the "crash". If you need another set of logs I'm sure I can get some tomorrow for you.

The crashlog is from shutdown ... nope - try with the 4.4-rc5 kernel versions and turn on debug logging before reproducing it.

[b0mb]

hmmmm....

Sorry, no debug.log but i guess i am not the only one with the problem i have.

With latest build on my NUC5PPYH the screen is way too bright.

i reverted back to the build from 131215 and everything is ok again.

[fritsch]

hmmmm....

Sorry, no debug.log but i guess i am not the only one with the problem i have.

With latest build on my NUC5PPYH the screen is way too bright.

i reverted back to the build from 131215 and everything is ok again.

Then happy guessing :-) without xrandr --verbose I cannot do anything ... manually setting it to full range via xrandr fixes the issue?

[b0mb]

I did not try yet ...

I run kodi in fullrgb mode and after updating to the latest build it looks like when you set the hdmi port on tv to 16-235 instead of 0-255.

When i now switch kodi itself from 0-255 to 16-235 the screen becomes really foggy ...

[Devil-Strike]

Latest build is shit , occasional high cpu usage and frame dropping below 17fps on a simple apple trailer on a baytrail j1800 system.

Logs vainfo: http://sprunge.us/YRcC
kodi: http://sprunge.us/VOXN
dmsg: http://sprunge.us/ZPPY

[fritsch]

Latest build is shit , occasional high cpu usage and frame dropping below 17fps on a simple apple trailer on a baytrail j1800 system.

Logs vainfo: http://sprunge.us/YRcC
kodi: http://sprunge.us/VOXN
dmsg: http://sprunge.us/ZPPY

Thx - can be clearly seen in the logfile.

[VirtualRain]

Third question, for everyone. Are Milhouses builds EGL or no? Any reason someone would choose to run his generic version on a chromebox over fritsch builds?

My builds are EGL. They're essentially the same as fritsch builds, but with updated OpenELEC packages which can be both good and bad (if you're a Pandora user, my builds are not a good choice right now due to some broken upstream certificates). Plus of course Nvidia_Legacy support where fritsch is focused on Intel. My builds may also contain forthcoming Kodi features not found in fritsch builds.

Horses for courses, really - if you want a more stable Intel experience based on an older OpenELEC and less experimental Kodi base then go with fritsch. If you want a more bleeding edge OpenELEC/Kodi experience and/or Nvidia support, then there's my build.

Thanks for yours and others replies.

Anyone have any thoughts on why my Haswell Mac Mini (currently running OE Isenguard Fritsch edition) is not handshaking with my AVR after a refresh rate change? What code component is responsible for this? Is there any possible work-around?

As it stands, after a refresh rate change I need to unplug and replug the HDMI cable to get a signal. I had no problems on Helix (OE5) with this.