[Spyderturbo007]

Hello. I'm having some issues with movies becoming pixelated during playback. I have ruled out everything except for my NUC by swapping out cables, and substituting a laptop for the NUC. It comes down to the NUC.

Intel NUC6i3SYH

• i6-6100U Dual Core @ 2.3GHz
  
• Intel HD Graphics 520
  
• 8GB Kingston HyperX DDR4 @ 2400MHz
  
• Hardwired gigabit connection
  

LibreELEC v7.0.3 (I updated to 7.9.5.3, but lost my audio and still had the pixelization issues, so I downgraded back to v7.0.3)
Kodi v17

The issue is consistent and happens at almost the same spots every time.



Here is my Kodi.log file. I enabled Debugging, rebooted the NUC and played a section of the movie were the pixelization occurs. Then I copied the log.

http://pastebin.com/XRskCFq5

[whysoserious]

Is the video file encoded using VC-1? I get a similar effect on some VC-1 encoded Blu Ray movies with hardware acceleration enabled for VC-1. If I turn off HW acceleration for VC-1 (only for VC-1, leaving all others enabled) it seems to work better.

[Spyderturbo007]

It looks like it is. VLC Shows:

Codec: Windows Media Video VC1 (WVC1)

Where would I find that setting to disable it for VC1 files?

[Spyderturbo007]

Ah. Found it. I needed to change my settings to Expert.

You are a genius. It worked like a charm!!

[whysoserious]

Ah. Found it. I needed to change my settings to Expert.

You are a genius. It worked like a charm!!

Every now and then, I get something right!

Thx!

[goujam]

I have seen this same problem on Harry Potter blu-ray rips when ever there is a bright scene it pixels around that area. Setting VC-1 to software decode fixes this

[fritsch]

Wait! This was fixed in vaapi ... some weeks ago: https://github.com/01org/intel-vaapi-dri...93f790361c and for SNB: https://github.com/01org/intel-vaapi-dri...a2c4f88270

@MillhouseVH: Could you include those two commits in your nightlies?

[goujam]

On this machine I'm running librelec 8.0.2 so this fix may not have reached me if it's been implemented at all

[Milhouse]

Wait! This was fixed in vaapi ... some weeks ago: https://github.com/01org/intel-vaapi-dri...93f790361c and for SNB: https://github.com/01org/intel-vaapi-dri...a2c4f88270

@MillhouseVH: Could you include those two commits in your nightlies?

Hi. Unfortunately the first commit only applies on intel-vaapi-driver 1.8.3 and we're currently using 1.8.2, so I bumped to 1.8.3 along with both patches, and now Kodi crashes on playback of VC-1 content:

crashlog: http://sprunge.us/PPWX
vainfo: http://sprunge.us/gOFE

1.8.3 without the patches does not crash, and plays back my VC-1 test file.

Latest tip of tree 2f2f0ba (what will be 1.8.4) also crashes (and requires updated libva due to new VA API version: patches):

crashlog: http://sprunge.us/HHbE
vainfo: http://sprunge.us/heQZ

Since the patches don't work, I'll stay on 1.8.2 for now.

Not sure if you're in touch with anyone at Intel, but feel free to pass along the crashlogs (or I'll add them on the first commit you linked).

[Milhouse]

Just an addendum to the above, it looks like intel-vaapi-driver 1.8.4 (and also 1.8.3 with PR:234) is crashing when *RESUMING* a VC-1 video (ie. "Resume from 00:17:00"), but will play the same video "from the beginning" without a problem (and can seek within the video once playing), so possibly a seek-at-start issue? Maybe the intensity compensation change in the driver doesn't allow for missing P or B frames (guessing that might be the case when resuming)?

[Milhouse]

@Spyderturbo007 & @goujam: If you wanted to test if this issue is now fixed, you can try build #0826p: Generic

Note that this is a LibreELEC 9.0 alpha build with Kodi 18a1. It uses the current intel-vaapi-driver 1.8.3 plus the intensity compensation fix (PR:234) and a fix for the crash caused by PR:234 when resuming certain VC-1 videos (PR:260, thanks @fritsch).