Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
output_clamping [2012/11/21 17:49]
gds [Output Clamping in Other Hosts]
output_clamping [2013/08/22 21:09] (current)
Line 29: Line 29:
  
   * **After Effects** supports 32-bit floating point rendering but FxFactory plug-ins running in this host do not. High-precision renders may occur using a 16-bit integer format that is specific to After Effects, but the output is always clamped to legal range during these operations.   * **After Effects** supports 32-bit floating point rendering but FxFactory plug-ins running in this host do not. High-precision renders may occur using a 16-bit integer format that is specific to After Effects, but the output is always clamped to legal range during these operations.
-  * **Final Cut Pro 6** behaves identically to Final Cut Pro 7.+  * **Final Cut Pro 6** behaves identically to Final Cut Pro 7, and it is not expressly mentioned above because recent versions of FxFactory no longer support it.
   * **Final Cut Express 4** only supports 8-bit integer rendering, so output clamping is not required and thus this parameter is never displayed.   * **Final Cut Express 4** only supports 8-bit integer rendering, so output clamping is not required and thus this parameter is never displayed.
   * **Motion 3 and 4** give limited benefits for allowing out-of-range values during a high-precision render, thus the output clamping parameter is never displayed and the output is always clamped to legal range.   * **Motion 3 and 4** give limited benefits for allowing out-of-range values during a high-precision render, thus the output clamping parameter is never displayed and the output is always clamped to legal range.
  
Trace: