[D-an-W]

Morning fritsch!

This morning I backed up my OE config and performed a Hard Reset from the OE section.

I then have four *.xml files to copy into the /userdata which after setting the Content type of the folders usually gets me up and running however nothing happened after setting the content type and telling OE to update the library (Using OpenELEC-Generic.x86_64-6.0.95-fritsch.tar).

I then tried restoring the backup I created and all worked well but ideally I wanted a "fresh start" with the fritsch build.

Could this be anything at all to do with the build I am using or do you think I need to look elsewhere for the problem (Sorry if this is totally off topic!)?

[AndyFurniss]

I don't know what I am talking about really :-)

Not sure I do either :-)

Possibly working with decoded raw video is just easier from a generic design POV.

Yes - definitely - and works with any codec.

AIUI mpeg don't specify anywhere what an encoder should do (apart from producing a compliant bitstream). Which means variety between encoders then extra variety between mpeg2/h264/VC1/whatever. Perhaps for specialised silicone it's just far more robust to work with the decoded output.

Yep - and I think deinterlacing is not a high priority for many designers who are more interested in progressive content (interlacing is slowly disappearing - but it will still be a while before it has gone completely)

For TVs they are going to be doing far more than de-interlacing anyway. I recall reading of phase plane correlation as being one way motion interpolaters worked, but don't know anything about Alchemist or Quasar.

Phase Correlation is a motion detection algorithm. Unlike pure block-matching it can also cope with scaling and rotation - not just linear translation. It is often used with block matching though ISTR. https://en.wikipedia.org/wiki/Phase_correlation

It's extensively used in high-end broadcast frame rate converters - such as the Snell (now SAM) Alchemist range of standards converters. For near-transparent conversion between 50 and 60Hz TV systems you need very high quality motion detection to allow frames to be interpolated with minimal artefacts. Alchemist is still the gold standard for this. Quasar is the equivalent up converter which takes SD interlaced video and up converts it to HD. Deinterlacing to maximise the vertical resolution is a key part of this, and AIUI phase correlation is used to ensure the highest quality interpolation of the missing fields in an interlaced signal.

Alchemist : https://s-a-m.com/products/alchemist-ph.c-hd/c-24/p-209
Quasar : https://youtu.be/oltaH2Ez82g?t=120
Quasar : https://www.youtube.com/watch?v=7kZGZeCOsL4

[paradix]

Yeah - set the Scaling method to "Bilinear" and save it for all files - also too much for Baytrail.

I made the changes in the settings according to the above but picture is still jerky.
Could you take a look at the debug log if you see something suspicious

[soder]

I got a question about watching 4k with this version.

I got a NUC Braswell, running OE Fritsch, and a new 4k TV.

Just when I got it I tested the 4k videos I got and it was all smooth.

Now it isn't and the only thing I know I've changed is that I now use the hdmi cable for sound too. Before I used a toslink cable for sound.

Can that make the video not play smooth?

/Söder

LOL, it was the auto update in OE that had updated to official version. LOL! =)

[BigL-New]

For anyone interested here are kernel packages ready-to-use in Ubuntu. They are targeted for Asus Beebox but it's vanilla 4.3.0 kernel with passthrough patch and few other patches from OpenElec so for sure will work well at leas on any BSW hardware:

http://37.235.60.68/linux-headers-4.3.0-..._amd64.deb
http://37.235.60.68/linux-image-4.3.0-pa..._amd64.deb

List of patches:

linux-003-no_dev_console.patch
linux-011-Thermal-initialize-thermal-zone-device-correctly.patch
linux-012-Thermal-handle-thermal-zone-device-properly-during-s.patch
linux-013-Thermal-do-thermal-zone-update-after-a-cooling-devic.patch
linux-054-nuvoton_revert_d7b290a1056c5564eec8a1b169c6e84ff3.6.114c13.patch
linux-057-Removed-MCE-customer-code-restriction-in-rc6-decode.patch
linux-990.06-hda-Avoid-outputting-HDMI-audio-before-prepare-.patch
linux-999.02-0001-pm-disable-async-suspend-resume-by-default.patch
linux-999-i915-implement-passthrough-colors.patch
linux-999-i915-use-legacy-turbo.patch

To use passthrough patch in Kodi put this into ~kodi/.config/openbox/autostart (please copy, don't try to write it from screen):

Code:

OUTPUT=`xrandr -q | sed '/ connected/!d;s/ .*//;q'`
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Full"
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Video 16:235 pass-through"
xrandr -display :0 --output $OUTPUT --off ; xrandr -display :0 --output $OUTPUT --auto
/usr/bin/kodi --standalone

Big thanks goes to d0dger for providing space on web-server!

[BigL-New]

After reboot of my Ubuntu after kernel change i've noticed that problem with washed-out colors after reboot has returned. Everything returns to great colors after watching any movie.

I've latest packages from ppa and my autostart is as follows:

OUTPUT=`xrandr -q | sed '/ connected/!d;s/ .*//;q'`
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Video 16:235 pass-through"
/usr/bin/kodi --standalone

What is wrong?

[fritsch]

No idea ... you are the kernel expert :-)

Try:
OUTPUT=`xrandr -q | sed '/ connected/!d;s/ .*//;q'`
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Full"
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Video 16:235 pass-through"
xrandr -display :0 --output $OUTPUT --off ; xrandr -display :0 --output $OUTPUT --auto
/usr/bin/kodi --standalone

[fritsch]

I got a question about watching 4k with this version.

I got a NUC Braswell, running OE Fritsch, and a new 4k TV.

Just when I got it I tested the 4k videos I got and it was all smooth.

Now it isn't and the only thing I know I've changed is that I now use the hdmi cable for sound too. Before I used a toslink cable for sound.

Can that make the video not play smooth?

/Söder

LOL, it was the auto update in OE that had updated to official version. LOL! =)

Yeah - use the 6.0.95 version.

[schmoko]

I'm seeing sporadic flickering display at all times using OpenElec builds, both Isengard and Jarvis. It seems like a driver issue, the flicker starts with the openelec logo, before X has even loaded. It almost looks like the GPU is overheating. Is this a known issue?

I was using a build from 10/04 [1] before I saw the issue, but didn't upgrade until 10/26 [2], so the regression could be anywhere in that (very large) window. I'd be happy to try to bisect if archived builds are available. Reverting to the 10-04 build or the official OpenElec fixes the issue.

Hardware is an ASUS Celeron chromebox 2955U, connected via HDMI to a Denon AVR.

[1: OpenELEC-Generic.x86_64-6.0-devel-20151004165234-r21363-gd89c515]
[2: OpenELEC-Generic.x86_64-6.0-devel-20151025194904-r21541-gda1b74a]

Is it the occasional horizontal line flashing across the screen? Because I am having that since updating to the custom EGL build of Open ELEC. I have the same Chromebox as you and a Denon 3311CI AVR connected via HDMI.

This was a constant flickering. The UI was near unusable and video was unwatchable.

Just to update on this issue (in case anyone else experiences it.) Based on everyone's feedback, I decided this was probably a thermal issue and moved the Chromebox out of the cabinet it was in and away from other electronic devices. This fixed the flickering.

I'm guessing the GPU runs a bit hotter with the VAAPI changes, and hence the issue went away when I rolled back to vanilla OpenElec. I'm willing to keep the box out in the open for better playback and colors.

Fritsch,

If you think that running hotter than normal is unexpected behavior let me know and I can try capturing logs or lmsensors data.

Ian.

[ilovethakush]

I'm seeing sporadic flickering display at all times using OpenElec builds, both Isengard and Jarvis. It seems like a driver issue, the flicker starts with the openelec logo, before X has even loaded. It almost looks like the GPU is overheating. Is this a known issue?

I was using a build from 10/04 [1] before I saw the issue, but didn't upgrade until 10/26 [2], so the regression could be anywhere in that (very large) window. I'd be happy to try to bisect if archived builds are available. Reverting to the 10-04 build or the official OpenElec fixes the issue.

Hardware is an ASUS Celeron chromebox 2955U, connected via HDMI to a Denon AVR.

[1: OpenELEC-Generic.x86_64-6.0-devel-20151004165234-r21363-gd89c515]
[2: OpenELEC-Generic.x86_64-6.0-devel-20151025194904-r21541-gda1b74a]

Is it the occasional horizontal line flashing across the screen? Because I am having that since updating to the custom EGL build of Open ELEC. I have the same Chromebox as you and a Denon 3311CI AVR connected via HDMI.

This was a constant flickering. The UI was near unusable and video was unwatchable.

Just to update on this issue (in case anyone else experiences it.) Based on everyone's feedback, I decided this was probably a thermal issue and moved the Chromebox out of the cabinet it was in and away from other electronic devices. This fixed the flickering.

I'm guessing the GPU runs a bit hotter with the VAAPI changes, and hence the issue went away when I rolled back to vanilla OpenElec. I'm willing to keep the box out in the open for better playback and colors.

Fritsch,

If you think that running hotter than normal is unexpected behavior let me know and I can try capturing logs or lmsensors data.

Ian.

Yes I think running hotter than normal is unexpected behavior, but considering you had it locked up in a cabinet, it may not be all that unexpected. Why would you put a computer with fans and air paths in a cabinet?

Just to be clear. I'm running the EGL build and if anything, my box is actually quieter and cooler than it was on previous versions of openelec.

[grantonstar]

Hi everyone,

I've been using these builds for a couple of years now with almost no issues (thanks to the excellent work of those here). Now however I'm finally upgrading my old Celeron 1037U (Gigabyte Brix) for a self made custom box with a Sky Lake i3 (HD Graphics 530). Is there anything I need to do or consider before starting off with the installation of Ubuntu Server 15.10 as per the instructions on the first page? Does the included kernel support the Skylake? Any hints/tips?

Thanks

[fritsch]

Is it the occasional horizontal line flashing across the screen? Because I am having that since updating to the custom EGL build of Open ELEC. I have the same Chromebox as you and a Denon 3311CI AVR connected via HDMI.

This was a constant flickering. The UI was near unusable and video was unwatchable.

Just to update on this issue (in case anyone else experiences it.) Based on everyone's feedback, I decided this was probably a thermal issue and moved the Chromebox out of the cabinet it was in and away from other electronic devices. This fixed the flickering.

I'm guessing the GPU runs a bit hotter with the VAAPI changes, and hence the issue went away when I rolled back to vanilla OpenElec. I'm willing to keep the box out in the open for better playback and colors.

Fritsch,

If you think that running hotter than normal is unexpected behavior let me know and I can try capturing logs or lmsensors data.

Ian.

Yes I think running hotter than normal is unexpected behavior, but considering you had it locked up in a cabinet, it may not be all that unexpected. Why would you put a computer with fans and air paths in a cabinet?

Just to be clear. I'm running the EGL build and if anything, my box is actually quieter and cooler than it was on previous versions of openelec.

It runs cooler (!) even up to 20 degrees on my passively cooled system. As we do not have to copy the outputsurfaces but can render them directly. What could "heat it up" for you is, that you perhaps did not use Lanczos 3 Optimized for upscaling before, as by default 720p was upscaled via bilinear only ...

[fritsch]

Hi everyone,

I've been using these builds for a couple of years now with almost no issues (thanks to the excellent work of those here). Now however I'm finally upgrading my old Celeron 1037U (Gigabyte Brix) for a self made custom box with a Sky Lake i3 (HD Graphics 530). Is there anything I need to do or consider before starting off with the installation of Ubuntu Server 15.10 as per the instructions on the first page? Does the included kernel support the Skylake? Any hints/tips?

Thanks

SKL is fully work in progress by intel. Linux performance is quite bad actually (see latest phoronix comparison). Make sure to upgrade the kernel to linux 4.3.0 and also make sure to use latest linux-firmware. For the rest: good luck.

[grantonstar]

Hi everyone,

I've been using these builds for a couple of years now with almost no issues (thanks to the excellent work of those here). Now however I'm finally upgrading my old Celeron 1037U (Gigabyte Brix) for a self made custom box with a Sky Lake i3 (HD Graphics 530). Is there anything I need to do or consider before starting off with the installation of Ubuntu Server 15.10 as per the instructions on the first page? Does the included kernel support the Skylake? Any hints/tips?

Thanks

SKL is fully work in progress by intel. Linux performance is quite bad actually (see latest phoronix comparison). Make sure to upgrade the kernel to linux 4.3.0 and also make sure to use latest linux-firmware. For the rest: good luck.

Do you mean this?

I don't mind installing the new kernel. Any other drivers I need to look at installing? Has anyone had any success with a Sky Lake on here thus far?

Failing that, I can move all my server stuff over to the new box and wait for the drivers to stabilise and support Sky Lake properly for Kodi.Is there any ETA from Intel on having better support?

[fritsch]

Kernel 4.4 looks promissing. Check what the drm maintainer said when doing the PR :-) it's on lkml.