1. I have a measure with an upstem 1/8  note and a downstem 1/8 note.
2. The 1st note has a staccato under it and the 2nd has an accent over it.
3. I run Articulations/Horizontal Position with "50" input in the box. Everything moves to the right as expected.
4. I run Articulations/Vertical Position with "50" input in the box. The staccato moves down and the accent moves up. I suppose this makes sense as the number increases the distance the articulation is away from the notehead (of course a large negative number would do the same in the opposite direction). However, you may want to clarify the movement in this command's description. Someone could easily think that inputting "50" should move everything in one direction - up 50EVPUs - and -50 would move everything down.
5. I run Articulations/Clear Position. The articulations don't go back to their "original" positions - the positions they were in before I moved them with the other commands. It appears that this command is equivalent to setting the vertical and horizontal positions to "0" which is, apparently, different from their defaults. This is not intuitive and it looks like a bug. To get them back to their default position I have to select the articulations and hit the BACKSPACE key. I would expect the "Clear Position" command to be equivalent to hitting the BACKSPACE key (i.e., removing manual or plugin enacted positioning). "Clear Position" certainly doesn't "Reset manual positioning of the articulation" as its description says - it actual "sets" it to 0. (The "re" implies a return to a previous setting.)

Ken

I don't know how easy it is to add fonts to the font lists in the plugin (e.g., noteheads/fonts, articulations/fonts, etc.) but here are a few that I've found useful over the years.

MetTimes, MetHelvetica (not show but by the same vendor), Metronome, DVMarticulations, Kidnotes

CrescendoFLF, GraceNotesFLF

Ken
PS Why are MaestroWide, EngraverFontExtr, Maestro Percussion in the lists?

I'm getting some surprising behaviour with Rests/Beaming where Beam to Previous breaks some beams and Break Beam After Entry actually extends some beams. Is there some functionality that hasn't been hooked up yet that I should know about or would you like me to send specifics now?

Ken
My Doc Opts are Extend Beam Over Rests and Extend Secondary Beam Over Rests are both checked.

When Display half-stem for beamed rests is check in Doc Opts. the only way to hide a select group of these half stems is to assign a blank custom stem to them (at least that's the only way I can think of right now). Do you think it would be worth it to add a function for this under Stems or Rests (e.g., "Visibility [half-stems]"). Currently, the "Stems Visibility" command doesn't work on half-stem rests.

Ken
I don't think I'd have much use for this but I'm just playing around with the plugin now and some else may find half-stems on some rest more readable in some cases but not in others - in which case this plugin with its filters may be very helpful.

1. Select all of the music with the selection tool.
2. open JWChange/Rests/Beaming and select "Break Beam After Entry" as the beaming mode. (I'm not even sure what this is supposed to do. I think it's meant to break the beam on an entry [note or rest] that appears after a rest [since we're in the Rests container]...? Can you clarify?).
3. Click Apply and see that the beam in m.3 has extended itself rather than being broken in any way. (Same thing happens with "Break Beam Before Entry" as the beaming mode.)

1. Select all of the music with the selection tool.
2. open JWChange/Rests/Beaming and select "Beam to Previous" as the beaming mode. (I think this is suppose to beam any 1/8 or shorter rests to any 1/8 or shorter note that preceeds it).
3. Click Apply and see that the beams in m.1 and m.3 have been broken!

Post Edited (Jari Williamsson) : 3/5/2012 1:45:25 PM (GMT-6)

Post Edited (michelp) : 3/21/2012 9:21:49 AM (GMT-5)