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: stephen j. <ste...@gm...> - 2013-10-08 16:32:46
|
Hi. All i want to create custom ofx bundle .How to create and any example or tutorial Thanks |
From: Gary O. <ga...@ge...> - 2012-05-23 18:45:00
|
yes, as a member you should sign up for all three (you're already signed up for the three old lists, right? This is just migrating to a new list server.) -- Gary ----- Original Message ----- > From: "Peter Litwinowicz" <pe...@re...> > To: "Developer oriented mailing list" > <ope...@li...> > Sent: Wednesday, May 23, 2012 1:28:36 PM > Subject: Re: [Openfx-developer] Moving OFX mailing list to google > groups > Are we supposed to sign up for all 3 if that's appropriate? Would > really like to avoid 3 lists to manage internally, and then trying > to pick the right one to post to, etc. > Pete > From: Bruno Nicoletti < br...@th... > > Reply-To: Developer oriented mailing list < > ope...@li... > > Date: Friday, May 18, 2012 6:32 AM > To: < Ope...@li... > > Subject: [Openfx-developer] Moving OFX mailing list to google groups > Hi All, > we are moving the OFX Association's mailing lists to Google Groups. > Thanks to Gary Oberbrunner for setting it up. > There will be three new lists... > One for paid up members of the association... > ofx...@go... > https://groups.google.com/d/forum/ofxa-members > One for announcements... > ofx...@go... > https://groups.google.com/d/forum/ofxa-announcements > And one for general discusions > ofx...@go... > https://groups.google.com/d/forum/ofx-discussion > Please use the web addresses to sign up to the appropriate group. > Thanks > -- > Bruno Nicoletti, Founder and Head of Technology > The Foundry > Email: br...@th... > Skype: brunonicoletti > Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 > Web: www.thefoundry.co.uk > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer -- Gary Oberbrunner |
From: Peter L. <pe...@re...> - 2012-05-23 18:21:07
|
Are we supposed to sign up for all 3 if that's appropriate? Would really like to avoid 3 lists to manage internally, and then trying to pick the right one to post to, etc. Pete From: Bruno Nicoletti <br...@th...> Reply-To: Developer oriented mailing list <ope...@li...> Date: Friday, May 18, 2012 6:32 AM To: <Ope...@li...> Subject: [Openfx-developer] Moving OFX mailing list to google groups Hi All, we are moving the OFX Association's mailing lists to Google Groups. Thanks to Gary Oberbrunner for setting it up. There will be three new lists... One for paid up members of the association... ofx...@go... https://groups.google.com/d/forum/ofxa-members One for announcements... ofx...@go... https://groups.google.com/d/forum/ofxa-announcements And one for general discusions ofx...@go... https://groups.google.com/d/forum/ofx-discussion Please use the web addresses to sign up to the appropriate group. Thanks -- Bruno Nicoletti, Founder and Head of Technology The Foundry Email: br...@th... Skype: brunonicoletti Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Openfx-developer mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openfx-developer |
From: Bruno N. <br...@th...> - 2012-05-21 10:35:23
|
You can create a google account tied to any email address here.... https://accounts.google.com/NewAccount Then use that for google groups. So you could make an account tied to your work email and that should all work fine. b On 21/05/2012 10:38, Phil Barrett wrote: > Hi Bruno > >> we are moving the OFX Association's mailing lists to Google Groups. >> Thanks to Gary Oberbrunner for setting it up. > > What's the recommended procedure for using this new system? > > My FilmLight email isn't a valid Google id, and I don't want to use any > of my personal Google accounts for OFX groups. If I create a new Google > account for my FilmLight identity, I'll never remember to log in and > check it. > > Maybe I'm missing something obvious... > > Phil -- Bruno Nicoletti, Founder and Head of Technology The Foundry Email: br...@th... Skype: brunonicoletti Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
From: Phil B. <ph...@fi...> - 2012-05-21 10:05:40
|
Hi Bruno > we are moving the OFX Association's mailing lists to Google Groups. > Thanks to Gary Oberbrunner for setting it up. What's the recommended procedure for using this new system? My FilmLight email isn't a valid Google id, and I don't want to use any of my personal Google accounts for OFX groups. If I create a new Google account for my FilmLight identity, I'll never remember to log in and check it. Maybe I'm missing something obvious... Phil -- Phil Barrett FilmLight |
From: Bruno N. <br...@th...> - 2012-05-18 13:58:14
|
Hi All, we are moving the OFX Association's mailing lists to Google Groups. Thanks to Gary Oberbrunner for setting it up. There will be three new lists... One for paid up members of the association... ofx...@go... https://groups.google.com/d/forum/ofxa-members One for announcements... ofx...@go... https://groups.google.com/d/forum/ofxa-announcements And one for general discusions ofx...@go... https://groups.google.com/d/forum/ofx-discussion Please use the web addresses to sign up to the appropriate group. Thanks -- Bruno Nicoletti, Founder and Head of Technology The Foundry Email: br...@th... Skype: brunonicoletti Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |
From: Philipp S. <ph...@fr...> - 2011-09-19 15:30:04
|
Hi there. I have a question regarding the c++ support wrapper and the ofx memory functions. OpenFX has two memory mechanisms. Managed memory using imageMemoryAlloc() the Memory Suite for the rest. Up until now I've been using managed memory for my image demands but completely ignored the memory suite. I never checked but assumed that the c++ wrapper would probably overload new and delete to use it. Now during refacturing I did check, realised it doesn't and did the overload myself. However there are some static constructs in the OFX namespace that are doing memory allocations before there is access to the memory suite. Now before I go and try to fix that I wanted to ask you guys. Is anybody actually using the memory suite? I don't assume many do as even the declaration of the allocate function in ofxsCore.h is wrong. The function is named 'alloc' while the implementation in the cpp file is called 'allocate'. Also what's really the point of the memory suite in the first place? What's the benefit of using it over the stdlib functions? I have to admit I'm very vague on what that could be. Does a host at any place have to free plugin reserved memory? Thank you, Philipp |
From: Pierre J. <ja...@re...> - 2011-04-25 21:15:22
|
Peter, Hope you are doing good, wish your company was an active member so we could pick your big brain :) Not trying to single you out here, but I vaguely remember back then you had an objection about when it's kosher to write params... (and my active mail box does not extend that far in the past) so I am thinking you probably have a strong opinion on this: Before we deprecate any flags (or adapt their meaning) it would probably be useful to have a best practice documentation note. I understand that some hosts might have some issues with param writing during the render call, so here's a simple scenario: A user presses a push button (or equivalent if not supported) and as a result of that event, the plugin wants to scan all the frames in the sequence (get and release images), write at each frame something in some parameters (e.g. the min and max values of each frame to keep the example simple). a. In which action is that allowed in your apps? b. Is it useful for you to know or not ahead that the plugin wants to do that ? If so when? c. Any other comments on that simple example? Mine is: Theorically there is sometimes an alternative which would be to store that in instance data and drop that in some custom param at OfxActionSyncPrivateData but that is also proving not reliable right now in many hosts. I am thinking if there was a clear documented note for that then maybe what|kOfxImageEffectPropInAnalysis| means would have a reference, and then at least it would have a reason to live (e.g.: to allow a plugin to bail out during initialization). Pierre On 4/21/2011 9:36 AM, Bruno Nicoletti wrote: > On 21 Apr 2011, at 17:32, Pierre Jasmin wrote: > >> On 4/21/2011 12:24 AM, Pierre Jasmin wrote: >>> On 4/20/2011 11:08 PM, Mike Wong wrote: >>>> Pierre, >>>> >>>> Thanks for the info. >>>> >>>> As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? >>>> >>> Actually I was working from memory instead of what the header files actually say and I see it says >>> that This feature is likely to be deprecated in future releases. So I am not clear. >>> >>> Right now here we only set param values during interact callback ( like in overlay.cpp example - gPropHost->propSetPointer(effectProps, kOfxImageEffectPluginPropOverlayInteractV1, 0, (void *) overlayMain); in describe action ). You can also maybe maintain instance data. >> I lied we of course also set params in actionInstanceChanged all over the place (particularly for hosts that don't support TypeBoolean and TypeChoice animation) >> >> I am also seeing kOfxParamPropPluginMayWrite I never noticed before, does not seem any host force us to tag that to each parameter that potentially can paramSetValue. >> Shouldn't that also be "likely to be deprecated in future releases" or there is something I am missing here? > The theory was that hosts might appreciate that property as a hint, however in practice it seems to be redundant. > > > -- > 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: Hybris <hy...@gm...> - 2011-04-21 20:28:56
|
>> 2) when defining a param only the name given in define*Param has >> effect while setScriptName has no effect > > What do you mean by 'no effect'? sorry i cannot reproduce it anymore forget about this |
From: Hybris <hy...@gm...> - 2011-04-21 20:22:14
|
> Well, it depends. Are you passing NULL or some uninitialized variable as > the param handle? during fetch i am not passing anything: OFX::Log::print("********************************before fetch scale"); rScale_ = fetchDoubleParam("scaleR"); if param "scaleR" has not been defined before (lets's say i have a typo there), the host crashes this is some log coming from OFX: ******************************************************************************** START mainEntry (OfxActionCreateInstance) Retrieved string property OfxImageEffectPropContext[0], was given OfxImageEffectContextFilter. Set pointer property OfxPropInstanceData[0] to be 0874FE90. Retrieved string property OfxImageEffectPropContext[0], was given OfxImageEffectContextFilter. ********************************before fetch scale Set pointer property OfxPropInstanceData[0] to be 00000000. STOP mainEntry (OfxActionCreateInstance) ******************************************************************************** START mainEntry (OfxActionBeginInstanceChanged) Retrieved pointer property OfxPropInstanceData[0], was given 00000000. ERROR : Instance data handle in effect instance properties is NULL! Retrieved string property OfxPropChangeReason[0], was given OfxChangeUserEdited. |
From: Bruno N. <br...@th...> - 2011-04-21 16:36:44
|
On 21 Apr 2011, at 17:32, Pierre Jasmin wrote: > On 4/21/2011 12:24 AM, Pierre Jasmin wrote: >> On 4/20/2011 11:08 PM, Mike Wong wrote: >>> Pierre, >>> >>> Thanks for the info. >>> >>> As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? >>> >> >> Actually I was working from memory instead of what the header files actually say and I see it says >> that This feature is likely to be deprecated in future releases. So I am not clear. >> >> Right now here we only set param values during interact callback ( like in overlay.cpp example - gPropHost->propSetPointer(effectProps, kOfxImageEffectPluginPropOverlayInteractV1, 0, (void *) overlayMain); in describe action ). You can also maybe maintain instance data. > > I lied we of course also set params in actionInstanceChanged all over the place (particularly for hosts that don't support TypeBoolean and TypeChoice animation) > > I am also seeing kOfxParamPropPluginMayWrite I never noticed before, does not seem any host force us to tag that to each parameter that potentially can paramSetValue. > Shouldn't that also be "likely to be deprecated in future releases" or there is something I am missing here? The theory was that hosts might appreciate that property as a hint, however in practice it seems to be redundant. -- 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: Pierre J. <ja...@re...> - 2011-04-21 16:33:34
|
On 4/21/2011 12:24 AM, Pierre Jasmin wrote: > On 4/20/2011 11:08 PM, Mike Wong wrote: >> Pierre, >> >> Thanks for the info. >> >> As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? > > Actually I was working from memory instead of what the header files actually say and I see it says > that This feature is likely to be deprecated in future releases. So I am not clear. > > Right now here we only set param values during interact callback ( like in overlay.cpp example - > gPropHost->propSetPointer(effectProps, kOfxImageEffectPluginPropOverlayInteractV1, 0, (void *) overlayMain); in describe action > ). You can also maybe maintain instance data. I lied we of course also set params in actionInstanceChanged all over the place (particularly for hosts that don't support TypeBoolean and TypeChoice animation) I am also seeing kOfxParamPropPluginMayWrite I never noticed before, does not seem any host force us to tag that to each parameter that potentially can paramSetValue. Shouldn't that also be "likely to be deprecated in future releases" or there is something I am missing here? > > > > || >>>> 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? >>> >>> The theory is if you need to write parameter values based on analyzing >>> the image content, some applications don't like you do that >>> at the actual render stage. >> >> >> >> ------------------------------------------------------------------------------ >> Benefiting from Server Virtualization: Beyond Initial Workload >> Consolidation -- Increasing the use of server virtualization is a top >> priority.Virtualization can reduce costs, simplify management, and improve >> application availability and disaster protection. Learn more about boosting >> the value of server virtualization.http://p.sf.net/sfu/vmware-sfdev2dev >> _______________________________________________ >> Openfx-developer mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openfx-developer >> > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > > > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer |
From: Fabien C. <fc...@qu...> - 2011-04-21 11:14:01
|
Bruno Nicoletti a écrit : > Exactly. > > Setting parameters during a render is a 'Bad Thing', as on some hosts it will either simply not work, or it will invalidate the output you just computed and cause a re-render, which will invalidate the output you computed, which will re-render and so on. > As it's written in the documentation that the property kOfxImageEffectPropInAnalysis "is likely to be deprecated in future releases", what the new solution to do this? Or maybe as it's only a reaction to an instance changed action, the host don't really need to know it? So we need nothing to set ? In practice this means that we need to have a button to update the internal values ? In the particular case, we want to have our analysis pass (frame independent) completly transparent to users (so we recompute the values first at each new render), but we want these values to be visibles to users (into disabled parameters). Is it a bad thing to modify, within the render, parameters declared with the property kOfxParamPropEvaluateOnChange = 0 ? Fabien |
From: Bruno N. <br...@th...> - 2011-04-21 08:36:22
|
Exactly. Setting parameters during a render is a 'Bad Thing', as on some hosts it will either simply not work, or it will invalidate the output you just computed and cause a re-render, which will invalidate the output you computed, which will re-render and so on. b On 21 Apr 2011, at 07:08, Mike Wong wrote: > > Pierre, > > Thanks for the info. > > As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? > >>> 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? >> >> The theory is if you need to write parameter values based on analyzing >> the image content, some applications don't like you do that >> at the actual render stage. > > > > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > 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: Bruno N. <br...@th...> - 2011-04-21 08:32:27
|
Hi, On 20 Apr 2011, at 20:46, Hybris wrote: > > 1) fetching a param that has not been defined crashes Vegas. I can't help with that one. > 2) when defining a param only the name given in define*Param has > effect while setScriptName has no effect What do you mean by 'no effect'? b -- 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: Pierre J. <ja...@re...> - 2011-04-21 07:38:49
|
On 4/20/2011 11:08 PM, Mike Wong wrote: > Pierre, > > Thanks for the info. > > As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? Actually I was working from memory instead of what the header files actually say and I see it says that This feature is likely to be deprecated in future releases. So I am not clear. Right now here we only set param values during interact callback ( like in overlay.cpp example - gPropHost->propSetPointer(effectProps, kOfxImageEffectPluginPropOverlayInteractV1, 0, (void *) overlayMain); in describe action ). You can also maybe maintain instance data. || >>> 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? >> >> The theory is if you need to write parameter values based on analyzing >> the image content, some applications don't like you do that >> at the actual render stage. > > > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > |
From: Mike W. <sm...@ci...> - 2011-04-21 06:08:57
|
Pierre, Thanks for the info. As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? > > 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? > > The theory is if you need to write parameter values based on analyzing > the image content, some applications don't like you do that > at the actual render stage. |
From: Pierre J. <ja...@re...> - 2011-04-21 05:37:04
|
On 4/19/2011 9:05 PM, Mike Wong wrote: > 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? The theory is if you need to write parameter values based on analyzing the image content, some applications don't like you do that at the actual render stage. > Thanks. > > Mike > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > |
From: Peter L. <pe...@ey...> - 2011-04-21 00:36:44
|
>> I'd suggest not doing that on _any_ host. Agreed. > indeed it's an error anyway so crash or not it does not really matter > but it seems odd to be able to crash an host that way Well, it depends. Are you passing NULL or some uninitialized variable as the param handle? I would hope most hosts would deal with NULL gracefully, but trying to do proper sanity checking on undefined handles isn't as easy. Fusion attempts to do it, but I'd be surprised if everyone does. FYI we use a magic value and type at the beginning of every handle, and check to see it's valid memory. For windows, say something similar to: if (!handle || IsBadReadPtr(handle, sizeof(*handle)) || (handle->m_Magic != FuOFXH_Magic) || (handle->m_Type != <appropriate type>)) return kOfxStatErrBadHandle; - Peter |
From: Adams, D. <Den...@am...> - 2011-04-20 22:48:20
|
Hybris: For Sony Vegas OFX host feedback, please use SCS...@am... Thanks. ///d@ ____________________________ Dennis Adams Sony Creative Software Inc. -----Original Message----- From: Hybris [mailto:hy...@gm...] Sent: Wednesday, April 20, 2011 3:11 PM To: ja...@re... Cc: Developer oriented mailing list Subject: Re: [Openfx-developer] are these buf in the host? 2011/4/20 Pierre Jasmin <ja...@re...>: > Sony like most hosts probably has it's own developer list for issues > specific to a particular host. not really, they still have the old directx plugins forum open and nothing for the new architecture they also not have published anything about ofx support, i.e. which version of the api is supported nothing for the home developer at least...i guess main plugins developers had access to some info > Depends on host, if the host has support for scripting is the theory here I > think ah i tought they were the same thing, this explains why the different behaviour ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Openfx-developer mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openfx-developer |
From: Hybris <hy...@gm...> - 2011-04-20 21:06:52
|
2011/4/20 Gary Oberbrunner <ga...@ge...>: > I'd suggest not doing that on _any_ host. indeed it's an error anyway so crash or not it does not really matter but it seems odd to be able to crash an host that way anyway i forgot to mention that i am using OfxSupport in case someone wants to investigate if the error is really in the host or in some layer between i wish i was able to test this better before writing but i could not find a way to debug it at runtime with the VS express cheers |
From: Gary O. <ga...@ge...> - 2011-04-20 20:38:30
|
----- Original Message ----- > From: "Pierre Jasmin" <ja...@re...> > On 4/20/2011 12:46 PM, Hybris wrote: > > 1) fetching a param that has not been defined crashes Vegas. I'd suggest not doing that on _any_ host. -- Gary |
From: Pierre J. <ja...@re...> - 2011-04-20 20:17:13
|
On 4/20/2011 12:46 PM, Hybris wrote: > I am still slowly developing a simple plugin while i learn the api in > my spare time. > I am targeting the only host i can put my hands on right now, Sony Vegas. > > I just crossed 2 odd behaviours. > I suspect that these are bugs in the host and i wish to have confirmation. > > 1) fetching a param that has not been defined crashes Vegas. Sony like most hosts probably has it's own developer list for issues specific to a particular host. > 2) when defining a param only the name given in define*Param has > effect while setScriptName has no effect Depends on host, if the host has support for scripting is the theory here I think > Thanks > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Openfx-developer mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfx-developer > |
From: Hybris <hy...@gm...> - 2011-04-20 20:11:05
|
2011/4/20 Pierre Jasmin <ja...@re...>: > Sony like most hosts probably has it's own developer list for issues > specific to a particular host. not really, they still have the old directx plugins forum open and nothing for the new architecture they also not have published anything about ofx support, i.e. which version of the api is supported nothing for the home developer at least...i guess main plugins developers had access to some info > Depends on host, if the host has support for scripting is the theory here I > think ah i tought they were the same thing, this explains why the different behaviour |
From: Hybris <hy...@gm...> - 2011-04-20 19:46:43
|
I am still slowly developing a simple plugin while i learn the api in my spare time. I am targeting the only host i can put my hands on right now, Sony Vegas. I just crossed 2 odd behaviours. I suspect that these are bugs in the host and i wish to have confirmation. 1) fetching a param that has not been defined crashes Vegas. 2) when defining a param only the name given in define*Param has effect while setScriptName has no effect Thanks |