As I see the Metal Texture API has option to create and get an IOSurfaceRef 
to/from a Metal texture, so probably that could be a workaround, but had no 
chance to try that out myself.

Mark: there are some really valuable info in that topic, thanks for letting us 
know!

> On 17 Jun 2015, at 13:23, George Toledo <gtole...@gmail.com> wrote:
> 
> Look at the Metal API...if it has compatibility to render to an OpenGL 
> context with a version number as old as what QC uses, there is some chance.
> 
> FWIW, I wish Apple would spend more time making sure all of their OpenGL 
> drivers are up to par, supporting as recent a version as they can. Aside from 
> QC issues. Stop reinventing the wheel or spending time on stop gap measures. 
> I know that efforts like this give a little hype and publicity but...I feel 
> like I've seen this dog and pony show before with OpenCL.
> 
> Best,
> gt
> 
> On Jun 17, 2015, at 1:20 AM, Mark Coniglio <m...@troikatronix.com 
> <mailto:m...@troikatronix.com>> wrote:
> 
>> Dear All,
>> 
>> A topic on the forum for my software Isadora (http://troikatronix.com/ 
>> <http://troikatronix.com/>) -- which hosts QC plugins -- might prove 
>> informative. The discussion is not focused on QC, but we discussed the 
>> general implications of the Metal announcement in some depth.
>> 
>> http://troikatronix.com/troikatronixforum/discussion/2049/metal-for- 
>> <http://troikatronix.com/troikatronixforum/discussion/2049/metal-for->mac
>> 
>> Specifically regarding QC, I spoke to someone who is far more of an expert 
>> at advanced GPU programming than me, and his feeling was that Quartz 
>> Composer and Metal were not going to play happily together.
>> 
>> I suspect the assumption made in a previous post in this thread -- that 
>> Quartz Composer would need to be written from the ground up before it would 
>> work properly with Metal -- is probably on target.
>> 
>> Best Wishes,
>> Mark
>> 
>> At 7:38 PM +0000 6/16/15, Brown George wrote:
>>> I was wondering about this as well.  There could be ways of taking 
>>> advantage of it in a custom plugin.  eg. write a plugin to perform it's 
>>> thing in Metal or other technology (Scenekit?), and output the result back 
>>> into the QC context, but I wonder if it's really worth the hassle.  If you 
>>> were really determined to do some powerful stuff for another QC compatible 
>>> application it might be worth it.  I've only ever briefly looked at writing 
>>> a QC Plugin, so not sure if there would be restrictions that would make it 
>>> impractical.  I was thinking of basically a QC Plugin that just wraps a 
>>> self contained visual or effect, while still allowing access to QC 
>>> inputs/outputs from whatever application you're playing QC from.
>>> 
>>> George
>>> On Tuesday, 16 June 2015, 21:06, 
>>> "quartzcomposer-dev-requ...@lists.apple.com 
>>> <mailto:quartzcomposer-dev-requ...@lists.apple.com>" 
>>> <quartzcomposer-dev-requ...@lists.apple.com 
>>> <mailto:quartzcomposer-dev-requ...@lists.apple.com>> wrote:
>>> 
>>> 
>>> Message: 1
>>> Date: Tue, 16 Jun 2015 22:27:55 +0700
>>> From: Roger Bolton <ro...@eskatonia.net <mailto:ro...@eskatonia.net>>
>>> To: Quartzcomposer-dev@lists.apple.com 
>>> <mailto:Quartzcomposer-dev@lists.apple.com>
>>> Subject: QC and Metal?
>>> Message-ID: <2efb44f4-a426-4459-bb21-a2b367b96...@eskatonia.net 
>>> <mailto:2efb44f4-a426-4459-bb21-a2b367b96...@eskatonia.net>>
>>> Content-Type: text/plain; charset=utf-8
>>> 
>>> Does anyone know if it will possible for us to take advantage of speedups 
>>> from Metal in QC?  Even if Apple does not specifically address that?  I 
>>> mean could we write individual new coreimage nodes and filters using the QC 
>>> API and Metal in order to speed up certain portions of the QC rendering 
>>> chain?
>>> 
>>> Or will Metal improvements happen automatically with new drivers from 
>>> Nvidia and AMD and we won't need to recode?
>>> 
>>> thanks
>>> 
>>> Roger
>>> CoreMelt
>>> 
>>> 
>>> ------------------------------
>>> 
>>> Message: 2
>>> Date: Tue, 16 Jun 2015 16:31:01 +0100
>>> From: Alex Drinkwater <the_vo...@yahoo.co.uk <mailto:the_vo...@yahoo.co.uk>>
>>> To: Roger Bolton <ro...@eskatonia.net <mailto:ro...@eskatonia.net>>
>>> Cc: "Quartzcomposer-dev@lists.apple.com 
>>> <mailto:Quartzcomposer-dev@lists.apple.com>"
>>>     <Quartzcomposer-dev@lists.apple.com 
>>> <mailto:Quartzcomposer-dev@lists.apple.com>>
>>> Subject: Re: QC and Metal?
>>> Message-ID: <e60183fc-c747-4531-baad-ed0831e9a...@yahoo.co.uk 
>>> <mailto:e60183fc-c747-4531-baad-ed0831e9a...@yahoo.co.uk>>
>>> Content-Type: text/plain; charset=utf-8
>>> 
>>> I have a feeling Metal will completely break QC, unless it's rewritten from 
>>> the ground up. Maybe I'm wrong though. Anyone at Apple care to comment?
>>> 
>>> Alex
>>> 
>>> > On 16 Jun 2015, at 16:27, Roger Bolton <ro...@eskatonia.net 
>>> > <mailto:ro...@eskatonia.net>> wrote:
>>> >
>>> > Does anyone know if it will possible for us to take advantage of speedups 
>>> > from Metal in QC?  Even if Apple does not specifically address that?  I 
>>> > mean could we write individual new coreimage nodes and filters using the 
>>> > QC API and Metal in order to speed up certain portions of the QC 
>>> > rendering chain?
>>> >
>>> > Or will Metal improvements happen automatically with new drivers from 
>>> > Nvidia and AMD and we won't need to recode?
>>> >
>>> > thanks
>>> >
>>> > Roger
>>> > CoreMelt
>>> > _______________________________________________
>>> > Do not post admin requests to the list. They will be ignored.
>>> > Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com 
>>> > <mailto:Quartzcomposer-dev@lists.apple.com>)
>>> > Help/Unsubscribe/Update your Subscription:
>>> > https://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%40yahoo.co.uk
>>> >  
>>> > <https://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%40yahoo.co.uk>
>>> >
>>> > This email sent to the_vo...@yahoo.co.uk <mailto:the_vo...@yahoo.co.uk>
>>> 
>>> 
>>> 
>>> ------------------------------
>>> 
>>> Message: 3
>>> Date: Tue, 16 Jun 2015 08:33:52 -0700 (PDT)
>>> From: Alastair Leith <qc.student...@gmail.com 
>>> <mailto:qc.student...@gmail.com>>
>>> To: Roger Bolton <ro...@eskatonia.net <mailto:ro...@eskatonia.net>>,    
>>> quartzcomposer-dev list list
>>>     <quartzcomposer-dev@lists.apple.com 
>>> <mailto:quartzcomposer-dev@lists.apple.com>>
>>> Subject: Re: QC and Metal?
>>> Message-ID: <1434468831949.2e5da5ae@Nodemailer 
>>> <mailto:1434468831949.2e5da5ae@Nodemailer>>
>>> Content-Type: text/plain; charset="utf-8"
>>> 
>>> good question! was assuming it wouldn't touch QC as my guess is it is an 
>>> alternative to OpenGL and bypasses it - so won't touch QC either way.
>>> 
>>> On Tue, Jun 16, 2015 at 11:29 PM, Roger Bolton <ro...@eskatonia.net 
>>> <mailto:ro...@eskatonia.net>>
>>> wrote:
>>> 
>>> > Does anyone know if it will possible for us to take advantage of speedups 
>>> > from Metal in QC?  Even if Apple does not specifically address that?  I 
>>> > mean could we write individual new coreimage nodes and filters using the 
>>> > QC API and Metal in order to speed up certain portions of the QC 
>>> > rendering chain?
>>> > Or will Metal improvements happen automatically with new drivers from 
>>> > Nvidia and AMD and we won't need to recode?
>>> > thanks
>>> > Roger
>>> > CoreMelt
>>> >  _______________________________________________
>>> > Do not post admin requests to the list. They will be ignored.
>>> > Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com 
>>> > <mailto:Quartzcomposer-dev@lists.apple.com>)
>>> > Help/Unsubscribe/Update your Subscription:
>>> > https://lists.apple.com/mailman/options/quartzcomposer-dev/qc.student.au%40gmail.com
>>> >  
>>> > <https://lists.apple.com/mailman/options/quartzcomposer-dev/qc.student.au%40gmail.com>
>>> > This email sent to qc.student...@gmail.com 
>>> > <mailto:qc.student...@gmail.com>
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: 
>>> <http://lists.apple.com/archives/quartzcomposer-dev/attachments/20150616/b3b7c6eb/attachment.html
>>>  
>>> <http://lists.apple.com/archives/quartzcomposer-dev/attachments/20150616/b3b7c6eb/attachment.html>>
>>> 
>>> ------------------------------
>>> 
>>> _______________________________________________
>>> Quartzcomposer-dev mailing list
>>> Quartzcomposer-dev@lists.apple.com 
>>> <mailto:Quartzcomposer-dev@lists.apple.com>
>>> https://lists.apple.com/mailman/listinfo/quartzcomposer-dev 
>>> <https://lists.apple.com/mailman/listinfo/quartzcomposer-dev>
>>> 
>>> 
>>> End of Quartzcomposer-dev Digest, Vol 119, Issue 1
>>> **************************************************
>>> 
>>>  _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com 
>>> <mailto:Quartzcomposer-dev@lists.apple.com>)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/mark%40tro 
>>> <https://lists.apple.com/mailman/options/quartzcomposer-dev/mark%40tro>ikatronix.com
>>>  <http://ikatronix.com/>
>>> 
>>> This email sent to m...@troikatronix.com 
>>> <mailto:m...@troikatronix.com></x-charset>t
>> 
>> 
>> -- 
>> =======================================================================
>>  Mark Coniglio             |  m...@troikatronix.com 
>> <mailto:m...@troikatronix.com>
>>  TroikaTronix              |  http://www.troikatronix.com/ 
>> <http://www.troikatronix.com/>
>>  Isadora®                  |  http://www.troikatronix.com/isadora.html 
>> <http://www.troikatronix.com/isadora.html>
>>                            |  (interactive media processing environment)
>> =======================================================================
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com 
>> <mailto:Quartzcomposer-dev@lists.apple.com>)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
>>  
>> <https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com>
>> 
>> This email sent to gtole...@gmail.com 
>> <mailto:gtole...@gmail.com>_______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list      (Quartzcomposer-dev@lists.apple.com 
> <mailto:Quartzcomposer-dev@lists.apple.com>)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/quartzcomposer-dev/info%40cogevj.hu 
> <https://lists.apple.com/mailman/options/quartzcomposer-dev/info%40cogevj.hu>
> 
> This email sent to i...@cogevj.hu <mailto:i...@cogevj.hu>

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

This email sent to arch...@mail-archive.com

Reply via email to