Clarinet transposition unexpected behavior

General notation questions, including advanced notation, formatting, etc., go here.

Moderators: Peter Thomsen, miker

Post Reply
horn_guy
Posts: 12
Joined: Sun Apr 02, 2017 9:30 pm
Finale Version: Finale 27
Operating System: Mac

Post by horn_guy » Fri Jul 14, 2017 1:10 am

Hello, I had a problem when I was changing two clarinet parts from A to Bb transposition. Mac F25.4.

The original score I was working on had them in A due to the key of E concert. After seeing this problem I tried creating a new document with the wizard for just the two clarinets:
Both clarinets in A before move.png
Both clarinets in A before move.png (175.07 KiB) Viewed 6678 times
After changing clarinet II to Bb transposition, it was off by an octave.
Clarinet II in Bb after move octave off.png
Clarinet II in Bb after move octave off.png (173.32 KiB) Viewed 6678 times
The clarinet I part changed to Bb transposition without an issue.
Both clarinets in Bb after move.png
Both clarinets in Bb after move.png (177.09 KiB) Viewed 6678 times
I do not see an obvious reason for this behavior, can someone please suggest a possible cause? Thanks.


User avatar
motet
Posts: 8230
Joined: Tue Dec 06, 2016 8:33 pm
Finale Version: 2014.5,2011,2005,27
Operating System: Windows

Post by motet » Fri Jul 14, 2017 1:19 am

I think there are two Bb transpostions in the menu, one for clarinet, the other for bass clarinet, tenor sax, baritone horn, etc. You probably picked the wrong one.

horn_guy
Posts: 12
Joined: Sun Apr 02, 2017 9:30 pm
Finale Version: Finale 27
Operating System: Mac

Post by horn_guy » Fri Jul 14, 2017 1:28 am

My Finale skills are very rusty and anything is possible but there is definitely a different selection for bass clarinet which shows the M9 transposition interval. I had this occur only when changing the instrument to clarinet in Bb, but it is behaving differently for the two clarinets which is also a little mystifying.
Bass clarinet.png
Bass clarinet.png (136.83 KiB) Viewed 6672 times

User avatar
motet
Posts: 8230
Joined: Tue Dec 06, 2016 8:33 pm
Finale Version: 2014.5,2011,2005,27
Operating System: Windows

Post by motet » Fri Jul 14, 2017 2:34 am

If you want, attach your file.

horn_guy
Posts: 12
Joined: Sun Apr 02, 2017 9:30 pm
Finale Version: Finale 27
Operating System: Mac

Post by horn_guy » Fri Jul 14, 2017 2:41 am

File is attached.
Attachments
Clarinet test before.musx
(88.54 KiB) Downloaded 146 times

cairnsz
Posts: 2
Joined: Fri Jul 14, 2017 3:10 am
Finale Version: Finale 25
Operating System: Windows

Post by cairnsz » Fri Jul 14, 2017 3:15 am

I have had a similar issue with randomly changing clarinet transpositions. On two separate files, Finale magically changed my 2nd Bb clarinet part to have a G transposition. It was still notated correctly, but the playback was in the wrong key. All the other instruments in the ensemble were unchanged -- just the 2nd Bb clarinets.

I can only assume Finale does this because our clarinet players are going to play all the wrong notes anyway, so it just added a touch of realism.

;-)

(More directly to your question, I was never able to fix it in the file -- I had to copy everything into a new, clean file.)

User avatar
motet
Posts: 8230
Joined: Tue Dec 06, 2016 8:33 pm
Finale Version: 2014.5,2011,2005,27
Operating System: Windows

Post by motet » Fri Jul 14, 2017 4:11 am

I pulled down the Instrument pull-down in the Score manager and changed each to Clarinet in Bb and it did the right thing. However, it took a very long time--in fact I thought Finale had crashed and I killed it with the Windows task manager a few times. If I change from VST to MIDI output, that takes a very long time, but then the instrument change is quick. This may be a problem on my system, though, since I don't normally use VST. But I get the right transposition regardless. But I'm on Windows with 2014.5 and you're on the Mac with 25.

User avatar
zuill
Posts: 4418
Joined: Sat Dec 10, 2016 9:35 pm
Finale Version: Finale 2011-v26.3.1
Operating System: Windows

Post by zuill » Fri Jul 14, 2017 5:44 am

Works as it should for me. Must be a Mac only bug.

Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."

User avatar
Peter Thomsen
Posts: 6603
Joined: Fri Jul 25, 2003 6:47 pm
Finale Version: Finale v27.4
Operating System: Mac

Post by Peter Thomsen » Fri Jul 14, 2017 11:20 am

horn_guy,

If my testing is correct, the culprit is the program setting “Respect Instrument Ranges when Copying or Changing Instruments” (in Preferences - Edit), combined with using the utility Change Instrument to change the instrument from A Clarinet to Bb Clarinet.

De-select “Respect Instrument Ranges when Copying or Changing Instruments”, and the Change Instrument utility works as expected.

Instead of de-selecting “Respect Instrument Ranges when …” you can also change the staff transposition, in the Score Manager’s chiclet Instrument List.
But then you have to, manually change the instrument name from A to Bb.

By The Way:
Take a look at
View menu > Out-of-Range Notes > …
Is the sub-menu set to level {Beginner}?
For the Beginner level, Finale considers {low F#} to be Out-of-Range.
I would set Out-of-Range Notes to Off - and Save Preferences.
Mac OS X 12.6.9 (Monterey), Finale user since 1996

User avatar
motet
Posts: 8230
Joined: Tue Dec 06, 2016 8:33 pm
Finale Version: 2014.5,2011,2005,27
Operating System: Windows

Post by motet » Fri Jul 14, 2017 4:18 pm

Good sleuthing!

Perhaps one of our clarinetists will weigh in, but I think those low notes on a clarinet are easy for a beginner. "Out of range notes" and "respect instrument ranges when copying" have caused so much confusion and add so little value that perhaps they should be off by default.

horn_guy
Posts: 12
Joined: Sun Apr 02, 2017 9:30 pm
Finale Version: Finale 27
Operating System: Mac

Post by horn_guy » Fri Jul 14, 2017 6:48 pm

I had hopes but my Out-of-range-notes was set to advanced, I tried to turn it to "off" and it still jumped up an octave.

No worries, nothing that can't be worked around.

User avatar
Peter Thomsen
Posts: 6603
Joined: Fri Jul 25, 2003 6:47 pm
Finale Version: Finale v27.4
Operating System: Mac

Post by Peter Thomsen » Fri Jul 14, 2017 8:03 pm

horn_guy wrote:I had hopes but my Out-of-range-notes was set to advanced, I tried to turn it to "off" and it still jumped up an octave …
To avoid the octave jump, de-select “Respect Instrument Ranges when Copying or Changing Instruments”.

I do not think that the {Out-of-Range Notes} choice matters.
Mac OS X 12.6.9 (Monterey), Finale user since 1996

horn_guy
Posts: 12
Joined: Sun Apr 02, 2017 9:30 pm
Finale Version: Finale 27
Operating System: Mac

Post by horn_guy » Fri Jul 14, 2017 8:23 pm

There you go, that fixed it.

Thanks.

Post Reply