Chord Names

Topic: Chord Names (Read 5912 times) previous topic - next topic

Chord Names

23 years ago

I use noteworthy to create arrangements of some really good songs (ex. So What by Miles Davis) and for the guitar + piano, i hate writing out the chords by hand...is there any way to just have the chords above the staff??
To see wut i mean, look at Caverns.nwc in the samples folder...

Re: Chord Names

Reply #1 – 23 years ago

Well, I'm afraid that the answer is currently "No". (I don't know if BIAB could do this??)

But I find very interesting to search for it (chord name), as we always learn from the chord progression and other things.
More over, you can make a "nwc chord chart" file and copy/paste the ones you need in your work-in-progress...

You can make your own entirely, or get some from ChordCharts.zip.

HTH

Re: Chord Names

Reply #2 – 23 years ago

In the sample, they're just added as text items. There are some advantages to entering them as lyrics, if you're not using lyrics; transposition is slightly less of a pain in the neck, for instance. I usually assign a user font for chords, something plain like boldface Arial.

Some extra symbols like º or ø can be found in the character map.

Re: Chord Names

Reply #3 – 16 years ago

I wrote an answer on this topic. You can find it listed under Topic: Entering Sharps and Flats for Chord Symbols with the NWC Font

In short: you can get alternative fonts - suitable for printing chord names like F#min en Bflat.

Need I to add that you need to manage the expression placement/staff position to 9 or 10 or so.

Re: Chord Names

Reply #4 – 16 years ago

Quote from: J.H. Sportel – 16 years ago

Need I to add that you need to manage the expression placement/staff position to 9 or 10 or so.

No; to add you need not. In many cases, 9 or 10 would be incorrect.

Re: Chord Names

Reply #5 – 16 years ago

Depending on the font, Pos 9 or 10 may well be appropriate. Certainly my Chord fonts tend to work well around there.

Re: Chord Names

Reply #6 – 16 years ago

Quote from: Lawrie Pardy – 16 years ago

Pos 9 or 10 may well be appropriate.

Or 17, as here:

Quote

!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Key|Signature:C
|TimeSig|Signature:Common
|Text|Text:"C"|Font:PageText|Pos:17|Justify:Center|Placement:AtNextNote
|TempoVariance|Style:Fermata|Pause:0|Pos:11|Justify:Center|Placement:AtNextNote
|Chord|Dur:Whole|Pos:1,8
!NoteWorthyComposerClip-End

Pos: has little to do with the font unless it is poorly designed or the user has it set to an absurd size.

Re: Chord Names

Reply #7 – 16 years ago

G'day Rick,

Quote from: Rick G. – 16 years ago

Pos: has little to do with the font unless it is poorly designed or the user has it set to an absurd size.

My chord font glyphs are positioned low within the available space. This was deliberate as they also match the positioning of the Sib. chord fonts. I had thought to make them available/useable for Sib. as well as NWC but this has fallen by the wayside.

Re: Chord Names

Reply #8 – 16 years ago

To use MusikChordSerif @ 12pt in my example, I need Pos:19 instead of Pos:17. No big deal. I've used several of your fonts. They work just fine.

My reaction was to those who claim that all the Chord symbols can be put at some fixed position across the entire song. They must have simpler music than I see:

Quote from: Rick G. – 16 years ago

I just went though my latest issue of Sheet Music Magazine (Winter 2009). Of the 15 songs, 14 had chords. None of the 14 had the chords vertically aligned for the entire song. Every song had some chord symbols that had to be moved up to avoid notes, slurs or triplet brackets.