Re: [Finale] Accidental Bug

2005-08-05 Thread Giovanni Doro
About the original subject, under my opinion, it isn't really a bug: if you 
imagine the situation between two different measure in different staves 
(last measure and first one), for G# you would see at the begin of new 
system a G tied to another (natural) G instead a G#.
My opinion is to repeat always the alteration between altered tied notes on 
different measures: I do it using cautionary accidentals plug-in but it 
can't remove the redundant accident: this is really an annoying bug!

Giovanni Doro
- Original Message - 
From: John Bell [EMAIL PROTECTED]
To: finale@shsu.edu
Sent: Monday, July 11, 2005 3:30 AM
Subject: [Finale] Accidental Bug


[FinMac 2005b]
There's a really annoying bug in Finale that's been there for years.
When a note with an accidental is tied to the next bar and then tied
again to another note in this same bar, the final note is given a
redundant accidental. For example, in 4/4: whole note with accidental
tied to half note tied to eighth note.

I reported this to Finale some years ago and they acknowledged that
it was a bug but have never fixed it. I'm so used to it that I
automatically hit * in these situations to hide the unwanted
accidental. Except when I forget. Sometimes they escape my proof-
reading, and are I believe rather confusing for the players as well
as being plain wrong.

John
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale 


___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-13 Thread Dennis Bathory-Kitsz
At 07:20 PM 7/12/05 -0700, Mark D Lew wrote:
On Jul 10, 2005, at 7:17 PM, Dennis Bathory-Kitsz wrote:

 And another one -- the bass-clef first-note speedy-entry bug. Type 
 along
 from the computer keyboard and at random the first note of some 
 measures
 will be way up high, as if it were displaying a treble clef. The bug's
 still there in 2005b.

This is correlated to what keystroke in Speedy you use to enter the new 
frame.  Some of them don't remember the clef properly.  The problem 
is cleared as soon as you use one of the keystrokes that rechecks.

I use the forward arrow as I'm touch-typing, right hand on the
numeric/arrow/control blocks and left hand on the right side of the
standard keyboard (starting at the 9-O-L column). I usually exit the frame
to clear this bug. What keystroke rechecks?

Pretty sad that the bug 
was never fixed.  I sometimes get the impression that speedy Qwerty 
entry doesn't get much attention.

Man, speedy is so fast for me, especially when composing. My autorepeat is
set to the fastest Windows allows (never fast enough for my taste), so I
know exactly how long to hold the up/down arrows to move the cursor
multiple positions.

(Far more annoying is the fact that 
the enter key does not act on the previous entry when the cursor is 
at the end of a frame, as just about every other Speedy key does.  That 
would save a ton of effort in entering piano parts that have lots of 
chords.)

Yes, I noticed that, but I tend to enter the additional notes after the
basic notes/rhythms of the measure are already filled in. Maybe I got into
that habit because of the behavior you mention ... it's been a long time,
and speedy was my default entry method when I started with Finale in
version 2.2 (I've never used simple or a Midi keyboard).

Dennis




___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-12 Thread Mark D Lew

On Jul 10, 2005, at 7:17 PM, Dennis Bathory-Kitsz wrote:

And another one -- the bass-clef first-note speedy-entry bug. Type 
along
from the computer keyboard and at random the first note of some 
measures

will be way up high, as if it were displaying a treble clef. The bug's
still there in 2005b.


This is correlated to what keystroke in Speedy you use to enter the new 
frame.  Some of them don't remember the clef properly.  The problem 
is cleared as soon as you use one of the keystrokes that rechecks.


I don't remember the exact details, but I researched it pretty 
thoroughly once upon a time.  I probably reported about it on this 
List, so if that openSubscriber.com archiving is as nifty as some here 
say it is, maybe someone can track it down.


That was at least a year ago, probably two.  Pretty sad that the bug 
was never fixed.  I sometimes get the impression that speedy Qwerty 
entry doesn't get much attention.  (Far more annoying is the fact that 
the enter key does not act on the previous entry when the cursor is 
at the end of a frame, as just about every other Speedy key does.  That 
would save a ton of effort in entering piano parts that have lots of 
chords.)


mdl

___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-12 Thread Mark D Lew

On Jul 10, 2005, at 6:58 PM, John Bell wrote:

Replying to myself: this bug doesn't always strike, but I have been 
unable to establish exactly what triggers it. Having experimented for 
the past five minutes, a surer way to elicit the bug seems to be:
(in 4/4): half note rest, half note with accidental tied to half note, 
tied to quarter note.


Trying that in Fin Mac 2k2, I don't have the problem.  I can't recall 
having any problem with accidentals on tied notes recently.  Maybe way 
back before v2000.


mdl

___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-11 Thread dhbailey

John Bell wrote:



On 11 Jul 2005, at 02:30, John Bell wrote:


[FinMac 2005b]
There's a really annoying bug in Finale that's been there for years. 
When a note with an accidental is tied to the next bar and then tied 
again to another note in this same bar, the final note is given a 
redundant accidental. For example, in 4/4: whole note with accidental 
tied to half note tied to eighth note.


I reported this to Finale some years ago and they acknowledged that it 
was a bug but have never fixed it. I'm so used to it that I 
automatically hit * in these situations to hide the unwanted 
accidental. Except when I forget. Sometimes they escape my 
proof-reading, and are I believe rather confusing for the players as 
well as being plain wrong.



Replying to myself: this bug doesn't always strike, but I have been 
unable to establish exactly what triggers it. Having experimented for 
the past five minutes, a surer way to elicit the bug seems to be:
(in 4/4): half note rest, half note with accidental tied to half note, 
tied to quarter note.




I just tried this in WinFin2005b and that bug doesn't appear on my 
computer. I wonder if it's a Mac-only bug.


--
David H. Bailey
[EMAIL PROTECTED]
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


[Finale] Accidental Bug

2005-07-10 Thread John Bell

[FinMac 2005b]
There's a really annoying bug in Finale that's been there for years.  
When a note with an accidental is tied to the next bar and then tied  
again to another note in this same bar, the final note is given a  
redundant accidental. For example, in 4/4: whole note with accidental  
tied to half note tied to eighth note.


I reported this to Finale some years ago and they acknowledged that  
it was a bug but have never fixed it. I'm so used to it that I  
automatically hit * in these situations to hide the unwanted  
accidental. Except when I forget. Sometimes they escape my proof- 
reading, and are I believe rather confusing for the players as well  
as being plain wrong.


John
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-10 Thread John Bell
On 11 Jul 2005, at 02:30, John Bell wrote:[FinMac 2005b]There's a really annoying bug in Finale that's been there for years. When a note with an accidental is tied to the next bar and then tied again to another note in this same bar, the final note is given a redundant accidental. For example, in 4/4: whole note with accidental tied to half note tied to eighth note.I reported this to Finale some years ago and they acknowledged that it was a bug but have never fixed it. I'm so used to it that I automatically hit * in these situations to hide the unwanted accidental. Except when I forget. Sometimes they escape my proof-reading, and are I believe rather confusing for the players as well as being plain wrong.Replying to myself: this bug doesn't always strike, but I have been unable to establish exactly what triggers it. Having experimented for the past five minutes, a surer way to elicit the bug seems to be:(in 4/4): half note rest, half note with accidental tied to half note, tied to quarter note.John___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-10 Thread Dennis Bathory-Kitsz
At 02:30 AM 7/11/05 +0100, John Bell wrote:
There's a really annoying bug in Finale that's been there for years.

And another one -- the bass-clef first-note speedy-entry bug. Type along
from the computer keyboard and at random the first note of some measures
will be way up high, as if it were displaying a treble clef. The bug's
still there in 2005b.

Dennis


___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-10 Thread Christopher Smith


On Jul 10, 2005, at 9:58 PM, John Bell wrote:



On 11 Jul 2005, at 02:30, John Bell wrote:


[FinMac 2005b]
There's a really annoying bug in Finale that's been there for years. 
When a note with an accidental is tied to the next bar and then tied 
again to another note in this same bar, the final note is given a 
redundant accidental. For example, in 4/4: whole note with accidental 
tied to half note tied to eighth note.


I reported this to Finale some years ago and they acknowledged that 
it was a bug but have never fixed it. I'm so used to it that I 
automatically hit * in these situations to hide the unwanted 
accidental. Except when I forget. Sometimes they escape my 
proof-reading, and are I believe rather confusing for the players as 
well as being plain wrong.
Replying to myself: this bug doesn't always strike, but I have been 
unable to establish exactly what triggers it. Having experimented for 
the past five minutes, a surer way to elicit the bug seems to be:
(in 4/4): half note rest, half note with accidental tied to half note, 
tied to quarter note.

\


Wow! Same version of Finale, I can't believe I've never noticed this 
before! Yet sure enough, there it is. Very consistent, too.


Christopher


___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] Accidental Bug

2005-07-10 Thread John Bell
On 11 Jul 2005, at 03:17, Dennis Bathory-Kitsz wrote:And another one -- the bass-clef first-note speedy-entry bug. Type along from the computer keyboard and at random the first note of some measures will be way up high, as if it were displaying a treble clef. The bug's still there in 2005b. Yes I've encountered that too, but it seems to rectify itself eventually without any intervention, whereas my bug doesn't.John___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale