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 - CDon

4
General Discussion / Nwctxt to Harmonica Tab
Among other things, I am a diatonic harmonica player.  While I read music without any problem, most harmonica (in the vernacular, usually called ‘harp’) players do not.  But many do read a more or less customary harp tab.  I have written a small Python program (attached) that extracts note position from an nwctxt file and converts it to harp tab.

The way it works is you start with an NWC2 file with a single staff of single melody notes in the key of C.  Export the file to <tmp.nwctxt> and run the conversion program.  This produces the file <tab.txt> that consists of a single line of text containing the harp tab.  This text can be used as is if you know the melody, but it is best copied and inserted into the original NWC2 file as a lyric line.  Being in the key of C is not as restrictive as it sounds.  The diatonic harmonica can be treated as a transposing instrument, and a player typically changes keys by changing harps.  The tab remains the same for all keys.  (For harp players only: This is a 1st position discussion.)

Now, I would be surprised if more than three people on this forum would find this program useful.  The intent of posting it is not necessarily to provide something useful.  Rather, this is intended to provide a small example of the sort of thing that can be done now that Eric has made nwctxt available.  THANK YOU ERIC!  And it is also wonderful that you allow the first character in a lyric word to be a hyphen, as opposed to treating it as a separator.  That turned out to be a stroke of good fortune for me.

I am not a Python programmer, so if my programming style offends a real Python programmer, ‘scuse me…  :-) The program has not been exhaustively tested, but works correctly for a number of cases that I have tried.  And if you don’t like Python, I also have versions in Perl, Ruby, and Lua… I am evaluating some of the scripting programs to determine what to use for a more ambitious project that I have in mind.  But that is for a future discussion.
6
General Discussion / Re: Beta 2.08 : Dots placement
Quote from: Lawrie Pardy –
Personally, I'd prefer to always see the dots in the space above except when there are 2 voices on a staff.  Then, the lower voice should use the lower space only if there is some potential for confusion.

Should there be a vote, I completely agree... The dot seems far more prominent when it is in the space above.  When there is only one note present, it just doesn't look right if the dot is in the lower space, regardless of the stem direction.
8
General Discussion / Re: Working with FINALE
Are you certain that your friend knows how to import MIDI files in Finale?  As far as I know, NoteWorthy generated MIDI files are no different from any other MIDI files...
9
General Discussion / Re: Lost in Beta 2.05?
Quote from: Rick G. –

You might try keeping this note:
Code: [Select · Download]
|Chord|Dur:Whole,Grace|Pos:-12z,12z|Visibility:Never
at the end and do your note entry just before it.

Rick,
Thank you!  This works quite well.  I can put it in the template files that I use all the time, and it will be there when needed.

David,
Thank you as well for your suggestion.  I have used this at previous times, but Rick's idea seems a bit simpler.
10
General Discussion / Re: Lost in Beta 2.05?
I think that it would be helpful as well if the current vertical position value of the cursor was shown somewhere on the editor GUI... Maybe in the status bar at the bottom.  (?)  Hummm.  That would help also with the personal issue that I have with the lack of courtesy ledger lines... You could 'see' where the cursor is vertically located.
11
General Discussion / Re: My biggest bugbear with Noteworthy Composer!
Quote from: Rick G. –
The solution to courtesty leger lines is similar to octave entry. E. g., if you are on a bass staff and need the lower G, just position to the low staff G, hit Ctrl+Dn <enter>

Rick, that is not a solution; That is another work-around.  In my view, the only solution is, well, courtesy leger lines.  Right now it is probably best to take a shot at it, swear if you miss it, backspace, adjust and go.  Generally get it right (or close) if not too far from the staff.

Merriam-Webster Main Entry: work-around
Pronunciation: 'w&rk-&-"raund
Function: noun
: a plan or method to circumvent a problem (as in computer software) without eliminating it  

Quote
What do you mean by subtitles?  Something to help you read French music?

Basically, yes, but actually, Yiddish.  I do a lot of Yiddish titles and it would be nice to English subtitles... As John said above.
16
General Discussion / Re: Comfotable Notation Size?
A large 'Thank you!' to those who provided input to this topic…! You have provided exactly the sort of info that I was looking for.  With that, I’m going to undertake a project that I have in mind, and, hopefully, I can complete it with a minimum of rework.  I do appreciate everyone’s time.
17
General Discussion / Comfotable Notation Size?
I am curious as to what notation/staff size most brass or wind instrumentalist prefer.  I know what I like, but if one were writing parts for other people, what would be a good size that most people would find suitable?  Too small is, of course, just that.  Too large can be very distracting as well.  I realize that it would be dependent to some degree on the compass of the instrument and that tweaks may be necessary to accommodate desired paging, odd measures and breaks.  What I am looking for is the best (?) starting point for staff size for parts that most people would find comfortable and attractive.  Any experience or opinions on this?