Skip to main content

Messages

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

Messages - Rick G.

301
General Discussion / Re: more space between some lines
Try this at the end of measure 9:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|Bar|XBarCnt:Y|SysBreak:Y|Visibility:Never
|Boundary|Style:NewSize|Upper:16
|Text|Text:"Refrein"|Font:StaffItalic|Pos:8
|Note|Dur:4th|Pos:0
|Boundary|Style:Reset
!NoteWorthyComposerClip-End
306
Object Plugins / Re: Trill.ms (1.1)
If there is a fermata delay then it does not trill through the added delay.
Example:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)
|Instrument|Name:"Recorder"|Patch:74|Pos:12
|Clef|Type:Treble
|TimeSig|Signature:4/4
|User|Trill.ms|Pos:9|AccStyle:2|Span:1|WhichFirst:Auxiliary
|TempoVariance|Style:Fermata|Pause:8|Pos:9|Justify:Center|Placement:AtNextNote
|Note|Dur:Half|Pos:1|Opts:Muted
|Rest|Dur:Half
!NoteWorthyComposer-End
307
General Discussion / Re: Adjust font size of rest?
Is there a way to get the bottom tie to be downward and the upper one upward? I tried, and was unable to do that.
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Treble
|Key|Signature:Bb,Eb,Ab,Db|Tonic:A
|Chord|Dur:4th,Grace|Pos:-9^,-2^|Visibility:Never
|Text|Text:"n"|Font:StaffSymbols|Scale:60|Pos:-6|Justify:Center|Placement:AtNextNote
|RestChord|Dur:4th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:Half|Pos2:-9^,-2^
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,StemLength=5,Beam=First
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,StemLength=5,Beam=End
|Text|Text:"n"|Font:StaffSymbols|Scale:60|Pos:-6|Justify:Center|Placement:AtNextNote
|RestChord|Dur:4th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:Half|Pos2:-9,-2
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=First
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=End
|Bar
!NoteWorthyComposer-End
309
General Discussion / Re: Adjust font size of rest?
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Treble
|Key|Signature:Bb,Eb,Ab,Db|Tonic:A
|Text|Text:"n"|Font:StaffSymbols|Scale:60|Pos:-6|Justify:Center|Placement:AtNextNote
|RestChord|Dur:4th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:Half|Pos2:-9,-2
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=First
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=End
|Text|Text:"n"|Font:StaffSymbols|Scale:60|Pos:-6|Justify:Center|Placement:AtNextNote
|RestChord|Dur:4th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:Half|Pos2:-9,-2
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=First
|Chord|Dur:8th|Pos:-5,-4|Opts:Stem=Down,Beam=End
|Bar
!NoteWorthyComposer-End
312
General Discussion / Re: Positioning accidentals
If your intent is to tuck an accidental above/below a second interval, extra note/accidental space won't help.
Text can be used if you don't care if it highlights during playback. A layer is needed if you do:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)|WithNextStaff:Layer
|Chord|Dur:4th|Pos:#-3,2,3
|Bar
|Note|Dur:4th,Grace|Pos:#-3|Opts:Muted|Visibility:Never
|Text|Text:"d _"|Font:StaffSymbols|Pos:-3|Justify:Right|Placement:AtNextNote
|Chord|Dur:4th|Pos:-3,2,3
|Bar
|Chord|Dur:4th|Pos:2,3
|Bar
|AddStaff|Name:"Staff-1"
|StaffProperties|EndingBar:Open (hidden)|BoundaryTop:10|BoundaryBottom:10
|StaffProperties|Channel:2
|Rest|Dur:4th|Visibility:Never
|Bar|Visibility:Never
|Rest|Dur:4th|Visibility:Never
|Bar|Visibility:Never
|RestChord|Dur:4th|Opts:Stem=Up,ArticulationsOnStem,HideRest|Dur2:4th|Pos2:#-3
|Bar
!NoteWorthyComposer-End
314
User Tools / Re: (a) Tool to create single voices from chords? (b) Class model of NWC2ClipItem
What I do not understand at all, was that "position thing", including accidentals??
Assuming you mean:
Quote from: adp_Parts.php
<pos> is a position on the staff, including accidental
(accidentals are ## for double sharp, # for sharp, b for flat, bb for double)
0 is the centre line
eg remove pos=#0 will remove all sharp centre line notes or chord members
It is used to extract percussion parts.
319
General Discussion / Re: nwctxt syntax reference
The actual notation objects use the same representation as is available from Edit, Copy while working in the editor.

A sample file is shown below.
Code: [Select · Download]
# This is a sample NWC Text file. As you can see, any text starting with 
# a '#' character is treated as a comment.
#
# ------------------------------------------------------------------------------
# This first non-comment line of the file should be the !NoteWorthyComposer
# header line. This indicates that this file contains NoteWorthy Composer Text.
# This sample targets version 2.0 (newer files use version 2.5).
#
!NoteWorthyComposer(2.0)

# Blank lines can appear anywhere in the file after the
# initial !NoteWorthyComposer header

# ------------------------------------------------------------------------------
# The SongInfo, PgSetup, PgMargins, and Font lines can appear anywhere in
# the file, but it is good form to have them at the top, prior to adding
# any staff data.

# It is fine to use multiple SongInfo, PgSetup, and PgMargins in a file.
# If a field is specified more than once, the last one overrides any
# previous assignment.
|SongInfo|Title:"<FileTitle>"|Author:"<Author>"|Lyricist:"<Lyricist>"
|SongInfo|Copyright1:"<Copyright1>"
|SongInfo||Copyright2:"<Copyright2>"
|SongInfo|Comments:"<Comments>"

|PgSetup|StaffSize:16|NtnTypeface:NWC2SwingDings|Zoom:4
|PgSetup|TitlePage:Y|JustifyVertically:Y|ExtendLastSystem:Y
|PgSetup|DurationPadding:Y|PageNumbers:3|StaffLabels:First System
|PgSetup|BarNumbers:Circled|StartingBar:20|AllowLayering:Y

# Margins are specified in Centimeters. You can convert to
# inches by dividing these values by 2.54.
|PgMargins|Left:1.27|Top:1.27|Right:1.27|Bottom:1.27
|PgMargins|Mirror:Y

# Unlike the other top level instructions, each Font instruction should
# be defined on a single line. Each Font instruction must include the
# Style option, which identifies which named font is being defined on
# the line. The Size is in points. The CharSet comes from Script field
# in the Font dialog.
|Font|Style:Staff Italic|Typeface:"Times New Roman"|Size:10|Bold:Y|Italic:Y|CharSet:0
|Font|Style:Staff Bold|Typeface:"Times New Roman"|Size:8|Bold:Y|Italic:N|CharSet:0
|Font|Style:Staff Lyric|Typeface:"Times New Roman"|Size:7|Bold:N|Italic:N|CharSet:0
|Font|Style:Page Title Text|Typeface:"Times New Roman"|Size:24|Bold:Y|Italic:N|CharSet:0
|Font|Style:Page Text|Typeface:"Times New Roman"|Size:12|Bold:N|Italic:N|CharSet:0
|Font|Style:Page Small Text|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0

# If a particular User font is not used in the file, then it might
# not appear in the file.  When scanning an existing nwctxt file,
# you cannot assume that any particular fields or instructions
# will exist in the file.
|Font|Style:User 1|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User 2|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User 3|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User 4|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User 5|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User 6|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0

# ------------------------------------------------------------------------------
# The first AddStaff line is optional, although it is required if you want to name,
# label, or group a staff
|AddStaff|Name:"<Staff1Name>"|Label:"<StaffLabel>"|Group:"Vocal"

# The various StaffProperties can be assigned using multiple instances of
# the instruction.
|StaffProperties|EndingBar:Section Close|Visible:Y
|StaffProperties|BoundaryTop:14|BoundaryBottom:12
|StaffProperties|Lines:5|Style:Standard|Layer:N|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2

# The StaffInstrument uses the same syntax as the Instrument instruction
# used in NWC clip text
|StaffInstrument|Name:"Lead 6 (voice)"|Patch:85|Trans:0|DynVel:10,30,45,60,75,92,108,127

# Lyrics can be defined anywhere after the AddStaff line, but it is good form
# to place them before the notation for the staff
|Lyrics|Placement:Bottom|Align:Standard Rules|Offset:0|UnderscoreAsSpace:N
|Lyric1|Text:"Aaaaaaaah________\r\n"

# The notation contained in the staff uses the same format as NWC2 Clip
# Text from the NWC2 User Tool and clipboard mechanisms
|Clef|Type:Treble
|Note|Dur:Whole|Pos:1^
|Bar
|TempoVariance|Style:Fermata|Pos:9
|Note|Dur:Whole|Pos:1

# ------------------------------------------------------------------------------
# Whenever an AddStaff is encountered, a new staff is created. The new
# staff then becomes the target for the instructions that follow it, until
# another AddStaff is encountered.
|AddStaff|Name:"<Staff2Name>"|Label:"<PianoStaffLabel>"|Group:"Piano"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:18|Lines:5|Style:Upper Grand Staff|Layer:N|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Lyrics|Placement:Bottom|Align:Start of Accidental/Note|Offset:2
|Lyric1|Text:"1_1 1_2 1_3 1_4\r\n1_5 1_6 1_7 1_8\r\n"
|Lyric2|Text:"2_1 2_2 2_3 2_4\r\n2_5 2_6 2_7 2_8\r\n"
|Clef|Type:Treble
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:-2
|Note|Dur:4th|Pos:-1
|Bar
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:2
|TempoVariance|Style:Fermata|Pause:5|Pos:9
|Chord|Dur:4th|Pos:1,3,5

# ------------------------------------------------------------------------------
|AddStaff|Name:"<Staff3Name>"|Group:"Piano"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:15|BoundaryBottom:14|Lines:5|Style:Lower Grand Staff|Layer:N|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Lyrics|Placement:Top|Align:Standard Rules|Offset:-2|UnderscoreAsSpace:N
|Lyric1|Text:"1_1 1_2 1_3 1_4\r\n1_5 1_6 1_7 1_8\r\n"
|Lyric2|Text:"2_1 2_2 2_3 2_4\r\n2_5 2_6 2_7 2_8\r\n"
|Clef|Type:Bass
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:2
|Bar
|Note|Dur:4th|Pos:3
|Note|Dur:4th|Pos:4
|Note|Dur:4th|Pos:5
|TempoVariance|Style:Fermata|Pause:0|Pos:-7
|Note|Dur:4th|Pos:6
!NoteWorthyComposer-End
321
General Discussion / Re: accidental octave
You have discovered a longstanding bug in NoteWorthy. I won't bore and confuse you with all the links to the discussion. The bottom line is that there are no plans to fix it. :(
This is an architectural quirk of NWC. Note accidentals apply in all octaves within the bar. The way to avoid the problem at present is to always use the correct accidental in all other octaves of that same named note after you use an accidental in one octave of the named note.
325
General Discussion / Re: odd behavior of a forced system break
An actual example is generally a prerequisite to further discussion.
Agree. IMO, this could be handled better:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)|WithNextStaff:ConnectBars
|RestMultiBar|NumBars:8|PrintOnce:N|WhenHidden:ShowBars,ShowRests|Visibility:Always
|Bar
|Rest|Dur:Half
|Bar|SysBreak:Y
|Rest|Dur:Half
|Bar
|RestMultiBar|NumBars:8|PrintOnce:N|WhenHidden:ShowBars,ShowRests|Visibility:Always
|Bar
|AddStaff|Name:"Staff-2"
|StaffProperties|EndingBar:Open (hidden)
|RestMultiBar|NumBars:8|PrintOnce:N|WhenHidden:ShowBars,ShowRests
|Bar
|Rest|Dur:Half
|Rest|Dur:Half
|Bar
|RestMultiBar|NumBars:8|PrintOnce:N|WhenHidden:ShowBars,ShowRests
|Bar
!NoteWorthyComposer-End
329
General Discussion / Re: Abbreviated alternating sixteenths
I'm transcribing an orchestral score so that I can transpose a violin concerto down an octave and a fifth for cello.
A big task. I have downloaded the score to help me with further questions you may have.

It looks like there's no option to specify a round open notehead, surprisingly, so I can't just make two sixteenths and set their noteheads.  Any ideas?
Yes. Set to notehead qlyph to 'Blank Space' and use Text:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|Text|Text:"j"|Font:StaffSymbols|Pos:-6|Justify:Right|Placement:AtNextNote
|Note|Dur:16th|Pos:-6z
!NoteWorthyComposerClip-End
330
General Discussion / Re: Ignored tempo change
The tempo change in bar 39 is ignored.
I agree. You can fix it with this replacement for bar 39:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|Bar
|Tempo|Tempo:50|Pos:11|Visibility:Never
|Rest|Dur:4th,Dotted
|Tempo|Tempo:140|Pos:7|Visibility:Never
|Rest|Dur:4th,Dotted
!NoteWorthyComposerClip-End
This is a new bug. NWC 2.51a plays as I would expect. It gives a time of 3:18 while NWC 2.75 is 3:37
332
General Discussion / Re: Transparent bar line
The only way to detect it's presence is throught the bar counter.
Not the only way, and not even the best way.
To find transparent bar lines for staves that are not tagged: 'Visible:N', Press Ctrl+F and paste the following in the 'Find what' field:
Code: [Select · Download]
|Bar|Style:Transparent

what's a "transparent bar line" good for?
As of Beta Pre 35, it is recommended that you use a transparent bar line after the boundary change gap width. This will allow:

  • a system change immediately after the gap width
  • the bar line to orphan at the end of a system and not be visible

The system connection will no longer be shown when the gap width is at the end of the staff.
I have not tested the validity of NoteWorthy's advice, I merely report it.
336
General Discussion / Re: Markers
Are you saying that 2.51 (and earlier) used to display correcting in these conditions?
NWC 2.51a display attached.

.I don't think Flurmy is saying that markers are terrible; in fact, in his opening message, he says that having them is "very good".
Not quite. Flurmy writes that the possiblity of using markers [] is very good. He titles the topic: Markers and ends with "terrible."

A discussion of slur defaults ensues, with some agreement that their start/end points have taken a turn for the worse ...
339
General Discussion / Re: Markers
I looked at page 10 of the MPA guidelines. I was not favorably impressed. Off topic to explain.
I still await an example of what makes Markers "terrible."
340
General Discussion / Re: Markers
Maybe what isn't clear to you, Rick, is that Flurmy and I are talking about articulations at the end points of slurs.
I don't read that as what Flurmy writes. In any case, your example might be an argument for changing slur defaults, but it has little to do with the topic which is Markers.
I would not use such strong language as "wrong" and "correct" for your example.
342
General Discussion / Re: Markers
Terrible. PITA
So far, I disagree.

Without examples, these sentiments are hard to understand.
343
General Discussion / Re: bar lines
One way is to use grace notes:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|PgSetup|StaffLabels:First System
|AddStaff|Name:"Staff"|Label:"Soprano"
|StaffProperties|EndingBar:Open (hidden)|WithNextStaff:Layer
|Clef|Type:Treble
|Note|Dur:4th|Pos:3
|Note|Dur:4th|Pos:3
|Note|Dur:Half|Pos:3
|Bar
|AddStaff|Name:"Staff-2"
|StaffProperties|EndingBar:Open (hidden)|BoundaryTop:6|BoundaryBottom:6
|Rest|Dur:Half|Visibility:Never
|Note|Dur:4th,Grace|Pos:-4z|Opts:Stem=Down,StemLength=24,Muted
|Rest|Dur:Half|Visibility:Never
|Bar
|AddStaff|Name:"Staff-3"|Label:"Alto"
|StaffProperties|EndingBar:Open (hidden)|WithNextStaff:Layer
|Clef|Type:Treble
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:1
|Note|Dur:Half|Pos:1
|Bar
|AddStaff|Name:"Staff-4"
|StaffProperties|EndingBar:Open (hidden)|BoundaryTop:6|BoundaryBottom:6
|Rest|Dur:Half|Visibility:Never
|Note|Dur:4th,Grace|Pos:-4z|Opts:Stem=Down,StemLength=24,Muted
|Rest|Dur:Half|Visibility:Never
|Bar
|AddStaff|Name:"Staff-5"|Label:"Baritone"
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Bass
|Note|Dur:4th|Pos:3
|Note|Dur:4th|Pos:3
|Note|Dur:Half|Pos:3
|Bar
!NoteWorthyComposer-End
345
General Discussion / Re: Midi (as is) to .wav
Btw, I would fully support an option in NWC to save files as mp3 or wav. I think that would be excellent for all of us. But I get if that's complicated.
It is. The complication is that it would require external libraries that would need licences to be added to a comercial product (NoteWorthy).

I AM mentioning <snip> all these sites that have helped me in the credits for the gig.
Credit who you like. I used NoteWorthy for years to produce wedding music that I and others performed for profit. I didn't credit anything. IMO, crediting those who don't ask for it is asking for trouble that you do not need.
346
General Discussion / Re: Midi (as is) to .wav
I'd actually been using Solmire.com to convert my midis, which is how I found the SGM sound font which is what I want. Then I looked at the terms of service: "You can use Solmire.com for non-commercial purposes."

I'm sorry if this sounds dumb or anything, but what exactly does that mean? Does that mean you can't be paid for a gig using backing tracks generated through their site? Or something else?
Something else, I would say. They would probably object if you set up a website charging (or profiting via ads) for conversion that simply farmed the task out to them.

I wouldn't worry out using the mp3's for a gig.

As melismata says, you ought to be able to use SynthFont.
347
General Discussion / Re: Measure numbers in Noteworthy Player
Is there any way to make the measure numbers in Noteworthy show up in the free Noteworthy Player?  It would be helpful when you are trying to communicate info about certain measures to not have to count them out.  You could scroll right to the measure(s) in question.
I assume you are referring to NoteWorthy Viewer.
NoteWorthy had a product it called NoteWorthy Player, but it has not been updated in more than a decade.
My impression of the Viewer is that it is time oriented rather than measure oriented. It allows you to goto a certain time and begin playback. NoteWorthy Composer lacks this. In Composer, you can go to a measure and begin playback, but if the measure is played more than once, you have little to no control of where playback occurs in the flow of the song.

I see the pair of programs as different views into the same data. My advice to you when communicating info about a song in the Viewer: do it in terms of time rather than measure.
348
Object Plugins / Re: Tremolo.ms (version 1.0)
How can i remove the "flags" from the stems since I can't beam the rest chords?
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:4th|Pos2:1
|User|Tremolo.ms|Pos:1
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:4th|Pos2:-1
|RestChord|Dur:16th,DblDotted|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:4th,Dotted|Pos2:#-3
|User|Tremolo.ms|Pos:1
|RestChord|Dur:16th,DblDotted|Opts:Stem=Down,ArticulationsOnStem,HideRest|Dur2:4th,Dotted|Pos2:#-5
!NoteWorthyComposerClip-End
349
General Discussion / Re: Problems with "Audit Accidentals"
This morning I came across a place in the piano part where the right hand plays two D's an octave apart, the upper one a D-flat, the lower one a D-natural, both marked with accidentals. The very next note in the right hand is another D, supposed to be played natural.
But if left unaltered, NoteWorthy will play a D-flat. I agree that it should not, but that is the sofware that we have.
This is an architectural quirk of NWC. Note accidentals apply in all octaves within the bar. The way to avoid the problem at present is to always use the correct accidental in all other octaves of that same named note after you use an accidental in one octave of the named note.
So, to keep Audit Accidentals from displaying what you don't want and playing what you do want, use:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Treble
|Chord|Dur:Half|Pos:n-5,b2
|Note|Dur:4th,Grace|Pos:n-5|Opts:Muted|Visibility:Never
|Note|Dur:Half|Pos:-5
|Bar
!NoteWorthyComposer-End
350
General Discussion / Re: Problems with "Audit Accidentals"
In the "new" NWC, no target accidental is required, which is an improvement. <snip> if you bring an old score into any version since this change was made, the target accidentals all unhide themselves and show up blatantly
Remove them with this:
Code: (Lua) [Select · Download]
-- rg_ZapTieDestAlterations.Lua ver 1.0 User Tool <http://nwsw.net/-f9323>
local playContext = nwcPlayContext.new()

for item in nwcut.items() do
for np in item:AllNotePositions() do
if playContext:FindTieIndex(np) then np.Accidental = '' end
end
playContext:put(item)
nwcut.writeline(item)
end