Thanks to both of you.
First of all, a solo performer will have a tendency to add a lot of rubato, true, but that doesn't mean that he/she will change the beat every second note. This becomes especially true with on orchestra, where rubato are less possible as a group. But in concerto for example, there may be moments when the soloist is alone, and enjoys his/her "freedom" with more rubato; while he/she won't be lingering freely on note when the orchestra is following.
I invite you to hear this song that I'm talkibng about https://www.youtube.com/watch?v=ZSOMXrdTGEE. I finished the timing with 74 sections, and I'm very happy with the result.
In the first 23 seconds for example, it's barely noticeable but the baet changes several times. You just can't keep one bpm, or it'l be ugly. I changed it 5 times in this period, with BPMs going from 154.589 to 155.844. There is no rubato, but still, a tempo irregularity.
To focus on the feature I ask for, it's very simple to implement, and to use, and won't disturb any one. It follows this way :
Instead of one "BPM" field, there would be one BPM field plus a "number of notes before next marked point". Moreover, there would be 2 check boxes, one for each field. And then, the mapper just checks the box he/she wants to be manually set. The other one is automatically computed. Simple as that
Cheers!
First of all, a solo performer will have a tendency to add a lot of rubato, true, but that doesn't mean that he/she will change the beat every second note. This becomes especially true with on orchestra, where rubato are less possible as a group. But in concerto for example, there may be moments when the soloist is alone, and enjoys his/her "freedom" with more rubato; while he/she won't be lingering freely on note when the orchestra is following.
I invite you to hear this song that I'm talkibng about https://www.youtube.com/watch?v=ZSOMXrdTGEE. I finished the timing with 74 sections, and I'm very happy with the result.
In the first 23 seconds for example, it's barely noticeable but the baet changes several times. You just can't keep one bpm, or it'l be ugly. I changed it 5 times in this period, with BPMs going from 154.589 to 155.844. There is no rubato, but still, a tempo irregularity.
To focus on the feature I ask for, it's very simple to implement, and to use, and won't disturb any one. It follows this way :
Instead of one "BPM" field, there would be one BPM field plus a "number of notes before next marked point". Moreover, there would be 2 check boxes, one for each field. And then, the mapper just checks the box he/she wants to be manually set. The other one is automatically computed. Simple as that
Cheers!