View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009939 | ardour | bugs | public | 2025-05-30 13:33 | 2025-05-30 14:14 |
| Reporter | bgribble | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Debian GNU | OS | Linux | OS Version | (any) |
| Product Version | 8.12 | ||||
| Summary | 0009939: MTC (QFRAME) events not sent to MIDI tracks | ||||
| Description | MIDI time code events are not sent to MIDI tracks when the "MTC out" source is selected in the MIDI track source grid. | ||||
| Steps To Reproduce | * Make sure "Preferences > Transport > Generate > Enable MTC Generator" is on * Add a MIDI track to a new session * In the track's MIDI source grid, enable "MTC out" * Open the MIDI Tracer and select the track's MIDI input to trace * Click the Play button Expected: A stream of MTC Quarter events Actual: No events For comparison, if you select "MTC out" in the tracer, you do see the events as expected. | ||||
| Tags | No tags attached. | ||||
|
|
This is likely a won`t fix. Timecode generators and masters are outside the session's process graph. Their data is not [usually] available to tracks and busses. Besides one cannot display or edit MTC on an Ardour Track to begin with.. Is there any specific use use-case that you try to accomplish by routing MTC to a MIDI track? Perhaps there is a better solution for that use-case.. |
|
|
I noticed this problem when implementing a plugin that wants to track the session's current time pointer for use in a generic patching system. No specific use case, just decoding the data that is indicated to be available from the host. TBH, in a plugin, the SMPTE time is less useful than the bar:beat clock time (which is needed if you want to implement a sequencer that tracks the song position) and I can track bar:beat time from MIDI Clock events, which do work as expected. I included MTC in the time decoding process, it behaves as expected when connected to the external-facing "MTC out" port on Ardour, and the "MTC out" is advertised in the source grid as a source of events, so it seemed like a bug. |
