Coda Finale - 2005music notation: create, edit, print sheet music |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| Version 2005: | |||||
| Overall Rating: | Features: | Support: | |||
| Ease of Use: | Quality / Stability: | Price: | |||
Key to Types of Feedback:
Reviews
Troubleshooting
Usage Tips
Developer Notes
Commentary
Featured Reviews
And another flaw - Version: 2009b.r3, 9/26/2009 10:11PM PST
dgatwood
Not so much a bug so much a a missing critical feature. When doing multiple parts in a single stave in the score and breaking it out into separate parts in the linked parts, there doesn't appear to be any per-part control over the position of rests. This means that if you need to modify the default position of the rest to avoid a collision with the other part in the score, you'll end up with the rest in entirely the wrong place in the linked part. In short, you merely have a choice about which version looks bad.
And several more significant bugs - Version: 2010, 9/25/2009 11:18PM PST
(1 of 1 users found this comment useful)
dgatwood
1. When doing part splits from one staff into multiple separate parts, there's no way to specify that you want things from two layers. So you can't specify that you want layer 1 and layer 3 (cue notes) together in one part. Instead, you have to clumsily hide layer 2. Woe be unto anyone who has more than one set of cue notes for the different parts in such a stave.
2. When doing part splits from one staff into multiple separate parts, there's no way to specify what "note-attached" symbols to include from other staves. The last thing I want is multiple copies of dynamics, one per part, but this means I have to hide every other symbol that IS layer-specific. There's just not enough granularity.
3. When using linked parts, measure width changes to multimeasure rests go away as soon as you switch to another part and switch back. This makes it VERY clumsy to deal with any long text expressions such as "March Tempo (q = 60 M.M.)" or whatever.
2. When doing part splits from one staff into multiple separate parts, there's no way to specify what "note-attached" symbols to include from other staves. The last thing I want is multiple copies of dynamics, one per part, but this means I have to hide every other symbol that IS layer-specific. There's just not enough granularity.
3. When using linked parts, measure width changes to multimeasure rests go away as soon as you switch to another part and switch back. This makes it VERY clumsy to deal with any long text expressions such as "March Tempo (q = 60 M.M.)" or whatever.
Most Recent Replies: View All 1 Replies
- And several more significant bugs
Won't install at all - Version: 2009b.r3, 12/31/2008 12:17PM PST
(1 of 1 users found this comment useful)
dgatwood
Apparently, MakeMusic doesn't feel it necessary to test their software on case-sensitive HFS+ systems. I filed a problem report more than a year ago about the Finale 2007 compatibility problem along with a simple couple of commands you could use to fix it and asking them to publish that information in their help library. To date, they have not bothered to do so. I hoped that at minimum, this would wake up their testers and get them to actually pay attention to these things. Apparently it failed to do that as well.
We just got Finale 2009. It won't even install. When you click "Install", it just sits there and does absolutely nothing. In the console, it produces the error "2008-12-31 07:48:17.281 Finale Suite[165:10b] launch path not accessible".
A simple "strings" on their install binary told me all I need to know. These two strings:
/applications/utilities/installer.app/contents/MacOS/installer
/System/Library/CoreServices/Installer.app/contents/MacOS/installer
should be:
/Applications/Utilities/Installer.app/Contents/MacOS/Installer
/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer
Fortunately, it's fairly easy to work around this problem if you know what you are doing....
Mac OS X 10.5 (with case-sensitive HFS+):
cd /System/Library/CoreServices/Installer.app
ln -s Contents contents
cd Contents/MacOS/
ln -s Installer installer
Mac OS X 10.4 Server (with case-sensitive HFS+):
I'm not sure if 10.4 had its installer in /Applications/Utilities or in /System/Library/CoreServices. If Installer.app is in /System/Library/CoreServices, follow the 10.5 directions. If not, do this:
cd /
ln -s Applications applications
cd Applications
ln -s Utilities utilities
cd Utilities
ln -s Installer.app installer.app
cd Installer.app
ln -s Contents contents
cd Contents/MacOS/
ln -s Installer installer
We just got Finale 2009. It won't even install. When you click "Install", it just sits there and does absolutely nothing. In the console, it produces the error "2008-12-31 07:48:17.281 Finale Suite[165:10b] launch path not accessible".
A simple "strings" on their install binary told me all I need to know. These two strings:
/applications/utilities/installer.app/contents/MacOS/installer
/System/Library/CoreServices/Installer.app/contents/MacOS/installer
should be:
/Applications/Utilities/Installer.app/Contents/MacOS/Installer
/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer
Fortunately, it's fairly easy to work around this problem if you know what you are doing....
Mac OS X 10.5 (with case-sensitive HFS+):
cd /System/Library/CoreServices/Installer.app
ln -s Contents contents
cd Contents/MacOS/
ln -s Installer installer
Mac OS X 10.4 Server (with case-sensitive HFS+):
I'm not sure if 10.4 had its installer in /Applications/Utilities or in /System/Library/CoreServices. If Installer.app is in /System/Library/CoreServices, follow the 10.5 directions. If not, do this:
cd /
ln -s Applications applications
cd Applications
ln -s Utilities utilities
cd Utilities
ln -s Installer.app installer.app
cd Installer.app
ln -s Contents contents
cd Contents/MacOS/
ln -s Installer installer
Most Recent Replies: View All 9 Replies
- Won't install at all (1 replies)
- More bugs (1 replies)
- Poor CPU idle performance and battery life (1 replies)
- Won't install at all (1 replies)