|
|
image.png (151,894 bytes) |
|
|
Update: I tried adding a BBT *after* having added a tempo ramp. 1. New Tempo at bar 17 (marker 1) 2. new tempo at bar 24, set to 200 BPM 3. edit marker 1, set ramped 4. add a BBT marker at bar 17 5. the tempo map get really confused: there are extra grid lines, and —although the markers are set to 120 to 200 BPM—the tempo goes up to 0000127:0000383 BPM. Screenshot from 2024-04-17 17-17-50.png (36,590 bytes) |
|
|
point 5 above should read "the tempo goes up to circa 383 BPM" |
|
|
Hi Piergi, I'm not a developer but I've been experiencing the same problem so I started to poke around in order to fix it. BBT markers are stored in the session file (session_name.ardour) under <MusicTimes> with the following format... <MusicTimes> <MusicTime sclock="1693440000" quarters="12:0" bbt="1|1|0" name="A"> <Tempo npm="120" enpm="60" note-type="4" type="Ramped" locked-to-meter="0" continuing="0" active="1"/> <Meter note-value="4" divisions-per-bar="4"/> </MusicTime> </MusicTimes> In the example above there is one BBT marker called A (name="A") and I set it to "Ramp to next" so it should slow down from 120bpm to 60bpm. I've found that in order to work as expected it needs to define a parameter called omega (I think it is some sort of rate of change). If I manually add omega="-4.4288548752834465e-10" at the end of the line <Tempo, then it works perfectly. The new section would look like this: <MusicTimes> <MusicTime sclock="1693440000" quarters="12:0" bbt="1|1|0" name="A"> <Tempo npm="120" enpm="60" note-type="4" type="Ramped" locked-to-meter="0" continuing="0" active="1" omega="-4.4288548752834465e-10"/> <Meter note-value="4" divisions-per-bar="4"/> </MusicTime> </MusicTimes> Of course, I'm not capable of deploying a solution but I hope this comment might be helpful. |
- Anonymous
