never mind. found something that works, only posted here for closure.
eg
.\ffmpeg.exe -hide_banner -v verbose -init_hw_device
opencl=ocl:1.0 -filter_hw_device ocl -i
".\test_01.mpg" -an -map_metadata -1 -sws_flags
lanczos+accurate_rnd+full_chroma_int+full_chroma_inp -filter_complex
"[0:v]yad
OK and thank you, these do work fine and produce handy results and the
documentation you linked works.
".\ffmpeg_3.latest_master.exe" -v verbose -init_hw_device list
".\ffmpeg_3.latest_master.exe" -v verbose -init_hw_device opencl
I'll head over to ffmpeg-user (and do some reading) to find out
On 26/11/17 16:14, hydra3...@gmail.com wrote:
> Most systems have a "clinfo" program which will list all the queryable
> properties of the available devices.
>
>> From docs:
>
> -init_hw_device type[=name][:device[,key=value...]]
> Initialise a new hardware device of type type called name, us
Most systems have a "clinfo" program which will list all the queryable
properties of the available devices.
From docs:
-init_hw_device type[=name][:device[,key=value...]]
Initialise a new hardware device of type type called name, using the
given device parameters. If no name is specified
On 26/11/17 13:07, hydra3...@gmail.com wrote:
> OK, the experimental -opencl_bench option has been removed by recent commits.
> Thank you for the updates to OpenCL.
>
> It cross-compiles OK, however I'm not sure about the replacement
> functionality. So, 2 things.
>
> 1. may I enquire how one a
-Original Message-
From: hydra3...@gmail.com
Sent: Sunday, November 26, 2017 11:37 PM
To: ffmpeg-devel@ffmpeg.org
Cc: hydra
Subject: Re: [FFmpeg-devel] [PATCH 00/15] OpenCL infrastructure, filters
OK, the experimental -opencl_bench option has been removed by recent
commits.
Thank
OK, the experimental -opencl_bench option has been removed by recent
commits.
Thank you for the updates to OpenCL.
It cross-compiles OK, however I'm not sure about the replacement
functionality. So, 2 things.
1. may I enquire how one ascertains the numbers to use like this ?
-opencl_option
2017-11-23 0:26 GMT+01:00 Mark Thompson :
> On 22/11/17 00:59, Carl Eugen Hoyos wrote:
>> 2017-11-22 1:30 GMT+01:00 Mark Thompson :
>>> On 14/11/17 19:47, Mark Thompson wrote:
Changes since the last time this was posted:
* Add unsharp filter (to replace existing unsharp).
* Remove ol
On 22/11/17 00:59, Carl Eugen Hoyos wrote:
> 2017-11-22 1:30 GMT+01:00 Mark Thompson :
>> On 14/11/17 19:47, Mark Thompson wrote:
>>> Changes since the last time this was posted:
>>> * Add unsharp filter (to replace existing unsharp).
>>> * Remove old experimental API.
>>> * Miscellaneous fixes.
>>
On 14 November 2017 at 19:47, Mark Thompson wrote:
> Changes since the last time this was posted:
> * Add unsharp filter (to replace existing unsharp).
> * Remove old experimental API.
> * Miscellaneous fixes.
>
> Now also tested with AMD OpenCL on Windows (DXVA2 mapping works nicely,
> D3D11 doe
2017-11-22 1:30 GMT+01:00 Mark Thompson :
> On 14/11/17 19:47, Mark Thompson wrote:
>> Changes since the last time this was posted:
>> * Add unsharp filter (to replace existing unsharp).
>> * Remove old experimental API.
>> * Miscellaneous fixes.
>>
>> Now also tested with AMD OpenCL on Windows (DX
On 14/11/17 19:47, Mark Thompson wrote:
> Changes since the last time this was posted:
> * Add unsharp filter (to replace existing unsharp).
> * Remove old experimental API.
> * Miscellaneous fixes.
>
> Now also tested with AMD OpenCL on Windows (DXVA2 mapping works nicely, D3D11
> does not becau
On 15/11/17 15:39, Carl Eugen Hoyos wrote:
> 2017-11-15 15:34 GMT+01:00 Mark Thompson :
>> On 14/11/17 22:30, Carl Eugen Hoyos wrote:
>>> 2017-11-14 20:47 GMT+01:00 Mark Thompson :
>>>
Silly example using everything (for i965 VAAPI + Beignet):
./ffmpeg_g -y -init_hw_device vaapi=va:/
2017-11-15 15:34 GMT+01:00 Mark Thompson :
> On 14/11/17 22:30, Carl Eugen Hoyos wrote:
>> 2017-11-14 20:47 GMT+01:00 Mark Thompson :
>>
>>> Silly example using everything (for i965 VAAPI + Beignet):
>>>
>>> ./ffmpeg_g -y -init_hw_device vaapi=va:/dev/dri/renderD128
>>> -init_hw_device opencl=ocl@v
On 14/11/17 22:30, Carl Eugen Hoyos wrote:
> 2017-11-14 20:47 GMT+01:00 Mark Thompson :
>
>> Silly example using everything (for i965 VAAPI + Beignet):
>>
>> ./ffmpeg_g -y -init_hw_device vaapi=va:/dev/dri/renderD128
>> -init_hw_device opencl=ocl@va -hwaccel vaapi
>> -hwaccel_device va -hwaccel_ou
2017-11-14 20:47 GMT+01:00 Mark Thompson :
> Silly example using everything (for i965 VAAPI + Beignet):
>
> ./ffmpeg_g -y -init_hw_device vaapi=va:/dev/dri/renderD128
> -init_hw_device opencl=ocl@va -hwaccel vaapi
> -hwaccel_device va -hwaccel_output_format vaapi -i in.mp4
> -f image2 -r 1 -i over
Changes since the last time this was posted:
* Add unsharp filter (to replace existing unsharp).
* Remove old experimental API.
* Miscellaneous fixes.
Now also tested with AMD OpenCL on Windows (DXVA2 mapping works nicely, D3D11
does not because it wants the Intel extension for NV12 support).
Th
17 matches
Mail list logo
