Re: [Finale] Blessed be the ties that bind ... and, why don't some?
To tie all notes of a chord, position the cursor above the top note or below the lowest, then hit the tie command. Harold At 12:42 -0700 17/10/09, Dean M. Estabrook wrote: >Often when I attempt to tie one chord across a bar line, and the stack has >three or more note in it ... only some of the notes tie. A) why, and B) how do >I fix it? > >Dean > > >Canto ergo sum >And, >I'd rather be composing than decomposing > >Dean M. Estabrook >http://deanestabrook.googlepages.com/home > > > > > >___ >Finale mailing list >Finale@shsu.edu >http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
[Finale] FinaleScript for Dummies..
On the Mac... 2009 All that I want to do is change margins. Can't seem to find a simple explanation of loading the format to be used. Noel Jones, AAGO 423 887-7594 noeljo...@usit.net www.thecatholichymnal.com Friends, life is short and we do not have much time to gladden the hearts of those who travel with us; so be swift to love and make haste to be kind. ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Blessed be the ties that bind ... and, why don't some?
Dean M. Estabrook wrote: Well, what you said worked until the part where I try to make the cursor tie all possible notes in the chords. Then, nothing seemed to occur at all. Hmmm Are you sure? Sometimes you have to be zoomed in pretty close to tell. And some notes might have something about them that makes them unfriendly. cd In my experience, the keyboard shortcut to create a tie between two pitches is a toggle: pressing it once and it creates the tie; pressing it twice removes it. If the cursor is on a pitch in the chord, when you press the key the first time it creates a tie between the notes on that pitch, and pressing it a second time creates the tie between the other notes in the chord, and removes the tie between the notes on the pitch on which the cursor is located. If one wishes to create ties between all possible notes in two (existing) chords, one needs to make sure that the cursor is not on any of the pitches represented in either chord. ns ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale Canto ergo sum And, I'd rather be composing than decomposing Dean M. Estabrook http://deanestabrook.googlepages.com/home ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale -- http://www.livejournal.com/users/dershem/# http://members.cox.net/dershem ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Blessed be the ties that bind ... and, why don't some?
Put it inside the chord but not directly on a note. Sent from my iPhone On Oct 17, 2009, at 5:38 PM, "Dean M. Estabrook" wrote: > Well, what you said worked until the part where I try to make the > cursor tie all possible notes in the chords. Then, nothing seemed to > occur at all. Hmmm > > > Dean > > On Oct 17, 2009, at 1:09 PM, Noel Stoutenburg wrote: > >> Dean M. Estabrook wrote: >>> Often when I attempt to tie one chord across a bar line, and the >>> stack has three or more note in it ... only some of the notes tie. >>> A) why, and B) how do I fix it? >>> >> >> In my experience, the keyboard shortcut to create a tie between two >> pitches is a toggle: pressing it once and it creates the tie; >> pressing it twice removes it. If the cursor is on a pitch in the >> chord, when you press the key the first time it creates a tie >> between the notes on that pitch, and pressing it a second time >> creates the tie between the other notes in the chord, and removes >> the tie between the notes on the pitch on which the cursor is >> located. If one wishes to create ties between all possible notes in >> two (existing) chords, one needs to make sure that the cursor is >> not on any of the pitches represented in either chord. >> >> ns >> ___ >> Finale mailing list >> Finale@shsu.edu >> http://lists.shsu.edu/mailman/listinfo/finale > > Canto ergo sum > And, > I'd rather be composing than decomposing > > Dean M. Estabrook > http://deanestabrook.googlepages.com/home > > > > > > ___ > Finale mailing list > Finale@shsu.edu > http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Blessed be the ties that bind ... and, why don't some?
Well, what you said worked until the part where I try to make the cursor tie all possible notes in the chords. Then, nothing seemed to occur at all. Hmmm Dean On Oct 17, 2009, at 1:09 PM, Noel Stoutenburg wrote: Dean M. Estabrook wrote: Often when I attempt to tie one chord across a bar line, and the stack has three or more note in it ... only some of the notes tie. A) why, and B) how do I fix it? In my experience, the keyboard shortcut to create a tie between two pitches is a toggle: pressing it once and it creates the tie; pressing it twice removes it. If the cursor is on a pitch in the chord, when you press the key the first time it creates a tie between the notes on that pitch, and pressing it a second time creates the tie between the other notes in the chord, and removes the tie between the notes on the pitch on which the cursor is located. If one wishes to create ties between all possible notes in two (existing) chords, one needs to make sure that the cursor is not on any of the pitches represented in either chord. ns ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale Canto ergo sum And, I'd rather be composing than decomposing Dean M. Estabrook http://deanestabrook.googlepages.com/home ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Blessed be the ties that bind ... and, why don't some?
Dean M. Estabrook wrote: Often when I attempt to tie one chord across a bar line, and the stack has three or more note in it ... only some of the notes tie. A) why, and B) how do I fix it? In my experience, the keyboard shortcut to create a tie between two pitches is a toggle: pressing it once and it creates the tie; pressing it twice removes it. If the cursor is on a pitch in the chord, when you press the key the first time it creates a tie between the notes on that pitch, and pressing it a second time creates the tie between the other notes in the chord, and removes the tie between the notes on the pitch on which the cursor is located. If one wishes to create ties between all possible notes in two (existing) chords, one needs to make sure that the cursor is not on any of the pitches represented in either chord. ns ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
David W. Fenton quoted my comment,: If I recall correctly, I had a similar experience with an earlier version than 2007, perhaps 2002 or 2003, and finally determined that it was an unintended consequence of using the "9" key in speedy entry to hide an accidental. and replied Don't you mean "*" to show/hide the accidental? The 9 key flips the enharmonics, which is not going to hide an accidental (it will probably make it worse!). to which I must confess a temporary parity error in the biological memory. Of course, I meant "*". And I should also note, that I neglected to consider that the OP might be using the MAC version. ns ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
[Finale] Blessed be the ties that bind ... and, why don't some?
Often when I attempt to tie one chord across a bar line, and the stack has three or more note in it ... only some of the notes tie. A) why, and B) how do I fix it? Dean Canto ergo sum And, I'd rather be composing than decomposing Dean M. Estabrook http://deanestabrook.googlepages.com/home ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
On 17 Oct 2009 at 8:21, Noel Stoutenburg wrote: > Dan Tillberg wrote > > > It is simply regarding disappearing accidentals. It happens (rarely) that > > a specific note is not shown with any accidental although it is there: it > > plays correctly, and when changing the note with +/- to lower or raise the > > note it really happens soundwise and again plays correctly but no > > accidental is shown at all. There is no difference between the score and > > the part - if the accidental disappears in the score is also gone in the > > part. > > > > The problem is minor (provided that you discover it before distributing > > the result!), it does not happen often and is simply solved by erasing a > > note and putting it back again. So therefore I haven't taken the time to > > ask about it. > > If I recall correctly, I had a similar experience with an earlier > version than 2007, perhaps 2002 or 2003, and finally determined that it > was an unintended consequence of using the "9" key in speedy entry to > hide an accidental. Don't you mean "*" to show/hide the accidental? The 9 key flips the enharmonics, which is not going to hide an accidental (it will probably make it worse!). > The forced display (or hiding) of an accidental > might persist, even though the note were moved to another pitch, > although the forced display was canceled if the note was deleted and > re-entered. I never experienced the phenomenon in a later version, and > since I'm at the moment away from my engraving computer, I don't have > the means to check to see if my memory is accurate. I've occasionally had it happen, but * always corrects it -- but, of course, I have to notice it to fix it. -- David W. Fentonhttp://dfenton.com David Fenton Associates http://dfenton.com/DFA/ ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
On 17 Oct 2009 at 6:44, dhbailey wrote: > In effect, > we end-users have become the final beta-testers, for which > privilege we pay full retail upgrade prices. Only those who choose to buy the initial release end up as de facto beta testers. Others wait to buy a new version until after the patch is released. > MakeMusic > waits a bit to see which of the known bugs raise the largest > outrage and complaints and then it fixes those and chooses > to let the rest of the known bugs lie until it can get > around to them. You do not know this to be the case. Stating it as fact is really a dishonest thing to do. And you probably don't even believe that this is the case. Software is complicated and fixing bugs is difficult and fraught with all sorts of risks and trade-offs. I've tried to explain this any time the issue comes up. Unless you the people at MM are crooks (which I don't think you believe), they are just doing the best they can with limited resources. The only software that lacks bugs is software that hasn't been released. Shipping is more important than stamping out 100% of known bugs. And no software company ships bug-free code. The only difference between various companies is what level and what quantity of bugs they tolerate in their shipping product. Because Finale's developers are yoked to the treadmill of yearly releases, they have to tolerate more bugs than if they had a more leisurely schedule, since otherwise they'd run out of revenues to pay the employees. I wish they could figure out a way to get off that treadmill, but I just don't see how it's possible for them to do it. Apple can afford to use an entire development cycle for bug fixes and performance improvements in their flagship OS because they have plenty of other revenue streams as larger or larger than what they get from sales of OS X -- they can afford to lose the revenue on the reduced-price Snow Leopard because they have plenty of other cash coming in. MM doesn't have but the one other major revenue stream, and I don't think it's as large as the Finale revenue stream. Sibelius may have shown the way on this when they were acquired by Avid -- it puts the Sibelius development within a larger company with other significant revenue streams that can subsidize major investments in Sibelius should a maintenance release (like Snow Leopard) become necessary (though Sibelius has already done a better job on this with releases ever 2 or 3 years -- they never got on the yearly-release treadmill, so they don't have to get off it). To me, the only solution for MM is to be acquired by a larger company that is willing to invest in Finale's long-term development. But I haven't a clue what companies might want to take on that investment given the big picture with Sibelius. -- David W. Fentonhttp://dfenton.com David Fenton Associates http://dfenton.com/DFA/ ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
[Finale] 2010A to be available 10/20/09, allegedly.
Posted 10/15/09 at MM Forum: "I did contact MM Music Support who advise that 2010A will be out by next Tuesday," 10/20/09. Doesn't anyone else here read that list too? ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
On Oct 17, 2009, at 5:38 AM, Dan Tillberg wrote: It happens (rarely) that a specific note is not shown with any accidental although it is there: it plays correctly, and when changing the note with +/- to lower or raise the note it really happens soundwise and again plays correctly but no accidental is shown at all. This is a longstanding bug when using option-equals to create a tie to a previous note. It properly hides any notated accidental that the tied note may have, but it also hides all other accidentals that may appear in the chord containing the tied note. The solution is either to use the regular tie command (from the starting note rather than the ending one), or to go back and hit the asterisk key (not the 9 as someone else suggested) to force the improperly hidden accidental to reappear. Andrew Stiller Kallisti Music Press http://www.kallistimusic.com/ ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
Dan Tillberg wrote It is simply regarding disappearing accidentals. It happens (rarely) that a specific note is not shown with any accidental although it is there: it plays correctly, and when changing the note with +/- to lower or raise the note it really happens soundwise and again plays correctly but no accidental is shown at all. There is no difference between the score and the part - if the accidental disappears in the score is also gone in the part. The problem is minor (provided that you discover it before distributing the result!), it does not happen often and is simply solved by erasing a note and putting it back again. So therefore I haven't taken the time to ask about it. If I recall correctly, I had a similar experience with an earlier version than 2007, perhaps 2002 or 2003, and finally determined that it was an unintended consequence of using the "9" key in speedy entry to hide an accidental. The forced display (or hiding) of an accidental might persist, even though the note were moved to another pitch, although the forced display was canceled if the note was deleted and re-entered. I never experienced the phenomenon in a later version, and since I'm at the moment away from my engraving computer, I don't have the means to check to see if my memory is accurate. And it probably bears noting that while in many instance Finale makes it possible to achieve the same result in different ways, it might also be possible to have the same apparent "bug" from different ways, too. ns ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
Actually, I've had this happen a couple of times. I have no clue why. My work around has been to use the accidental plugin to fix it. Though I can't remember the last time it happened --- send out and aboot on my iPhone --- On Oct 17, 2009, at 2:38 AM, Dan Tillberg wrote: Yep I can understand this frustration and I am not too irritated with all the criticism I see from time to time. Perhaps a little surprised how many people on this list who seem to prefer Sibelius instead... But I agree that a list like this should give room for other issues than strict technical questions. I admit that I enjoy some of the more amusing and sometimes sarcastic messages... So if you have a question, ask away! :-) Come to think of it, and in the area of bugs, actually I do. I have seen a problem both in Fin 2007 and now in Fin 2010 that I haven't seen mentioned on this list and I haven't asked the question myself. In fact, I have talked with some people and noone has acknowledged to have seen the problem. Perhaps there is something I don't understand... It is simply regarding disappearing accidentals. It happens (rarely) that a specific note is not shown with any accidental although it is there: it plays correctly, and when changing the note with +/- to lower or raise the note it really happens soundwise and again plays correctly but no accidental is shown at all. There is no difference between the score and the part - if the accidental disappears in the score is also gone in the part. The problem is minor (provided that you discover it before distributing the result!), it does not happen often and is simply solved by erasing a note and putting it back again. So therefore I haven't taken the time to ask about it. But now since you provoce me... ;-) Anyone having seen this? Cheers /D ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
Yep I can understand this frustration and I am not too irritated with all the criticism I see from time to time. Perhaps a little surprised how many people on this list who seem to prefer Sibelius instead... But I agree that a list like this should give room for other issues than strict technical questions. I admit that I enjoy some of the more amusing and sometimes sarcastic messages... > > So if you have a question, ask away! :-) > Come to think of it, and in the area of bugs, actually I do. I have seen a problem both in Fin 2007 and now in Fin 2010 that I haven't seen mentioned on this list and I haven't asked the question myself. In fact, I have talked with some people and noone has acknowledged to have seen the problem. Perhaps there is something I don't understand... It is simply regarding disappearing accidentals. It happens (rarely) that a specific note is not shown with any accidental although it is there: it plays correctly, and when changing the note with +/- to lower or raise the note it really happens soundwise and again plays correctly but no accidental is shown at all. There is no difference between the score and the part - if the accidental disappears in the score is also gone in the part. The problem is minor (provided that you discover it before distributing the result!), it does not happen often and is simply solved by erasing a note and putting it back again. So therefore I haven't taken the time to ask about it. But now since you provoce me... ;-) Anyone having seen this? Cheers /D ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] End of Make Music?
Dan Tillberg wrote: Perhaps I am too new on this list. Only two years now. So excuse me if this is your view. But I think I can see a lot of criticism towards Finale and MakeMusic and since I am not a shareholder of MakeMusic (just a simple customer paying a lot of money!) I don't react too badly on this. Citicism might be good and even developing if it is not just simple grumble. Sibelius is probably also fine and Finale and MakeMusic might be as bad as many of you say. But...isn't this forum ment to exchange great "technical" knowledge regarding FINALE when having problems or trying to do things that are not obviously documented or a bit...eh...uncommon? Or is it a general forum that also should give room to express frustration and anger with Finale, MakeMusic and the world and it's people as an entity...in more general terms? It's a discussion group for matters relating to Finale and thus to MakeMusic. If you want to gain technical knowledge about Finale, ask a question about some aspect of the program about which you wish to learn more. If nobody asks a finale-specific question or raises a finale-specific issue then as most groups of humans will do, the conversation will stray onto other topics. Regarding the postings about the supposedly upcoming update to Fin2010, the long-term users of this program have grown very frustrated with the fact that MakeMusic releases known buggy versions of the program with the "promise" to repair the most egregious bugs in an interim patch, which comes out anywhere from 2 to 8 months after the release. In effect, we end-users have become the final beta-testers, for which privilege we pay full retail upgrade prices. MakeMusic waits a bit to see which of the known bugs raise the largest outrage and complaints and then it fixes those and chooses to let the rest of the known bugs lie until it can get around to them. Some bugs have remained for many versions since not many people complain. That still doesn't lessen the major impact of those bugs on the people who encounter them, it just is a gambling game which MakeMusic plays in an attempt to reduce development costs while retaining the largest customer base it can. And we've become bitter over the years as MakeMusic has become entrenched in this "annual upgrade to a new buggy version which will be slightly repaired in the interim update patch" business model, all the while Sibelius is on more of a 2-year "let's get it as correct as we possibly can before releasing the new version" business model. The tone of the two main on-line discussion groups for these two program is vastly different in regards to complaints about new versions and which bugs have been chosen to be fixed or not. But the members of this group remain dedicated to Finale and I think I speak for all the members when I say that we will be very happy to discuss technical issues related to Finale when anybody raises them. So if you have a question, ask away! :-) -- David H. Bailey dhbai...@davidbaileymusicstudio.com ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
