Hi!

Where I can find patch?

17.04.2015, 11:47, "Xiang, Haihao" <haihao.xi...@intel.com>:
> I sent a patch to fix this issue. It would be better to use avcenc if
> you want to try h.264/avc encoding with libva-intel-driver.
>
> Thanks
> Haihao
>>  Hello!
>>
>>  I have such problem:
>>
>>  $ ./h264encode --rcmode CBR
>>
>>  INPUT:Try to encode H264...
>>  INPUT: RateControl  : CBR
>>  INPUT: Resolution   : 176x144, 60 frames
>>  INPUT: FrameRate    : 30
>>  INPUT: Bitrate      : 182476
>>  INPUT: Slieces      : 1
>>  INPUT: IntraPeriod  : 30
>>  INPUT: IDRPeriod    : 60
>>  INPUT: IpPeriod     : 1
>>  INPUT: Initial QP   : 26
>>  INPUT: Min QP       : 0
>>  INPUT: Source YUV   : AUTO generated
>>  INPUT: Coded Clip   : /tmp/test.264
>>  INPUT: Rec   Clip   : Not save reconstructed frame
>>
>>  error: can't connect to X server!
>>  libva info: VA-API version 0.37.0
>>  libva info: va_getDriverName() returns 0
>>  libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so
>>  libva info: Found init function __vaDriverInit_0_37
>>  libva info: va_openDriver() returns 0
>>  Use profile VAProfileH264High
>>  Support rate control mode (0x12):CBR CQP
>>  Support VAConfigAttribEncPackedHeaders
>>  Support packed sequence headers
>>  Support packed picture headers
>>  Support packed slice headers
>>  Support packed misc headers
>>  Support 1 RefPicList0 and 1 RefPicList1
>>  Loading data into surface 15.....Complete surface loading
>>  Segmentation fault
>>
>>  My system is Debian testing distrib.
>>  Kernel 3.14.4 with beignet security patch
>>  intel driver is 1.5.1
>>
>>  Is this common problem?
>>
>>  --
>>  Nikita Orlov
>>  Skype: nik_stet
>>  QQ: 2717846083
>>  _______________________________________________
>>  Libva mailing list
>>  Libva@lists.freedesktop.org
>>  http://lists.freedesktop.org/mailman/listinfo/libva

-- 
Nikita Orlov
Skype: nik_stet
QQ: 2717846083
_______________________________________________
Libva mailing list
Libva@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libva

Reply via email to