Menu
▾
▴
openfx-developer — Developer oriented mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(16) |
Jul
(6) |
Aug
(20) |
Sep
(6) |
Oct
(2) |
Nov
(9) |
Dec
(11) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(29) |
Feb
(16) |
Mar
(9) |
Apr
(75) |
May
(66) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(6) |
Nov
(8) |
Dec
|
| 2006 |
Jan
(3) |
Feb
(15) |
Mar
(6) |
Apr
(3) |
May
(6) |
Jun
(31) |
Jul
(1) |
Aug
(12) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
(59) |
Mar
(37) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(3) |
| 2008 |
Jan
|
Feb
(2) |
Mar
(8) |
Apr
(14) |
May
(8) |
Jun
(32) |
Jul
(1) |
Aug
(2) |
Sep
(6) |
Oct
(4) |
Nov
|
Dec
|
| 2009 |
Jan
(5) |
Feb
(10) |
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
(30) |
Aug
(10) |
Sep
|
Oct
|
Nov
(5) |
Dec
(15) |
| 2010 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(6) |
May
(3) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(12) |
| 2011 |
Jan
(6) |
Feb
(6) |
Mar
(12) |
Apr
(19) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Bruno N. <br...@th...> - 2010-12-24 09:36:12
|
OK, fixes are up in CVS and as a new file release. b On 23 Dec 2010, at 20:59, Pau Gargallo wrote: > Thanks a lot Bruno, sorry for inciting more work :( > Merry Christmas to everyone, > pau > > On Thu, Dec 23, 2010 at 7:39 PM, Bruno Nicoletti <br...@th...> wrote: >> I'm being a bit slow on this, in theory I am on holidays and I am sharing child care duties. >> >> I'm doing a slightly more general fix to all the example plugins, not just basic. Should be up soon ish. >> >> b >> >> On 22 Dec 2010, at 15:24, Pau Gargallo wrote: >> >>> use this one instead then, it returns OK. >>> >>> thanks, >>> pau >>> >>> On Wed, Dec 22, 2010 at 1:19 PM, Bruno Nicoletti <br...@th...> wrote: >>>> Yes it would, I'll add in your patch when I get the chance later on today. >>>> >>>> b >>>> >>> <basic.cpp.patch>------------------------------------------------------------------------------ >>> 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 >> >> -- >> 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 >> >> >> ------------------------------------------------------------------------------ >> Learn how Oracle Real Application Clusters (RAC) One Node allows customers >> to consolidate database storage, standardize their database environment, and, >> should the need arise, upgrade to a full multi-node Oracle RAC database >> without downtime or disruption >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Openfx-developer mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openfx-developer >> > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > 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 |
|
From: Pau G. <pau...@gm...> - 2010-12-23 20:59:41
|
Thanks a lot Bruno, sorry for inciting more work :( Merry Christmas to everyone, pau On Thu, Dec 23, 2010 at 7:39 PM, Bruno Nicoletti <br...@th...> wrote: > I'm being a bit slow on this, in theory I am on holidays and I am sharing child care duties. > > I'm doing a slightly more general fix to all the example plugins, not just basic. Should be up soon ish. > > b > > On 22 Dec 2010, at 15:24, Pau Gargallo wrote: > >> use this one instead then, it returns OK. >> >> thanks, >> pau >> >> On Wed, Dec 22, 2010 at 1:19 PM, Bruno Nicoletti <br...@th...> wrote: >>> Yes it would, I'll add in your patch when I get the chance later on today. >>> >>> b >>> >> <basic.cpp.patch>------------------------------------------------------------------------------ >> 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 > > -- > 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 > > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > |
|
From: Bruno N. <br...@th...> - 2010-12-23 18:39:12
|
I'm being a bit slow on this, in theory I am on holidays and I am sharing child care duties. I'm doing a slightly more general fix to all the example plugins, not just basic. Should be up soon ish. b On 22 Dec 2010, at 15:24, Pau Gargallo wrote: > use this one instead then, it returns OK. > > thanks, > pau > > On Wed, Dec 22, 2010 at 1:19 PM, Bruno Nicoletti <br...@th...> wrote: >> Yes it would, I'll add in your patch when I get the chance later on today. >> >> b >> > <basic.cpp.patch>------------------------------------------------------------------------------ > 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 -- 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 |
|
From: Pau G. <pau...@gm...> - 2010-12-22 15:24:08
|
use this one instead then, it returns OK. thanks, pau On Wed, Dec 22, 2010 at 1:19 PM, Bruno Nicoletti <br...@th...> wrote: > Yes it would, I'll add in your patch when I get the chance later on today. > > b > |
|
From: Bruno N. <br...@th...> - 2010-12-22 12:20:05
|
Yes it would, I'll add in your patch when I get the chance later on today. b On 22 Dec 2010, at 12:04, Pau Gargallo wrote: > That clarifies my doubts, thanks Bruno! > > Does it make sense to update the openfx examples to handle such case > and avoid the crash? I understand that they are not meant to be > complete implementations, but it would be instructive for newbies like > me ;-) > > pau > > > On Wed, Dec 22, 2010 at 11:46 AM, Bruno Nicoletti > <br...@th...> wrote: >> What is happening is that Nuke is interrupting all process when you move a slider about. Which means you plugin gets interrupted. >> >> So if a plugin fetches an image and part way through that Nuke interrupts, then the fetch image will fail, because all upstream processing has halted. This is not a bug in Nuke, it is the way Nuke works. If you check the interruption status after a fetch, you will see that you will have been interrupted. >> >> Interruption is not an error state, you plugin has not gone wrong. In which case you should return OK. >> >> b >> >> >> On 21 Dec 2010, at 22:10, 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 >> >> -- >> 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 >> >> >> ------------------------------------------------------------------------------ >> 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 >> > > ------------------------------------------------------------------------------ > 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 -- 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 |
|
From: Pau G. <pau...@gm...> - 2010-12-22 12:04:46
|
That clarifies my doubts, thanks Bruno! Does it make sense to update the openfx examples to handle such case and avoid the crash? I understand that they are not meant to be complete implementations, but it would be instructive for newbies like me ;-) pau On Wed, Dec 22, 2010 at 11:46 AM, Bruno Nicoletti <br...@th...> wrote: > What is happening is that Nuke is interrupting all process when you move a slider about. Which means you plugin gets interrupted. > > So if a plugin fetches an image and part way through that Nuke interrupts, then the fetch image will fail, because all upstream processing has halted. This is not a bug in Nuke, it is the way Nuke works. If you check the interruption status after a fetch, you will see that you will have been interrupted. > > Interruption is not an error state, you plugin has not gone wrong. In which case you should return OK. > > b > > > On 21 Dec 2010, at 22:10, 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 > > -- > 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 > > > ------------------------------------------------------------------------------ > 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 > |
|
From: Bruno N. <br...@th...> - 2010-12-22 11:19:25
|
What is happening is that Nuke is interrupting all process when you move a slider about. Which means you plugin gets interrupted. So if a plugin fetches an image and part way through that Nuke interrupts, then the fetch image will fail, because all upstream processing has halted. This is not a bug in Nuke, it is the way Nuke works. If you check the interruption status after a fetch, you will see that you will have been interrupted. Interruption is not an error state, you plugin has not gone wrong. In which case you should return OK. b On 21 Dec 2010, at 22:10, 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 -- 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 |
|
From: Pau G. <pau...@gm...> - 2010-12-22 08:55:02
|
Thanks a lot for the cookbook Pierre!
It will be very helpful.
pau
On Wed, Dec 22, 2010 at 12:57 AM, Pierre Jasmin <ja...@re...> wrote:
> On 12/21/2010 2:42 PM, Pau Gargallo wrote:
>
> Ok, for what it's worth, here is a patch against OpenFX version 1.2.1
> of Examples/Basic/basic.cpp to handle empty images and make the
> plug-in work with Nuke.
>
> To apply:
> $ cd Examples/Basic
> $ patch < basic.cpp.patch
>
>
> Nuke does not like to be returned Failed, you have to catch that and return
> kOfxStatOK;
>
> FWIW, Here's my cookbook for all tested OFX hosts here (varies, not just
> Nuke here)
>
> * check main input is connected
> gPropHost->propGetInt(props, kOfxImageClipPropConnected, 0, &connected);
> (if not throw)
>
> * check current time you are asked to render is within valid frame range of
> clip
> gPropHost->propGetDoubleN(props, kOfxImageEffectPropFrameRange, 2,
> frameRange);
> (if not throw)
>
> * get handle
> gEffectHost->clipGetHandle(effect, clipToGet, &clipHandle , 0);
>
> * get image
> ofxStatus = gEffectHost->clipGetImage(...,&img[i]);)
> if (ofxStatus != kOfxStatOK || img[i] == NULL)
> { throw and cleanup }
>
> * get image pointer
> gPropHost->propGetPointer(imageHandle, kOfxImagePropData, 0, &r);
> check again if data is null, if it is { throw and cleanup }
>
> * check abort...
> if ->abort (throw and cleanup)
>
>
> Cheers,
> pau
>
>
> On Tue, Dec 21, 2010 at 11:10 PM, Pau Gargallo <pau...@gm...>
> 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
>
>
> ------------------------------------------------------------------------------
> 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
>
>
|
|
From: Pierre J. <ja...@re...> - 2010-12-22 00:11:44
|
On 12/21/2010 2:42 PM, Pau Gargallo wrote:
> Ok, for what it's worth, here is a patch against OpenFX version 1.2.1
> of Examples/Basic/basic.cpp to handle empty images and make the
> plug-in work with Nuke.
>
> To apply:
> $ cd Examples/Basic
> $ patch< basic.cpp.patch
>
Nuke does not like to be returned Failed, you have to catch that and
return kOfxStatOK;
FWIW, Here's my cookbook for all tested OFX hosts here (varies, not just
Nuke here)
* check main input is connected
gPropHost->propGetInt(props, kOfxImageClipPropConnected, 0, &connected);
(if not throw)
* check current time you are asked to render is within valid frame range
of clip
gPropHost->propGetDoubleN(props, kOfxImageEffectPropFrameRange, 2,
frameRange);
(if not throw)
* get handle
gEffectHost->clipGetHandle(effect, clipToGet, &clipHandle , 0);
* get image
ofxStatus = gEffectHost->clipGetImage(...,&img[i]);)
if (ofxStatus != kOfxStatOK || img[i] == NULL)
{ throw and cleanup }
* get image pointer
gPropHost->propGetPointer(imageHandle, kOfxImagePropData, 0, &r);
check again if data is null, if it is { throw and cleanup }
* check abort...
if ->abort (throw and cleanup)
> Cheers,
> pau
>
>
> On Tue, Dec 21, 2010 at 11:10 PM, Pau Gargallo<pau...@gm...> 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
>>
|
|
From: Pau G. <pau...@gm...> - 2010-12-21 22:42:28
|
Ok, for what it's worth, here is a patch against OpenFX version 1.2.1 of Examples/Basic/basic.cpp to handle empty images and make the plug-in work with Nuke. To apply: $ cd Examples/Basic $ patch < basic.cpp.patch Cheers, pau On Tue, Dec 21, 2010 at 11:10 PM, Pau Gargallo <pau...@gm...> 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 >> > |
|
From: Pau G. <pau...@gm...> - 2010-12-21 22:10:28
|
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 > |
|
From: Pau G. <pau...@gm...> - 2010-12-21 12:01:43
|
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
|
|
From: Bruno N. <br...@th...> - 2010-10-26 17:31:16
|
Sorted, ofx 1.2.1 is up there with relevant fixes. b On 26 Oct 2010, at 18:05, Bruno Nicoletti wrote: > Hi Marvin, > > that is a stupidity that crept in, thanks for spotting it. I believe Vegas is supporting the 1.1 API, which doesn't have the error in there. I'll fix that promptly. > > b > > On 26 Oct 2010, at 17:03, Marvin Herbold wrote: > >> Hello... >> >> Is the OpenFX API and samples supposed to be functioning? >> >> I have Sony Vegas Pro 10 and they said they support OpenFX which makes it sound like its supposed to be. >> >> I downloaded the latest OpenFX release (apparently 1.2) and fired up visual studio 2010, made a new project, put in one of the examples from the examples folder (basic.cpp), set up the appropriate include directories. >> >> First error I get when compiling is that OfxRGBAColorB is not defined. I did a search of the headers and see that its in ofxPixels.h... so I #include that and try again. >> >> Next error is that OfxRGBAColorD is defined twice in ofxPixels.h - I check, and sure enough it is. Line 59 then again on line 81. This makes me think this stuff isn't actually usable... but then how could Sony claim VP10 works with OpenFX plugins... >> >> I comment out the duplicate struct definition and it seems to compile OK... but... >> >> ...??? any insight appreciated!!! >> >> Thanks, >> Marvin Herbold >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev_______________________________________________ >> Openfx-developer mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openfx-developer > > -- > Bruno Nicoletti, > Chief Technology Officer > The Foundry, 1 Wardour Street, London. W1D 6PA > Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti > Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 > Web: www.thefoundry.co.uk > Email: br...@th... > > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer -- Bruno Nicoletti, Chief Technology Officer The Foundry, 1 Wardour Street, London. W1D 6PA Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 Web: www.thefoundry.co.uk Email: br...@th... The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
|
From: Bruno N. <br...@th...> - 2010-10-26 17:05:48
|
Hi Marvin, that is a stupidity that crept in, thanks for spotting it. I believe Vegas is supporting the 1.1 API, which doesn't have the error in there. I'll fix that promptly. b On 26 Oct 2010, at 17:03, Marvin Herbold wrote: > Hello... > > Is the OpenFX API and samples supposed to be functioning? > > I have Sony Vegas Pro 10 and they said they support OpenFX which makes it sound like its supposed to be. > > I downloaded the latest OpenFX release (apparently 1.2) and fired up visual studio 2010, made a new project, put in one of the examples from the examples folder (basic.cpp), set up the appropriate include directories. > > First error I get when compiling is that OfxRGBAColorB is not defined. I did a search of the headers and see that its in ofxPixels.h... so I #include that and try again. > > Next error is that OfxRGBAColorD is defined twice in ofxPixels.h - I check, and sure enough it is. Line 59 then again on line 81. This makes me think this stuff isn't actually usable... but then how could Sony claim VP10 works with OpenFX plugins... > > I comment out the duplicate struct definition and it seems to compile OK... but... > > ...??? any insight appreciated!!! > > Thanks, > Marvin Herbold > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev_______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer -- Bruno Nicoletti, Chief Technology Officer The Foundry, 1 Wardour Street, London. W1D 6PA Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 Web: www.thefoundry.co.uk Email: br...@th... The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
|
From: Marvin H. <mhe...@co...> - 2010-10-26 16:04:18
|
?Hello... Is the OpenFX API and samples supposed to be functioning? I have Sony Vegas Pro 10 and they said they support OpenFX which makes it sound like its supposed to be. I downloaded the latest OpenFX release (apparently 1.2) and fired up visual studio 2010, made a new project, put in one of the examples from the examples folder (basic.cpp), set up the appropriate include directories. First error I get when compiling is that OfxRGBAColorB is not defined. I did a search of the headers and see that its in ofxPixels.h... so I #include that and try again. Next error is that OfxRGBAColorD is defined twice in ofxPixels.h - I check, and sure enough it is. Line 59 then again on line 81. This makes me think this stuff isn't actually usable... but then how could Sony claim VP10 works with OpenFX plugins... I comment out the duplicate struct definition and it seems to compile OK... but... ...??? any insight appreciated!!! Thanks, Marvin Herbold |
|
From: Haarm-Pieter D. <li...@du...> - 2010-09-10 11:56:13
|
Hey, Have you guys looked at the OpenImageIO that Imageworks has been working on? http://openimageio.org/wiki/index.php?title=Main_Page It was written to solve image-processing issues in the context of rendering, but may be of some use. Don't know how performant it is, or how well it handles image sequences. HP Duiker On Wed, Nov 25, 2009 at 11:27 PM, Pierre Jasmin <ja...@re...>wrote: > > cool > > pay attention to the initial notes on V1.2 and preliminary V2 on docuwiki: > http://www.openeffects.org/dokuwiki/doku.php > > if you want to work on an OFXIO branch and fit it somehow in V2 specs being > *slowly* worked on right now, HD3D might consider joining the association > and make it official (admin contact for that now is SteveHayes at genarts > dot com) > > you might also maybe consider taking over the effect type "Clip" as context > since I don't think any apps supports only that right now > > Pierre > RE:Vision Effects > > > > Guillaume Chatelet wrote: > > Hi everyone, > > As a collaborative effort of a group of French Post Production > companies known as HD3D(1), we are developing a set of tools to > alleviate a few common and shared issues of the trade. HD3D creates > outcomes from asset manager to dispatcher as well as watermarking > technologies to human resources manager. HD3D gathers Mikros Image(2), > 2 minutes(3), Mac Guff Line(4), Teamto(5), Eclair(6) and Duran > Duboi(7). > > One of HD3D's outcomes called TuttleOFX, lead by Mikros and Duran > Duboi, is an attempt to provide an easy to use command-line image > processing batching tool. TuttleOFX is under heavy development right > now and the plan is to release it as an Open Source project( LGPL ). > TuttleOFX aims to be extensible and performance oriented, it can be > used to resize a sequence of EXR files as well as render a flash movie > to H264 movie file. TuttleOFX is based on OpenFX to > + enable interoperability between the industry and our own internal developments > + guaranty that we can work together easily on a shared production > + use commercial plugins into our own applications > > TuttleOFX is a library and will provide a Python binding, the library > is used by "sam" the command line program for user interaction out of > the box. > > The first step is to add Read and Write plugins to the OpenFX > framework. So the goal of this message is to let you know we are now > trying to design some extensions to OpenFX to provide such features. > > We are trying our best to keep the original philosophy you established > so your feedback is very welcome. For the moment, it's quite > unfinished and still under heavy design so it really is an > introduction message. As soon as we have anything to show we'll let > you know and if the new concepts we've introduced are of any interest > to the OpenFX community, we'll be glad to contribute to the standard. > > We look forward to hearing from you, > Sincerely, > The TuttleOFX team > ---------------------------------- > 1 http://www.hd3d.fr/en/ > 2 http://www.mikrosimage.eu/english/ > 3 http://www.2minutes.fr/ > 4 http://www.macguff.fr/?lang=en > 5 http://www.teamto.com/ > 6 http://www.eclair.fr/Website/site/eng_accueil.htm > 7 http://www.duranduboi.com/ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Openfx-developer mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/openfx-developer > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > > |
|
From: Pierre J. <ja...@re...> - 2010-07-21 22:48:21
|
On 7/19/2010 6:36 AM, fab...@fr... wrote:
> Hi,
>
> I would like to propose an important new parameter type : kOfxParamTypeList, which can really improve the openfx possibilities.
> Hosts could use something like a listView (in Qt terms) to display the list of parameters. This listView can be a treeView with a list of list.
> A simple example, kOfxParamTypeList<kOfxParamTypeDouble2D>
>
I am all for it as I requested similar before - not the same - (calling
it then predefined array of parameters versus completely dynamic)
I see we forgot a sort of parameter array group type in 2.0 list
The distinction I see is you suggest "Only the number of parameters or
group of parameters inside will be dynamic."
while back then I tried to separate fully dynamic from a growable block
of parameters (with some host provided Add+, Delete-)... so where group
count changes but not number of params per instance as a distinction.
= it would be better to be able to add a variable list of parameters per
such "Add" block instance, but I am just not sure every hosts can do that.
Rethinking this a bit, perhaps it's just a matter of the host telling
you so one knows in the "Add" callback a fixed size group is autocreate
and all you need to do is perhaps change some defaults (e.g names of
some params, value of color,...), and then so possibly use the
hide/disable mechanism for these parameters at fixed slot to represent
the same when variable size array is not possible? OR the "Add"
callback is for you to fill with an arbitrary parameter create list then
probably based on some other menu or something in the plugin.
Also what is the largest number of parameters per block you envision
would make sense, I am worried about this being robust in 2D UI layouts
- for example is it reasonable / useful to cap a max like 10-15
parameters (some numbers) per such group?
- pierre
////////////////////////////////////////////////////////////////////////////
I repaste some highlights from
"V2 Expansions - dynamic parameter creation" may 2005 thread
below
"
Hi All,
dynamic parameter creation has been requested by various people, but
nobody has put forward a spec or the modifications/extra suites required
to do it.
I think it is a good idea, however I'm not going to do the work in
defining it, as I have enough (unpaid) OFX work on my plate right now.
Unless, of course, someone wants to trade redocumenting the API for
defining the suite.
So, over to one of you to come up with a spec and a OFX suite to do it.
My one suggestion is that we break the V1 parameters suite and provide a
new V2 suite to accomplish this.
b
"
Pierre says primarly interested in blocks of parameters
"There is two types of dynamism, pre-defined and completely dynamic..."
Abstracting Array of Parameters idea here: A mechanism with Add, Delete
that comes with a menu (1,2,3,4,5...), or a scrollable list or another
way to enter the proper one, and a block of parameters (same usual
parameters supported by host). The xml ressource, defaults,.. could be
shared for each block. API wise a way to loop all the current arrays
(getNumMembers, for i to NumMembers, for i to NumParams get...). One
fair host side UI implementation could be a box showing the current
selection parameters and not the other instances of the list. (showing 3
but not 1,2 and 4,5...). This works very well at least for 2D geometry
etc...
Bruno Nicoletti <br...@th...> 5/4/2005 12:29 PM:
"
I was just drafting a reply to Pierre's post and yours answered some of
my questions.
Firstly we already do have show/hide available under OFX.
How about this for a spec...
- parameters can be declared to be "list" params at plug-in
description,
- parameters that are "lists" can have elements added or removed
from an instance dynamically under plug-in control,
- using the current "group" param, you can declare a group param to
be a list, where adding or deleting to it creates a new set of params in
the group.
So for your case (assuming we add a rotospline param type) you would
declare a group to contain a spline and the other associated bits you
want. The plug-in would have push buttons to add/delete sets to the
group, voila you get new rotos as you need them, with the extra bits on
the side.
If the listing capabilities only worked on non-grouped parameter types,
you could still have it work, simply by declaring the N params
(including the roto) you need to be lists and doing the add/delete to
each of them when the user hits add/delete.
Some glue needs to be thought about and host developers need to be
consulted, but is this what you would want?
Does anybody out there currently want to be able to create arbitrary new
parameters on the fly and which can't fit into this scheme?
Would any host manufacturers have a problem with this list scheme?
"
Gary Oberbrunner <ga...@ge...>
"
Peter Litwinowicz wrote:
> I'm still very unclear about what you propose as a list and what you
> propose
> as a group. Can't we call everything one or the other?
If I understand correctly, a list is just a logically related collection
of params. A group looks like a group to the user (box around it or
whatever). Bruno's saying that a group can be made into a list so you
can have something that looks like a group but behaves like a list, i.e.
is replicable.
> Again, we don't really need dynamically allocated param settings that
> vary
> for each spline. We can simply say " for this plugin, create a
> checkbox, 2
> popup-menus and 3 float sliders" whenever a new spline is added. No need
> for us to change that per-spline, or vary it once our plugin is
> initialized
> (I'm not speaking for anyone else!)
The spline plus your list of params is the list. That list gets
duplicated once per spline.
> 4) the host app sees that the user creates a spline for our plugin, then
> adds the necessary parameters for that spline (based on what we declare
> about spline params upon initialization of our plugin)
Or the host could call the plugin and tell it "new spline created" and
the plugin could add the new copy of the list (or group). Maybe that
gives more flexibility? In any case the new params should cause the
host to know the plugin needs to be rerendered.
-- Gary
"
Bruno Nicoletti <br...@th...> "
Almost but not quite right. Obviously we are having terminology issues
here and I wasn't clear enough in my post. I also have a horrid head
cold, which isn't helping.
By group, I mean a set of logically grouped parameters. In OFX this is
currently done with an explicit "group" parameter type that has other
parameters as children. This is typically done so hierarchical param
layouts (think After Effects or the FLAME animation sheet) are able to
group params nicely.
By list I mean a parameter that can have zero or more values in it, the
number of which are dynamically controlled by the plug-in. So you say
during the plugin description phase "I want 2D position parameter fred
to be a list". By doing so, fred can have zero or more 2D values inside
it, each behaving as a separate 2D param. During the lifetime of the
instance, the plug-in adds or deletes values in that list.
Using the STL as pseudo code to explain the concept,
FloatParam barney; // basic float param, what we have now
std::list<FloatParam> fred; // an array of float params, what I'm
suggesting
I was suggesting that by declaring a group parameter to be a list,
creating a new element in that group param's list creates new elements
in the children of the group as well.
I was also suggesting rotosplines be made explicit parameters that the
effect declares in the same way as any other parameter, and so can be
list params or added to groups.
Linking these concepts together, I was suggesting that Pete and Pierre
could achieve what he was asking for without having to do some non
orthogonal magic linking sets of parameters to implicit rotosplines.
Does that make more sense? "
"
///////////////////////////////////
SO,
All missing from above is the implicit association I think of "Add" and
"Delete" (Add and Delete needs their own callback ) as explicitely part
of the list super-param type
and the understanding that different hosts can display such parameter
groupings completely differently:
- some usual schemes for example include:
* a menu (e.g. light 1,light 2,light 3,light 7,..) - selected one is
the controls that get displayed in UI, need alt to menu for cases where
there are too many items
* a scrollable list that grows as you "Add" (e.g. as in Fusion natively
now)
* a dedicated UI page for such (for the 2D parameter layout folks) - I
think toxik 2011 has some internal "meta-widget" like that now that
would map to this
-- display one only in Controls UI but all in animation channels editor...
Ideally Interact functions need a reset(currentId) to tell host which
one to display or goto in UI.
Some other suites could be easier to design if that based mechanism was
supported.
> -------------
> | Position |
> -------------
> | ( 15, 1) |
> | (255, 10) |
> | ( 5, 200) |
> | ... |
> -------------
>
> I imagine a solution allowing to create a list of a group of parameters, so with one column for each parameter of the group. The parameters inside the list will be declared at the description step, like for all parameters. Only the number of parameters or group of parameters inside will be dynamic.
>
> See an example, kOfxParamTypeList< kOfxParamTypeGroup<kOfxParamTypeString, kOfxParamTypeDouble2D, kOfxParamTypeRGBA, kOfxParamTypeBoolean> >
>
> ---------------------------------------------------------
> | Name | Position | Color | Enabled |
> ---------------------------------------------------------
> | "foo" | ( 15, 1) | (1.0, 0.0, 0.0, 1.0) | True |
> | "foo2" | (255, 10) | (1.0, 1.0, 1.0, 1.0) | True |
> | "foo3" | ( 5, 200) | (0.0, 0.0, 0.0, 1.0) | False |
> | ... |
> ---------------------------------------------------------
>
> We can imagine a code like that:
>
> OFX::GroupParamDescriptor* myListTypes = desc.defineGroupParam( "myListTypes" );
> myListTypes->setLabel( "Headers" );
>
> OFX::StringParamDescriptor* name = desc.defineStringParam( "myList_name" );
> name->setLabel( "Name" );
> name->setParent( *myListTypes );
> name->setDefault( "foo" );
> name->setEvaluateOnChange(false);
> name->setHint( "The name option of the list" );
>
> OFX::Double2DParamDescriptor* position = desc.defineDouble2DParam( "myList_position" );
> position->setLabel( "Position" );
> position->setParent( *myListTypes );
> position->setDefault( 1, 1 );
>
> OFX::RGBAParamDescriptor
> ...
> OFX::BooleanParamDescriptor
> ...
>
> OFX::ListParamDescriptor* myList = desc.defineListParam( "myList" );
> myList->setLabel( "My list" );
> myList->setParameterType( *myListTypes );
>
> There are still many things to discuss about the implementation, from example changedParam action...
>
> I read the discussion for openfx 2.0 about dynamic parameters.
> In my opinion, the problem is entierly solved simply with a property "unused" and a list parameter type. I think it simplify the problem and keeps the ofx philosophy of description step (describe/describeInContext).
> I think a new property "unused" is needed, which is different from "isSecret" because secret parameters needs to be stored in project file unlike unused parameters.
> Even if openfx supports dynamic parameters, a list type have a sense.
>
> What do you think about this idea ?
>
> Best regards,
> Fabien Castan
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first --http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Openfx-developer mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openfx-developer
>
>
|
|
From: <fab...@fr...> - 2010-07-19 13:41:59
|
Hi, I would like to propose an important new parameter type : kOfxParamTypeList, which can really improve the openfx possibilities. Hosts could use something like a listView (in Qt terms) to display the list of parameters. This listView can be a treeView with a list of list. A simple example, kOfxParamTypeList<kOfxParamTypeDouble2D> ------------- | Position | ------------- | ( 15, 1) | | (255, 10) | | ( 5, 200) | | ... | ------------- I imagine a solution allowing to create a list of a group of parameters, so with one column for each parameter of the group. The parameters inside the list will be declared at the description step, like for all parameters. Only the number of parameters or group of parameters inside will be dynamic. See an example, kOfxParamTypeList< kOfxParamTypeGroup<kOfxParamTypeString, kOfxParamTypeDouble2D, kOfxParamTypeRGBA, kOfxParamTypeBoolean> > --------------------------------------------------------- | Name | Position | Color | Enabled | --------------------------------------------------------- | "foo" | ( 15, 1) | (1.0, 0.0, 0.0, 1.0) | True | | "foo2" | (255, 10) | (1.0, 1.0, 1.0, 1.0) | True | | "foo3" | ( 5, 200) | (0.0, 0.0, 0.0, 1.0) | False | | ... | --------------------------------------------------------- We can imagine a code like that: OFX::GroupParamDescriptor* myListTypes = desc.defineGroupParam( "myListTypes" ); myListTypes->setLabel( "Headers" ); OFX::StringParamDescriptor* name = desc.defineStringParam( "myList_name" ); name->setLabel( "Name" ); name->setParent( *myListTypes ); name->setDefault( "foo" ); name->setEvaluateOnChange(false); name->setHint( "The name option of the list" ); OFX::Double2DParamDescriptor* position = desc.defineDouble2DParam( "myList_position" ); position->setLabel( "Position" ); position->setParent( *myListTypes ); position->setDefault( 1, 1 ); OFX::RGBAParamDescriptor ... OFX::BooleanParamDescriptor ... OFX::ListParamDescriptor* myList = desc.defineListParam( "myList" ); myList->setLabel( "My list" ); myList->setParameterType( *myListTypes ); There are still many things to discuss about the implementation, from example changedParam action... I read the discussion for openfx 2.0 about dynamic parameters. In my opinion, the problem is entierly solved simply with a property "unused" and a list parameter type. I think it simplify the problem and keeps the ofx philosophy of description step (describe/describeInContext). I think a new property "unused" is needed, which is different from "isSecret" because secret parameters needs to be stored in project file unlike unused parameters. Even if openfx supports dynamic parameters, a list type have a sense. What do you think about this idea ? Best regards, Fabien Castan |
|
From: Bruno N. <br...@th...> - 2010-05-13 08:36:14
|
Hi Peter, thanks for pointing out the ambiguity. It is meant to be simple, so there is only a single currently posted message, which persists until changed with a new message or cleared. b On 13 May 2010, at 02:19, Peter Loveday wrote: > Greetings! > > Is the intention that the new message suite function 'stack' multiple > messages? The documentation is unclear on this; it implies that the message > persists until an explicit clear is done, and not that a new message > overrides a previous one. > > However, if this is the case, there is no means for a plugin to selectively > clear an error state without clearing other informational messages? > > Thanks, > > Love, Light and Peace, > - Peter Loveday > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer -- Bruno Nicoletti, Chief Technology Officer The Foundry, 1 Wardour Street, London. W1D 6PA Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 Web: www.thefoundry.co.uk Email: br...@th... The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
|
From: Peter L. <pe...@ey...> - 2010-05-13 01:44:44
|
Greetings! Is the intention that the new message suite function 'stack' multiple messages? The documentation is unclear on this; it implies that the message persists until an explicit clear is done, and not that a new message overrides a previous one. However, if this is the case, there is no means for a plugin to selectively clear an error state without clearing other informational messages? Thanks, Love, Light and Peace, - Peter Loveday |
|
From: Bruno N. <br...@th...> - 2010-05-11 17:26:38
|
Hello OFX Developer,
the 1.2.0 version of the OFX Image Processing API has been released. The files are now available for down load from sourceforge.
The C++ plugin and host wrapper layers have not yet been updated to reflect the 1.2 API, that will occur shortly.
For details on the changes, please see...
http://openfx.sourceforge.net/Documentation/1.2/ofxProgrammingReference.html#APIChanges_1_2
--
Bruno Nicoletti,
Chief Technology Officer
The Foundry, 1 Wardour Street, London. W1D 6PA
Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti
Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550
Web: www.thefoundry.co.uk
Email: br...@th...
The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027
|
|
From: Pierre J. <ja...@re...> - 2010-04-30 16:41:48
|
On 4/29/2010 3:45 AM, Bruno Nicoletti wrote: > We took a similar approach when we had our motion estimation in Shake, we output vectors into RGBA channels. > > Not much use when you have 8 bit images though. > Yes in application where you can't bump to 16/32 bit you have to send a warning to user that tries to do that -p > b > > On 28 Apr 2010, at 19:33, Pierre Jasmin wrote: > > >> On 4/28/2010 9:52 AM, Pierre Jasmin wrote: >> >>> On 4/28/2010 5:10 AM, Esteban Tovagliari wrote: >>> >>>> Hi all >>>> >>>> I'm developing an OFX host. I'd like to support motion vector inputs and outputs but >>>> I couldn't find anything in ofx's headers or CVS repository. >>>> >>>> Where I can find the info to add them to my host? >>>> >>> that reads Motion Vectors and there is also a plugin that reads them in there as well. >>> >> Of course I can't write before I have coffee >> " that reads Motion Vectors" should have been "that writes Motion Vectors" >> >> Pierre >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Openfx-developer mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openfx-developer >> > -- > Bruno Nicoletti, > Chief Technology Officer > The Foundry, 1 Wardour Street, London. W1D 6PA > Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti > Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 > Web: www.thefoundry.co.uk > Email: br...@th... > > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > > |
|
From: Bruno N. <br...@th...> - 2010-04-29 10:46:02
|
We took a similar approach when we had our motion estimation in Shake, we output vectors into RGBA channels. Not much use when you have 8 bit images though. b On 28 Apr 2010, at 19:33, Pierre Jasmin wrote: > On 4/28/2010 9:52 AM, Pierre Jasmin wrote: >> >> On 4/28/2010 5:10 AM, Esteban Tovagliari wrote: >>> >>> Hi all >>> >>> I'm developing an OFX host. I'd like to support motion vector inputs and outputs but >>> I couldn't find anything in ofx's headers or CVS repository. >>> >>> Where I can find the info to add them to my host? >> that reads Motion Vectors and there is also a plugin that reads them in there as well. > > Of course I can't write before I have coffee > " that reads Motion Vectors" should have been "that writes Motion Vectors" > > Pierre > > ------------------------------------------------------------------------------ > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer -- Bruno Nicoletti, Chief Technology Officer The Foundry, 1 Wardour Street, London. W1D 6PA Direct: +44 (0)20 7255 8569 - Skype: brunonicoletti Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 Web: www.thefoundry.co.uk Email: br...@th... The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
|
From: Pierre J. <ja...@re...> - 2010-04-28 18:33:37
|
On 4/28/2010 9:52 AM, Pierre Jasmin wrote: > On 4/28/2010 5:10 AM, Esteban Tovagliari wrote: >> Hi all >> >> I'm developing an OFX host. I'd like to support motion vector inputs >> and outputs but >> I couldn't find anything in ofx's headers or CVS repository. >> >> Where I can find the info to add them to my host? > that reads Motion Vectors and there is also a plugin that reads them > in there as well. Of course I can't write before I have coffee " that reads Motion Vectors" should have been "that writes Motion Vectors" Pierre |
|
From: Pierre J. <ja...@re...> - 2010-04-28 17:06:10
|
On 4/28/2010 5:10 AM, Esteban Tovagliari wrote: > Hi all > > I'm developing an OFX host. I'd like to support motion vector inputs > and outputs but > I couldn't find anything in ofx's headers or CVS repository. > > Where I can find the info to add them to my host? We use standard images to store dense normalized vectors here http://revisionfx.com/support/faqs/motion_vector_FAQs/motion_vector/ That form is supported by pretty much all 3D renderers as well If you want to play, you can download Twixtor for OFX on our website, it has a plugin called "Motion Vectors Create" that reads Motion Vectors and there is also a plugin that reads them in there as well. Pierre > > Thank you > > Est. > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > |
2 messages has been excluded from this view by a project administrator.
