Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3075 Discussions

Error configure a Y416 HEVC encoder

cedronius__anders
New Contributor I
‎04-12-2021 06:08 AM
660 Views

 

System : Ubuntu 20.04

CPU:

model name : Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz

libva:

libva info: VA-API version 1.11.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_11
libva info: va_openDriver() returns 0

MSDK:

Notification: The MSDK version Loaded is: v1.35

 

When trying to encode Y416 frames I get the error unsupported

cedronius__anders_2-1618232364798.png

Results in ->

cedronius__anders_1-1618230546472.png

Forcing the code/encoder to encode P010 frames generates no errors >

cedronius__anders_0-1618230380130.png

Results in ->

cedronius__anders_3-1618232860431.png

Why?

 

Thanks for helping.

/Anders.

 

0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.