All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98278] Corrupted videos VA-API HW encoding radeonsi
Date: Sun, 16 Oct 2016 14:59:30 +0000	[thread overview]
Message-ID: <bug-98278-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4013 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98278

            Bug ID: 98278
           Summary: Corrupted videos VA-API HW encoding radeonsi
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: neatnoise@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Hello,

There is an issue in hardware encoding using radeonsi driver and VA-API. It
happens when 2 encoding software - gstreamer and avconf are used. Generated
output videos are corrupted, full of green and purple colors. There is no error
in the terminal output.

There is no problem in HW decoding, it generates valid output.
I've tried to use omx HW acceleration, but gstreamer couldn't even initialize
gst-omx plugin.

Generated video: https://www.youtube.com/watch?v=XJlWCdgB4Lc

gst command: LIBVA_DRIVER_NAME=radeonsi gst-launch-1.0 -e ximagesrc
display-name=:0 use-damage=0 startx=0 starty=0 endx=1919 endy=1079 ! multiqueue
! video/x-raw,format=BGRx,framerate=60/1 ! vaapipostproc format=i420 !
video/x-raw,format=I420,framerate=60/1 ! multiqueue ! vaapih264enc bitrate=3000
dct8x8=true ! h264parse ! multiqueue ! matroskamux name=muxer muxer. !
progressreport name=Rec_time ! filesink location=test.mp4

glxinfo:
OpenGL renderer string: Gallium 0.4 on AMD BONAIRE (DRM 2.46.0 / 4.8.1-1-ARCH,
LLVM 4.0.0)
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel
(git-b7d9677)

kernel driver: radeon

vainfo:
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.2)
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileNone                   : VAEntrypointVideoProc

omx:
 Scanning directory /usr/lib/bellagio/

 Scanning library /usr/lib/bellagio/libomxclocksrc.so
Component OMX.st.clocksrc registered with 0 quality levels
  Specific role OMX.st.clocksrc registered

 Scanning library /usr/lib/bellagio/libomx_mesa.so
Component OMX.mesa.video_decoder registered with 0 quality levels
  Specific role OMX.mesa.video_decoder.mpeg2 registered
  Specific role OMX.mesa.video_decoder.avc registered
  Specific role OMX.mesa.video_decoder.hevc registered
Component OMX.mesa.video_encoder registered with 0 quality levels
  Specific role OMX.mesa.video_encoder.avc registered

 Scanning library /usr/lib/bellagio/libomxvideosched.so
Component OMX.st.video.scheduler registered with 2 quality levels
  Specific role OMX.st.video.scheduler registered

 Scanning library /usr/lib/bellagio/libomxaudio_effects.so
Component OMX.st.volume.component registered with 2 quality levels
  Specific role OMX.st.volume.component registered
Component OMX.st.audio.mixer registered with 1 quality levels
  Specific role OMX.st.audio.mixer registered

 6 OpenMAX IL ST static components in 4 libraries succesfully scanned

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5440 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-10-16 14:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 14:59 bugzilla-daemon [this message]
2016-10-16 15:20 ` [Bug 98278] Corrupted videos VA-API HW encoding radeonsi bugzilla-daemon
2016-10-16 16:28 ` bugzilla-daemon
2016-10-16 18:45 ` bugzilla-daemon
2016-10-16 18:55 ` bugzilla-daemon
2016-10-16 18:57 ` bugzilla-daemon
2016-10-16 19:01 ` bugzilla-daemon
2016-10-16 19:05 ` bugzilla-daemon
2016-10-16 19:49 ` bugzilla-daemon
2016-10-16 21:00 ` bugzilla-daemon
2016-10-16 21:52 ` bugzilla-daemon
2016-10-16 21:52 ` bugzilla-daemon
2016-10-16 23:26 ` bugzilla-daemon
2016-10-17  0:10 ` bugzilla-daemon
2016-10-17 10:19 ` bugzilla-daemon
2016-10-17 11:01 ` bugzilla-daemon
2016-10-17 12:05 ` bugzilla-daemon
2016-10-17 14:20 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98278-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.