kOfxPropIsInteractive
¶Indicates if a host is actively editing the effect with some GUI.
Type - int X 1
Property Set - effect instance (read only)
Valid Values - 0 or 1
If false the effect currently has no interface, however this may be because the effect is loaded in a background render host, or it may be loaded on an interactive host that has not yet opened an editor for the effect.
The output of an effect should only ever depend on the state of its parameters, not on the interactive flag. The interactive flag is more a courtesy flag to let a plugin know that it has an interace. If a plugin want’s to have its behaviour dependant on the interactive flag, it can always make a secret parameter which shadows the state if the flag.
kOfxImageEffectHostPropIsBackground
Indicates if a host is a background render.
Type - int X 1
Property Set - host descriptor (read only)
Valid Values - This must be one of
0 if the host is a foreground host, it may open the effect in an interactive session (or not)
1 if the host is a background ‘processing only’ host, and the effect will never be opened in an interactive session.
Your case is a good example. Here’s table of 4 types of plug-in
context with regards to licensing.
Rereading doc, doing it correctly license wise, note we do special case special case right
column here...
Interactive-only – e.g. Divergent Media, monitoring only |
Interactive front end with back-end server (e.g. BaselightX) |
Interactive + render-only (command-line) – e.g. Nuke -I or Fusion GUI (dongle) with render nodes. |
Render-only, example tuttleOFX no GUI software – command line only |
Maybe two concepts are being merged here.
One concept was knowing “render only / non-interactive” for licensing purposes (i.e., you pay different rate for interactive instances versus render farm instances). This is mostly handled already with kOfxPropIsInteractive, but maybe not all hosts use it.
The other concept is that for a given kOfxImageEffectActionRender, it would be nice to know if it was for:
For 1—3 an additional flag could indicate if playback is paused, scrubbing, or in playback.
That’s my take on it. What about other folks?
///d@
--
You received this message because you are subscribed to the Google Groups "ofx-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ofx-discussio...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ofx-discussion/0ed36b3f-56b3-4a81-84b9-e2a7d4b6730b%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ofx-dis...@googlegroups.com.
kOfxImageEffectPropInteractiveRenderStatus
To unsubscribe from this group and stop receiving emails from it, send an email to ofx-discussion+unsubscribe@googlegroups.com.

You are right that I confused PropIsInteractive and EffectPropInteractiveRenderStatus, not something I ever used.
Another idea is to create a Preview button and use that to set
kOfxParamPropCacheInvalidation
if supported or via an hidden param you change each time you pass
through Instance Changed to do the invalidation - this way one could
maybe rely on
EffectPropInteractiveRenderStatus to send frames out or not.
Pierre
To unsubscribe from this group and stop receiving emails from it, send an email to ofx-discussion+unsubscribe@googlegroups.com.
Sorry Mike - finally catching up here with some email.
Silhouette does this - if the frame is in the cache no render functions are called.
But here is a thought - could you not create a custom Interact and fetch the frame from there?
To unsubscribe from this group and stop receiving emails from it, send an email to ofx-discussio...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ofx-discussion/aa7aedd6-3022-4628-aeba-8fe928ee75ed%40googlegroups.com.