Hi Rui, I am using 0.9.35. I will compile you lastest version soon :-)
I am having problem with your tempo guessing code. I have Ardour generating Midi Clock and MMC. Qtr is set to Jack = None. In Qtractor settings I have set receive Midi Clock and receive MMC. In QjackCtl I have set connections from Ardour to Qtractor.
Bar 1 of my song is 117 BPM. The song slows down at the end. Starting from Bar 122 the tempo changes to 112, it drops -5 beats per bar, down to 87 BPM over 6 bars. I have the same tempo map loaded in Ardour as well.
Qtractor is not following the Tempo map. It is using quess the tempo over the mapped BPM value.
Also Qtractor over writes the tempo map value with the guessed values. This means I can not save any other changes to Qtractor in the mix-down stage, as it saves the wrong tempo map.
Question: Can Qtractor use the tempo map first before guessing the tempo ? Question: Can the tempo map be locked ?
PS, I love using Qtractor. Regards Dave M.
re. Midi Clock Sync
hi,
you cannot set a tempo map via MIDI Clock, sorry.
you can only set the current tempo of the qtractor timeline; also, tempo maps of different applications (Ardour vs qtractor) are not exactly shareable or set with MIDI Clock, not even with with JACK transport/timebase: the master, the one sending tempo information, often overrides the slaved (the receiving one).
moreover, the ardour tempo map maybe very loose or continuous with varying tempo across the timeline, while in qtractor tempo changes are discrete and strict to bar/measure locations.
all that to say in conclusion, there's no way to convert one tempo map (ardour) into another (qtractor), at least automatically via MIDI Clock or JACK timebase; the opposite (qtractor to ardour) might be possible tho idk.
cheers
Add new comment