Hello
Is there a way to make 2.9 git master to use more than one core?
Changing in GIMP settings doesn't make effect.
With respect,
Alexander Rabtchevich
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailm
You could try the OpenCL support in GEGL, it should use all of your cores.
ps: there are bugs still, but I'm solving them.
Victor
On Mon, Jan 28, 2013 at 4:27 PM, Alexander Rabtchevich
wrote:
> Hello
>
> Is there a way to make 2.9 git master to use more than one core? Changing in
> GIMP setting
I have embedded AMD 4290 graphics, which does not support OpenCL. So
trying ENABLE_OPENCL=yes doesn't make any difference. And the processor
is 6-cores Phenom II 1075T.
With respect,
Alexander Rabtchevich
Victor Oliveira wrote:
You could try the OpenCL support in GEGL, it should use all of
You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL
looks for libOpenCL.so in /usr/lib.
You should use GEGL_ENABLE_OPENCL=yes
On Tue, Jan 29, 2013 at 1:24 AM, Alexander Rabtchevich
wrote:
> I have embedded AMD 4290 graphics, which does not support OpenCL. So trying
> ENABLE_OPEN
* Victor Oliveira [01-29-13 07:39]:
> You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL
> looks for libOpenCL.so in /usr/lib.
>
> You should use GEGL_ENABLE_OPENCL=yes
export as environment varible or ??
tks,
--
(paka)Patrick Shanahan Plainfield, Indiana, USA HOG
yes,
export GEGL_ENABLE_OPENCL=yes
also, when you build GEGL, put the option --enable-config.
with that you can set:
export GEGL_DEBUG=opencl
so you can see if OpenCL is really being used or if there is some bug.
Victor
On Tue, Jan 29, 2013 at 11:31 AM, Paka wrote:
> * Victor Oliveira [01-2
* Victor Oliveira [01-29-13 12:34]:
> yes,
>
> export GEGL_ENABLE_OPENCL=yes
>
> also, when you build GEGL, put the option --enable-config.
> with that you can set:
>
> export GEGL_DEBUG=opencl
>
> so you can see if OpenCL is really being used or if there is some bug.
tks, I added to ~/.bashr
no, besides building gegl by yourself, no.
GIMP doesn't require OpenCL because the libOpenCL.so is loaded at
runtime (like, dlopen) in the case it is present at the machine.
Victor
On Tue, Jan 29, 2013 at 3:57 PM, Paka wrote:
> * Victor Oliveira [01-29-13 12:34]:
>> yes,
>>
>> export GEGL_ENABL
* Victor Oliveira [01-29-13 14:35]:
> no, besides building gegl by yourself, no.
> GIMP doesn't require OpenCL because the libOpenCL.so is loaded at
> runtime (like, dlopen) in the case it is present at the machine.
Then I guess the gimp package on my system does not utilize opencl. I
opened gim
On Tue, 2013-01-29 at 17:10 -0500, Paka wrote:
> psaux does not reveal any opencl process
> or library being loaded.
You'd more likely need to use strace to see if the library was opened; I
am not sure that anything would show up in ps in this case.
Liam
--
Liam Quin - XML Activity Lead, W3
* Liam R E Quin [01-29-13 18:12]:
> On Tue, 2013-01-29 at 17:10 -0500, Paka wrote:
> > psaux does not reveal any opencl process
> > or library being loaded.
>
> You'd more likely need to use strace to see if the library was opened; I
> am not sure that anything would show up in ps in this case
It should work on GIMP 2.8.2. Do you have libOpenCL.so?
Also, I'm not sure if it spawn a separated process.
If you continue to have problems, I suggest you to build GEGL.
Victor
On Tue, Jan 29, 2013 at 8:10 PM, Paka wrote:
> * Victor Oliveira [01-29-13 14:35]:
>> no, besides building gegl by y
* Victor Oliveira [01-29-13 18:49]:
> It should work on GIMP 2.8.2. Do you have libOpenCL.so?
> Also, I'm not sure if it spawn a separated process.
/usr/lib/libnvidia-opencl.so.1
/usr/lib/libnvidia-opencl.so.310.32
/usr/lib64/libnvidia-opencl.so.1
/usr/lib64/libnvidia-opencl.so.310.32
provided b
that's strange, because it looks for the exact name "libOpenCL.so",
don't you have it? It should be installed with the driver.
But probably you have it considering that you can use darktable
without problems.
I have also a nvidia GPU with GIMP-2.8 (from Ubuntu 12.10) and
noise-reduction works fine
Victor,
When I look at the code, I don't understand how you are handling the Mac
OS, when you don't typically see so libraries, by dylibs. Can you elaborate?
Also, when I try to add --enable-config to configure, I get
configure: WARNING: unrecognized options: --enable-config
Thanks,
Partha
O
Hello Partha.
I'm sorry, I mean "--enable-debug" instead of "--enable-config".
That's a good observation. In Windows I look for "OpenCL.dll" and in
Linux I look for "libOpenCL.so", but I'm not sure how I should handle
it in MacOS. I was assuming it was the same as the Linux way. Do you
know how I
Hi Victor,
I think on Windows for 32-bit you are OK with call OpenCL.dll, but I think
you need to call OpenCL64.dll for 64-bit?
For Mac, according to
http://developer.apple.com/library/mac/documentation/Performance/Conceptual/OpenCL_MacProgGuide/OpenCL_MacProgGuide.pdf
the sample code on page 17
On Fri, Feb 1, 2013 at 11:10 PM, Partha Bagchi wrote:
> Hi Victor,
>
> I think on Windows for 32-bit you are OK with call OpenCL.dll, but I think
> you need to call OpenCL64.dll for 64-bit?
>
I have a 64-bit Windows system and it comes with OpenCL.dll.
> For Mac, according to
> http://developer.
On Fri, Feb 1, 2013 at 8:46 PM, Victor Oliveira wrote:
> On Fri, Feb 1, 2013 at 11:10 PM, Partha Bagchi wrote:
> > Hi Victor,
> >
> > I think on Windows for 32-bit you are OK with call OpenCL.dll, but I
> think
> > you need to call OpenCL64.dll for 64-bit?
> >
>
> I have a 64-bit Windows system a
19 matches
Mail list logo
