You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,30 @@
2
2
3
3
Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
4
4
5
+
## What's New in v2.75.0
6
+
7
+
The offline AAF reader now recovers retime ratios instead of only flagging them.
8
+
9
+
### Added
10
+
11
+
-**Motion Control speed recovery.** OperationGroup parameters are read: a
12
+
constant `SpeedRatio` emits `speedRatio` (play rate) and corrects `speed`, so
13
+
consumers reading only `speed` are no longer told 100 for a 175% clip. Variable
14
+
timewarps (multi-point speed maps) report `speedVarying: true` rather than a
15
+
fabricated number — the reader's honest-refuse contract extends to speeds.
16
+
Note the stored AAF rational is RECORD/SOURCE (Edit Protocol output-over-input),
17
+
the inverse of play rate; the reader emits play rate, verified against the
18
+
length identity (sourceLen = recordLen / |ratio|) and Avid's own speed maps.
19
+
20
+
### Fixed
21
+
22
+
-**Motion Control events inflated `recOut`.** Record advancement used the inner
23
+
source clip's length instead of the OperationGroup's declared record length, so
24
+
fast-motion clips claimed more record time than they occupy (and slow motion
25
+
claimed less). On a real 83-minute turnover this produced 40 spurious record
26
+
overlaps; with the declared length driving advancement, one remains — a
27
+
two-input blend genuinely sharing its record span.
0 commit comments