v5.979 included this update:
Quote:
+ Tempo map: improve actions to set tempo from time selection when multiple bars are selected
|
which affects
* Create measure from time selection (detect tempo)
* Set project tempo from time selection (detect tempo)
Instead of setting a *single* measure as before, REAPER now tries to guess how many measures the user intended to select:
v5.978+dev0604 - June 4 2019, and seems to prefer bpm's around 100.
This was not a well-considered update.
* The names of these actions refer to a single "measure", not multiple "measures", so the names are now inaccurate.
* The alternative action "Create measure from time selection (new time signature)" already worked perfectly well with multiple measures, so the new behavior of the "(detect tempo)" version is not needed.
* When a user intends to create a single measure with slow bpm, REAPER now instead creates multiple measures.
Tempo Mapping - computes 2x value ??. If the tempo has more significant digits than are displayed in the Edit tempo dialog, it is difficult for the user to calculate the proper, slower bpm for a single measure.
* REAPER guesses badly: Even if the surrounding tempos are all 50bpm, and Project BPM = 50 in project settings, and I select precisely one measure, the action will insist on converting the selection to two 100bpm measures!
I therefore suggest that the action should revert to its original behavior.
Users that want to create multiple measures, should simply use "Create measure from time selection (new time signature)". (Perhaps the name of this action should be changed to refer to "measures".)