Re: [Openfx-developer] Nuke's supported contexts

[Mike W. <sm...@ci...>]

Thanks a lot Fabien :)

----- Original Message -----
From: fab...@fr...
Date: Sunday, February 13, 2011 6:30 pm
Subject: Re: [Openfx-developer] Nuke's supported contexts
To: Developer oriented mailing list <ope...@li...>


> > (1) Via a brief 1.2.1 api test, I notice that Nuke6.2v2 supports 
> only two contexts so far,
> > they are General and Filter OFX contexts, is this correct? 
> Yes
> 
> >(2) When I have my plug-in described as "General" with only output 
> clip defined with NO other additional input clips
> > (via ClipDefine call), Nuke6.2v2 is not happy and it crashes right 
> away. However, if I define one additional
> > arbitrary clip, everything is just fine. Is it true that Nuke 
> expects a "general" plugin to have at least one extra
> > Clip defined in addition to the "Output" clip ? 
> I already reported this bug introduced in nuke 6.2. It will be fixed 
> in a future release.
> 
> fabien
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio 
> XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer