[Rwp] Osara or reaper bug with bpm edit field it's only readable

[James Teh]

Just tested with REAPER 5.03. The BPM field in that dialog is read-only 
in 5.03 also; I see no change.

On 9/04/2016 2:44 PM, Efren Chavez wrote:
> Hey guys. I just ran into a problem when setting time measure and bpm.
> Not sure if it's an oasara or a reaper bug introduced in 5.16 or 5.17
> because  using the set project tempo, from time selection, “new time
> signature” worked properly in 5.15. I tried reinstalling 5.15 and
> osara wasn’t functioning, so I updated back up to 5.18. Using osara
> 2016 pre36.
> Here is what is happening.
> I set the start selection at bar 1.
> Page down to bar 3 and set selection end
> Hit context menue followed by S till I get to set project tempo from
> selection, new measure.
> Here is where it gets iffy.
> I set time signature to 8/4.(everything is fine there)
> Set to one bar.
> Tempo will double, which makes senseand expected. That happened
> before, but the difference is that the bpm edit field is only readable
> in 5.18.
> I normally will set that anywhere from 130 to 160.
> Can someone who has an earlier than 5.16 reaper version test that?
> Also, do you think it’s a reaper update bug as I suspect?If so, I will
> report that to their tech support.
> I noticed this with reaper v5.17. I skipped 5.16.
> Thank you.
>
>
>
>

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie at nvaccess.org