|
|
6608700e82
|
no more need to update locations after a tempo map change
|
2021-08-13 12:51:33 -06:00 |
|
|
|
3b06ce6e67
|
remove 3 nutempo #warnings - use plugin (processor) time_domain() when creating AutomationLists
|
2021-08-13 12:51:33 -06:00 |
|
|
|
9d4d3908e6
|
remove some nutempo #warnings and fix up Location time domain API
|
2021-08-13 12:51:33 -06:00 |
|
|
|
a8f9f268b4
|
use integer division when computing tempo map positions from SMF data
|
2021-08-13 12:51:33 -06:00 |
|
|
|
97a3469972
|
use new Tempo API in two places where Tempo is explicitly constructed
|
2021-08-13 12:51:33 -06:00 |
|
|
|
b8a7de43b6
|
libtemporal: change Tempo API to ensure that the correct construtor is called
This could be probably be improved with an even more distinct ramped/non-ramped API
|
2021-08-13 12:51:33 -06:00 |
|
|
|
888239a834
|
remove dual (x,y) version of AutomationLine::view_to_model_coord()
The x-axis coordinate was never transformed or modified anyway (6.x just changed it
from double to integer and back again!)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
12855c1a83
|
fix types for MIDI source API, and remove unusued loop length member
|
2021-08-13 12:51:33 -06:00 |
|
|
|
4e761807bf
|
remove NUTEMPO warning
|
2021-08-13 12:51:33 -06:00 |
|
|
|
18e925e4ac
|
remove another NUTEMPO warning (potentially allows audio regions to have beat time position)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
d131a9aa12
|
remove debug output
|
2021-08-13 12:51:33 -06:00 |
|
|
|
c32de2355e
|
extra DEBUG_TRACE statement in tempo map grid computation
|
2021-08-13 12:51:33 -06:00 |
|
|
|
80f543dc17
|
fix missing conversions between samples & superclock for ruler display
|
2021-08-13 12:51:33 -06:00 |
|
|
|
e36affe3ae
|
remove another NUTEMPO #warning (use time_domain() of the processor)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
101a9e3a2c
|
remove another NUTEMPO #warning
For the foreseeable future, all audio region fades will be define in audio time
|
2021-08-13 12:51:33 -06:00 |
|
|
|
1a41e98c1c
|
improve comment for future readers
|
2021-08-13 12:51:33 -06:00 |
|
|
|
068cc4135f
|
remove another NUTEMPO #warning (see comment)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
f321dd4dac
|
remove NUTEMPO #warning (comment explains more)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
87dfef28f6
|
allow new locations creation from playhead to use default time domain
|
2021-08-13 12:51:33 -06:00 |
|
|
|
874a009d76
|
remove NUTEMPO #warning (comment explains more)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
9c1e88e675
|
remove NUTEMPO #warning (dealt with in caller)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
e4e953df14
|
no need to copy-construct here
|
2021-08-13 12:51:33 -06:00 |
|
|
|
7e6f0ea2bb
|
remove NUTEMPO warning
|
2021-08-13 12:51:33 -06:00 |
|
|
|
b39a771655
|
start using Editor::canvas_event_time(), initially just in the button release handler
|
2021-08-13 12:51:33 -06:00 |
|
|
|
6a44dcbdad
|
add Editor::canvas_event_time()
See comments in header for more
|
2021-08-13 12:51:33 -06:00 |
|
|
|
0114059c9d
|
nutempo warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
5074553f15
|
add Editor::default_time_domain()
Not 100% certain about the logic here, but at least the method exists now
|
2021-08-13 12:51:33 -06:00 |
|
|
|
af9bc21a07
|
nutempo warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
7cefa5fd7e
|
nutempo warning removing - Region::set_position_time_domain() works again
We might not allow this operation/method in the future
|
2021-08-13 12:51:33 -06:00 |
|
|
|
25375ee6f4
|
add timepos_t::set_time_domain() to potentially change time domains
|
2021-08-13 12:51:33 -06:00 |
|
|
|
6f861c63b5
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
5974f68250
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
84da57eb02
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
815028752e
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
24c84bff59
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
d7cb40f177
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
1ccebbf1f0
|
fixup Lua TempoMap bindings (these will likelyneed to expand in the future
This also likely breaks script back-compatibility for anything tempo-map related
|
2021-08-13 12:51:33 -06:00 |
|
|
|
57311c7643
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
65d5ddb357
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
c03b588011
|
nutempo #warning removal
|
2021-08-13 12:51:33 -06:00 |
|
|
|
125c20e148
|
manual fixups for recent rebase conflicts left in the wrong state (GUI edition)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
04688292d6
|
manual fixups for recent rebase conflicts left in the wrong state
|
2021-08-13 12:51:33 -06:00 |
|
|
|
5ea862ccc2
|
fix several more controls to take a time domain from their owner (Automatable)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
df37c62e37
|
mute controls starts with its stripable's time domain
|
2021-08-13 12:51:33 -06:00 |
|
|
|
ceba073065
|
pan controls starts with its route's time domain
|
2021-08-13 12:51:33 -06:00 |
|
|
|
e72ce1317e
|
record enable control starts with its route's time domain
|
2021-08-13 12:51:33 -06:00 |
|
|
|
dc66a963bb
|
use Automatable's time_domain() to set time_domain() for some controls at creation
|
2021-08-13 12:51:33 -06:00 |
|
|
|
d671dc0fa1
|
plugins use their route's automation time domain (GUI edition)
|
2021-08-13 12:51:33 -06:00 |
|
|
|
495cc1e4bc
|
plugins use their route's automation time domain
|
2021-08-13 12:51:33 -06:00 |
|
|
|
cd59f876f7
|
solo isolate control starts with its route's time domain
|
2021-08-13 12:51:33 -06:00 |
|
