macros:example:timecodestarttimefrompalettefade
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
macros:example:timecodestarttimefrompalettefade [2022/02/04 09:35] – created icke_siegen | macros:example:timecodestarttimefrompalettefade [2022/02/04 10:05] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 8: | Line 8: | ||
^ remarks: | best used with Web API. Set the fade time via POST request and then fire this macro to set the start time. | | ^ remarks: | best used with Web API. Set the fade time via POST request and then fire this macro to set the start time. | | ||
- | This is a brilliant workaround for versions before Titan v14 when the TimecodeTime cast was introduced. | + | This is a brilliant workaround for versions before Titan v14 when the TimecodeTime cast was introduced. |
{{tag> | {{tag> | ||
Line 51: | Line 51: | ||
- [[: | - [[: | ||
- you can now input a time with the number keys and then fire this macro to transfer this into a timecode start time | - you can now input a time with the number keys and then fire this macro to transfer this into a timecode start time | ||
- | - in order to use this with WebAPI you do not need to copy this macro to a handle - it is enough to have it available | + | - in order to use this with WebAPI you need to copy this macro to a handle - albeit |
> For WebAPI workflow would be to set the Palette.Numeric.InputValue from WebAPI first and then run the macro. The seconds value will rollover into minutes and even hours so you can use a value of 120 for 2 minutes etc.. | > For WebAPI workflow would be to set the Palette.Numeric.InputValue from WebAPI first and then run the macro. The seconds value will rollover into minutes and even hours so you can use a value of 120 for 2 minutes etc.. |
macros/example/timecodestarttimefrompalettefade.1643967333.txt.gz · Last modified: 2022/02/04 09:35 (external edit)