I would expect a muted staff to be removed from playback.
For MIDI Export, I would expect that a muted staff would not be exported.
It is too soon for me to have an opinion on whether muted tracks should be excluded from nwctxt.
I would suggest that muted notes produce a note off. There is no harm in producing a note off without a previous note on. Many programs will send a 128 note offs X 16 channels encompassing every MIDI note as a brute force "kill switch". Every MIDI playback device must be able to deal with it. There are seldom many muted notes in a playback staff. The file and processing overhead would be undetectable to the listener.
I would suggest that grace notes produce a note off, but no pause.This is what I would expect a muted grace note to do. I don't expect, nor desire it to inject a pause into playback. I can't see a downside to this change as a muted grace rest could be used to simulate NWC's current playback behaviour.
Slurs. Muted, hidden grace notes are very useful for adding arc to slurs, but I'd rather not hear their effects.
The biggest advantage to me is that the program would do what I expect. For the person starting out, I would think it even more important.IMO, Software that does unnatural things in an attempt to be "accurate from its own point of view" is not friendly.
I assume that a "rest" produces no MIDI events at all? This makes sense to me and is what I would expect. How can it result in a "stuck note" unless there has been a previous note on event? This only makes sense if the "note on" note was tied to the muted note - I don't see why anyone would do this... Though, in the interests of "fool proofing" things perhaps a "note off" event is wise...
I would like much more control over grace notes than this simple change, though in the context above I have no objection.
... I'm not sure about the muted notes. It seems to me as though they have to be treated as rests in order to synchronize the playback of the remainder of the music.
Rests and muted notes are both holes in the music, and it seems redundant to have two different ways to make them happen.
As for ties to muted notes: I had actually made some on purpose a few minutes before I read your post. I had a multi-measure held note followed by a multi-measure rest in one voice against passagework in another, and I was trying to figure out how long to hold the note before cutting it off to begin the rest. I thought muting the tied notes one at a time, beginning at the rest and moving back toward the first note of the tied series, would be a clever way to test this. Of course, it didn't work. I'm not sure it has to work, but it does show one possible use of a tie to a muted note.
But I'm certainly with you on the muted staves and muted grace notes.
Like every (non-grace) Rest/RestChord/Note/Chord, a muted (non-grace) note must have duration to synchronize playback. That does not mean that it cannot be programmed produce a note off. Ideally, it would only do this when needed, but I cannot see any harm if it always produced a note off.
I would expect muted staves to generate no midi events at all, whether to the midi port or an exported midi file,
...but neither muting nor hiding removes a staff from the score, and so long as things like tempi and fermatas are permitted on more than one staff, muting a staff should not make these ineffective. Perhaps a new sequester or recuse attribute could make everyone happy. Of course, muting a visible staff should not affect the note chase.
...so I would ask that an illegal tie be flagged with an otherwise unavailable highlight color or made to blink or be given some such marker, and be ignored during playback.
The third case should not present a problem if muted notes generate only a note off event at the proper time, which is apparently not the case. For this reason they certainly should not be treated as rests.
Muting a grace note should, I think, be just like muting any other note; no aspect of the surrounding notes should change. A grace note interpreted as beginning before the beat need steal no time from any other note, but that interpretation needs a new attribute, probably at all of the score, staff, and note levels. Again, this new feature could make everyone happy.
I would expect muted staves to generate no midi events at all, whether to the midi port or an exported midi file, but neither muting nor hiding removes a staff from the score, and so long as things like tempi and fermatas are permitted on more than one staff, muting a staff should not make these ineffective. Perhaps a new sequester or recuse attribute could make everyone happy.
Of course, muting a visible staff should not affect the note chase.
The three ways to generate a stuck note represent, I think, only two different cases. <snip> The third case should not present a problem if muted notes generate only a note off event at the proper time, which is apparently not the case. For this reason they certainly should not be treated as rests.
Muting a grace note should, I think, be just like muting any other note; no aspect of the surrounding notes should change.
A grace note interpreted as beginning before the beat need steal no time from any other note.
Finally, no input to a program should produce a catastrophic failure, certainly not an illegal page fault, but probably not even a stuck note.
I only ever use a conductor staff for tempo variation events
We used to have a |Edit|Find...|Hanging Note Tie| facility (it's still in 1.75), perhaps that could come back..?
Better control of grace notes has long been desired.
I am changing my position on this to:A tie destination note should always produce a note off (muted or not).A muted grace notes that are not tie destinations should not alter MIDI.
Many argue that a "crush" is played by sounding both notes together and the releasing one quickly. Few instruments are capable of it and it is not what is done in the majority of cases that a grace note is encountered by a musician.For a single voice instrument, it must cut the prior note short, effectively "stealing" time from it.
I would submit that the real reason you do this is that you cannot disable them. If you could (at the staff level), I'd bet that in some pieces, you would have several conductor staves as you "try out" different options. The "choir users" could create a 1/2 tempo staff and mute one or the other.
IIRC, It left because the stuck note problem was considered solved.
I curse everytime I hit "e" for Tempo Variance and select Fermata. NWC2 inserts it as Left, Best Fit and that is never, never no never, correct for a fermata! It should always, always, yes always be Center, At Next Note/Bar. grrrr....It just occurred to me that I can write a User Tool that accepts a note and returns it with a properly placed Fermata. Sometimes it takes anger to get the creative juices flowing. I feel better now.
I use muted notes extensively.
if your muted grace notes were unmuted and tied to the main note, then no "hiccups" would result.
I hope I haven't missed the point, either.
NWC2 Beta 2.26 changes the behavior of a muted grace note such that it no longer shifts the play back time for the note that follows it.
An experimental change is also added that treats Visibility=Never, inwardly tied grace notes in a similar fashion. However, I don't think that this change is going to be kept.
I would expect a muted staff to be removed from playback.This would allow the user to set up multiple tempi and MPC staves and experiment by muting staves. Currently, I copy the staves into NotePad and insert/delete them from NWC. I can't save a work in progress, without starting the whole process over.
Page created in 0.044 seconds with 24 queries.