Skip to main content

Show Posts

This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.

Messages - acasson

2
General Discussion / Re: V 2.17 Beta Observation: Suggested Additions
Lawrie, strumming and bowing are two different actions. When I say "classic" notation, I'm referring to that which has been used for around two hundred or so years. You'll have to dig into some classical guitar music to find it. A ghost note is common popular guitar notation. To use something other than that leads to confusion for the player. There are some unsual notes and symbols in guitar music due to the nature of the instrument and its versatility- vibrato, harmonics, mordents, trills, bends, pre-bends, bend releases, hammer-ons, pull-offs, mutes, taps, etc., etc. Using text to describe an action won't cut it on many pieces of music. The score would simply become quite unwieldy and overly cluttered for the musician to read.
3
General Discussion / Re: V 2.17 Beta Observation: Suggested Additions
NWC- Afterthought regarding strum notation: either the classic style (indicating direction also) or the popular straight line with an arrowhead would be nice. Personally, I prefer the classical notation over the popular arrowhead configuration. Up to ya. Thanks.
5
General Discussion / Re: V 2.17 Beta Observation: Key Changes
Hey David. Nope, XP. I agree. There was more than likely something that corrupted the original installation. It seems o.k. now. I ran through several changes on a blank score without problems. I then opened the song of our discussion and made the changes without incident. Makes life easier for me. Again thanks to all.
7
General Discussion / Re: V 2.17 Beta Observation: Key Changes
There's nothing to see in this particular song, other than the fact that the key change isn't there. Yep, I'm using the incorporated tool to set the key and changes that follow. Perhaps, as Dave has alluded, it has something to do with my use of section bars to define the section. Presently, I'm busy preparing the song of our discussion for release to some musicians- my work with NWC is finished, regarding this particular song. But, knock on wood, I'll play with the issue again, within the next day or so, and report back.
8
General Discussion / Re: V 2.17 Beta Observation: Key Changes
Thanks for the welcome David. Here, I'm speaking of a single line, serial as it were. When the line wraps, it automatically posts the original signature of the song. It may be that when I change the key at the beginning of the line, as earlier suggested, the problem will disappear. But, more than likely, rather than deal with "X" number of empty measures, etc., etc., I'll likely use accidentals or pen the key signatures. In this case, the section isn't very long, so until the final arrangement is created, on other software, I'll simply use accidentals. I agree with you regarding NWC. I've used it since circa '98 for writing basic tunes. Since this is a Beta run, I thought I'd toss my "two cents" in for NWC to ponder. Oh, the cup holder: I'm an IT tech support rep for a number of universities colleges around the nation. A staffer once called complaining that her pc's retractable cup holder broke. Go figure.
10
General Discussion / Re: V 2.17 Beta Observation: Key Changes
Afterthought- Rick, for NWC's info, I'd like to have the ability to change the key at any point in the staff and see the key reflected in subsequent staves until such time as the key is again changed. No strange effects- just scripting the song as it's to be played without undue hurdles for the player. Such changes, midstream, aren't unusual.
12
General Discussion / Re: V 2.17 Beta Observation: Print Flaw- Horizontal lines (i.e., staves)
Yep, David, the problem is in the printer, that's known. Nope, Lawry, the driver is fine, except for the possibility of engineering/production errors, i.e., calibration. There could be any number of causes. Frankly, I have no desire to remedy the situation. If publishers and players can read it, it's fine with me. I simply posted the point as a suggestion (this is a Beta) for NWC to heed or pitch. As I stated earlier, such variations in quality are bound to rise from time to time. I'd like to see NWC incorporate a bit of fine tuning for all the John and Jane Does who may not be able to dash out and replace a printer whose performance isn't quite par. Of course, I should have prefaced the original post with my intent. Then again, perhaps NWC should be like so many other hardware and software manufacturers- offer no option for seamless integration. Oh, BTW, no cats here- at least not the four-legged kind. But thanks for the video. Forgive me, but now  I must direct my attention toward fixing my computer's retractable cup holder- any ideas?
13
General Discussion / Re: V 2.17 Beta Observation: Suggested Additions
David, the common symbol for a ghost note is a note enclosed in parenthesis. The x note is usually used for muted notes (both as used in guitar applications). The use of a ghost note removes the headache and confusion of using ties to annotate sounds that are decaying, but contribute something to the overall desired effect.
16
General Discussion / V 2.17 Beta Observation: Key Changes
When changing keys for a section of a song (opening and closing section bars, clef and new key signature, return to the original key- posting clef and key signature after the closing bar) only the section bars are seen on the printed copy. Further, when such a key change traverses more than one staff line, the new signature isn't affixed to the first measure of the subsequent staves. Instead, one finds the song's default (original) key posted.
19
General Discussion / V 2.17 Beta Observation: Print Flaw- Horizontal lines (i.e., staves)
When a score is printed, the upper line of some staves is shadowed by a duplicate line. Changing page setup (top and bottom margins and/or unit of measure) changes the quantity, severity and location of the defective lines. Changing printer setup or resolution yields no change in the anomaly. Finer print resolution required in the software to compensate for printer irregularities?