New post
Avatar
0

Anyone not subscribed to ScoringNotes is missing out on a handy resource. I in addition to the occasional How to article that I've found most useful, I've saved a few $$ here and there by knowing about updates/sales/products to avoid info that I've gleaned from its pages. You can follow the link below to sign up — it's free.

 

From ScoringNotes

https://www.scoringnotes.com/news/noteperformer-updated-to-3-3/ 

 

Finale-specific fixes

NotePerformer now uses key-switches rather than MIDI controllers for articulations in Finale, based on the fact that this is what Garritan’s internal sounds use. To the extent possible, NotePerformer’s choice of key switches also matches that of Garritan’s built-in sounds, which should make NotePerformer somewhat more immune to playback errors as a result of stray key-switches that are hard-coded into existing scores.

Slurs would sometimes initiate or end legato playback on the wrong note. Also, slurs ending on a staccato note would not always playback correctly. These problems have been fixed.

Doits and falls would sometimes play on the preceeding note instead. An error which could also make the articulation inaudible. The problem has been corrected.

3 comments

Date Votes
Avatar
0

Hi Mike,

 

I just downloaded the 26.2 update and now noteperformer 3 is causing delays in note entry and sound (like with v25 but actually worse). Everything runs slower with it now. When I switch the garritan sounds the delay goes away. Any idea what might be happening? Have you experienced that at all?

Comment actions Permalink
Avatar
0

I just happened to have visited the NotePerformer site, and found a list of known problems and fixes to previous problems.

They seem to have trouble with MakeMusic, but also seem to do their best to fix the incompatibility issues.

Have yet to try it, but will soon.

:-)
Vanessa

Comment actions Permalink
Avatar
0

The only problem I have, is the delay in playback. As the cursor moves in the score during playback, the audio is a beat or two behind. This is due to NotePerformer scanning ahead to give better playback. I'm used to it now and it's not an issue for me.

Comment actions Permalink

Please sign in to leave a comment.