You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VAAPI invalid chip id or driver is being used. #254
Hey, I am trying to get gstreamer to stream an mpegts stream over udp with hardware accelerated encoding on video using VAAPI. With intel integrated GPU.
Basically I can run this command in command line to do this and it works without any problems.
As you can see both pipelines are identical.
However I am getting an error from gstreamer:
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
Now my idea is that, somehow VAAPI is using the wrong driver while working in JVM but the correct one in command line.
There is this Environment variable that needs to be set for the VAAPI to tell which driver to use:
LIBVA_DRIVER_NAME, which I have set to correct value for my GPU, as, LIBVA_DRIVER_NAME=iHD.
Is there a possibility that when gstreamer is ran through this library, this environment variable is not passed to the gstreamer process?
I can see the environment variable using System.getenv("LIBVA_DRIVER_NAME")
Basically what makes me paranoid is the line: DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
the "I915" makes me think that the wrong driver is being used. Because the commonly used driver for Intel gpu's seems to be the I915 one. Maybe this is the default?
Activity
Nycrera commentedon Aug 9, 2022
Basically what makes me paranoid is the line:
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argumentthe "I915" makes me think that the wrong driver is being used. Because the commonly used driver for Intel gpu's seems to be the I915 one. Maybe this is the default?
I have set up my VAAPI following the https://wiki.archlinux.org/title/Hardware_video_acceleration#Intel
But in the end why would it work on command line and not work on the library with a simple parseLaunch as this.
Nycrera commentedon Aug 9, 2022
I have updated to
Gst.init(Version.of(1,20))No change.