When you place the patch on the Editor, the "Devices" input port is an
unlabeled index port. The second you run the Viewer, even without a consumer
patch attached, it populated with labelled names for your devices. If you
get a patch from someone, it will say the name of their devices, and then
reconfigure when you run it on your system.

Then, one can check if it's a GPU or CPU device by looking at the output of
Device Type.

I don't know if Device Count produces 0 if it's only CPU supported, but you
can certainly tell exactly what's going on with Device Type.

-GT

On Sat, Dec 11, 2010 at 10:06 AM, Alex Drinkwater <[email protected]>wrote:

> Can anyone tell me how to use the OpenCL Context Info patch to tell if a
> given machine is able to run OpenCL on the currently-active GPU? I'm
> assuming it's going to produce a '0' at the 'Device Count' output, but I
> can't test it right now.
>
> Cheers,
>
> alx
>
>
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
>
> http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
>
> This email sent to [email protected]
>



-- 
George Toledo
[email protected]
www.georgetoledo.com

The information contained in this E-mail and any attachments may be
confidential.
If you have received this E-mail in error, please notify us immediately by
telephone or return E-mail.
You should not use or disclose the contents of this E-mail or any of the
attachments for any purpose or to any persons.

Attachment: OpenCL Context Info CPU or GPU and Name.qtz
Description: Binary data

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to