Muting top staff causes tempo marking to be ignored

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

Moderators: Peter Thomsen, miker

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

Post by motet » Sun Apr 08, 2018 12:52 am

Using a tempo mark in the Tempo Marks category with the score list set to Top Staff, if I mute the top staff or solo one of the other staves in the Score Manager, the tempo mark then seems to be ignored. I can work around this, but is this really the way it works?


Vaughan
Posts: 267
Joined: Wed May 12, 2010 2:50 pm
Finale Version: Finale 25
Operating System: Mac

Post by Vaughan » Sun Apr 08, 2018 10:04 am

I remarked about this annoying and unexpected behaviour quite some time ago. It's works the same way on the Mac side. Shall we call it a 'feature'?
Vaughan

Finale 3.2 - 26, Sibelius 4 - 7, Dorico 2.2
Tobias Giesen's plugins, full version, Robert Patterson plugins, Jari's plugins
MacOS 10.14.2
MacPro (2016) 16 GB, MacBookPro (2018) 16 GB

Amsterdam

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

Post by motet » Wed Apr 11, 2018 4:21 pm

I reported this to MM who said they couldn't reproduce it, and I couldn't either, trying from scratch. Perhaps it's peculiar to my file (attached)? But you say you've experienced it too, Vaughan?

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 » Wed Apr 11, 2018 4:54 pm

This is just another manifestation of a very old programming error. I'm not surprised MakeMusic is not aware of it. They have been informed by me regarding this, but under slightly different circumstances. They don't seem to have a very comprehensive grasp on how their own program works.

I reported this regarding Swing Playback not being applied to all the staves. In this case, however, either soloing a staff (as you did), or muting the upper staff, it defeats the expression, which is applied to the top staff in the score and each of the parts. If you modify the Score List to also include all staves in the parts (in the right column), then muting the upper staff or soloing another staff will not interfere with the working of the tempo expression.

Again, I shake my head to thing the programmers are just not getting it. They might need to take some time to come to grips with this. I hope you report back to them about this. You can use my name, and remind them of my prior reports.

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

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

Post by motet » Wed Apr 11, 2018 6:13 pm

Thanks, Zuill.

They are telling me to run my file through MusicXML, which I'm unwilling to do since I did a fair amount of tweaking. I can of course set the playback tempo in the playback controls to match the tempo of the piece. My wish to solo was to record "part tracks" for an amateur chorus, so that's what i did. But I also like to see bugs fixed, not just get around them for myself.

Are you able to create a simple file from scratch which exhibits the problem? I was unable to do so.

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 » Wed Apr 11, 2018 7:34 pm

I believe it is a design issue, which I can duplicate in a new file. The issue is revealed when you have HP set to None. If yopu set your file to HP Standard, then it should work.

However, you can modify the Score List as I have suggested, and the expression will be recognized, even with HP set to None. No need for XML.

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

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

Post by motet » Wed Apr 11, 2018 7:53 pm

Ah, Human Playback was covering up the bug! Thanks.

What seems to get MM's attention is if they can recreate it from scratch themselves, so I've given them instructions to do that. That way, they can't dismiss it as a problem with preferences file or the file itself. I'll let you know what they say.

User avatar
miker
Posts: 6009
Joined: Fri Mar 13, 2009 4:28 pm
Finale Version: Finale 27.4
Operating System: Mac

Post by miker » Wed Apr 11, 2018 8:37 pm

I’ve never understood why the swing expression only applies to the top staff, unless you edit the Staff list. That’s right up there (for me) with why the format of additional pages doesn’t follow existing pages, without changing the page layout settings.
Finale 27 | SmartScorePro 64
Mac OS 13.2.1 Ventura
Copyist for Barbershop Harmony Society

Vaughan
Posts: 267
Joined: Wed May 12, 2010 2:50 pm
Finale Version: Finale 25
Operating System: Mac

Post by Vaughan » Wed Apr 11, 2018 8:51 pm

Motet, your file exhibits this behaviour for me, too. I looked through my past cases to MM and apparently I also reported this 4 months ago. I even sent them a file which demonstrated the problem but their response, as usual, was that they couldn’t reproduce the problem and that I should reset my preferences. Apparently I gave up at the time and didn’t persue the issue any further.
Vaughan

Finale 3.2 - 26, Sibelius 4 - 7, Dorico 2.2
Tobias Giesen's plugins, full version, Robert Patterson plugins, Jari's plugins
MacOS 10.14.2
MacPro (2016) 16 GB, MacBookPro (2018) 16 GB

Amsterdam

User avatar
David Ward
Posts: 814
Joined: Thu Dec 01, 2016 4:48 pm
Finale Version: F 25.5 & 26.3
Operating System: Mac

Post by David Ward » Wed Apr 11, 2018 9:10 pm

I've certainly encountered this in the past, but I can't remember the details.
Finale 25.5 & 26.3
Mac 10.13.6 & 10.14.6

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

Post by motet » Fri Apr 13, 2018 6:32 am

MM Support was able to reproduce the problem and said, "I see we do have a bug report for this problem, so I'll link this ticket to the bug report."

Vaughan
Posts: 267
Joined: Wed May 12, 2010 2:50 pm
Finale Version: Finale 25
Operating System: Mac

Post by Vaughan » Fri Apr 13, 2018 10:28 am

Gee, I'm glad I didn't reset my preferences as MM suggested. :P
Vaughan

Finale 3.2 - 26, Sibelius 4 - 7, Dorico 2.2
Tobias Giesen's plugins, full version, Robert Patterson plugins, Jari's plugins
MacOS 10.14.2
MacPro (2016) 16 GB, MacBookPro (2018) 16 GB

Amsterdam

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

Post by motet » Fri Apr 13, 2018 4:52 pm

It sounds like they have no good way of checking for already-known bugs when someone presents a problem.

User avatar
miker
Posts: 6009
Joined: Fri Mar 13, 2009 4:28 pm
Finale Version: Finale 27.4
Operating System: Mac

Post by miker » Fri Apr 13, 2018 8:32 pm

motet wrote:It sounds like they have no good way of checking for already-known bugs when someone presents a problem.
They've never had one in the past. Why should now be different?
Finale 27 | SmartScorePro 64
Mac OS 13.2.1 Ventura
Copyist for Barbershop Harmony Society

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

Post by motet » Fri Apr 13, 2018 9:12 pm

Fortunately, I neither trashed the preferences file nor ran my piece through MusicXML.

Post Reply