New post
Avatar
0

I'm running Finale (v25) on a custom-built Windows machine and I'm looking to upgrade to improve Finale's performance.

I use Finale only for notation and have uninstalled the sample libraries (so I don't care about my sound card). However, I am trying to work in larger files whenever possible for workflow. I realize that Finale's lag is a known issue in large files (6+ staves over 1000+ measures), but I would like to mitigate this effect as much as possible.

Right now, the most obvious thing to do is to upgrade my processor (it's the oldest piece of hardware, an high-powered i3). I'm looking to purchase an i7, but...

Should I be looking at any other hardware for weaknesses? Where does Finale pull most of its load from?

I'm hoping for a tactical solution here, not a $2000 overhaul.

Thanks for any suggestions!

 

My current specs:

Windows 10 Home (64x)

i3-4130 (3.40 GHz)

8GB RAM (DDR3)

SSD system drive, HDD storage drives

5 comments

Date Votes
Avatar
0

Your graphics engine affects performance, too.

 

You have not given enough info for me to have a clue.

Comment actions Permalink
Avatar
0

Okay then. Graphics card is a GeForce GTX 750 Ti (2GB GDDR5).

I'm flying blind here too--what other info would be helpful?

Comment actions Permalink
Avatar
0

I could go into detail about the particular project, but both projects I have created of about this length experienced the exact same problems:

1) Severe lag in simple entry, which is all I use. (Not really interested in other methods.)

2) Incorrect selection of measures toward the end of a 1000+ measure score.

I realize that second one is difficult to describe, so I'll give a specific example. If I want to switch my bottom staff to treble clef in measure 1014, I right click on the appropriate measure with the clef tool, select the treble clef, and when I click OK, or Done or whatever, the treble clef appears in measure 1016. This effect is more pronounced the longer the score gets. It makes it impossible to do mid-measure clef changes because the selection tool defaults to whole measures as a side effect of this problem.

Point being I'm hoping that improving my hardware will make these problems managable since MakeMusic has acknowledged there is an issue and the problems themselves won't be going away anytime soon (or so I gather from the tone of the post on the subject).

Thoughts?

Comment actions Permalink
Avatar
0

… If I want to switch my bottom staff to treble clef in measure 1014, I right click on the appropriate measure with the clef tool, select the treble clef, and when I click OK, or Done or whatever, the treble clef appears in measure 1016. This effect is more pronounced the longer the score gets …

 

I suspect that there is a simple fix for this issue:

Preferences > View > Measure Numbers > Display Actual Measure Numbers

Your problem appears when {Display Defined Measure Numbers} is chosen.

Choose {Display Actual Measure Numbers}, and you are “back in business”.

 

Do not worry! This setting for Measure Numbers is a program setting (not a document setting).

The setting does not affect the layout, only the display in dialog boxes.

 

 

(The problem appears where there are measures with the Measure Attributes setting {Include in Measure Numbering} de-selected)

Comment actions Permalink
Avatar
0

Are you editing in page view or scroll view?

 

Score I am editing is over 1700 measures, around 50 staves. I use Speedy Entry, so cannot speak to your Simple Entry woes. I haven't run into your incorrect measure selection issue (although I have run into some other weird stuff). However our machines are probably not a fair comparison (64 GB RAM, 12 cores... but don't worry – that would be overkill if it was just for Finale. It's a sequencing machine, too).

Comment actions Permalink

Please sign in to leave a comment.