Ticket #767 (assigned planned)
basic internal Timecode support
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | lesser | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | integration design data interfaces |
| Cc: | Blocked By: | #177, #744, #745, #750, #768 | |
| Blocking: | #748, #766 |
Description (last modified by ichthyo) (diff)
define the basics how timecode is represented internally and the connection to internal time values in general
Change History
comment:2 Changed 13 months ago by ichthyo
- Description modified (diff)
- Blocked By 177, 744, 745, 750 added
comment:3 Changed 13 months ago by ichthyo
- Status changed from new to accepted
- Blocked By
already in work since last December, low-priority, ongoing
comment:4 Changed 12 months ago by ichthyo
- Status changed from accepted to assigned
- Type changed from todo to planned
did quite some work on sub-tasks here, so the foundations are in place now.
Still to do
- refactor the timecode widget to use the new timecode framework; esp. use Digxel for display
- integrate SMPTE-drop-frame into the existing timecode
- implement a quantised timespan
Pushing these to future...
Note: See
TracTickets for help on using
tickets.
