Cue: finish the stretch options

diff --git a/include/clip-stretch-options.html b/include/clip-stretch-options.html
index 52c29f1f96d1dafbdec1c8e9319903d0f91f2536..1b461a853639c185770d30150ce0016332b980a1 100644 (file)
--- a/include/clip-stretch-options.html
+++ b/include/clip-stretch-options.html
@@ -55,22 +55,15 @@
 
 <h2>Clip Length</h2>
 
-Measured in beats. Affects the bpm. FIXME
+<p>
+       This control allows adjusting the estimated tempo in a finer manner,
+       by changing the amount of beats it takes to play the clip in the selected
+       trigger slot. The change is immediately displayed in the BPM field above.
+</p>
 
 <h2>Length in Bars</h2>
 
-<p>It’s a hint to help you counting. FIXME</p>
-
-<p>1) when a file is loaded, we infer its bpm either by minibpm's estimate, a flag in the filename, metadata (TBD) or other means</p>
-
-<p>2) we assume the clip must have an integer number of beats in it  (simplest case is a one-bar loop with 4 beats in it)</p>
-
-<p>3) ...so we round to the nearest beat length, and set the tempo to *exactly* fit the sample-length into the assumed beat-length</p>
-
-<p>4) the user may recognize a problem:  "this was a 3/4 beat, which was rounded to 4 beats but it should have been 3"</p>
-
-<p>5) if the user changes the beat-length, then the tempo is recalculated for use during stretching</p>
-
-<p>6) someday, we will also allow the sample start and length to be adjusted in a trimmer, and that will also adjust the tempo</p>
-
-<p>7) in all cases the user should be in final control; but our "internal" value for stretching are just sample-start and BPM, end of story</p>
\ No newline at end of file
+<p>
+       This is an estimate of the clip's length as measured in bars for two
+       popular time signatures: 4/4 and 3/4.
+</p>