View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007854 | ardour | bugs | public | 2019-11-25 13:28 | 2019-12-15 20:41 |
| Reporter | juliend | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | macOS | OS | Mojave | OS Version | 10.14.6 |
| Product Version | 5.12 | ||||
| Summary | 0007854: MMC in locate command delay | ||||
| Description | The mmc in locate commands misinterpret the timecode infomation by adding 32 frames at 24FPS. this offset is constant depending on the framerate of the session. I use pro tools to send the mmc locate command. when i add a delay in pro tools of 32 frames on the mmc, the timecode in ardour is right after a locate command. But the mtc received by pro tools is also delayed. When i send a locate command from pro tools to reaper, reaper see the right timecode everytime. Ardour seems to interpret differently the timecode information. Or the MMC part have implemented differently than the 'standart'. | ||||
| Steps To Reproduce | Send MMC locate command from a daw to ardour and compare. | ||||
| Tags | MTC, timecode | ||||
