AcademySoftwareFoundation / AcademySoftwareFoundation/OpenTimelineIO
CMX 3600 adapter ignores M2 effects exported form Davinci Resolve
- Dominant language
- C++
- Stars
- 2k
- Forks
- 351
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 1
Description
### Incorrect Functionality and General Questions
Currently, M2 (CMX 3600) events only get parsed if SRC and REC durations are different. When we export Davinci Resolve EDLs with speed changes, the SCR time range is set as if played with normal speed and the effect is ignored. I wonder what's the correct behavior?
## Resolve EDL (24FPS)
```
TITLE: Test Timeline
FCM: NON-DROP FRAME
001 AX V C 00:00:00:00 00:00:04:19 01:00:00:00 01:00:04:19
M2 AX 048.0 00:00:00:00
* FROM CLIP NAME: SEQ_010_LAY_v001
```
Contributor guide
Research direction
Start at the CMX 3600 adapter and reproduce the Resolve EDL example with its M2 event. Trace how SRC and REC durations are interpreted, then determine the expected behavior for speed changes before identifying the relevant adapter tests or adding coverage. Done means the M2 effect is handled according to the agreed CMX 3600 semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100