Thurletta Brown-Gavins wrote:
From: [EMAIL PROTECTED]
Subject: [Finale] Hyperscribe - - annoying latency
I was wondering how I can keep Hyperscribe from putting an annoying
latency
into the recording off a keyboard.
Even when I record quarter notes, it puts a sixteenth note before each
one.
In other words, all the note events are moved over exactly 1/4 of a
beat too
late.
So far, I can't figure out how to prevent this latency.
Is there a way to easily correct the mistakes it put in after it's been
recorded? Or do I have to hand edit every single measure? In other
words, how do I
move the notes over 1/4 beat to the left in one mass edit operation?
Gosh, am I glad you asked this question! I've had this problem for years
and it is only when I have the "tap" really slo-o-o-ow and LOUD, and
take time to hit each note exactly where it should fall beatwise, that
anything comes out looking remotely the way I intended it. Can't wait to
hear the answer to your question...this is just a "me too" post.
Thurletta Brown-Gavins
Well there's a huge difference between latency and rhythmic accuracy.
What Thurletta is describing sounds to me like what I experience when
I'm not careful in how I set the quantization. It is important that you
tell the program (any program, actually, if you want notational
accuracy, even sequencers) what the shortest note value you are
attempting to play is. And even with that, if you don't hold the midi
key down for exactly one complete beat in 4/4 time, there's no way that
the program can tell that you meant to play a quarter note, when you
released the key closer to the 3rd 16th-note's place. So the program
has to decide which rhythmic subdivision you ended your note closest to
and then it notates that. So if you let the key up in the 3rd
16th-note's place, the program will notate a dotted-8th-note followed by
a 16th-rest unless you have told the program that the shortest note
value you're playing is 8th-notes, in which case it will calculate that
you released the note closer to the end of the second 8th-note's space
and will notate a quarter-note. The shorter the note values you tell
the program you're trying to enter, the more difficult the rhythmic
accuracy becomes for the program to calculate. Listening, we determine
the rhythms we hear by where the notes begin, and not so much by where
each note ends but the program can't think like that. It can only work
with the two pieces of rhythmic data it receives for each note you play:
where the note begins and where it ends, so unless you end it exactly
perfectly the program will notate exactly what you played rather than
what you intended to play. ThoughtNotator(tm) hasn't been invented yet,
but I'm sure the marketing department at MakeMusic is working hard on
the Finale developers to figure something out that they can make a big
splash out of for Finale2008.
That's a very different problem from what Bill describes, where every
note is appearing a 16th-note late.
--
David H. Bailey
[EMAIL PROTECTED]
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
