This video for Mixbus shows how one can use the grid tool to ramp up or slow down the tempo inside a bar (by clicking on a beat grid line inside the bar). I thought I had used this before with Ardour, but now it does not seem to work, and I did not find an alternative way.
Is that a feature only of Mixbus, or is it possible to do it with Ardour as well. (I am using the latest official version, 8.10.)
I often use it with 8.10 and it works great. However, the metronome should already be set to a tempo that comes closest to the material to be edited. An additional aspect is the starting point of the material to be edited at which the metronome is adjusted to the material from then on.
I often record my drums with the Tascam DR1 and then align it to the grid in the 8.10, and can then convert other tonal midi instruments.
Unfortunately, it does not work for me. I installed Ardour 8.10 (official) on another computer, and tried it both on the same session and on a newly created session. I have the same result:
Add tempo markers before the current bar and after.
Select the grid tool.
Left-click and hold on a beat grid line inside the bar (between tempo markers). A new tempo marker is created at the spot.
Dragging (still holding) creates a ramp up to the new tempo marker.
Here is a gif: https://luisfinotti.org/misc/ramp.gif (Even though it is only 1.2MB and the size limit is 4MB, I could not add it directly here, for some reason.)
Thatās doing precisely what it is supposed to do. If you just want a ramp between two existing tempo markers, right click on the earlier one and pick āRamp to nextā.
Thanks, @paul, for the reply, but I must be missing something.
On the video I linked above and on the third video/animation of the manual link you posted you can see how one can create a ramp between two tempo markers (without moving them in the time line) by clicking inside the bar and dragging. (The cursor becomes a double arrow.) That is what I cannot do.
I do not want to set different tempos and ramp manually. I want to do it visually, by matching the beats inside the bar, as in the video and animation from the manual.
Doesnāt the Grid tool cursor behave differently on Beat 1 (the thicker grid lines)? For me I tap click the metronome, highlight and drag all tracks so beat 1 of the song aligns with a thicker beat 1 grid line. This way I can drag beat 1 of every bar into alignment with the source and then drag the other beats (thinner grid lines) in between until they line up with the rest of the source beats within the bar.
That is what I am trying to do and failingā¦ So, it also works for you on 8.10 (as in this video from the manual)? I canāt imagine why it would not work for me.
Ardour 8.10, I have the same behaviour as Luis: when I click on or near a grid-line (thick or thin it does not matter) I get a new tempo marker, and no ramp. When I click between the grid-lines, nothing happens (also the cursor shows the normal pointer, not the double-arrow).
I cannot remember if in older 8-versions it worked.
Iāll need to recheck the version, I havenāt done this for awhile and I donāt recall if our Studio box is updated to 8.10 yet or not, I try to hold a good working version out there. Will post back.
After importing waves, it works in Win10 as demonstrated in the manual. Whatās new for me is that I can even implement a ritardando / accelerando with it. Letās see the next time I use it.
What if you import an actual sound file, approximate the tempo with tap then line up bar 1 beat 1 and then adjust bar 2 beat 1 so it creates a new tempo marker and its tempo differs from bar 1 beat 1 and then adjust in between?
In the GIF example there is no source material and the actual tempo has not been adjusted further on in the arrangement (itās 120/120). I could be wrong and donāt have time to test today but it seems to me if you create a new tempo value first on a bar line and then go back and adjust between after a new tempo has been set then it worksā¦?
I found that it works well, though the cursor doesnāt change to arrows.
Also the right click on the marker did not consistently produce the same options in the context menu, sometimes Ramp to next didnāt appear initially, but eventually after a few more tries it did show.
Using A8.10 on AVL21.3 up to date
Thanks @paul For this tip. I will defo try this
I found on my other drive which has AVL23 and A8.10 that the latest nvidia graphics drivers have caused flickering and jumping on the edit screen at different zooms.
Theres always something, Eh
Happy new year
Not to derail the original topic but this stood out to me, forgive the intrusion Iāll keep it briefā¦
So this issue appeared after an update or it has always been there? I ask because I recently updated my Video card to an nVidia 4080 SUPER on my development machine and it has been absolute rocket fuel on my Windows side and an absolute flaky Video artifact nightmare on the Linux side and I havenāt had an nVidia card for many yearsā¦ Anyway in my case I found that using the card without openGL compositing in AVL 23 (Enlightenment) has made things behave better so if you are testing AVL 23 on another drive with nVidia this might be something to tryā¦ Then again if you had no problems before it could be exactly what you think; a bad driver updateā¦ It seems kernel 6.12 and nVidia in general are not playing nice together in case you are trying 6.12ā¦
Anyway this is the compositing setting in Enlightenment that worked for my situation:
Here a screenshot, with some audio imported, with tempo markers at the bars, in āYā mode, with the cursor between grid-lines. If I click, nothing happens. If I go a bit near to a grid-line, the cursor changes and by clicking it will add a new tempo marker at the bar or at the quarter note mark.
(I have also tried all sort of modifier+click, just to be sure.)
(Also tried switching the session from āmusical timeā to āaudio timeā and back.)