RPR_format_timestr_pos invalid for measures and beats
It seems it uses the first time signature change(meter and tempo) and so it can be invalid when a project changes values.
I guess it allow optional parameters to either specify the time location to use the meter at (e.g., 43s for 42 seconds in to the project where it gets the current meter at that position)
or to be able to specify the meter and tempo.
|