Thanks for comment.
If increasing number of bars into the same time space, number of beats increase and tempo should too.
Now it’s the reverse - tempo is lowered.
And I found if using the scale factor in dialog as presented - and multiply by that - it becomes like Process Tempo do.
But if I divide by the scale factor shown - it becomes as manual calculation tells it should be.
Original tempo can be set to anything - but it is 100 now as I did this test and 4/4 is signature.
Length is 01:01.739s meaning 61.739s. Locators show 00:00:00.0 and 00:01:01.739.
Seconds should stay the same . I want bars to change into the space chosen - new range in dialog is that I increase bars to 32.
Tempo become 80.39 in process tempo and should be 124.395.
128 beats/61.739 seconds=2.073243817 beats per second * 60 = 124.395 bpm.
You have in dialog start at 1.1.1.0 bars+beats.
End at 25.2.3.x(don’t remember exactly)
New range show same as End from start.
You increase New Range to be 33.1.1.0 - length shown become 32.0.0.0.
Pressing Process - you expect End to become 33.1.1.0 as you selected as new range.
And if calculations reverse the scale factor this would be the case.
Instead it recalculate dialog fields to correspond to wrong tempo calculation it did.
You choose new range length to be 32 bars - then that stays as you do process - and other fields as End change.
This makes sense to me, and very useful - if it worked that way.
What dialog in Process Tempo do now - length become 20.2.2.212 when you selected you wanted 32.0.0.0 - that makes no sense to me, not in any context.
If somebody can confirm, please.
Simplest test would be to set locators to 2 bar range, open dialog and say this should be 4 bars - and process. It will adjust previous node to half tempo of now, instead of correct double tempo - now squising in double amount of bars in the same space. Undo works for this operation so easy to do.