Differences

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

Link to this comparison view

Both sides previous revision Previous revision
timecode_format [2018/03/09 21:39]
gds
timecode_format [2018/07/17 19:20] (current)
gds
Line 9: Line 9:
 Developers should add this unique parameter to their plug-in only if the composition needs to know if the current project is using the "drop frame" timecode standard available for NTSC frame rates of 29.97 or 59.94. If a plug-in does not generate or process timecode this parameter may be omitted. Developers should add this unique parameter to their plug-in only if the composition needs to know if the current project is using the "drop frame" timecode standard available for NTSC frame rates of 29.97 or 59.94. If a plug-in does not generate or process timecode this parameter may be omitted.
  
-This parameter is never displayed ​in After Effects and Premiere Pro because ​the timecode format can be extracted by FxFactory through ​the SDK and fed to your compositionUnfortunately the FxPlug SDK lacks this capabilityhence requiring ​the user to manually adjust ​this parameter to match the current project setting^+This parameter is mapped to a boolean or numeric input in the composition. In After Effects and Premiere Prothe input will be true if the sequence is set to use drop-frame notation, false otherwiseIn Final Cut Pro and Motionthe input value is entirely dependent on what the user selects in the UI, since the FxPlug SDK currently does not provide an API to extract ​this information.
  
-Whether the timecode format is specified by the user or obtained transparently through the plug-in SDK, the resulting value is accessible through a new output in the **[[timing_info_structure|Timing Info Structure]]** patch called "Drop Frame Timecode"​. ​ The output can only be true when the current frame rate is either 29.97 or 59.94.+^ This parameter is never displayed in After Effects and Premiere Pro because the timecode format is extracted by FxFactory through the SDK and fed to the composition. Unfortunately the FxPlug SDK lacks this capability, hence requiring the user to manually adjust this parameter to match the current project setting. ^ 
 + 
 +Whether the timecode format is specified by the user or obtained transparently through the plug-in SDK, the resulting value is //​also// ​accessible through a new output in the **[[timing_info_structure|Timing Info Structure]]** patch called "Drop Frame Timecode"​. ​ The output can only be true when the current frame rate is either 29.97 or 59.94.
  
 In Final Cut Pro and Motion a "​non-drop frame" timecode format is always reported for frame rates that do not require or support the "drop frame" convention, regardless of the user selection in the host. In other words, "drop frame" timecode format may be on when the current frame rate is 29.97 or 59.94, but it would always be off for exact frame rates such as 24, 25, 30, etc. In Final Cut Pro and Motion a "​non-drop frame" timecode format is always reported for frame rates that do not require or support the "drop frame" convention, regardless of the user selection in the host. In other words, "drop frame" timecode format may be on when the current frame rate is 29.97 or 59.94, but it would always be off for exact frame rates such as 24, 25, 30, etc.
Trace: