Posts: 467
Joined: May 2008
Reputation:
0
I believe I have.
There's no "De-interlace" option when VAAPI is enabled. Just Auto-select, Bob and Bob (inverted). "De-interlace" only appears when using software decoding.
There's also no options for
Use Mpeg-2 VAAPI: Yes
Use Mpeg-4 VAAPI: if you like
UseVC-1 VAAPI: off
So I imagine I'm not using a build with these changes.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
I have no idea which OpenELEC version you are running - but OpenELEC 4.0 has the Option "Use SW Filter", Deinterlace can only be used in this version when that option is enabled. It's hidden in Experimental hierarchy.
All newer version, which run the code of the first page don't need to trigger that setting seprately, cause it can be switched on the fly - directly from selection screen.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 56
Joined: Oct 2010
Reputation:
4
Thanks for the information. Reverted to the June 30 version from apt cache and it works again.
Posts: 467
Joined: May 2008
Reputation:
0
Currently using
OpenELEC_Helix (official) Version: devel-20140611170617-r18580-ga84b926
OpenELEC_Helix git: a84b926724c7b96c48aa0295ecb2bf599d98eb6f
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Most likely the patch was not integrated ... use a 4.0.7 build and you will get it.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 467
Joined: May 2008
Reputation:
0
Apologies, I'm an idiot. I only had Advanced settings enabled and not Expert.
Well it looks like the Intel J1900 isn't fast enough to do yadif well enough with VAAPI enabled but it's fine when using full software decoding which is nice to know.
Stable 50fps with all software
30-40 fps with yadif and vaapi
(You probably know all this already though!)
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Yeah the J1900 has probably the worst GPU that you can imagine ... intel fucked that up completely.
VAAPI + YADIF won't work on this J1900, cause the GPU is under too much load when doing decoding + rendering ... it sucks balls :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
The only thing we got to work "gpu only" is VAAPI decoding + VAAPI BOB, which is not in your current version.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 467
Joined: May 2008
Reputation:
0
But it handles it all fine in software which isn't so bad I guess.
Shame I can't get the nvidia 820m graphics in my Asus EB1037 working alongside side it!
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Yes - the CPU is really okay. GPU is stressed to death in the above scenario.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Hopefully ... File a bug on freedesktop and tell them that the Baytrail GPU is currently unusable ... will get funny to see the reply :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.