From 090c5f7e7054a230b44d94c57f650d9c80e2f346 Mon Sep 17 00:00:00 2001
From: Alexandre Prokoudine FIXME. Optional. What happens when disabled? Won’t match the current timeline
-tempo: START THE SECTION WITH THIS: ARDOUR ALWAYS MATCHES CURRENT SESSION
-TEMPO, SO TEMPO RAMPS WILL WORK FOR CLIPS
+ When you load an audio clip into a trigger slot, Ardour applies some
+ heuristics to estimate its temo in beats per minute. If neither the file
+ name nor the metadata specify it, Ardour will use
+ minibpm to analyze
+ the file assuming it has a fixed tempo.
+
+ After estimating the tempo, Ardour will enable stretching for the clip
+ to make it match session's bpm at any given time. This means that should
+ session's tempo change over time (in either ramped or constant mode),
+ Ardour will re-stretch all audio clips to accomodate for that.
+
+ Disabling stretching when original clip's tempo doesn't match that of the
+ session will most of the times make the clip audibly go out of sync with
+ the beat.
+ Stretch modes:
+ Once stretching is enabled, you have several options how to apply it:
+Stretch
+Stretching
-
+ This is where Ardour displays the estimated tempo rounded to the closest + integer. You can progressively divide or mutiply by two whatever Ardour + thinks is the original tempo. +
+ ++ Supposing, session's tempo is currently 120bpm and original clip's tempo + is 90bpm. Stretching the clip to match session's tempo will make it sound + faster that it originally is. +
+ ++ If you divide the estimated clip's tempo by 2, you get 45bpm. Stretching it + back to 120bpm will make it sound faster. And multiplying the original + clip's tempo by 2 will make it 180bpm. Stretched down to 120bpm, the clip + will sound slower than it originally is. +