[fritsch]

Please provide: xrandr --verbose | pastebinit from this setup, please, cause if you don't have the full xrandr in use - the driver will scale twice ...

[ix400]

Hi fritsch,

can you please continue to provide the openelec builds?

That would be really nice of you!

Chris

[fritsch]

Hi fritsch,

can you please continue to provide the openelec builds?

That would be really nice of you!

Chris

Time does not allow it sorry. For now I don't have implemented an automated system to build those. But it's fairly easy for every one else. Basically, you need to use the mkpkg_kodi scripts from OpenELEC and change the version in package.mk of kodi and kodi-theme-confluence. For the time being you can use my jarvis-egl branch, which will be a good base (it's OE 6.0) for the hw - as we don't have many driver problems there.

[aesthetiker]

Perfect! everything is working :-) including pvr

http://fritsch.fruehberger.net/openelec/

Changelog:
- VAAPI works again
- SW playback broken :-) but audio works.
Fixed, current branch: https://github.com/fritsch/OpenELEC.tv/c...jarvis-egl

[ix400]

Hi fritsch,

can you please continue to provide the openelec builds?

That would be really nice of you!

Chris

Time does not allow it sorry. For now I don't have implemented an automated system to build those. But it's fairly easy for every one else. Basically, you need to use the mkpkg_kodi scripts from OpenELEC and change the version in package.mk of kodi and kodi-theme-confluence. For the time being you can use my jarvis-egl branch, which will be a good base (it's OE 6.0) for the hw - as we don't have many driver problems there.

... but still way to complicated for me to do this on my own.

Maybe you can provide a new openelec build once in a while, in case your time allows it. Maybe once a month or so. Would be cool.

[fritsch]

That should be doable, but only if users start to post debuglogs and are not going on my nerves with unrelated n00b questions :-)

[ix400]

That should be doable, but only if users start to post debuglogs and are not going on my nerves with unrelated n00b questions :-)

... promised, no complaints without a debug log.

Thanks a lot,
Chris

[VirtualRain]

That should be doable, but only if users start to post debuglogs and are not going on my nerves with unrelated n00b questions :-)

I don't blame you, but you have to admit when you start to promise better video quality, you're going to attract a lot of interest... even noobs want better quality video

I echo the request for an occasional OE drop... One a month would be more than enough for those of us wanting to experience your bleeding edge work but minimize the fuss. But I can also wait til this hits the mainstream if that's what it takes.

[aesthetiker]

Can someone try PowerOff of htpc with this release? No function when i click on the remote PowerOff anymore.

[Roby77]

Can someone try PowerOff of htpc with this release? No function when i click on the remote PowerOff anymore.

You are ot here

http://openelec.tv/forum/90-miscellaneou...ot-working

[Milhouse]

There are OpenELEC Jarvis x86 builds here which I think contain all the latest commits (don't have Intel hardware myself, so that's pretty much untested). If they're confirmed as good maybe this will take some of the load off of fritsch.

[fritsch]

Looks good. Thanks @ Milhouse!

[noggin]

My Sony TV is a 2015 UHD set. The TV has an HDMI setting for "Auto", "Limited", and "Full". Are you saying the TV ignores this setting, or it just doesn't work properly on "Auto"?

I've not tried forcing mine. I have a 2014 set. I just know that in default mode that the VAAPI EGL stuff that fritsch and co have developed here - that allows 16-235 to be preserved by using the GPU in full range AND allows for VAAPI MCDI deinterlacing doesn't work for me in this mode because the TV interprets the xrandr Full setting as Full, when it is there as a 'cheat' (and a very good one) to get Limited all the way through without 0-255 scaling.

FYI, I've currently got things working with OpenElec 5 and Kodi 14.2 with Kodi set to 16-235 (and "Prefer VAAPI render method" disabled), No change to GPU, TV set to "Limited" where I'm getting proper preservation of levels without conversion... I can see blacker than blacks and whiter than whites making it easy to set my TV black level to reference black. Banding is minimal - better than when converting to full range but not as smooth as what I saw in a post on the previous page.

Yep - but that's not what is being discussed in this thread. We specifically want to use VAAPI rendering as it lets us do decent quality Motion Compensated Hardware deinterlacing. The work in this thread allows you to use VAAPI rendering and to avoid 0-255 banding - or if you can't at least mitigate it with dithering.

If you have "Prefer VAAPI render method" disabled you are going to be using software deinterlacing?

If you are only watching progressive sources, this may not be an issue, but lots of us use Kodi for watching Live/Recorded TV, and much of this is interlaced, and MCDI VAAPI deinterlacing is worth having.

In this situation you have two options. Stick with Full level output (not an issue if you switch between Limited and Full sources with an AVR as this should pass through the info frames that the TV follows), however disable the 16-235 settings in Kodi, and run with dithering enabled to help mask the banding otherwise caused by 16-235->0-255 range extension, or run the HDMI output in "Limited" mode (i.e. don't do the xrandr thing to change the GPU output range) and also make sure Limited levels in Kodi are disabled but again ensure dithering is enabled to hide the banding.

Maybe I misunderstand, but in either of these scenarios, you're going to lose your BTB and WTW information. It's not just about banding. You need everything to pass through without levels conversion... player, GPU and TV. When any part of the signal chain does a conversion, 16 becomes 0 and 235 becomes 256 and you lose that extra dynamic range. Dithering is better than nothing, but no conversion is the ideal solution.

Does your TV not have a mode where it can be forced to accept 16-235 without conversion?

BTB and WTW don't really worry me. Yes - they help you calibrate your TV - but any content <16 shouldn't be visible on a correctly calibrated display, so clipping it in the digital domain (whilst not good practice) isn't the end of the world with a well mastered source (though clipping <16 >235 transients can cause issues with scaling at a later date)

Scaling artefacts do worry me - as I don't like banding. A little bit of dither helps a lot to mask them. (My first employer patented such a technique...)

[fritsch]

http://cgit.freedesktop.org/vaapi/intel-...d4cf9080b3 - not good for HSW people.

[sat4all]

http://cgit.freedesktop.org/vaapi/intel-...d4cf9080b3 - not good for HSW people.

Intel