[ubuntu-studio-users] Tempo changes in qTractor

David Sumbler david at aeolia.co.uk
Thu Sep 15 08:03:41 UTC 2016

On Thu, 2016-09-15 at 01:49 +0200, Ralf Mardorf wrote:
> On Thu, 15 Sep 2016 01:45:47 +0200, Ralf Mardorf wrote:
> > 
> > On Thu, 15 Sep 2016 01:31:02 +0200, Ralf Mardorf wrote:
> > > 
> > > A workaround could be to chose different meters, even
> > > asymmetrical
> > > meters seem to be possible.  
> > And I'm not thinking about 1/4 or 3/4, but e.g. 7/8, which
> > seemingly
> > is possible. I didn't test, but perhaps even 1/8 or 1/16 are
> > possible.
> PPS:
> Btw. when you mentioned tempi within a bar, my google search was
> https://www.google.de/?gws_rd=ssl#q=qtractor+tempo+ramp
> since this is the only reason IMO, when it makes sense to change
> tempi
> within a bar.

Thanks again for all your help.  I have read the manual, and even have
a printed copy here.

The problem is having to define the time in terms of beats, which are
largely irrelevant to my project.  I want to be able to define these
points at any time, regardless of the notional beat.  This can, of
course, be done in a midi file - I can do it using midicsv and then
csvmidi, but that is not nearly so easy to do as I hoped it would be in
qTractor - not easy, for instance, to try something and then undo it
and try a slightly different version.

Perhaps I need to experiment with other editors, which may have the
facility I want.

In case you're wondering why the midi beats are irrelevant, what I have
done (and want to do with quite a lot of other music) is to enter
tracks from a midi keyboard, with all the subtleties of timing that a
live performance can have and should have for certain types of music.
 I can then tweak details.  The actual "beats" in the midi file are
irrelevant except as a means of controlling the timing of the output -
the actual notes will only be approximately with those beats, or
perhaps not at all.


More information about the ubuntu-studio-users mailing list