On 4/23/2012 3:21 AM, Bruno Nicoletti wrote:
To do it properly there needs to be a 'set format' action for the effect, which could simply 
be piggy backed on the "set clip preferences" action. This would set the nominal 
display format for the effect, which is distinct from the region of definition. eg: it is 
NTSC format image, but we only has pixels defined for (10,10)->(100, 100).

Probably a worthwhile OFX extension for the other OFX host apps as well.

That would be nice  (height,widht,par), probably useful for generators too
It does not have to be animatable (should be settable but same across a clip duration) It's listed in Feature List of API right now under Spatial Format, I am all for bumping it up to OFX V1.4 candidates.

Pierre

b

On 20 Apr 2012, at 18:16, Pierre Jasmin wrote:

Another way as we don't really understand how to do that in Nuke either, what 
we do right now for OFX plugins that need to produce an output larger then the 
source is add an additional input as main input to plugin and connect to it a 
constant node or something and make that the correct wanted size (use that 
workaround to specify the output size). File a feature request :)

Pierre


On 4/19/2012 12:28 PM, Volker wrote:
You need a crop node following your OFX plugin.
There, set the new output size and enable reformat.

-Volker

On Thu, 19 Apr 2012 19:17:07 +0200
Víctor M. Feliz (MOTIVA)<vic...@motivacg.com>   wrote:

Thank you to everyone for the responses I've tried this but without luck
neither.

OfxStatus rst_getSpatialRoD( OfxImageEffectHandle  effect,
OfxPropertySetHandle inArgs,  OfxPropertySetHandle outArgs)
{
   // retrieve any instance data associated with this effect
   realStereoInstanceData *myData = getrealStereoInstanceData(effect);

   OfxTime time;
   gPropHost->propGetDouble(inArgs, kOfxPropTime, 0,&time);

   // my RoD is the same as my input's
   OfxRectD rod;
   gEffectHost->clipGetRegionOfDefinition(myData->sourceClip, time,&rod);
   rod.x2=rod.x2+(rod.x2-rod.x1); // TRYING TO MAKE X DOUBLE

   // set the rod in the out args
   gPropHost->propSetDoubleN(outArgs, kOfxImageEffectPropRegionOfDefinition,
4,&rod.x1);

   return kOfxStatOK;
}


On Thu, Apr 19, 2012 at 6:19 PM, Bruno Nicoletti<br...@thefoundry.co.uk>wrote:

The region of definition action should do it for you. It will change the
equivalent of the 'bbox' in Nuke. There is currently no way to change the
'format'.


http://openfx.sourceforge.net/Documentation/1.2/ofxProgrammingReference.html#kOfxImageEffectActionGetRegionOfDefinition

b

On 19 Apr 2012, at 14:06, Steven Booth wrote:

I confess, I’m not familiar with ‘OFX’ format, but if you need to output
a double-wide image, I would start by setting the format.width in
_validate, and then simply provide the extra pixels in each engine call.
Steve
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
--
Bruno Nicoletti,
Founder and Head Of Technology

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

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


_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev

Reply via email to