Mark Thompson wrote:
On 19/06/16 00:34, Andy Furniss wrote:
Mark Thompson wrote:
What h/w is yours?
R7 360 (Bonaire, a Sea Island), so yours is one generation newer. I
am therefore using radeonsi, though I believe the back-end parts
talking to UVD/VCE here are actually in common between
On 19/06/16 00:34, Andy Furniss wrote:
> Mark Thompson wrote:
>>
>> So, I also went and built mesa with the encode patches and had a go. With
>> the changes above, it does get to actually trying to encode, but that nuked
>> my GPU to the point of requiring reboot.
>
> Same here, I need both
Mark Thompson wrote:
On 18/06/16 16:37, Mark Thompson wrote:
On 17/06/16 23:33, Andy Furniss wrote:
AMD are working on vaapi encode for mesa, only a few patches about so far and
they got rejected - though not for functionality.
They do work with gstreamer, but trying above with ffmpeg fails
Mark Thompson wrote:
I tried avconv and it does care = bail, but I can use -profile 66 and then get
the same error as ffmpeg (though it converts to rgba rather than rgb0)
Default for H264 is High, so yeah you need -profile 66 to get it to work.
OK, does baseline support b frames? I see
On 18/06/16 16:37, Mark Thompson wrote:
> On 17/06/16 23:33, Andy Furniss wrote:
>>
>> AMD are working on vaapi encode for mesa, only a few patches about so far
>> and they got rejected - though not for functionality.
>>
>> They do work with gstreamer, but trying above with ffmpeg fails as below
On 17/06/16 23:33, Andy Furniss wrote:
>
> AMD are working on vaapi encode for mesa, only a few patches about so far and
> they got rejected - though not for functionality.
>
> They do work with gstreamer, but trying above with ffmpeg fails as below
> (render node or X) seems the surface is
Andy Furniss wrote:
libva info: va_openDriver() returns 0
[vaapi @ 0x190e300] Initialised VAAPI connection: version 0.38
[AVHWDeviceContext @ 0x3ca4c40] Format 0x3231564e -> unknown.
Hmm, so this bit is a bit strange saying unknown as searching tells me
that it's nv12.
On 14.05.2016 18:41, Mark Thompson wrote:
> On 13/05/16 20:43, Armin K. wrote:
>> I noticed that recently a VAAPI based H264 encoder was added to ffmpeg.
>> I built ffmpeg from git and now I have h264_vaapi listed in ffmpeg -encoders
>> output.
>>
>> However, when I try to use ffmpeg ... -vcodec
On 13/05/16 20:43, Armin K. wrote:
> I noticed that recently a VAAPI based H264 encoder was added to ffmpeg.
> I built ffmpeg from git and now I have h264_vaapi listed in ffmpeg -encoders
> output.
>
> However, when I try to use ffmpeg ... -vcodec h264_vaapi I get the following
> error:
>
>
Hi everyone,
I noticed that recently a VAAPI based H264 encoder was added to ffmpeg.
I built ffmpeg from git and now I have h264_vaapi listed in ffmpeg -encoders
output.
However, when I try to use ffmpeg ... -vcodec h264_vaapi I get the following
error:
Impossible to convert between the formats
10 matches
Mail list logo