Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
Yes - that will get it attention from the vaapi devs. I posted some posts back what files to provide.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
Well done! all in that is needed.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 157
Joined: Aug 2008
Reputation:
1
tret
Senior Member
Posts: 157
FYI, installed OpenELEC v4.0.6 on a USB drive and ran it on my Late 2013 Macbook Pro 13" w/ Haswell Core i5 and saw the exact same behaviors noted here and in the bug. Definitely appears to be consistent across the Haswell line.
tret
Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
I still think we have two bugs here. I can absolutely not reproduce a freeze with everyday content like LiveTV when Use SWFilter is enabled or in newer version where "Prefer VAAPI Render Method" is disabled.
The only difference makes this sample that was posted above. Therefore I wanted this bug to be filed separately as I think this one is LIBVA issue whereas the other one is some mesa/drm bug.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
"Use SW Filter for VAAPI" is obsolete. v14 has the option: "Prefer VAAPI Render Method", which is the "inverse" of the Filter. On the chromebox you need to turn that "Prefer VAAPI Render method" off to get the same effect as turning "Use SW Filter for VAAPI" on in 13.2 version.
In Helix the setting will be called "Prefer VAAPI Render Method". -> follow Matt's support thread. I talked to him lately and he knows that things.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
Yeah, it at least helps the chrome people to watch bluray rips (progressive) without frequent stutter. That celeron 2955U is the machine with the most problems with this current intel driver bug, it makes that "stutter" every 3 to 5 minutes if the "Prefer VAAPI Render Method" is enabled.
There was a reason I PRd that as default to mainline. For VAAPI-Deinterlacing it won't help, yes. Sometimes users don't need to know all details to be happy.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,371
Joined: Aug 2011
Reputation:
1,088
fritsch
Team-Kodi Developer
Posts: 23,371
Perhaps for the chrome people:
- Disable Prefer VAAPI Render Method
- Set Deinterlace: Auto, Deinterlacing-Method: BOB (_not_ the VAAPI BOB) or De-Interlace (More cpu load).
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.