On 18 Feb 2009 at 7:15, Noel Stoutenburg wrote:
> David W. Fenton wrote:
> > How, exactly, would a stuck key cause the inputting of the rhythm to
> > get the wrong pitch?
>
> I don't know the internals of Finale well enough to be able to answer
> the question, but I should note that in the case
David W. Fenton wrote:
How, exactly, would a stuck key cause the inputting of the rhythm to
get the wrong pitch?
I don't know the internals of Finale well enough to be able to answer
the question, but I should note that in the case I experienced, the key
was not stuck. I didn't bother to disas
The problem is definitely there in WinFin2006 - it happens to me very often.
Cheers,
Lawrence
Lawrenceyates.co.uk
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale
On Feb 17, 2009, at 8:07 PM, David W. Fenton wrote:
And I seem to recall it happening in more than just the single part
that has a bass clef -- I know it happens at least in alto clef (in
addition to bass), but I'm almost certain it's happened to me in
treble clef, too (but I can't vouch for tha
On 17 Feb 2009 at 21:03, Mark D Lew wrote:
> I
> forget exactly how it plays out, but at some point in its logic Speedy
> assumes a treble clef positioning when you're actually in bass clef and
> somehow that results in the notes appearing way too high. (It's not
> actually an octave, I think it's
On 17 Feb 2009 at 16:58, Noel Stoutenburg wrote:
> Well, perhaps my suggestion is implausible, perhaps not. My suggestion
> is caused by my own personal experience where I had a problem with a
> particular key combination in Finale not working as I expected, but in
> another application (runnin
I'm at work and only seeing today's messages, so I've missed the beginning of
this thread, but if this is the problem I think it is, I remember it quite
well. It's not actually an octave problem; it's a clef problem. I forget
exactly how it plays out, but at some point in its logic Speedy assume
>>Based on the above, it would be worth checking your computer keyboard to
>>see if there is some debris down inside.
>This may become my favorite response to drop into Usenet flame wars! RY
Let me add that I do realize your suggestion was serious and, in fact, I
occasionally run into a situati
>Based on the above, it would be worth checking your computer keyboard to
see if there is some debris down inside.
This may become my favorite response to drop into usenet flame wars! RY
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/ma
David W. Fenton wrote:
And if my keyboard is dirty, why don't I have any keyboard errors in
any other applications?
For that matter, it's not that they keyboard doesn't do what I tell
it -- the cursor is in exactly the right place vertically, it's just
that the note that comes out is wrong (t
On 17 Feb 2009 at 15:20, Noel Stoutenburg wrote:
> David W. Fenton wrote:
>
> > Actually, the reason it's happening to me a lot now is simply because
> > I'm using Speedy with computer keyboard for note entry exclusively,
> > whereas previously I only used MIDI keyboard -- and the problem never
David W. Fenton wrote:
Actually, the reason it's happening to me a lot now is simply because
I'm using Speedy with computer keyboard for note entry exclusively,
whereas previously I only used MIDI keyboard -- and the problem never
happened there, of course. I do recall it from many years ago b
On 17 Feb 2009 at 9:51, dhbailey wrote:
> Can you reproduce that behavior consistently in your version
> of Finale?
No, I can't.
> It sounded like it just crept into your setup
> recently, so if someone had asked you a couple of weeks ago
> if it had been squashed in your version, you could
David W. Fenton wrote:
On 16 Feb 2009 at 21:45, Richard Yates wrote:
I have a vague memory of Speedy octave errors at the beginning of
measures. I think I found that hitting keypad '0' twice (to exit and
reenter Speedy) minimized the hassle.
In general, deleting and then re-entering the note
In FinWin 2k6 it happens sometimes at the beginning of a measure without
any apparent reason.
If I can recall well it happens more frequently in bass clef staves.
David W. Fenton ha scritto:
On 16 Feb 2009 at 21:45, Richard Yates wrote:
I have a vague memory of Speedy octave errors at the
On 16 Feb 2009 at 21:45, Richard Yates wrote:
> I have a vague memory of Speedy octave errors at the beginning of
> measures. I think I found that hitting keypad '0' twice (to exit and
> reenter Speedy) minimized the hassle.
In general, deleting and then re-entering the note always fixes the
pro
I have a vague memory of Speedy octave errors at the beginning of measures.
I think I found that hitting keypad '0' twice (to exit and reenter Speedy)
minimized the hassle. I recall no other details, however.
>
>> I believe that there was some sort of clef confusion--you enter
>> treble, it gives
On 16 Feb 2009 at 23:33, Williams, Jim wrote:
> I believe that there was some sort of clef confusion--you enter treble, it
> gives bass, or some such, and I do believe it was fixed. I can't say that
> it has bitten me in 08 or 09.
But it doesn't matter what the clef situation is -- it happens in
f measures.
From: finale-boun...@shsu.edu [finale-boun...@shsu.edu] On Behalf Of David W.
Fenton [lists.fin...@dfenton.com]
Sent: Monday, February 16, 2009 10:36 PM
To: finale@shsu.edu
Subject: [Finale] Speedy wrong octave
I've been doing a lot of Speedy entry fr
I've been doing a lot of Speedy entry from the computer keyboard
lately (the PC I normally use had to have the hard drives rebuilt and
somewhere along the line, the sound card drivers got screwed up (I
think it's because I moved the sound card to a different PCI slot)
and now locks up Speedy wh
20 matches
Mail list logo
