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
adding_an_object_tracker_to_templates [2019/11/27 16:01]
gds
adding_an_object_tracker_to_templates [2020/05/23 19:46] (current)
gds [Avoid multiple overlapping rows of on-screen buttons]
Line 80: Line 80:
   - The watermark generator should continue to appear at the very top of your layer hierarchy, so that the watermark is rendered above any other content. ​   - The watermark generator should continue to appear at the very top of your layer hierarchy, so that the watermark is rendered above any other content. ​
   - The custom UI generator can appear anywhere in the hierarchy, its layer disabled since your Motion Template does not need the output of the generator ((An alternative to disabling the Watermark Generator layer is to set its output opacity to 0%)).   - The custom UI generator can appear anywhere in the hierarchy, its layer disabled since your Motion Template does not need the output of the generator ((An alternative to disabling the Watermark Generator layer is to set its output opacity to 0%)).
 +
 +==== What about the watermark? ====
 +
 +There is more than one way to build a product, and more than one way to delegate the responsibility of rendering a watermark. Ultimately only one plugin, present in every Motion Template, should be rendering a watermark. And ultimately only one plugin in each Motion Template should have its "​Publish OSC" parameter enabled, so that you provide only one row of buttons to users. In the scenario described so far you should have:
 +  * One or two plugins in the FxPack, for custom UI and object tracking.
 +  *  The "​Requires watermark"​ option in the FxPack should be off.
 +  * The "​Requires watermark generator"​ option in the FxTemplates should be on.
 +  * Each Motion Template should contain an instance of the watermark generator, corresponding to the product you are working on, in a topmost 2D-only layer that is always as large as the frame dimensions for the current snapshot.
  
 ==== Avoid multiple overlapping rows of on-screen buttons ==== ==== Avoid multiple overlapping rows of on-screen buttons ====
  
-No matter what approach you choose, it helps to remember that only one of the plugins in your Motion Template should display a row of buttons on-screen. That role belongs to the object tracker, since its on-screen controls make it easier for users to access object tracking functionality. +No matter what approach you choose, it helps to remember that only one of the plugins in your Motion Template should display a row of buttons on-screen. That role belongs to the object tracker, since its on-screen controls make it easier for users to access object tracking functionality. ​\\ 
-Other plugins ​in the FxPack ​may **by default** create a row of on-screen buttons too. You need to instruct FxFactory to avoid this behavior ​by turning off the **Automatically display on-screen controls for licensing, help, etc...** for all but the object tracking filter:\\+As you may recall, ​plugins ​are allowed by Final Cut Pro to display any on-screen controls based on the value of the **Publish OSC** parameter inside the Motion Template. \\ 
 +\\ 
 +If you added a watermark generator to the same Motion Template that uses an object tracker plugin, remember to turn **off** its **Publish OSC** parameter. This prevents the watermark generator from automatically adding its row of buttons to the Canvas. 
 +If your Motion Template uses other native plugins from the same product (FxPack), remember that those other plugins too will **by default** create a row of on-screen buttons too. In this scenario, you need to instruct FxFactory to avoid displaying multiple rows of buttons on-screen ​by turning off the **Automatically display on-screen controls for licensing, help, etc...** for all but the object tracking filter:\\
 \\ \\
 {{:​fxtemplates-object-tracker:​disable-on-screen-buttons.jpg|}} \\ {{:​fxtemplates-object-tracker:​disable-on-screen-buttons.jpg|}} \\
 \\ \\
 **If you follow the approach described so far, the above option should remain on only for the filter in the FxPack that hosts the object tracking parameter.** **If you follow the approach described so far, the above option should remain on only for the filter in the FxPack that hosts the object tracking parameter.**
- 
-As you may recall, plugins are allowed by Final Cut Pro to display any on-screen controls based on the value of the **Publish OSC** parameter inside the Motion Template. //Another// strategy to avoid conflicts between on-screen controls from multiple plugins is to turn the **Publish OSC** parameter on only for the filter that hosts the object tracker. ​ 
  
 For better or worse, there is more than one way to solve the problems described in this document. What you end up doing is entirely dependent on how your product is structured. It helps to be familiar with Motion Templates and FxFactory to create the best possible user experience. When in doubt, contact us for assistance. For better or worse, there is more than one way to solve the problems described in this document. What you end up doing is entirely dependent on how your product is structured. It helps to be familiar with Motion Templates and FxFactory to create the best possible user experience. When in doubt, contact us for assistance.
Trace: