According to this (1 year old) post https://software.intel.com/en-us/forums/topic/386795,
the media sdk has better encode quality than vaapi/libva. Is this a feature of the mfx or the customized (and closed source) vaapi (together with closed source vaapi driver implementation) shipped with media sdk?
Could someone explain the differences between vaapi/libva, vaapi/mediasdk and mfx/mediasdk ?
It seems eg sps/pps/slice-header parsing is implemented in mfx, while one have to do that separately when using vaapi.
Is the mfx api basically a wrapper with such convenience functionality implemented?
Yes, the Media SDK library (mfx) makes use of the VA-API (libva) shipped with the "Media SDK for Linux Servers" product and adds value (as you mentioned). Because the Media SDK provides a higher level API, the library can make use of other platform resources and features. You also can have confidence that the Media SDK API has been validated for the specific supported platform.
Thanks, but do I loose compression quality by using the VA-API shipped with Media SDK for Linux Servers?
In other words, I'd like to stay with the VA-API, but have the best compression quality / performance / latency available.