[sib-access] Re: A tempo after ritard won't play

  • From: "Kevin Gibbs" <kevjazz@xxxxxxxxx>
  • To: <sib-access@xxxxxxxxxxxxx>
  • Date: Sun, 18 Oct 2009 10:45:30 -0500

All I put in was an a tempo from the tempo text options.  I didn't put a
hidden Q=80.  I just did that and hid it and it seems to be okay.
Thanks,
Kevin

-----Original Message-----
From: sib-access-bounce@xxxxxxxxxxxxx
[mailto:sib-access-bounce@xxxxxxxxxxxxx] On Behalf Of Dave Carlson
Sent: Saturday, October 17, 2009 7:07 PM
To: sib-access@xxxxxxxxxxxxx
Subject: [sib-access] Re: A tempo after ritard won't play


Kevin,

I wonder if your ritard line is too long, extending past where you put in 
the resuming tempo? Shorten it to the penultimate beat in that bar.

Or did I understand that you did put in a Q=80 back into bar 9, correct? If 
you didn't then of course that would be a problem. You need to put that back

in, and if you don't want it to show, them use the hide function.

Dave

----- Original Message ----- 
From: "Kevin Gibbs" <kevjazz@xxxxxxxxx>
To: <sib-access@xxxxxxxxxxxxx>
Sent: Saturday, October 17, 2009 17:01
Subject: [sib-access] A tempo after ritard won't play


Guys,
    I have a tempo of 80 at the beginning of a score.  The tempo lasts
through the end of bar 6.  At bar 7, I have a ritard for two measures and I
then want my original tempo of q to resume at bar 9.  I placed an a tempo in
the score at bar 9 but my playback is stil playing as if the ritard was stil
in effect.  How can I get my playback to respect this a tempo?  Is it
possible?  Do I have to put up with the rest of the score playing at the
wrong tempo? Kevin

If you wish to unsubscribe, send a blank message
with the single word, unsubscribe - in the Subject line to:
sib-access-request@xxxxxxxxxxxxx 

If you wish to unsubscribe, send a blank message
with the single word, unsubscribe - in the Subject line to:
sib-access-request@xxxxxxxxxxxxx

If you wish to unsubscribe, send a blank message
with the single word, unsubscribe - in the Subject line to:
sib-access-request@xxxxxxxxxxxxx

Other related posts: