[Klaus Smedegaard Bjerre:]
>Tedious, but you could make a copy of the file. There you could
>delete all notes in the offending bar. Then listen if there is an
>artifact in the bar. If not add the notes one by one and listen after
>each entry, whether something wrong occurs. If so check if the
>offending note is a resultant pitch of the notes entered so far. If
>everything comes out well, then go on working from this file. The
>error then were a one-off corruption in the original entry process.
>
>If there is an artifact in the bad bar, my first attempt would be
>about deleting the whole stack of that bar. Then listen whether the
>artifact is rooted in a different bar. If not then insert a new bar
>and then re-enter the contents of the stack again. Most certainly not
>by copying from the original file.
>
>I am a retired teacher and without knowing any code it has been
>helpful to me treating the computer like a kid with learning
>disabilities: Cut up the process in its smallest bits and check after
>each step.
Hallo, Klaus. Thanks for your suggestion.
Should have thought of that - maybe would have in time.
I will try that, so thank you.
Michael Edwards.
_______________________________________________
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale
To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu
