[FFmpeg-trac] #5685(undetermined:closed): scale_vaapi does not scale full image, but crops to upper left corner instead

[FFmpeg]

#5685: scale_vaapi does not scale full image, but crops to upper left corner
instead
-------------------------------------+-------------------------------------
             Reporter:               |                    Owner:
  radek.hvizdos                      |                   Status:  closed
                 Type:  defect       |                Component:
             Priority:  normal       |  undetermined
              Version:  git-master   |               Resolution:  wontfix
             Keywords:  scale_vaapi  |               Blocked By:
  h264                               |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by radek.hvizdos):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Hi jkqxz,

 Thank you very much for your suggestions. I was able to use official
 Debian packages of libva and i965-va-driver from Debian Stretch on my
 Jessie installation, and '''now the video resize works as intended'''.


 {{{
 wget
 http://ftp.cz.debian.org/debian/pool/main/libv/libva/libva1_1.7.1-1_amd64.deb
 dpkg -i libva1_1.7.1-1_amd64.deb

 wget http://ftp.cz.debian.org/debian/pool/main/i/intel-vaapi-driver/i965
 -va-driver_1.7.1-1_amd64.deb
 dpkg -i i965-va-driver_1.7.1-1_amd64.deb
 }}}

 I left vainfo the existing version, it wanted to pull in some extra
 dependencies...
 {{{
 vainfo
 error: XDG_RUNTIME_DIR not set in the environment.
 error: can't connect to X server!
 libva info: VA-API version 0.39.2
 libva info: va_getDriverName() returns 0
 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_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.4.1)
 vainfo: Driver version: Intel i965 driver for Intel(R) Bay Trail - 1.7.1
 vainfo: Supported profile and entrypoints
       VAProfileMPEG2Simple            : VAEntrypointVLD
       VAProfileMPEG2Simple            : VAEntrypointEncSlice
       VAProfileMPEG2Main              : VAEntrypointVLD
       VAProfileMPEG2Main              : VAEntrypointEncSlice
       VAProfileH264ConstrainedBaseline: VAEntrypointVLD
       VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
       VAProfileH264Main               : VAEntrypointVLD
       VAProfileH264Main               : VAEntrypointEncSlice
       VAProfileH264High               : VAEntrypointVLD
       VAProfileH264High               : VAEntrypointEncSlice
       VAProfileH264StereoHigh         : VAEntrypointVLD
       VAProfileVC1Simple              : VAEntrypointVLD
       VAProfileVC1Main                : VAEntrypointVLD
       VAProfileVC1Advanced            : VAEntrypointVLD
       VAProfileNone                   : VAEntrypointVideoProc
       VAProfileJPEGBaseline           : VAEntrypointVLD
 }}}

 So this confirms the bug was in the VA support packages, and not ffmpeg.

 Thank you and the ffmpeg team for all your support!

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5685#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker