[FFmpeg-devel] lavu/opencl: questions about opencl create binary file

Wei Gao highgod0401 at gmail.com
Tue Jul 2 10:46:48 CEST 2013


Hi,

Thanks for reply.

some explanations is as follows:

2013/7/2 Stefano Sabatini <stefasab at gmail.com>

> On date Tuesday 2013-07-02 14:29:09 +0800, Wei Gao encoded:
> > Hi,
> >
> > Because we have add opencl options, so can we use it to control the
> > creation of binary which can avoid opencl be compiled every time?
> >
>
> > My idea is that add the use build options to control the binary file
> > creation and load path, a flag to control whether to rewrite the binary
> file
>
> I'm not sure I understand, do you want to use the OpenCL build option
> or do you want to introduce another option?


I mean that, we can add a path to enable user spefic where the binary can
write. it can solve the problem of user authority.

>

If the already existing
> options can be used, we should prefer that rather than makeing the
> interface more complex.
>

may add a option to enable user to create the binary file and another
option to tell ffmpeg whether to rewite the binary file.

>
> >
> > is it OK
> >
>
> > btw, another question.Can we modified the deshake and unsharp filter to
> > detect the opencl first, if opencl can run, then use opencl as default?
>
> Add a third option opencl=auto, which will automatically enable the
> opencl path if opencl is available. This allows the user to disable
> opencl if she doesn't want it for whatever reason (e.g. in case it
> crashes).
>
> Then I'm not against to change the default value to auto.
>
thanks

> --
> FFmpeg = Fanciful & Funny Maxi Philosofic Enlightening God
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>


More information about the ffmpeg-devel mailing list