Orange stems?

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

Moderators: Peter Thomsen, miker

User avatar
MikeHalloran
Posts: 711
Joined: Mon Jan 02, 2017 2:56 am
Finale Version: 27
Operating System: Mac

Post by MikeHalloran » Mon May 29, 2017 11:18 pm

motet wrote:Please submit this to MM. Telling you to trash your document by running it through MusicXML seems thus irresponsible.
How does exporting via .xml "trash" a document? It doesn't. How is this somehow "irresponsible"? It isn't.

Software gets updated. Things change. That older templates are not going to be fully compatible is part of the process. At least they can be opened.

My Finale 1998 and earlier documents still open. Yes, I get orange stems but they print black. Using Graphics/Export Pages they are black in .pdf files.

There are things to get worked up about with Finale (the movie window comes to mind) but I can't see how this is one of them.
Mike Halloran

Finale 27.4.1, SmartScore X2 Pro, GPO5 & World Instruments
MacOS Ventura 14.5 (public beta); 2023 Studio M2 Ultra, 192G RAM, 8TB; 2021 MBAir M1
NotePerformer4, Dorico 5, Overture, Notion 6, DP 11, Logic Pro


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 » Mon May 29, 2017 11:21 pm

MusicXML is lossy. If you read the thread, you'll see that the bug exists in V25-created documents, so blaming it on importing from a old version is unfounded.

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 » Mon May 29, 2017 11:32 pm

-
Last edited by motet on Mon May 29, 2017 11:57 pm, edited 1 time in total.

User avatar
gogreen
Posts: 305
Joined: Fri Dec 02, 2016 12:50 am
Finale Version: Finale 27.4.1.146
Operating System: Mac

Post by gogreen » Mon May 29, 2017 11:45 pm

If I apply copy/paste. and enter Speedy on a measure in the Score, stems stay black. But when in the part, they turn orange.
Hmmm. Score and parts are fine for me. In which version of Finale did you create your test document. Mine was F2007.
Art
Finale 27
NotePerformer, GPO5, COMB2
MacOS Ventura 13.6.6
https://www.amazon.com/dp/B08BRHBTHT/ref=sr_1_2?dchild=1&keywords=%22Arthur+J.+Michaels%22&qid=1593016536&sr=8-2

User avatar
MikeHalloran
Posts: 711
Joined: Mon Jan 02, 2017 2:56 am
Finale Version: 27
Operating System: Mac

Post by MikeHalloran » Tue May 30, 2017 7:00 pm

motet wrote: so blaming it on importing from a old version is unfounded.
Yea... whatever floats your boat. You would certainly benefit by learning more about it before telling others that they are incorrect. Dolet 5, released 2010(?) supported MusicXML 2 and the plugin added that functionality to Finale 2007 or 2004 depending on the platform.

MusicXML 3.1 is due to be released next month or so along with a new version of the Dolet plug-in and Finale 25 update incorporating it. I was told I wouldn't be telling tales out of school if I posted this as it is being discussed elsewhere. It would surprise me if the next update to Dolet goes back to Finale 2007.
Mike Halloran

Finale 27.4.1, SmartScore X2 Pro, GPO5 & World Instruments
MacOS Ventura 14.5 (public beta); 2023 Studio M2 Ultra, 192G RAM, 8TB; 2021 MBAir M1
NotePerformer4, Dorico 5, Overture, Notion 6, DP 11, Logic Pro

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 » Tue May 30, 2017 7:43 pm

My understanding is that MM told michelp to export and then import both from Finale V25, not from Finale 2007, so you may be laboring under a misunderstanding. Perhaps he can clear it up.

But again, if you read this thread carefully, it looks to be a new bug in Finale 25--he was able to create a new Finale 25 document and cause the bug. So MusicXML, while it might get rid of the orange stems, is not germane, no matter what version of Dolet it is (exporting to and from MIDI would probably get rid of orange stems, too!). If you reread this thread carefully you see he tried MusicXML and reported
• My own libraries are absent (chord suffixes, expressions, staff styles etc...).
• Staves with zero line now have 5
• Some text blocks are missing, such as titles, some text inserts (Date, Hour...)
• Default rests are now selected. Not what I had in the original.
• All the metatools have to be recreated for each library (not a surprise)
• Page sizes are lost in Page Format
• Parts have to be redone
• Sounds have to be redefined in the ScoreManager
so I maintain it was a bit thoughtless of MM to suggest that rather than taking the bug seriously. As we've seen, a copy and paste is a much easier and less destructive solution.

Again, I think MusicXML is a great thing, but not as a catch-all work-around of bugs.

BuonTempi
Posts: 1306
Joined: Fri Aug 20, 2010 8:59 am
Finale Version: Finale 27
Operating System: Mac

Post by BuonTempi » Tue May 30, 2017 8:01 pm

motet wrote:Again, I think MusicXML is a great thing, but not as a catch-all work-around of bugs.
I suspect that Support offer the "XML-rinse" solution as an answer to many oddities in documents, where the alternative is "just put up with it until it gets fixed."

However, if they just offered the latter, there would be much more vocal complaint. They need to prefix the suggestion with "if you really want to make this go away...." and suffix with ".. but this might introduce other issues too".

User avatar
michelp
Posts: 2055
Joined: Fri Jul 25, 2003 3:35 pm
Finale Version: 27.4.1,26.3.1, Mont.
Operating System: Mac

Post by michelp » Tue May 30, 2017 10:20 pm

motet wrote:My understanding is that MM told michelp to export and then import both from Finale V25, not from Finale 2007, so you may be laboring under a misunderstanding. Perhaps he can clear it up.
That's correct. Originally, an older document showed the problem when opened in Finale 25. Then MM suggested the MusicXML procedure, which I applied within Finale 25.
motet wrote:But again, if you read this thread carefully, it looks to be a new bug in Finale 25--he was able to create a new Finale 25 document and cause the bug. So MusicXML, while it might get rid of the orange stems, is not germane, no matter what version of Dolet it is (exporting to and from MIDI would probably get rid of orange stems, too!). If you reread this thread carefully you see he tried MusicXML and reported
• My own libraries are absent (chord suffixes, expressions, staff styles etc...).
• Staves with zero line now have 5
• Some text blocks are missing, such as titles, some text inserts (Date, Hour...)
• Default rests are now selected. Not what I had in the original.
• All the metatools have to be recreated for each library (not a surprise)
• Page sizes are lost in Page Format
• Parts have to be redone
• Sounds have to be redefined in the ScoreManager
Correct, too. I have created a brand new document in Finale 25, and it showed the problem. I've thus reported this 3/4 days ago (Sunday) to MM support, and I am still waiting for a reply (I'll keep you posted).
motet wrote:...copy and paste is a much easier and less destructive solution.
True (thank you for that solution), with the downside that I mentioned : all edits are lost in the parts.
P.S. : I can follow your global point.
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua

User avatar
michelp
Posts: 2055
Joined: Fri Jul 25, 2003 3:35 pm
Finale Version: 27.4.1,26.3.1, Mont.
Operating System: Mac

Post by michelp » Thu Jun 01, 2017 10:05 pm

I promised to report about my exchanges with MM support. I have sent them 2 files, an old one imported into 25 and a new one made in 25.

In short, they acknowledged the orange stems problem is a bug, which they seemed to discover.
Excerpts from their replies :

"The problem is that Finale is considering these notes' stems to be unlinked from the score, but their behavior isn't in line with that...

... I went through these (files) and -- to my surprise -- I was actually able to make orange stems on a new Finale document on both of my computers here.
So what you've found is a bug in Finale that needs to be fixed.
I will write it up and submit it for our team to address...

...There will be no problem with them in the finished product -- you can print and they will print black the same as everything else....

...In the meantime, the fastest way is to correct that is to address each note individually. If you would like to get rid of the orange color, choose the Stem Direction Tool, CONTROL + click those notes and choose Relink to Score...

...It would definitely be best to avoid those steps that creates the stems to begin with, if possible. Then you wouldn't have to change them at all."


P.S. : the suggestion to re-link the orange stems one note at a time is of course not very convenient.
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua

TubaMan215
Posts: 1
Joined: Thu Dec 21, 2017 7:56 pm
Finale Version: Finale 25
Operating System: Mac

Post by TubaMan215 » Thu Dec 21, 2017 8:02 pm

To get rid of colored stems go to:

The Display Colors dialog box can be accessed in two ways:

Choose Finale > Preferences and select Display Colors.
Choose View > Select Display Colors.

Turn colors OFF.

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 » Thu Dec 21, 2017 8:45 pm

That seems like throwing out the baby with the bath water.

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 » Thu Dec 21, 2017 9:11 pm

I'm guessing that being a first time poster, he/she didn't read through the entire discussion to see what the real need was.

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

Post Reply