openfx-developer — Developer oriented mailing list

[Openfx-developer] analysis pass ?

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

Hi there,

I come across this 'analysis pass' term in the 1.2 documentation but I am not sure what it is referring to exactly as there is not much mentioned in the whole doc.  Does it mean one may set this flag "kOfxImageEffectPropInAnalysis" during rendering and what exactly does it serve?  

Thanks.

Mike

Re: [Openfx-developer] OfxGetPlugin not called?

[Bruno N. <br...@th...>]

Happy it was resolved.

b

On 15 Mar 2011, at 20:38, Haarm-Pieter Duiker wrote:

> Hi Bruno,
> 
> Thanks for the help. I was able to work through this issue to some degree. It's not ideal and other hosts don't take the same approach of loading the same .ofx library multiple times, but the affect now seems to be harmless.
> 
> Regards,
> HP Duiker
> Duiker Research
> 
> On Thu, Mar 10, 2011 at 2:46 AM, Bruno Nicoletti <br...@th...> wrote:
> Hi Haarm-Pieter,
> 
> for host specific issues you should contact the host developers directly. For Nuke, try nuk...@su...
> 
> To avoid continually reloading and re-describing all plugins, Nuke will cache away the information about an OFX plugin when it first encounters it, this is in the NUKE_TMP_DIR/ofxplugincache directory. On Unix-alikes this is /var/tmp/USERID/ofxplugincache
> 
> So what is probably happening is that Nuke has done the whole load/describe rigmorale the first time round and cached the plugin away. Next time round, as the plugin on disk has not changed, it doesn't load it at all, but it can make menus from the cached descriptions, which means Nuke starts up much faster. So when you create one of your plugins in Nuke, it only then loads the dynamic library containing it, and as it knows which index in the binary that plugin belongs to it is probably skipping the OfxGetNumberOfPlugins call.
> 
> It still has to call OfxGetPlugin, as otherwise it can't get the needed function pointers for that plugin, also you will be guaranteed that the "On Load" action will be called before any other action is.
> 
> b
> 
> 
> On 28 Feb 2011, at 06:40, Haarm-Pieter Duiker wrote:
> 
> > Hi,
> >
> > I'm running into an issue where OfxGetNumberOfPlugins isn't being called by Nuke. It's a little bit of an issue because that's where I'd like to insert some licensing code... Nuke appears not to call OfxGetNumberOfPlugins when a file is reopened very quickly after a recent exit or crash (!). Is this expected behavior for an OpenFX host? Can plugin writers plan for any specific ordering of calls to the plugin's public functions? Is there a suggested location to insert licensing calls?
> >
> > In Nuke, the ordering is, sometimes, OfxGetNumberOfPlugins followed by successive calls to OfxGetPlugin. In other cases, OfxGetPlugin is called directly, as if the result of OfxGetNumberOfPlugins was cached between Nuke launches. Either way, for each of call to OfxGetPlugin, Nuke seems to reload the dynamic library entirely as evidenced by repeated instantiations of static variables and calls to library constructors and destructors.
> >
> > I'm testing specifically on OSX with Nuke 5.01v1, 6.1v3 and 6.2v2 for i386 and x86_64.
> >
> > Thanks in advance for any help,
> > HP Duiker
> > Duiker Research
> > ------------------------------------------------------------------------------
> > Free Software Download: Index, Search & Analyze Logs and other IT data in
> > Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> > generated by your applications, servers and devices whether physical, virtual
> > or in the cloud. Deliver compliance at lower cost and gain new business
> > insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________
> > Openfx-developer mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openfx-developer
> 
> --
> Bruno Nicoletti,
> Chief Technology Officer
> The Foundry
> 6th Floor, The Communications Building,
> 48, Leicester Square,
> London, WC2H 7LT, UK
> Skype: brunonicoletti
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: br...@th...
> 
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
> 
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d_______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer

--
Bruno Nicoletti, 
Chief Technology Officer
The Foundry
6th Floor, The Communications Building,
48, Leicester Square,
London, WC2H 7LT, UK
Skype: brunonicoletti
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
Web: www.thefoundry.co.uk
Email: br...@th...  

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

Re: [Openfx-developer] OfxGetPlugin not called?

[Haarm-Pieter D. <li...@du...>]

Hi Bruno,

Thanks for the help. I was able to work through this issue to some degree.
It's not ideal and other hosts don't take the same approach of loading the
same .ofx library multiple times, but the affect now seems to be harmless.

Regards,
HP Duiker
Duiker Research

On Thu, Mar 10, 2011 at 2:46 AM, Bruno Nicoletti <br...@th...>wrote:

> Hi Haarm-Pieter,
>
> for host specific issues you should contact the host developers directly.
> For Nuke, try nuk...@su...
>
> To avoid continually reloading and re-describing all plugins, Nuke will
> cache away the information about an OFX plugin when it first encounters it,
> this is in the NUKE_TMP_DIR/ofxplugincache directory. On Unix-alikes this is
> /var/tmp/USERID/ofxplugincache
>
> So what is probably happening is that Nuke has done the whole load/describe
> rigmorale the first time round and cached the plugin away. Next time round,
> as the plugin on disk has not changed, it doesn't load it at all, but it can
> make menus from the cached descriptions, which means Nuke starts up much
> faster. So when you create one of your plugins in Nuke, it only then loads
> the dynamic library containing it, and as it knows which index in the binary
> that plugin belongs to it is probably skipping the OfxGetNumberOfPlugins
> call.
>
> It still has to call OfxGetPlugin, as otherwise it can't get the needed
> function pointers for that plugin, also you will be guaranteed that the "On
> Load" action will be called before any other action is.
>
> b
>
>
> On 28 Feb 2011, at 06:40, Haarm-Pieter Duiker wrote:
>
> > Hi,
> >
> > I'm running into an issue where OfxGetNumberOfPlugins isn't being called
> by Nuke. It's a little bit of an issue because that's where I'd like to
> insert some licensing code... Nuke appears not to call OfxGetNumberOfPlugins
> when a file is reopened very quickly after a recent exit or crash (!). Is
> this expected behavior for an OpenFX host? Can plugin writers plan for any
> specific ordering of calls to the plugin's public functions? Is there a
> suggested location to insert licensing calls?
> >
> > In Nuke, the ordering is, sometimes, OfxGetNumberOfPlugins followed by
> successive calls to OfxGetPlugin. In other cases, OfxGetPlugin is called
> directly, as if the result of OfxGetNumberOfPlugins was cached between Nuke
> launches. Either way, for each of call to OfxGetPlugin, Nuke seems to reload
> the dynamic library entirely as evidenced by repeated instantiations of
> static variables and calls to library constructors and destructors.
> >
> > I'm testing specifically on OSX with Nuke 5.01v1, 6.1v3 and 6.2v2 for
> i386 and x86_64.
> >
> > Thanks in advance for any help,
> > HP Duiker
> > Duiker Research
> >
> ------------------------------------------------------------------------------
> > Free Software Download: Index, Search & Analyze Logs and other IT data in
> > Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> > generated by your applications, servers and devices whether physical,
> virtual
> > or in the cloud. Deliver compliance at lower cost and gain new business
> > insights. http://p.sf.net/sfu/splunk-dev2dev_______________________________________________
> > Openfx-developer mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openfx-developer
>
> --
> Bruno Nicoletti,
> Chief Technology Officer
> The Foundry
> 6th Floor, The Communications Building,
> 48, Leicester Square,
> London, WC2H 7LT, UK
> Skype: brunonicoletti
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: br...@th...
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>

Re: [Openfx-developer] OfxGetPlugin not called?

[Bruno N. <br...@th...>]

Hi Haarm-Pieter,

for host specific issues you should contact the host developers directly. For Nuke, try nuk...@su...

To avoid continually reloading and re-describing all plugins, Nuke will cache away the information about an OFX plugin when it first encounters it, this is in the NUKE_TMP_DIR/ofxplugincache directory. On Unix-alikes this is /var/tmp/USERID/ofxplugincache

So what is probably happening is that Nuke has done the whole load/describe rigmorale the first time round and cached the plugin away. Next time round, as the plugin on disk has not changed, it doesn't load it at all, but it can make menus from the cached descriptions, which means Nuke starts up much faster. So when you create one of your plugins in Nuke, it only then loads the dynamic library containing it, and as it knows which index in the binary that plugin belongs to it is probably skipping the OfxGetNumberOfPlugins call.

It still has to call OfxGetPlugin, as otherwise it can't get the needed function pointers for that plugin, also you will be guaranteed that the "On Load" action will be called before any other action is.

b


On 28 Feb 2011, at 06:40, Haarm-Pieter Duiker wrote:

> Hi,
> 
> I'm running into an issue where OfxGetNumberOfPlugins isn't being called by Nuke. It's a little bit of an issue because that's where I'd like to insert some licensing code... Nuke appears not to call OfxGetNumberOfPlugins when a file is reopened very quickly after a recent exit or crash (!). Is this expected behavior for an OpenFX host? Can plugin writers plan for any specific ordering of calls to the plugin's public functions? Is there a suggested location to insert licensing calls?
> 
> In Nuke, the ordering is, sometimes, OfxGetNumberOfPlugins followed by successive calls to OfxGetPlugin. In other cases, OfxGetPlugin is called directly, as if the result of OfxGetNumberOfPlugins was cached between Nuke launches. Either way, for each of call to OfxGetPlugin, Nuke seems to reload the dynamic library entirely as evidenced by repeated instantiations of static variables and calls to library constructors and destructors.
> 
> I'm testing specifically on OSX with Nuke 5.01v1, 6.1v3 and 6.2v2 for i386 and x86_64.
> 
> Thanks in advance for any help,
> HP Duiker
> Duiker Research
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer

--
Bruno Nicoletti, 
Chief Technology Officer
The Foundry
6th Floor, The Communications Building,
48, Leicester Square,
London, WC2H 7LT, UK
Skype: brunonicoletti
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
Web: www.thefoundry.co.uk
Email: br...@th...  

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

Re: [Openfx-developer] String Parameter (kOfxParamStringIsLabel), plug-in editable?

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

I see.  thx !

----- Original Message -----
From: Bruno Nicoletti <br...@th...>
Date: Thursday, March 10, 2011 6:27 pm
Subject: Re: [Openfx-developer] String Parameter (kOfxParamStringIsLabel), plug-in editable?
To: Developer oriented mailing list <ope...@li...>


> Hi Mike,
> 
> I'm guessing that the feature hasn't been implemented yet. As this is 
> host specific you should contact the host developer via the Nuke 
> plugin developers list....
> 
>    nuk...@su...
> 
> b
> 
> On 7 Mar 2011, at 17:01, Mike Wong wrote:
> 
> > 
> > Hi everyone,
> > 
> > I have a plug-in with a string parameter defined as 
> "kOfxParamStringIsLabel" for displaying additional information of 
> another parameter to user.  I am trying to update its content during a 
> "instanceChanged" callback but it doesn't update at all (the 
> paramSetValue call returns kOfxStatOK though).  From the 1.2 
> documentation, it says a "Label" type string is not user-editable but 
> it doesn't mention whether it's plug-in editable.  any idea?
> > 
> > I am using "kOfxParamStringIsMultiLine" type (Enabled=0) as a 
> workaround instead at the moment.
> > 
> > I am testing on Nuke 6.2v2.
> > 
> > Any idea ?
> > 
> > Thanks.
> > 
> > Mike
> > 
> > ------------------------------------------------------------------------------
> > What You Don't Know About Data Connectivity CAN Hurt You
> > This paper provides an overview of data connectivity, details
> > its effect on application quality, and explores various alternative
> > solutions. http://p.sf.net/sfu/progress-d2d
> > _______________________________________________
> > Openfx-developer mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openfx-developer
> 
> --
> Bruno Nicoletti, 
> Chief Technology Officer
> The Foundry
> 6th Floor, The Communications Building,
> 48, Leicester Square,
> London, WC2H 7LT, UK
> Skype: brunonicoletti
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
> Web: www.thefoundry.co.uk
> Email: br...@th...  
> 
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
> 
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer

Re: [Openfx-developer] String Parameter (kOfxParamStringIsLabel), plug-in editable?

[Bruno N. <br...@th...>]

Hi Mike,

I'm guessing that the feature hasn't been implemented yet. As this is host specific you should contact the host developer via the Nuke plugin developers list....

   nuk...@su...

b

On 7 Mar 2011, at 17:01, Mike Wong wrote:

> 
> Hi everyone,
> 
> I have a plug-in with a string parameter defined as "kOfxParamStringIsLabel" for displaying additional information of another parameter to user.  I am trying to update its content during a "instanceChanged" callback but it doesn't update at all (the paramSetValue call returns kOfxStatOK though).  From the 1.2 documentation, it says a "Label" type string is not user-editable but it doesn't mention whether it's plug-in editable.  any idea?
> 
> I am using "kOfxParamStringIsMultiLine" type (Enabled=0) as a workaround instead at the moment.
> 
> I am testing on Nuke 6.2v2.
> 
> Any idea ?
> 
> Thanks.
> 
> Mike
> 
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer

--
Bruno Nicoletti, 
Chief Technology Officer
The Foundry
6th Floor, The Communications Building,
48, Leicester Square,
London, WC2H 7LT, UK
Skype: brunonicoletti
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
Web: www.thefoundry.co.uk
Email: br...@th...  

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

[Openfx-developer] String Parameter (kOfxParamStringIsLabel), plug-in editable?

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

Hi everyone,

I have a plug-in with a string parameter defined as "kOfxParamStringIsLabel" for displaying additional information of another parameter to user.  I am trying to update its content during a "instanceChanged" callback but it doesn't update at all (the paramSetValue call returns kOfxStatOK though).  From the 1.2 documentation, it says a "Label" type string is not user-editable but it doesn't mention whether it's plug-in editable.  any idea?

I am using "kOfxParamStringIsMultiLine" type (Enabled=0) as a workaround instead at the moment.

I am testing on Nuke 6.2v2.

Any idea ?

Thanks.

Mike

Re: [Openfx-developer] c++ support layer, myth or reality

[Hybris <hy...@gm...>]

> You can find a bunch of examples inside TuttleOFX project:
> https://github.com/tuttleofx/TuttleOFX/tree/master/plugins/image
>
> The simplest example:
> https://github.com/tuttleofx/TuttleOFX/tree/master/plugins/image/process/color/Invert/src
>
> I hope this can help. This is one of the goals of this project.

due to my lack of knowledge of the ofx suite (noob) it's still not
clear to me what the project does but that's an interesting source of
examples
thanks

Re: [Openfx-developer] c++ support layer, myth or reality

[Bruno N. <br...@th...>]

Hi,

1.1 is forward compatible with 1.2. (and vice versa). Not all of 1.2 is covered in the C++ layer, but that should not in general be much of an issue.

b

On 4 Mar 2011, at 10:02, Hybris wrote:

> Oh, i skipped this one.
> I thought it was a legacy package related to ofx 1.1 and no more needed for 1.2.
> 
> And it contains updated examples...great.
> Thanks
> 
> 2011/3/3 Bruno Nicoletti <br...@th...>:
>> The source is available as a download from the source forge site....
>> 
>>    http://sourceforge.net/projects/openfx/files/openfxSupport/
>> 
>> it is a skin on top of the C API and makes it much easier to write a plugin.
>> 
>> There are examples in there.
>> 
>> 
>> b
>> 
>> On 3 Mar 2011, at 22:01, Hybris wrote:
>> 
>>> Just kidding :)
>>> 
>>> I am reading the documentation and the examples and every now and then
>>> i find references to "the c++ support layer", like "don't do like
>>> this, use the c++ support layer" or so
>>> 
>>> I did not understand what this layer is about and the documentation
>>> clearly states that it does not cover it but it seems, or better i
>>> suspect, it should ease development in some way
>>> 
>>> So what can  i do to at least have some hint about this layer and how to use it?
>>> A tiny example maybe?
>>> 
>>> Sorry but since i do not know what i am talking about, i don't know
>>> what to ask and i am also a little embarassed in doing such a vague
>>> question.
>>> 
>>> Thanks for any clarification on this matter
>>> Cheers
>>> 
>>> ------------------------------------------------------------------------------
>>> What You Don't Know About Data Connectivity CAN Hurt You
>>> This paper provides an overview of data connectivity, details
>>> its effect on application quality, and explores various alternative
>>> solutions. http://p.sf.net/sfu/progress-d2d
>>> _______________________________________________
>>> Openfx-developer mailing list
>>> Ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>> 
>> --
>> Bruno Nicoletti,
>> Chief Technology Officer
>> The Foundry
>> 6th Floor, The Communications Building,
>> 48, Leicester Square,
>> London, WC2H 7LT, UK
>> Skype: brunonicoletti
>> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
>> Web: www.thefoundry.co.uk
>> Email: br...@th...
>> 
>> The Foundry Visionmongers Ltd.
>> Registered in England and Wales No: 4642027
>> 
>> 

--
Bruno Nicoletti, 
Chief Technology Officer
The Foundry
6th Floor, The Communications Building,
48, Leicester Square,
London, WC2H 7LT, UK
Skype: brunonicoletti
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
Web: www.thefoundry.co.uk
Email: br...@th...  

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

Re: [Openfx-developer] c++ support layer, myth or reality

[Hybris <hy...@gm...>]

Oh, i skipped this one.
I thought it was a legacy package related to ofx 1.1 and no more needed for 1.2.

And it contains updated examples...great.
Thanks

2011/3/3 Bruno Nicoletti <br...@th...>:
> The source is available as a download from the source forge site....
>
>    http://sourceforge.net/projects/openfx/files/openfxSupport/
>
> it is a skin on top of the C API and makes it much easier to write a plugin.
>
> There are examples in there.
>
>
> b
>
> On 3 Mar 2011, at 22:01, Hybris wrote:
>
>> Just kidding :)
>>
>> I am reading the documentation and the examples and every now and then
>> i find references to "the c++ support layer", like "don't do like
>> this, use the c++ support layer" or so
>>
>> I did not understand what this layer is about and the documentation
>> clearly states that it does not cover it but it seems, or better i
>> suspect, it should ease development in some way
>>
>> So what can  i do to at least have some hint about this layer and how to use it?
>> A tiny example maybe?
>>
>> Sorry but since i do not know what i am talking about, i don't know
>> what to ask and i am also a little embarassed in doing such a vague
>> question.
>>
>> Thanks for any clarification on this matter
>> Cheers
>>
>> ------------------------------------------------------------------------------
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Openfx-developer mailing list
>> Ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>
> --
> Bruno Nicoletti,
> Chief Technology Officer
> The Foundry
> 6th Floor, The Communications Building,
> 48, Leicester Square,
> London, WC2H 7LT, UK
> Skype: brunonicoletti
> Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906
> Web: www.thefoundry.co.uk
> Email: br...@th...
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
>

Re: [Openfx-developer] c++ support layer, myth or reality

[Bruno N. <br...@th...>]

The source is available as a download from the source forge site....

    http://sourceforge.net/projects/openfx/files/openfxSupport/

it is a skin on top of the C API and makes it much easier to write a plugin.

There are examples in there.


b

On 3 Mar 2011, at 22:01, Hybris wrote:

> Just kidding :)
> 
> I am reading the documentation and the examples and every now and then
> i find references to "the c++ support layer", like "don't do like
> this, use the c++ support layer" or so
> 
> I did not understand what this layer is about and the documentation
> clearly states that it does not cover it but it seems, or better i
> suspect, it should ease development in some way
> 
> So what can  i do to at least have some hint about this layer and how to use it?
> A tiny example maybe?
> 
> Sorry but since i do not know what i am talking about, i don't know
> what to ask and i am also a little embarassed in doing such a vague
> question.
> 
> Thanks for any clarification on this matter
> Cheers
> 
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer

--
Bruno Nicoletti, 
Chief Technology Officer
The Foundry
6th Floor, The Communications Building,
48, Leicester Square,
London, WC2H 7LT, UK
Skype: brunonicoletti
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 
Web: www.thefoundry.co.uk
Email: br...@th...  

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

Re: [Openfx-developer] c++ support layer, myth or reality

[<fab...@fr...>]

> I am reading the documentation and the examples and every now and then
> i find references to "the c++ support layer", like "don't do like
> this, use the c++ support layer" or so
yes, it's much easier with the c++ support library.

> So what can  i do to at least have some hint about this layer and how to use it?
> A tiny example maybe?
There is one or two examples in openfx source code, isn't it?

You can find a bunch of examples inside TuttleOFX project:
https://github.com/tuttleofx/TuttleOFX/tree/master/plugins/image

The simplest example:
https://github.com/tuttleofx/TuttleOFX/tree/master/plugins/image/process/color/Invert/src

I hope this can help. This is one of the goals of this project.

Regards,
Fabien

[Openfx-developer] c++ support layer, myth or reality

[Hybris <hy...@gm...>]

Just kidding :)

I am reading the documentation and the examples and every now and then
i find references to "the c++ support layer", like "don't do like
this, use the c++ support layer" or so

I did not understand what this layer is about and the documentation
clearly states that it does not cover it but it seems, or better i
suspect, it should ease development in some way

So what can  i do to at least have some hint about this layer and how to use it?
A tiny example maybe?

Sorry but since i do not know what i am talking about, i don't know
what to ask and i am also a little embarassed in doing such a vague
question.

Thanks for any clarification on this matter
Cheers

[Openfx-developer] OfxGetPlugin not called?

[Haarm-Pieter D. <li...@du...>]

Hi,

I'm running into an issue where OfxGetNumberOfPlugins isn't being called by
Nuke. It's a little bit of an issue because that's where I'd like to insert
some licensing code... Nuke appears not to call OfxGetNumberOfPlugins when a
file is reopened very quickly after a recent exit or crash (!). Is this
expected behavior for an OpenFX host? Can plugin writers plan for any
specific ordering of calls to the plugin's public functions? Is there a
suggested location to insert licensing calls?

In Nuke, the ordering is, sometimes, OfxGetNumberOfPlugins followed by
successive calls to OfxGetPlugin. In other cases, OfxGetPlugin is called
directly, as if the result of OfxGetNumberOfPlugins was cached between Nuke
launches. Either way, for each of call to OfxGetPlugin, Nuke seems to reload
the dynamic library entirely as evidenced by repeated instantiations of
static variables and calls to library constructors and destructors.

I'm testing specifically on OSX with Nuke 5.01v1, 6.1v3 and 6.2v2 for i386
and x86_64.

Thanks in advance for any help,
HP Duiker
Duiker Research

Re: [Openfx-developer] vegas runtime error with examples

[Hybris <hy...@gm...>]

Uhm.....building as release instead of debug "solves" the problem.
Examples seems to work correctly with release build despite the errors
given at runtime with debug build.

I take that those runtime errors can be safely ignored...


2011/2/19 Hybris <hy...@gm...>:
> Hi,
> i think i need a little kick to get started with the examples.
>
> I am compiling them with VS2010 under Vista 32bit and running the
> plugins under Vegas Pro 10.0c
>
> I am already having problems with the Basic example. :(
>
> Code compiles correctly, i then copy the Basic.ofx.bundle under OFX
> plugins directory in Vegas installation and plugin shows in the plugin
> list.
>
> I assign the effect to a clip on the timeline but then i am getting
> errors when moving the scale control in the plugin preferences dialog.
>
> I tried OFX 1.2 and i was getting a runtime error saying that
> maskRowBytes variable was being used without being initialized
>
> i thought that  maybe 1.2 was too modern for Vegas 10 (i could not
> find any info about this) and installed OFX 1.1.3...now i am getting
> another runtime error moving the same scale control but this time the
> error says that stack around variable scalecomponents was corrupted
>
> Any clue on what i am doing wrong?
>
> Thanks!
>

[Openfx-developer] vegas runtime error with examples

[Hybris <hy...@gm...>]

Hi,
i think i need a little kick to get started with the examples.

I am compiling them with VS2010 under Vista 32bit and running the
plugins under Vegas Pro 10.0c

I am already having problems with the Basic example. :(

Code compiles correctly, i then copy the Basic.ofx.bundle under OFX
plugins directory in Vegas installation and plugin shows in the plugin
list.

I assign the effect to a clip on the timeline but then i am getting
errors when moving the scale control in the plugin preferences dialog.

I tried OFX 1.2 and i was getting a runtime error saying that
maskRowBytes variable was being used without being initialized

i thought that  maybe 1.2 was too modern for Vegas 10 (i could not
find any info about this) and installed OFX 1.1.3...now i am getting
another runtime error moving the same scale control but this time the
error says that stack around variable scalecomponents was corrupted

Any clue on what i am doing wrong?

Thanks!

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

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

[<fab...@fr...>]

> (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

[Openfx-developer] Nuke's supported contexts

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

<BODY><P>Hi everyone,</P>
<P>I am new to OFX development and I&nbsp;am looking for some confirmations&nbsp;here.</P>
<P>(1) Via a brief 1.2.1 api test, I notice that Nuke6.2v2 supports only two contexts&nbsp;so far, they are General and Filter OFX contexts,&nbsp;is this correct?</P>
<P>(2) When I have my plug-in described as "General" with only&nbsp;output clip defined&nbsp;with NO other additional input clips (via ClipDefine call), Nuke6.2v2 is not happy&nbsp;and it crashes right away.&nbsp; However, if I define&nbsp;one additional arbitrary clip,&nbsp;everything is&nbsp;just fine.&nbsp; Is it true that Nuke expects a "general" plugin to have at least one&nbsp;extra Clip defined in addition to the "Output" clip ?</P>
<P>Thanks for your help !</P>
<P>Mike Wong</P>
<P>&nbsp;</P></BODY>

Re: [Openfx-developer] Openfx examples in Nuke, problems and fixes

[Fabien C. <fc...@qu...>]

Hi Paul,

 > I haven't look at it yet but my question would be how is this library
 > getting distributed, and where would it be installed? If each plugin
 > vendor distributes the library, wouldn't there be symbol contamination
 > if multiple versions are used?
I'm embarrassed, I wouldn't like to pollute the OpenFX mailing list with 
Tuttle questions...

I just activated some ways to contact us:
* The public mailing-list
tut...@go...
* To contact the team in private
tut...@go...
* The github issues module, so you can use the repository for bug report
http://github.com/tuttleofx/TuttleOFX/issues

To quickly answer, Tuttle is composed of multiple parts:
1) host library
Image processing library to manipulate a graph of openfx nodes
2) plugin library
A customization of the OpenFX C++ plugin wrapping. It's very small, just 
to get directly boost::gil views.
3) some plugins
4) some applications (nothing substantial yet)

About symbol contamination:
1) Applications using tuttle library, can link in static or dynamic with 
a particular version, like with all libraries. In this case, there is no 
reason to use multiple versions of the library.
2) Plugins are compiled in static with the c++ plugin wrapping, so each 
plugin can be compiled with a custom version.

About distribution and installation:
There is nothing special for this. You can install all the targets in a 
custom directory. Next you only need to add this path to the 
OFX_PLUGIN_PATH environnent variable. Tell me if I'm not answering your 
question.

Really sorry for the advertisement here...

Regards,
Fabien

Re: [Openfx-developer] Openfx examples in Nuke, problems and fixes

[Paul M. <pa...@fx...>]

On 1/4/2011 5:15 AM, Fabien Castan wrote:
> Correct me if I am wrong in my reading of the license.
> It's important to know if some companies don't accept to use LGPL
> licensed code. Could you explain me why ?

I haven't look at it yet but my question would be how is this library 
getting distributed, and where would it be installed? If each plugin 
vendor distributes the library, wouldn't there be symbol contamination 
if multiple versions are used?

Re: [Openfx-developer] Openfx examples in Nuke, problems and fixes

[Fabien C. <fc...@qu...>]

Hi Pierre,

 > Juut a short note:
 > I did a quick look at your source directory. I am noticing that you are
 > using an LPGL license v3 and you as well amend it.
Yes, we choose LGPL after a long discussion with all the initial 
partners, so it will be difficult to change it.

 > It's your project but, it might be more useful if you used an MIT
 > x11/Modified BSD/NCSA permissive license  (like OFX itself)?
 > http://www.gnu.org/licenses/license-list.html#Expat
OpenFX is an API, so it would be strange not to be fully permissive. 
TuttleOFX is a library, so it's a little different.

 > (at least for the core library, someone might have a reason for GPL-
 > e.g. for a useful example.cpp or a specialized codec...)
Sorry, I don't understand the idea. If someone would write GPL code, he 
can use an LGPL library.

 > Reason is some companies don't accept to use LPGL licensed code as it
 > becomes too complicated with their legal dept.
 > It's also becoming more common these days to just offer dual-licensing
 > -- http://en.wikipedia.org/wiki/Multi-licensing
 > (choose your own) so it doesn't have to become a religion.
I'm not sure to understand why companies wouldn't accept to use LGPL.
LGPL has only one real constrain: to redistribute the modifications in 
the library itself if you redistribute a product using it. That has 
nothing to do with GPL contaminating rule.
We doesn't choose this licence by religious belief, but it's a way to 
manage the collaboration between the different partners.
All partners can use this library in commercial products (applications 
or new plugins) as we do, but have to publish if they fix a bug in the 
core library, supports a new kind of parameter, etc. So all partners are 
really free to use it as they want but in the same time it's a way to 
keep the core library as best as possible in the interest of all.

Correct me if I am wrong in my reading of the license.
It's important to know if some companies don't accept to use LGPL 
licensed code. Could you explain me why ?

Regards,
Fabien

Re: [Openfx-developer] Openfx examples in Nuke, problems and fixes

[Pierre J. <ja...@re...>]

Fabien,

Juut a short note:
I did a quick look at your source directory. I am noticing that you are 
using an LPGL license v3 and you as well amend it.

It's your project but, it might be more useful if you used an MIT 
x11/Modified BSD/NCSA permissive license  (like OFX itself)?
http://www.gnu.org/licenses/license-list.html#Expat
(at least for the core library, someone might have a reason for GPL- 
e.g. for a useful example.cpp or a specialized codec...)

Reason is some companies don't accept to use LPGL licensed code as it 
becomes too complicated with their legal dept.
It's also becoming more common these days to just offer dual-licensing 
-- http://en.wikipedia.org/wiki/Multi-licensing
(choose your own) so it doesn't have to become a religion.

Pierre

On 12/21/2010 2:10 PM, Pau Gargallo wrote:
> Fabien,
>
> thanks for the answer and the pointer to your plug-ins, they will be
> very useful.
>
> After catching the kOfxStatFailed when fetching the images the
> examples work fine. I'll send a patch with the changes I've made.
>
> I'm using the last version of Nuke on a 64bits linux, but I've
> compulsively tried a bunch of versions from the Foundry's ftp, to see
> if the error happened only some of them. As it turned out, it was not
> a version problem but an oversight in the example.
>
> cheers,
> pau
>
>
>
> On Tue, Dec 21, 2010 at 5:10 PM,<fab...@fr...>  wrote:
>    
>> Hi,
>> The default examples are not really great.
>> Effectively, nuke often returns an empty image (I don't know why) and you have to return an error. And nuke does the process again, with a good image...
>> We have created an open source project for openfx plugins and a library to batch a graph of openfx nodes. The project is still under early development, but you can found a bunch of plugin examples, simple or advanced ones.
>> https://github.com/tuttleofx/TuttleOFX/tree/master/plugins/image/process
>> There is no documentation, so if you have any question, don't hesitate to ask me.
>> To build see INSTALL.scons (the bjam version is no more used and so not up to date).
>>
>> Regards,
>> Fabien Castan
>>
>> PS: which version of nuke are you using ? There is many openfx bug fixes in nuke>= 6.0.
>>
>> ----- Mail Original -----
>> De: "Pau Gargallo"<pau...@gm...>
>> À:ope...@li...
>> Envoyé: Mardi 21 Décembre 2010 13h01:37 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
>> Objet: [Openfx-developer] Openfx examples in Nuke, problems and fixes
>>
>> Hi all,
>>
>> I'm new to OpenFX. I've downloaded the headers and examples, compiled
>> them and loaded them into Nuke without problems. The problems arrive
>> when I actually use the plug-in examples. They work properly as long
>> as you do not move the sliders too much. But as soon as you move a
>> slider (any of them) a bit to fast, Nuke crashes.  I've tried multiple
>> combinations of Nuke and OpenFX versions both on linux and mac, and
>> had always the same crash.
>>
>> The problem seems to be that the render method in the examples does
>> not check the validity of the source image. The call
>>
>>      gEffectHost->clipGetImage(myData->sourceClip, time, NULL,&sourceImg);
>>
>> in line 667 of the basic.cpp example, is sporadically returning
>> kOfxStatFailed, but the return value is ignored.
>>
>> What is the proper way to handle such failure?
>> Should the code in the examples be modified to handle this?
>>
>> Thanks in advance,
>> pau
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>> _______________________________________________
>> Openfx-developer mailing list
>> Ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>>
>>      
> ------------------------------------------------------------------------------
> Forrester recently released a report on the Return on Investment (ROI) of
> Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
> within 7 months.  Over 3 million businesses have gone Google with Google Apps:
> an online email calendar, and document program that's accessible from your
> browser. Read the Forrester report:http://p.sf.net/sfu/googleapps-sfnew
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>
>    

[Openfx-developer] minor bugs in API

[<fab...@fr...>]

Hi,

I noticed some minor bugs, but this is important because it's in the C API.

* There is a "copy-paste" bug in ofxPixels.hpp
http://openfx.cvs.sourceforge.net/viewvc/openfx/include/ofxPixels.h?revision=1.3&view=markup
The structure OfxRGBColourD has an alpha value...

* There is a syntax error (comma problem) in ofxParametricParam.h, line 251, function parametricParamSetNthControlPoint

* OfxMultiThreadSuiteV1
The const must be removed from all "OfxMutexHandle" function parameter, because the host needs to modify it. This can be done without any compatibility problem as it's in "C" language, so arguments are not in the function definition. I removed them in the code I use.

Regards,
Fabien Castan

[Openfx-developer] parametric parameter

[<fab...@fr...>]

Hi,

In the openfx 1.2 documentation, there is a parametric parameter example which uses the param instance to set the default values.
http://openfx.sourceforge.net/Documentation/1.0/Reference/ch09s10.html

  // set a default curve, this example sets an invert 
  OfxParamHandle descriptor;
  gParamHost->paramGetHandle(paramSet, "lookupTable", &descriptor, NULL);
  // ... and sets values using this instance (parametricParamAddControlPoint)

But in the documentation of the "paramGetHandle" function, it's written:
"You cannot call this in a plugin's describe function, as it needs an instance to work on."

I'm not sure which part of the documentation is wrong. As it's clearly written about parametric parameter:
"The major complication with these parameters is how to allow a plug-in to set values, and defaults. The default default value of a parametric curve is to be an identity lookup. If a plugin wishes to set a different default value for a curve, it can use the suite to set key/value pairs on the  m descriptor of the param. When a new instance is made, it will have these curve values as a default."
I suppose it's only a problem about "paramGetHandle" documentation.

Regards,
Fabien Castan