View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009013 | ardour | features | public | 2022-10-20 02:49 | 2022-10-20 18:15 |
| Reporter | redd | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | Microsoft | OS | Windows | OS Version | 10 |
| Product Version | 7.0 | ||||
| Summary | 0009013: BWF export with user-selected timecode | ||||
| Description | BWF maintains timecode information. Sometimes the timecode desired should track to the ardour transport timecode at export. But sometimes what is needed is for the timecode to match some other real-world value (e.g., the timecode found in a recorded LTC track for instance). I have been able to accomplish this by moving all of my tracks way WAAAY out in the ardour editor to the desired timecode. This works, but is annoying to work in as now there is all that space, and it's a little touchy having to get multiple regions sync'd to that. It would be better if we could define that the ardour transport, at its left-most position, corresponded to a particular user-named timecode (and then for the LTC generator to start at this value, and for BWF exports to use that value for the first recorded sample/frame, etc. Failing that, it may remain valuable to have an LTC timecode offset in preferences as currently is implemeted, but to also have an export offset. I consider this less useful as all times reported in clocks, the transport, etc., won't read to match those "real-world" external values. This would be handiest if I could also select an track containing LTC and have the first timecode frame value reported. Or alternatively an option to set the transport timecode offset from an LTC track (THIS!) | ||||
| Steps To Reproduce | N/A | ||||
| Additional Information | N/A | ||||
| Tags | 6.0 | ||||
