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 - NoteWorthy Online

252
Object Plugins / Re: MIDIParm.nw
I would hope that controller 38 does not cause a problem, since @lew.myrick explicitly cited large paramater data numbers. If it does cause a problem, just delete the DataLSB property.
253
Object Plugins / Re: MIDIParm.nw
The latest plugin is attached here. The easiest way to get it is from Tools, User Objects (Ctrl+J), Options, Check online sources.

You can create and modify your own selector. Right click on any of the selectors in the Insert toolbar, then select Customize. I recommend the last selector, which is Selector 16. I created a starter Selector 16 for you, which is attached in an earlier reply.


254
Object Plugins / Re: MIDIParm.nw
Quote from: lew.myrick –
I would edit them into Cakewalk as follows

Channel 1 (Swell) Gedackt 8 stop = NRPN 40, 16256 to set the stop and NPRN 40, 0 to clear the stop
Channel 1 (Swell) Traverse Flute stop = NRPN 63, 16256 or NRPN 63, 0 to clear
Channel 2 (Great) Diapason 8 stop = NRPN 31, 16256 or 31,0
Channel 2 (Great) Harmonic Flute stop = NRPN 40, 16256, or 40,0
Channel 3 (Pedal) Choral Bass stop = NRPN 56, 16256 or 56,0

The plugin has been modified to accept a program number expression. For example, these NRPN instructions could be entered exactly as you have shown them:

Code: [Select · Download]
(Swell) Gedackt 8 stop = NRPN 40, 16256
(Swell) Gedackt 8 clear = NRPN 40, 0
(Swell) Traverse Flute stop = NRPN 63, 16256
(Swell) Traverse Flute clear = NRPN 63, 0
(Great) Diapason 8 stop = NRPN 31, 16256
(Great) Diapason 8 clear = NRPN 31, 0
(Great) Harmonic Flute stop = NRPN 40, 16256
(Great) Harmonic Flute clear = NRPN 40, 0
(Pedal) Choral Bass stop = NRPN 56, 16256
(Pedal) Choral Bass clear = NRPN 56, 0
255
Object Plugins / Re: MIDIParm.nw
I picked two example and created MIDIParm.nw clips that represents them below. Given your NRPN expressions as:

Code: [Select · Download]
Text Description stop = NRPN #v1, #v2

I assume that your #v1 is the actual NRPN number, and your #v2 is the combination of controller 6 (Data Entry MSB) and 36 (Data Entry LSB). The representation formula is then:

Type:NRPN
MSB:#v1/128
LSB:#v1 - (MSB * 128)
DataMSB:#v2/128
DataLSB:#v2 - (DataMSB * 128)
ShowAs:"Text Description stop"
Quote from: lew.myrick –
Channel 1 (Swell) Gedackt 8 stop = NRPN 40, 16256 to set the stop and NPRN 40, 0 to clear the stop

On your channel 1 staff, you can use these objects to send the above changes:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.749727,Single)
|User|MIDIParm.nw|Pos:6|Type:NRPN|MSB:0|LSB:40|DataMSB:127|DataLSB:0|ShowAs:"(Swell) Gedackt 8 stop"|Visibility:Never
|User|MIDIParm.nw|Pos:6|Type:NRPN|MSB:0|LSB:40|DataMSB:0|DataLSB:0|ShowAs:"(Swell) Gedackt 8 clear"|Visibility:Never
!NoteWorthyComposerClip-End

Quote from: lew.myrick –
Channel 3 (Pedal) Choral Bass stop = NRPN 56, 16256 or 56,0

On your channel 3 staff, you can use these objects to send the above changes:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.749727,Single)
|User|MIDIParm.nw|Pos:6|Type:NRPN|MSB:0|LSB:56|DataMSB:127|DataLSB:0|ShowAs:"(Pedal) Choral Bass stop"|Visibility:Never
|User|MIDIParm.nw|Pos:6|Type:NRPN|MSB:0|LSB:56|DataMSB:0|DataLSB:0|ShowAs:"(Pedal) Choral Bass clear"|Visibility:Never
!NoteWorthyComposerClip-End

I placed both of these clips in a file, which is attached. The top staff is on channel 1, and the bottom staff is on channel 3, as you indicated is required.

I have also attached a selector that encodes the first 10 items in your PDF. If you move this into your Tools, Options, Config Files folder, then restart NWC 2.75, this selector will show up in the default Insert toolbar.
256
General Discussion / Re: NRPNs in NWC 2.75 Beta
From an old message, you apparently have a Allen C12 organ. I looked up the manual, but could not find any NRPN details for this organ. If you have any further details, I can provide more assistance.
257
Object Plugins / Re: MIDIParm.nw
Follow the instructions in the About User Plugins. In short:

  • Select, copy and paste the above clip into NWC 2.75
  • Press Ctrl+J
  • If MIDIParm.nw is not shown as installed, then double-click it, and press Install

From now on, you can use Insert, User Object and enter MIDIParm.nw into the User Type box.

I would recommend that you construct your NRPN change objects, then copy and paste them where you need them.

As I said in your original topic, if you post technical details of your organ, I can post some object clips that do what you want. You could simply copy and paste them as needed.

258
Object Plugins / MIDIParm.nw
This object allows you to send MIDI RPN and NRPN changes. If you do not want these to show when printing, then you will need to hide the object. You can change the text that is displayed for the object by adding a ShowAs property.

The following clip uses MIDIParm.nw to temporarily change the pitch bend range to 12 semitones:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.749727,Single)
|Clef|Type:Treble
|Instrument|Name:"Violin"|Patch:40|Bank:0,112|Trans:0|BendRange:2|DynVel:10,30,45,60,75,92,108,127|Pos:8|Wide:Y
|Note|Dur:Whole|Pos:-2
|Bar
|MPC|Controller:pitch|Style:Linear Sweep|TimeRes:Quarter|SweepRes:32|Pt1:0,8192|Pt2:2,16383|Pt3:1,8192|Pos:8|Wide:Y
|Note|Dur:Whole|Pos:-2
|Bar
|User|MIDIParm.nw|Pos:6|Type:RPN|MSB:0|LSB:0|DataMSB:12|Visibility:Never
|User|MIDIParm.nw|Pos:6|Type:RPN|MSB:127|LSB:127|ShowAs:RPNCancel|Visibility:Never
|Note|Dur:Whole|Pos:-2
|Bar
|MPC|Controller:pitch|Style:Linear Sweep|TimeRes:Quarter|SweepRes:32|Pt1:0,8192|Pt2:2,16383|Pt3:1,8192|Pos:8|Wide:Y
|Note|Dur:Whole|Pos:-2
|User|MIDIParm.nw|Pos:6|Type:RPN|MSB:0|LSB:0|DataMSB:2|Visibility:Never
|User|MIDIParm.nw|Pos:6|Type:RPN|MSB:127|LSB:127|ShowAs:RPNCancel|Visibility:Never
!NoteWorthyComposerClip-End
259
General Discussion / Re: NRPNs in NWC 2.75 Beta
NWC 2.75 includes the necessary infrastructure to support NRPN instructions, but it does not offer any native controls to send such instructions. I created a user object that should make it very easy to control your organ stops. Refer to the new MIDIParm.nw  object plugin:

Quote from: NoteWorthy Online –
This object allows you to send MIDI RPN and NRPN changes. If you do not want these to show when printing, then you will need to hide the object. You can change the text that is displayed for the object by adding a ShowAs property.

If you need any help, just reply here. It would be useful to know additional details about the kind of parameter number changes needed by your organ.
260
Object Plugins / Melismatic.nw
Melismatic.nw will detect melismas in a staff and automatically draw an extender line that spans the notes contained within the melisma. Only a single Melismatic.nw object is required. Simply add it to the start of any staff with lyrics, and the rest is automatic.

You can turn off Melismatic.nw at any point in a staff by adding a Melismatic.nw object, then assigning its Visibility to Never.

This object was inspired by the original work of Rick G on his rg_LyrEx object. The Melimatic object would not have been
possible without his original effort.

To get started, copy and paste the following object into a staff:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|User|Melismatic.nw|Pos:-11|Class:StaffSig
!NoteWorthyComposerClip-End

To turn off the Melismatic.nw process, simply copy and paste the following into the staff at the point where the processing is no longer required:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|User|Melismatic.nw|Pos:-11|Class:StaffSig|Visibility:Never
!NoteWorthyComposerClip-End
261
Object Plugins / ChordPlay.nw
ChordPlay enables show and play of a named chord. For play back, the duration of the chord is determined by the indicated Span value, which defines the number of notes/rests for which the chord will play.

The Font, Size, and Style can be set within any instance of ChordPlay, but only the first instance in a staff generally needs to define the font details. By default, all subsequent ChordPlay objects will use the font details specified in the first instance in the staff. If the first instance is being used only for setting default display options, then it will show as a special object.

The following clip will get you started:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|User|ChordPlay.nw|Pos:7|Font:MusikChordSerif|Size:8|Style:b|Visibility:Never
|Clef|Type:Treble
|Instrument|Name:"Acoustic Guitar (nylon)"|Patch:24|Bank:0,112|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:-9
|TimeSig|Signature:4/4
|User|ChordPlay.nw|Pos:7|Name:A|Span:1
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:A
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:D
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:A
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:D
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:F#m
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:A
|Rest|Dur:Whole
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:C#m
|Rest|Dur:Half
|User|ChordPlay.nw|Pos:7|Span:1|Name:F#
|Rest|Dur:Half
|Bar
|User|ChordPlay.nw|Pos:7|Span:1|Name:B7
|Rest|Dur:Half
|User|ChordPlay.nw|Pos:7|Span:1|Name:E7
|Rest|Dur:Half
|Bar|Style:LocalRepeatClose|Repeat:4
!NoteWorthyComposerClip-End
262
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 33
NWC 2.75 Beta Preview 33 changes include:

  • Tools, User Objects command for assisting with the download and install of new and upgraded user object plugins that are published here
  • Marker object formally added to the Insert menu
  • Early beta preview edition of the program help file
263
General Discussion / Re: updates
Your question lacks some important details, but I assume you are asking if there are known problems in NoteWorthy Composer to trigger an erratic mouse response. We do not have any known issues that would cause something like this.
265
Object Plugins / CustomKey.nw
This object allows a list of accidental strings to be defined such that they form a custom key signature. The following sample will get you started:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.749727,Single)
|Clef|Type:Treble
|User|CustomKey.nw|Pos:0|Class:StaffSig|AccList:1,7,,,2
|TimeSig|Signature:28/4
!NoteWorthyComposerClip-End

A list of accidentals are defined by a series of comma separated strings. Each string in the sequence gets displayed at the next position in the circle of fifths. An empty string can be used to skip a position in the circle of fifths. By default, the circle of fifths position starts at position 0, and cycles through the standard flat circle of fifth positions. If the list continues, the traditional sharp circle of fifth positions are used. If the list continues, then the process wraps and starts over again with position 0.

The starting position in the flat to sharp circle of fifths can be defined. This can be used to start with the first sharp position. The exact location for each position is relative to the user object's position, which allows additional flexibility.

This object is best used with the Accidentals font, by Ertuğrul İnanç. It can be found at:

http://nwc-scriptorium.org/sfontr.html


See also:

267
Object Plugins / About Object Plugins
Object plugins allow a variety of custom functionality to be added to your NoteWorthy Composer file. Each Object can be subclassed using specially crafted scripts that can establish new behavior for each object type. An introductory video is available on our YouTube channel:

Introduction to Manage Objects Video

Prerequisite

Objects are a new feature in NoteWorthy Composer 2.75.


Installing a New Object Plugin

Objects are automatically loaded by NoteWorthy Composer when they are placed into the Object Plugins folder. This folder is set from Tools, Options, Folders, and by default uses a standard Windows location.

You can automatically download and install new object plugins published here by using the Tools, Manage Objects command, which opens with Ctrl+J. For new objects, you should generally open the sample's object clip first. Click the Options button, then Check online sources. This will identify any plugin source code that can be downloaded or upgraded from the forum. You can right click, or double click, any object types that you would like to install.

If you are using Windows Vista or later, you can also copy and paste the following URL into an Explorer or Open/Save window to go straight into the default location for these plugins:

Code: [Select · Download]
%ProgramData%\Noteworthy Software\nwc2\UserPlugins

Contributing

If you want to share an object plugin that you have created, then you can request post access to this area. Each object plugin must include a unique author designation, which is called its NWC Plugin-ID. Please indicate your preferred Plugin-ID with any request for posting access to this forum.

This forum board is intended to be used exclusively for posting new object plugins. The following rules apply:

  • All topics must publish at least one object plugin
  • Object plugins may only be attached in the primary/top message of each topic
  • All object types must be named with an official Plugin-ID, or .test if you are still in the development phase
  • The object's Plugin-ID must match your profile's Plugin-ID or .test
  • The title of a topic should indicate the object name
  • You should provide a sample nwctxt clip or file that includes your object

Any topic that is found to not follow these rules will be moved or deleted.
271
Announcements / Web site/server changes
We are in the process of migrating our online systems over to a new system. As a part of this process, we are moving NWC specific web resources over to the noteworthycomposer.com domain. During this process, you may experience occasional failures, unusual navigation results, and changes to the look and feel of some pages/areas.
273
General Discussion / Re: Data Security
Our metrics, and general industry trends, indicate that many people have moved to cloud based e-mail. Although this sacrifices privacy, it does tend to protect against catastrophic hacks. In this scenario, your provider wants to be the sole source of data tracking, so they tend to protect you from external attacks. Good news, bad news...
275
General Discussion / Re: Why does my Noteworthy keep crashing?
Sometimes, resolution by committee can lead to even more trouble.

I would recommend starting with the actual crash message, as well as what you are doing when the crash occurs. If these crashes are not consistent in message or trigger, then and only then would I recommend taking other steps (perhaps a memory/cpu stress test).

Also, as mentioned, the latest NWC version is 2.51a. If your version really says 2.55, then this is an obvious cause for concern.

Update: If you are using version 2.5.5, then you should definitely upgrade to version 2.51a. There were some stability problems in version 2.5.5 (in particular, File->New was prone to crash).
278
General Discussion / Re: Fetching preview...
From what I could tell, the root of this problem appears to be the failure of Firefox to forward the session cookie during the Preview request. A forum upgrade is in the works, so this issue may work itself out over time.

Update: After testing this in a variety of browsers, it appears as though the AJAX version of preview is just broken. Some browsers fall back to the standard POST preview, and others do not.
279
General Discussion / Re: Fetching preview...
As a temporary work around, you should be able to hold the Ctrl key down while pressing the Preview button. This disables the sendXMLDocument Javascript behavior, and forces a normal posted preview. Don't do this after adding attachments, though.
280
General Discussion / Re: Fetching preview...
If this problem is with Post Preview and not Print Preview, I can easily simulate a "Fetching preview..." hang by disabling Javascript after I start to author a reply. The post preview mechanism uses Javascript to perform its function when the browser reports that Javascript is enabled during page load.

Quote from: Flurmy –
Yes, I do: NoScript, Google Privacy, Setting Sanity, Privacy Badger Firefox.
I tried disabling all them but nothing changed.

I suspect that any of these would be capable of causing issues like this. Other things can also block your Javascript preview request, such as a router.


Quote from: Mike Shawaluk –
AND.... I just followed my own advice. I fired up Firefox (which I normally do not use), and lo and behold, IT DOESN'T PREVIEW FOR ME EITHER!!!!!

When I hit F12 and try to preview, I get this error:

TypeError: XMLDoc.getElementsByTagName(...)[0] is undefined

Post preview worked fine for me in Firefox. Then, I played around with the F12 console. Now, post preview no longer works. I'll try to track down why this is.
284
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 26
NWC 2.75 Beta Preview 26:

  • fixes the problems with text scaling and older format files
  • converts all font sizing to use floating point calculations
  • converts nwctxt Version handling to use full double precision floating point values
285
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 25
NWC 2.75 Beta Preview 25 includes a new scaling feature for text expressions. This allows each text expression to be individually sized, without using additional user font definitions. The editor allows direct adjustment of a single, selected text expression using the +/- keys.

This release also hardens the plugin mechanism against various mathematical overflow/range errors.
288
Announcements / Forum Crashed
Yesterday, we experienced a server crash, and subsequent forum corruption. During the recovery process, the "currently read posts" tracking mechanism was reset. This means that you will see all existing topics as "New Posts" regardless of whether you have read them or not. Frequent visitors might want to "MARK ALL MESSAGES AS READ" in the lower right of the main forum index. The forum should resume normal message read tracking from this point.
289
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 20
NWC 2.75 Beta Preview 20 makes the following changes to the experimental Lua based userdraw mechanism (further details can be found in the Back Stage area):

  • fix for program instability/crash when running userdraw plugin methods
  • the +/- keys now support a single, selected User item's Span property, if it contains one

293
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 15
NWC 2.75 Beta Preview 15 includes:

  • MPC empty time offsets
  • Visible (experimental) Marker object in Selectors
  • View and Play Span now show as real numbers in Score Review
  • Pitch Bend control is now centered when play is started for any channel that sends Patch or Bend Range instructions
  • F6 MIDI Stop/Reset use of the standard Channel Mode Messages (these were abandoned back in the day due to issues with some devices)
294
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 14
NWC 2.75 Beta Preview 14 changes include:

  • Modifies the new Pitch Bend Range to support 0 and 1 semitones
  • Play back pause and resume should now properly track both RPN (Registered Parameter Number) and NRPN (Non-Registered Parameter) controller data with both the Data Entry MSB (Controller 6) and Data Entry LSB (Controller 38) values
  • User objects from nwctxt now properly show Unicode text in Properties
  • Fixes a bug in the Multi-point Controller Properties preventing the direct entry of larger controller values
295
Announcements / Re: NoteWorthy Composer 2.75 Beta Preview 13
NWC 2.75 Beta Preview 13 includes numerous changes/additions (use with caution):

  • Pitch Bend Range can now be defined from the Instrument specification
  • Staff level Pitch Bend Range is shown in Score Review
  • Play back pause and resume should now properly track RPN (Registered Parameter Number) controller data
  • Score Review now shows full MIDI duration values in Play and View Span statistics
  • Many low level changes to the *.nwc file format (all notation data is now stored as nwctxt, with a standard *.nwc header)
297
Announcements / Re: Forum converted to utf-8 encoding
Thanks for the report.

I updated the code highlighting mechanisms to properly parse ' entities. Since my fix was very narrow, there might be other issues. If you notice other issues like this, please post here.