Zhang, Boyuan wrote:
Hi Andy,
I just submitted another patch set.
1. Fixed previously reported regression when using ffmpeg to encode.
2. Fixed I420 "width=720,height=480" garbage output issue.
Please give a try from your side.
Hi,
The width 720 is OK now. Colors are still wrong. It seems f
Hi Andy,
I just submitted another patch set.
1. Fixed previously reported regression when using ffmpeg to encode.
2. Fixed I420 "width=720,height=480" garbage output issue.
Please give a try from your side.
Regards,
Boyuan
Hi Christian,
As stated above, this new patch set just submitted fixe
Zhang, Boyuan wrote:
Hi Andy,
Thanks very much for providing all the information.
The I420 U V swapping issue still can't be reproduced from my side, I
will try it again later. CQP issue is fixed in the new patch set I
just submitted. Please use " ... vaapiencodeh264 rate-control=cqp
init-qp=x
Andy Furniss wrote:
I tried again, and there's a possible further regression - though I have
no idea whether it's ffmpeg or the newer patches here.
Just thought I would mention it, as I haven't had time to look into it
further yet.
I can confirm this is a regression with the current patches,
Hi Andy,
Thanks very much for providing all the information.
The I420 U V swapping issue still can't be reproduced from my side, I will try
it again later. CQP issue is fixed in the new patch set I just submitted.
Please use " ... vaapiencodeh264 rate-control=cqp init-qp=x ..." command, where
Zhang, Boyuan wrote:
Hi Andy,
Thanks for the confirmation. It seems like all basic functionality is
working now.
I will look into the cqp issue. And for the speed related issue, we
understand the reason and have already planned to work on it after
this bring-up. However, it will be a separate
Hi Andy,
Thanks for the confirmation. It seems like all basic functionality is working
now.
I will look into the cqp issue. And for the speed related issue, we understand
the reason and have already planned to work on it after this bring-up. However,
it will be a separate patch in future, an
Andy Furniss wrote:
Zhang, Boyuan wrote:
Hi Andy,
I just submitted another patch set, most of the issues you reported
are solved, please see the information below:
- Giving different frame rate should result different output size.
The final result from my side is very close to the CBR I set.
Zhang, Boyuan wrote:
Hi Andy,
I just submitted another patch set, most of the issues you reported are solved,
please see the information below:
- Giving different frame rate should result different output size. The final
result from my side is very close to the CBR I set. Please give a try wi
Hi Andy,
I just submitted another patch set, most of the issues you reported are solved,
please see the information below:
- Giving different frame rate should result different output size. The final
result from my side is very close to the CBR I set. Please give a try with
different frame rat
Am 16.07.2016 um 00:41 schrieb Boyuan Zhang:
Add function to copy from yv12 image to nv12 surface for VAAPI putimage call.
We need this function in VaPutImage call where copying from yv12 image to nv12
surface for encoding. Existing function can't be used because it only work for
copying from
Add function to copy from yv12 image to nv12 surface for VAAPI putimage call.
We need this function in VaPutImage call where copying from yv12 image to nv12
surface for encoding. Existing function can't be used because it only work for
copying from yv12 surface to nv12 image in Vaapi.
Signed-of
Add function to copy from yv12 image to nv12 surface for VAAPI putimage call.
We need this function in VaPutImage call where copying from yv12 image to nv12
surface for encoding. Existing function can't be used because it only work for
copying from yv12 surface to nv12 image in Vaapi.
Signed-of
13 matches
Mail list logo
