[Finale] Running Both Finale 2014d and 2014.5

Hello, I've just downloaded the Fin 2014.5 upgrade. As I understand, there are a fue issues with this last release, therefore I thought of running the two versions on my Mac: Would you suggest to do so, and, are there any contraindication in doing so (library issues an other possible conflicts)

Re: [Finale] New Bugs 2014.5

On 11/22/2015 3:53 PM, Chuck Israels wrote: > Because you mistyped 2015.5 :) Must be a Freudian slip. Let us hope so anyway. ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a messa

[Finale] FInale for the Visually Impaired?

Dear Collective Wisdom, I have been working with a student who is blind. What I have been doing is using Finale to re-orchestrate some hymns, entering the four part harmony into Soprano/Alto/Tenor/Bass lines, and then moving the lines around into the different instruments for her. Finale’s play

Re: [Finale] New Bugs 2014.5

Because you mistyped 2015.5 :) Chuck > On Nov 22, 2015, at 12:48 PM, Craig Parmerlee wrote: > > I don't understand that comment. Both 2014 and 2014.5 are available. > Can you please elaborate? > > > On 11/22/2015 2:16 PM, Jari Williamsson wrote: > >> My gut feel is that you are using a pr

Re: [Finale] New Bugs 2014.5

I don't understand that comment. Both 2014 and 2014.5 are available. Can you please elaborate? On 11/22/2015 2:16 PM, Jari Williamsson wrote: > My gut feel is that you are using a product that isn't available. ___ Finale mailing list Finale@shsu.edu

Re: [Finale] New Bugs 2014.5

JW Space Empty Rests It worked twice on one part. As soon as I move to a new part, it stops working. Damned irritating. > On Nov 22, 2015, at 12:20 PM, Chuck Israels wrote: > > Thanks, Les and Raymond. It was “Respect instrument ranges” that caused the > octave shifting behavior. > > I ju

Re: [Finale] New Bugs 2014.5

Thanks, Les and Raymond. It was “Respect instrument ranges” that caused the octave shifting behavior. I just rechecked the JW Space Empty Rests plugin. I can make it work by replacing the plugin with a newly downloaded one, and then it works. I will report when it doesn’t work the next time,

Re: [Finale] New Bugs 2014.5

Aha! That must be the explanation. Makes sense with what I am seeing. Thank you, Les. > On Nov 22, 2015, at 12:09 PM, Mariposa Symphony Orchestra > wrote: > > Hi, Chuck – re: the octave shifts when copying from one staff to another: > take a look to make sure “respect ranges when copying”

Re: [Finale] New Bugs 2014.5

Could the octave changes be from adjusting for instrument ranges? That can be turned off. Mind you, I do not have the new version installed, I'm using 2014 On Nov 22, 2015 2:46 PM, "Chuck Israels" wrote: > I asked for the old colored palettes too. Easier for me to see. When I > spoke on the pho

Re: [Finale] New Bugs 2014.5

Hi, Chuck – re: the octave shifts when copying from one staff to another: take a look to make sure “respect ranges when copying” isn’t selected. Go to Edit – Preferences – Edit and uncheck if you don’t want octaves to be altered into the target instruments’ ranges...which MAY be the problem you’

Re: [Finale] New Bugs 2014.5

And JW Space Empty Rests does not work for me. I downloaded the most recent version (which I believed I already had - and probably did), after which it worked when I tested it. Now, two days later, it does not.\ Chuck Chuck Israels cisra...@comcast.net (360) 201-

Re: [Finale] New Bugs 2014.5

100% agree. > On 22 Nov 2015, at 19:10, Craig Parmerlee wrote: > > On 11/22/2015 9:09 AM, Steve Parker wrote: >> >> I’ve beta tested notation products before and understand that things need >> prioritising and that pro users are often not the significant user base but.. > > > Sure, but I don

Re: [Finale] New Bugs 2014.5

I asked for the old colored palettes too. Easier for me to see. When I spoke on the phone to someone knowledgable at MM about this some time ago, she said that is was not a trivial fix - not as easy as it appeared to be. I took here at her word, but it is still irritating to me that something

Re: [Finale] New Bugs 2014.5

I am experiencing several compatibility issues with Windows 10. Need always to make sure I run as administrator (which should be by default) and check compatibility issues every now and then. And wasn't it that they were to rebundle the option of changing palettes? Rafael J On 22 November 2015 a

Re: [Finale] New Bugs 2014.5

On 2015-11-22 20:05, Craig Parmerlee wrote: >My gut feel is that 2015.5 is a little better than 2014 on > balance, My gut feel is that you are using a product that isn't available. Best regards, Jari Williamsson ___ Finale mailing list Finale@shsu.ed

Re: [Finale] New Bugs 2014.5

On 11/22/2015 9:09 AM, Steve Parker wrote: > > I’ve beta tested notation products before and understand that things need > prioritising and that pro users are often not the significant user base but.. Sure, but I don't see any excuse for: - Not fixing the HP problem with overlapping note-on not

Re: [Finale] New Bugs 2014.5

On 11/22/2015 9:06 AM, Rafael Leonardo Junchaya wrote: > Wonder why they have released a version that is so buggy. I came back to > 2014d because 2014.5 makes a lot of problems... > I didn't keep a good list of all the things that were really messed up in 2014, so I can't say that one release is

[Finale] New Bugs List, Please

Hi all, I think it would be helpful to keep a master list of the new bugs. Craig Parmalee has been keeping a list. Craig, could you please publish this list? If others have discovered bugs, please describe them and add to the list and let us know. This will help all of us try to determine workarou

Re: [Finale] New Bugs 2014.5

> The problem must be in the testing cycle. Users, actual users, not novice or > pretend users, seem to only take a few hours or days to turn up problems, > problems that should have been detected in alpha tests and never made it to > beta. This is what I don’t get. I’d assumed that a number

Re: [Finale] New Bugs 2014.5

Wonder why they have released a version that is so buggy. I came back to 2014d because 2014.5 makes a lot of problems... Rafael Junchaya On 22 November 2015 at 14:14, David H. Bailey wrote: > On 11/22/2015 6:38 AM, Graeme Gerrard wrote: > > I don’t get it. I am sure the new owners and engineer

Re: [Finale] New Bugs 2014.5

On 11/22/2015 6:38 AM, Graeme Gerrard wrote: > I don’t get it. I am sure the new owners and engineers have been working > hard and long on 2014.5. But again, a release has emerged that can’t have > been thoroughly tested or it wouldn’t have seen the light of day! > > The problem must be in the

Re: [Finale] New Bugs 2014.5

I don’t get it. I am sure the new owners and engineers have been working hard and long on 2014.5. But again, a release has emerged that can’t have been thoroughly tested or it wouldn’t have seen the light of day! The problem must be in the testing cycle. Users, actual users, not novice or pr

Re: [Finale] New Bugs 2014.5

On 11/22/2015 1:07 AM, Craig Parmerlee wrote: > FWIW, I have been keeping a list of the bizarre behaviors I have seen > with 2014.5. I have about 10 new bugs that never happened to me before > now and several of the most annoying prior problems that have not been > addressed. > > One of the things