| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
RouteTimeAxisView
Now that we have VCATimeAxisView, this needed to be done, but it also potentially applied with automation
|
|
|
|
methods which add a new track/bus
|
|
remote control ID and "order keys" have been removed.
|
|
- probably not what the user wants,
unless snapping beats to timecode frames.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
frame_at_bbt()
|
|
audioclock tempo display.
|
|
|
|
|
|
|
|
|
|
|
|
based bbt->pulse conversions.
|
|
|
|
|
|
|
|
|
|
- its now a bbt ruler / marker lane thing with the constraint modifier.
|
|
|
|
|
|
- display prev tempo and tempo at mouse while dragging
- simplify ramp dilation somewhat.
|
|
|
|
|
|
constraint modifier dilates previous tempo.
|
|
fixes.
- revert failed frameoffset_t experiment
- caclulate meters using bbt
- fix tempo dilation when first tempo is ramped.
|
|
|
|
|
|
- the bbt of a meter cannot be changed by moving tempos or other meters.
e.g. tempo motion will be disallowed if it would cause a bbt overlap
|
|
right-click of associalted tempo
|
|
|
|
- a meter can be dragged using the constraint modifier, which
sets the previous tempo accordingly.
This could be added to the bbt ruler to allow direct dragging
of beats and bars, but the exact behavior of that is still
undecided. comments?
- also preliminary work on the necessary tempos locked to
audio-locked meters.
|
|
|
|
- audio-locked meters retain their 'home' bar position
unless altered by another metric.
this is an alternative to a more strict model
which isn't quite so flexible.
|
|
|
|
successive ramped tempos are the same :|
|
|
|
|
|
|
- meter has already been placed there.
|
|
|
