Add new comment

wholly cow! we're getting somewhere now! :(...

yes, it seems that changing the baseline tempo (eg. from the toolbar) and while the playhead is located somewhere between the beginning and the first tempo map change node, then automation points gets into trouble... :S

is that the only case? or are there something else?
cheers

ps. ok. got it! as a matter of fact (again), automation curves only get rescaled correctly over _two_consecutive_ tempo changes and only... all gets lost over the third and beyond (yes, the first base counts as one in this rule...) gotta fix that :!o.O(...)

pps. hopefully fixed in qtractor >= v0.9.36.9git.08960f