Thu May 13, 2021 5:38 pm
Some changes in the 17.2 API broke backwards compatibility again. Nearly all of my existing apps and scripts are affected.
used to return a string like "29.97 DF' for example. Now it returns a float of the frame rate only. The DF/NDF state is accessed using 'timelineDropFrame' or something like that.
This change makes a perfect sense. I wish it was implemented like this from the start. However for users that have hundreds of existing scripts in production this means that any script deriving DF/NDF is now broken.
A way to implement this change without affecting backwards compatibility would have been to leave 'timelineFrameRate' unchanged and add 'timelineFrameRateFloat.'
- Code: Select all
GetSetting('timelineFrameRate')
used to return a string like "29.97 DF' for example. Now it returns a float of the frame rate only. The DF/NDF state is accessed using 'timelineDropFrame' or something like that.
This change makes a perfect sense. I wish it was implemented like this from the start. However for users that have hundreds of existing scripts in production this means that any script deriving DF/NDF is now broken.
A way to implement this change without affecting backwards compatibility would have been to leave 'timelineFrameRate' unchanged and add 'timelineFrameRateFloat.'
www.metafide.com - DaVinci Resolve™ Apps