Finale SmartMusic
  Home | Log In | Register | Search | Help
   
MakeMusic Forum > Public Forums > Plug-In Development - FORUM HAS MOVED! > New Beta plug-in: JW Change v0.27  Forum Quick Jump
 
You cannot post new topics in this forum. You cannot reply to topics in this forum. Printable Version
168 posts in this thread.
Viewing Page :
 1  2  3  4  5  6  7 
[ << Previous Thread | Next Thread >> | Show Oldest Post First ]

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/10/2012 10:08 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
Beta version 0.14 of JW Change is now available for download. New for this beta:
* Articulation resize now resize to the % of the default accidental font size for the document
Do you mean "Articulation resize now resize to the % of the default articulation font size for the document"?


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/10/2012 10:05 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Hi Jari,

"Placement" still exists under Rests instead of "Vertical Position". Is this intentional? (all the other elements have both horizontal and vertical position.)

The "Relative" checkbox option under "Rest/"Placement" doesn't seem to do anything. When I have rests in two layers (separated using the document/layer options) and try to move them up a couple of spaces relatively to their current position they get superimposed on top of one another (i.e., layer 2 rests get move up more than layer 1 rests).

Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Post Edited (KennethKen) : 2/10/2012 9:09:45 PM (GMT-6)

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/9/2012 6:29 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Beta version 0.14 of JW Change is now available for download. New for this beta:
* Articulation resize now resize to the % of the default accidental font size for the document
* Resize of objects now support relative resize
* Bug fix: 8th note beams didn't resize with Beams/Resize
* "Move" has globally been split into "Horizontal Position" and "Vertical Position". It's also consistently grouped with Clear Position. This gives more logic and power to the movement of objects.
* Functions that use popup options now have a title text above the popup.
* "Grace Note" entry filter added
* Durations now appear last in the "composite" entries filter popup (instead of in the middle)
* Speed optimization for all the articulation functions that might create new definitions
* Added the "z tremolo" to the "Tremolo" articulation filter
* Added "Known Music Fonts Only" to "Articulations/Fonts". If the option is checked, only articulations with a known music font name will be swapped.
* "Noteheads/Shape": Added support for "Filled Square" (208) and "Filled Triangle" (209)
* "Articulations/Swap" added


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/7/2012 3:36 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
KennethKen said...
So using Clear Position is a shortcut to resetting Horizontal and Vertical Positions to 0 at the same time?


Yes, if both X and Y position adjustments are available for the object type. And for some objects it involves even more than that (for beams for example).


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/6/2012 7:13 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
KennethKen said...
Very nice. Will the Clear Position option be available separately under the Horizontal and Vertical Positioning functions so that you can keep one direction aligned while resetting the other?

Setting the absolute position to 0 would do that.
So using Clear Position is a shortcut to resetting Horizontal and Vertical Positions to 0 at the same time?


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/6/2012 1:48 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
KennethKen said...
Very nice. Will the Clear Position option be available separately under the Horizontal and Vertical Positioning functions so that you can keep one direction aligned while resetting the other?


Setting the absolute position to 0 would do that.


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/6/2012 11:06 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
What's going to happen in the next beta is that "Move" will be split into "Horizontal Position" and "Vertical Position". That will solve quite a number of problems and limitations with the current "Move" approach. These will be lined up as following:
Horizontal Position (if available for the object type)
Vertical Position (if available for the object type)
Clear Position
Very nice. Will the Clear Position option be available separately under the Horizontal and Vertical Positioning functions so that you can keep one direction aligned while resetting the other?
 
Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/6/2012 10:50 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
KennethKen said...
Jari Williamsson said...

EDIT: I might actually rename "Move" globally to something else in the next beta. Stay tuned...
"Space" or "Spacing" ?

These words come to mind when I think of moving elements back and forth horizontally.


What's going to happen in the next beta is that "Move" will be split into "Horizontal Position" and "Vertical Position". That will solve quite a number of problems and limitations with the current "Move" approach. These will be lined up as following:
Horizontal Position (if available for the object type)
Vertical Position (if available for the object type)
Clear Position

"Position" above might be changed to "Adjustment", I've not decided on that yet.

Transpose for rests is a good suggestion. Thanks!


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/5/2012 1:08 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
EDIT: I might actually rename "Move" globally to something else in the next beta. Stay tuned...
"Space" or "Spacing" ?
 
These words come to mind when I think of moving elements back and forth horizontally.


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/5/2012 1:03 PM (GMT -6)    Quote This PostAlert An Admin About This Post.

How about this?

Change "Displace" to "Transpose" - It may be weird to think of rests as transposed but since the Displace function is so closely tied to the tonality of a passage I think a user would more easily draw the association between the rests position and the key/clef of this function. It would also make it more consistent with the term used to vertically "move"tongue notes.

Change "Displacement" to "Reposition" since the use of this funtion is to re-position rests that have already be "placed" manually or using a Placement Style.

Ken

PS Since you bring up the mess of the Articulation Definition DBX, I consider your "Rests/Placement Style" equivalent to "the Articulation's Designer's "Position" (ie.., Above Note, etc.) and your "Rests/Placement" equal to the setting "Default Vertical Position" of the Articulation Designer. (The Articulation's Designer's "Positioning" [i.e., Avoid staff lines, etc.] checkboxes I consider to be "Position Options")


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/4/2012 7:36 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
Ken:
I'll keep "Move" as it is, since that would make it consistent with the rest of the plug-in ("Move" always moves the element in measurement units). For example, noteheads are visually adjusted with "Move" but vertically adjusted with "Transpose". The day Finale will support vertical EVPU adjustments of the rests, the UI of the plug-in would still be consistent.

However, I agree that "Placement" isn't good. I'm thinking about using "Level" instead of "Placement"? What do you think? And "Displace" need to be reworded as well. You're right about the meaning of these functions. I'll rewrite the hint text for Placement/Level/whateveritwillbecalled.

I have a very similar issue regarding Articulations, where I need a difference between the origin location (for example, above/below entry) and position adjustment (EVPU location compared to the original attachment point). I the Articulation definition dialog box, it's IMO just a confusing mess of "Position" and "Positioning".

I aim to find a system that works equally well for all object types.

EDIT: I might actually rename "Move" globally to something else in the next beta. Stay tuned...


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Post Edited (Jari Williamsson) : 2/4/2012 3:40:58 PM (GMT-6)

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/1/2012 11:48 AM (GMT -6)    Quote This PostAlert An Admin About This Post.

Please permit me to take another shot at convincing you to clarify the "Move" title under the "Rests" heading.:-)

I do understand your desire to keep things consistent with the other headings. However, without stating which direction the "Move" function is meant to handle, that title under "Rests" is not the clearest or most intuitive title to use with Finale because of the follow reasons:

  1. The "Move Rests..." plugin that comes with Finale moves rests vertially not horizontal. When I see Rests/Move in your plugin I automatically think that's for vertical moving - like the other plugin.
  2. I believe Finale generally does a better job at automatically moving rests horizontally out of the way (automatic spacing) - and I would think most users would still first use the Beat Chart to move rests horizontally, especially when working on a score where the rhythms are supposed to line up. Anyone who works on piano music and multipart staves knows how Finale is not as good at moving rests vertically out of the way (since the layer placement options are not dynamic). So, at least for me, moving rests vertically is a more common chore. Therefore, when I see "Rests/Move" I think, "Great! I can move my rest up out of the way with this!" {Click} "Oh, no. I can't."
  3.  Since "moving" and "displacing" are synonyms, the titles must express to the user any basic difference you have programmed into these functions without the user having to click on them first. I would think you'd want to avoid puzzling the user with the titles simply because differentiating adverbs are missing from those verbs.idea

Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 2/1/2012 11:08 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
I like the new description you have for Displace (v0.12). It's very clear.
 
I'm still not clear on the definition of "Placement" which states that vertical placement of the rests are relative to the staff's top line. So when I type "0" I expect to see the rests move to the staff's top line. But they don't!?shocked
 
I'm beginning to understand the issue of naming these functions since any moving of rests is technically, "displacing" them (another reason why I feel the "Move" title needs more information to it). I understand "Displace", but my understanding of how it differs from "Placement" comes and goes since "Placement" also takes clef and key into account. I think "Displace" is a type of "Tonal Placement" while "Placement" is more of a "Visual Displacement" where clef and key information is retained but only used for positioning when the clef or key is changed...? Is this right?
 
I can do more testing in the next few days.
 
Ken
Sorry I'm focused on rests for now - making cues is my pet peeve (which is why I asked about clef editing).


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/1/2012 6:00 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
Beta version 0.12 of JW Change is now available for download. New stuff:
* New option for feathered beaming: "Align Horizontally" that will orientate the feathered beamed group along the horizontal line.
* Cleaned up some feathered beaming code
* "Beams/Clear Position" now also resets the custom adjustments for the primary beam
* "Beams/Move" is now implemented
* A 2+4 layer filter added as well
* "Rests/Displacement" renamed to "Rests/Displace"
* "Rests/Static Displacement" and "Rests/Position Style" renamed. All references to "position" regarding the vertical rest location is now changed to "placement".
* "Rests/Placement Style" changed again. Now 10 options.
* Fixed a bug where the rest placement "Moveable" had to be applied twice to actually be moveable


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 2/1/2012 6:00 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
Ken, I've taken a bit different approach in v0.12, but still based on you remarks. Let me know how it works.


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/31/2012 6:58 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
If I change "Move", I need to change it for note entries as well. I'll try not to rename if consistency is lost. I need to think a bit more about this.
I understand. It helps to know/be reminded which direction the "Move" is designed for without having to click on it. The Move Rest plugin is an up-down "move". "Move Horizontally" ?
Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 1/31/2012 6:26 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
I think I'll remove the word "Displacement" from the "Static Displacement", to something like "Static Position", "Fixed Position" or similar.

"Displacement" will probably stay. It's used and documented in Finale (in the Edit Frame dialog box).

If I change "Move", I need to change it for note entries as well. I'll try not to rename if consistency is lost. I need to think a bit more about this.


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/31/2012 1:20 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Thinking about your "Displacement" vs "Static Displacement" issue, maybe "Displacement should be renamed "Relative Displacement"
 and there could be 2 ratio buttons
  • "Relative to Current Position"
  • "Relative to middle C of the Clef/Transposition"

Static Displacement can be renamed "Non-Relative Displacement" (maybe there's a better word for non-relative). In your description you say that it measures from the staff's top line. However, it looks to be measuring from the center (3rd) line. I.e., When I set the displacement to 0 the rests congregate on/above the 3rd staff line. Is this correct?

Ken

Everytime I see "Move" in the Rests part of this pligin I think it means vertically - even after spending the last hour working with the displacement function. This may be because the Move Rest Plugin that comes with Finale does move things vertically. Can there be a clear distinction? Maybe you would consider the following. Instead of -

Resize
Clear Position
Visibility
Move
Position Style
Beaming
Presence
Displacement
Static Displacement

How about -

Resize
Visibility
Presence
Horizontal Displacement
{replaces "Move"}
Clear Horizontal Displacement {replaces "Clear Position"}
Vertical Position Style
Relative Vertical Displacement
Non-Relative Vertical Displacement
Beaming

This allows me to see what a function is meant to do with having to click on it to see its options first. It also place simpler functions next to each other (e.g., horizontal moving/clearing,  vertical moving/clearing, visibility/presence. I understand that you're trying to have all the other element lists be the same (Note Entries, Noteheads, etc.) but maybe you would consider reordering those as well.

Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/31/2012 12:45 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...

It currently assumes a 5-line staff, but these styles also take clef changes and transpositions into account. Rests/Displacement doesn't.

I'll add a different editing mode called "Static Displacement" (with the current lack of a better term, other suggestions? I don't want to use the word "absolute" here) where you can set the fixed displacement position relative to the top staff line. That way you can filter whole/half rests separately if you'll need a different positioning for them.
I don't think the difference between Displacement with "Relative" unchecked and Static Displacement is not clear enough. Maybe you can put in the description for Displacement something along the lines of the following:
 
Sets the vertical displacemenet offset of the rest (in note steps). When relative is unchecked transposition and clef are taken into account and the displacement number is measured from where a line equal to the sounding pitch of middle C would be notated. Therefore, the displacement for a concert pitched treble clef staff would be measured from the first ledger line belowthe staff; for a bass clef staff, the first ledger line above; and for a treble clef Horn in F staff, the 2 line.
I know, it's a bit wordy. But it would have saved me the last half hour trying to figure out what the heck was going on.idea
Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 1/31/2012 11:03 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
KennethKen said...
If the Rest/Displacement function does not affect the display of floating rests but does affect them if they are unfloated (either manual or through the plugin, I would clearly state that in the explaination of the option. Something like this:
Sets the vertical displacement offset of of the rests (in note steps). Note: The verical displacement will not "display" on floating rests until their floating attribute is remove via the Speedy Edit Frame or JW Plugin Change/Rests/Position Style/Movable.
Is it then adviseable to apply the "Movable" Position Stlye before doing any displacement so that the results are apparent?


Rests/Displacement automatically unfloats the rest (to make sure the displacement shows up) for convenience, no need to do the additional step.

KennethKen said...
the assumption of a 5-line staff or some users writing out percussion parts may get confused.


I consider it a "bug" that just 5-line staves are supported for correct rest placement. I'll implement support for it later on.

Thanks for you other comments! I'll look into each of these for the next beta release.


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/31/2012 10:19 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
KennethKen said...
* I'm not sure what I did to my rests in m.65 [Reh. F] but the Rest/Displacement function does not function as expected in these measures. The amount of displacement the whole rest moves (note: we're in 3/4 time here) seems different than the number of note stpes I requested. The file is attached (March of the Corn - Finale 2010 file opened in Finale 2012). Maybe you can figure out what's going on. I also seemed to have broken the function with a temporary file I created with Finale 2012a.


It's the nature of floating rests in Finale. A floating rest will not be affected by the displacement, so the "displayed displacement" for the layer 2 notes are actually 6 steps off (set in the Document Options). When rests are moveable, the displacement value is used instead of the layer options.

"Movable" is the positioning style that does the "unfloat rests". The manual positioning clears if you set the position style to "Float" again. In the next beta I'll add a "Float (Clear)" option as well, that will set the rest to float and also set the displacement to 0 (that doesn't make any visual difference compared to just set it to float, but if you later makes it moveable again it would show).
Ok. I'm trying to wrap my head around this and try to suggests terms that allow my brain to reconcile what I'm seeing.
  1. If the Rest/Displacement function does not affect the display of floating rests but does affect them if they are unfloated (either manual or through the plugin, I would clearly state that in the explaination of the option. Something like this:
    Sets the vertical displacement offset of of the rests (in note steps). Note: The verical displacement will not "display" on floating rests until their floating attribute is remove via the Speedy Edit Frame or JW Plugin Change/Rests/Position Style/Movable.
    Is it then adviseable to apply the "Movable" Position Stlye before doing any displacement so that the results are apparent?
  2. When I see the term, "Floating (Clear)", as a position style it tells me that hitting Apply will "clear" the "floating" attribute of the rests. Since this is not the case and "clear" refers to clearing (putting "0" in) the displacement attribute of the rests, I would suggest using the term, "Floating (Clear Displacement)".
  3. If Movable unfloats rests I would state that it does by using the term "Movable (Unfloat rests). However, I'm noticing that if I put a whole rest in a measure in both layers 1 & 2, it takes hitting "Apply" twice to unfloat the rest with this option. The first click doesn't appear to do anything and the second clicking of "Apply" places the rests under on the bottom staff line. Both the fact that it takes 2 clicks to unfloat the rests and that both rests move to the bottom line surprise and confuse me.eyes
 (BTW Both spelling are considered correct in most dictionaries. The Finale User's Manual uses "moveable" twice - once when talking about the Move Rests plugin - and uses "movable" 15 times. "Moveable" looks better to me and is therefore quicker for me to read even (though I'm using "movable" in this post) but either is ok.)
 
As far as naming the other options:
  • "Above Staff"[v0.11] can be changed "Far Above Staff"
  • "Above Top Staff Line"[v0.11] can change to "Above Staff". This looks too high to be referencing the top staff line.
  • "On Top Staff Line" [v0.10] (was displacement=10, I liked that option but you seem to have removed it) can change to "Above Top Staff Line". Yes, placing something "above staff" is also placing it above the top staff line but the title draws attention to the "top staff line" so I think users will better be able to predict what where the rest will be moved - just above the top staff line. This becomes more important with the lower options and different duration rests - see below.
  • What we're now missing is "On Bottom Staff Line"[v0.10] I think it was displacement=2 and I also liked this option). I would suggest renaming it to "Above Bottom Staff Line" so that it doesn't confuse people - as it did me - when a whole rest displays as hanging from the 2nd line (and not visually on the bottom staff line). (PS I just notice how weird Finale's 32nd rests look next to 16th and 8th rests. Are they really supposed to add "hooks" on the line above before adding them below the 16th rest "hook"?)
  • "Below Bottom Staff Line" is perfect. That's exactly were all types of rest appear - just below the bottom line.
  • "Below Staff" is perfect. Since the bottom staff line isn't mentioned I assume the rest will be plaved somewhat lower.
The verbage isn't as symetrical as you may like but it much easier for me to predict where rests - including/especially whole rests - are going to be repositioned. You may want to think about including a warning in the appropriate descriptions about the assumption of a 5-line staff or some users writing out percussion parts may get confused.
 
Ken
 



Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Post Edited (KennethKen) : 1/31/2012 9:44:10 AM (GMT-6)

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 1/31/2012 6:00 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
JW Change beta version 0.11 is now available for download, since there was a quite big introduced in 0.10 (where only note entries in the first measure in the selection were processed). Also, many modifications to rest editing in this new beta.

Changes in this version:
* Fixed bug (introduced in beta v0.10) where only the first selected measure with entries was processed
* The "Rests/Position Styles" has been changed into 8 options "Floating (Clear)", "Floating", "Movable", "Default-Centered on Staff", "Above Top Staff Line", "Below Bottom Staff Line", "Above Staff", "Below Staff"
* "Rests/Static Displacement" added. With this, a "fixed" vertical position can be set for the rest (regardless of clef/transposition) where the Position Styles doesn't do the job. 0 would give the same result as the standard rest placement for a floating rest in one-layered music.
* The word "Displacement:" is now fully visible on the Mac as well


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

Jari Williamsson
Registered Member

Click to send Jari Williamsson email.Click to visit Jari Williamsson's website.Send a Private Message to Jari WilliamssonAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 3246
 
   Posted 1/31/2012 4:37 AM (GMT -6)    Quote This PostAlert An Admin About This Post.
KennethKen said...
* The plugin seems to only work on the first measure of music select.


Thanks! Bug was introduced in v0.10, will be gone in v0.11.

KennethKen said...
* I'm not sure what I did to my rests in m.65 [Reh. F] but the Rest/Displacement function does not function as expected in these measures. The amount of displacement the whole rest moves (note: we're in 3/4 time here) seems different than the number of note stpes I requested. The file is attached (March of the Corn - Finale 2010 file opened in Finale 2012). Maybe you can figure out what's going on. I also seemed to have broken the function with a temporary file I created with Finale 2012a.


It's the nature of floating rests in Finale. A floating rest will not be affected by the displacement, so the "displayed displacement" for the layer 2 notes are actually 6 steps off (set in the Document Options). When rests are moveable, the displacement value is used instead of the layer options.

KennethKen said...
* Will there be an option for "Unfloat rests"? Will there be a function to clear manual vertical positioning? Even though this exits in the "Move Rests..." plugin, including it in yours will maake you plugin seem more complete and prevent us from having to go into that other plugin (which is not modeless).


"Movable" is the positioning style that does the "unfloat rests". The manual positioning clears if you set the position style to "Float" again. In the next beta I'll add a "Float (Clear)" option as well, that will set the rest to float and also set the displacement to 0 (that doesn't make any visual difference compared to just set it to float, but if you later makes it moveable again it would show).

BTW, should it be "movable" or "moveable"?

KennethKen said...
* "On Bottom Staff Line" places whole rests on the second line. I can see you're trying to keep the position of rests relative so that "On Bottom Staff Line" is actually having rests position themselves around the bottom line (as if it were the default 3rd staff line) - meaning that most will sit on it but the whole rests will actually hang from the line above it. This explains why "Centered on Staff" still puts the whole notes on the 4th line. The wording was a bit misleading to me given that this is a plugin that allows you to move rest exactly where you want to and since, when I'm moving rests for a 2-part staff or for cues, I often do hang a whole rest from the the line that the other rests are sitting on. E.g., whole rest hangs from top line while others sit on it. Given the vertical clearance needed for everything other than whole and half rests this provides better readbility for the other part (and a whole rest seldom appears in the same measure and layer as other rests). I think "Above Bottom/Top Staff Line" is more accurate for all types of rests and the results won't surprise anyone. You could then change the "Far Below/Above Staff" option to simply "Above/Below Staff".


Let's see if I got this right:
* "Below Staff" should be named "Below Bottom Staff Line"?
* "Far Below Staff" should be named "Below Staff"?
* I'll remove the "On Bottom Staff Line", and replace this with "Static Displacement" (see below).

KennethKen said...
Are the 7 bottom choices under Rests/Position Style simply a hardwired verison of Rests/Displacement?


It currently assumes a 5-line staff, but these styles also take clef changes and transpositions into account. Rests/Displacement doesn't.

I'll add a different editing mode called "Static Displacement" (with the current lack of a better term, other suggestions? I don't want to use the word "absolute" here) where you can set the fixed displacement position relative to the top staff line. That way you can filter whole/half rests separately if you'll need a different positioning for them.

KennethKen said...
Will Clefs be added to the lineup of editable musical elements in this plugin?


Perhaps. It's on the list for the future expansion.

Thanks very much for you valuable comments!!!


Jari Williamsson

Windows XP, Pentium 4
2.40 GHz, 4 GB RAM

www.finaletips.nu - The Finale Productivity Tips site

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/30/2012 9:57 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Jari Williamsson said...
KennethKen said...
Think you can add Multimeasure Rests to this plugin? I'm thinking of a quicker way to shorten the multimeasure rest shape (and possibly overall width) when a clef change (or cue) appears at the end of it, just before the barline. Going in and out of the context menu when editing parts is annoying.

I try to keep JW Change to handle "musical" contents. I might do another plug-in later on with layout stuff, that would include MM rest editing.
May I humbly submit the argument that shortening the appearance of a multimeasure rest's shape (to make room for a cue or clef change) is akin to horizontal moving rests (to make room for other stuff) - which is provided for by the Change plugin.
 
Ken
(Although, I do realize that there may differences in the programming of such things from a developer's point of view.:p )


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.

Back to Top

KennethKen
Registered Member



Email Address Not AvailableClick to visit KennethKen's website.Send a Private Message to KennethKenAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Dec 1998
Total Posts : 2570
 
   Posted 1/30/2012 9:50 PM (GMT -6)    Quote This PostAlert An Admin About This Post.
Hi Jari,
 
  1. The plugin seems to only work on the first measure of music select.
  2. I'm not sure what I did to my rests in m.65 [Reh. F] but the Rest/Displacement function does not function as expected in these measures. The amount of displacement the whole rest moves (note: we're in 3/4 time here) seems different than the number of note stpes I requested. The file is attached (March of the Corn - Finale 2010 file opened in Finale 2012). Maybe you can figure out what's going on. I also seemed to have broken the function with a temporary file I created with Finale 2012a.
  3. Will there be an option for "Unfloat rests"? Will there be a function to clear manual vertical positioning? Even though this exits in the "Move Rests..." plugin, including it in yours will maake you plugin seem more complete and prevent us from having to go into that other plugin (which is not modeless).
  4. "On Bottom Staff Line" places whole rests on the second line. I can see you're trying to keep the position of rests relative so that "On Bottom Staff Line" is actually having rests position themselves around the bottom line (as if it were the default 3rd staff line) - meaning that most will sit on it but the whole rests will actually hang from the line above it. This explains why "Centered on Staff"  still puts the whole notes on the 4th line. The wording was a bit misleading to me given that this is a plugin that allows you to move rest exactly where you want to and since, when I'm moving rests for a 2-part staff or for cues, I often do hang a whole rest from the the line that the other rests are sitting on. E.g., whole rest hangs from top line while others sit on it. Given the vertical clearance needed for everything other than whole and half rests this provides better readbility for the other part (and a whole rest seldom appears in the same measure and layer as other rests). I think "Above Bottom/Top Staff Line" is more accurate for all types of rests and the results won't surprise anyone. You could then change the "Far Below/Above Staff" option to simply "Above/Below Staff".

Are the 7 bottom choices under Rests/Position Style simply a hardwired verison of Rests/Displacement?

Will Clefs be added to the lineup of editable musical elements in this plugin? Specifically, changing the horizontal offset of mid-measure clefs.

Ken


Windows 7 Pro (64 bit), Finale 2012, Core i7 [email protected], 6GB Ram
Brass music, Woodwind Music, Concert Band Music, CDs, etc.



File Attachment :
March of the Corn - tmp Alto Sax. 1 2.mus   215KB (application/octet-stream)
This file has been downloaded 467 time(s).

File Attachment :
tmp.mus   113KB (application/octet-stream)
This file has been downloaded 482 time(s).
Back to Top
You cannot post new topics in this forum. You cannot reply to topics in this forum. Printable Version
168 posts in this thread.
Viewing Page :
 1  2  3  4  5  6  7 
   
Forum Information
Currently it is Tuesday, November 19, 2019 5:57 PM (GMT -6)
There are a total of 403,820 posts in 58,165 threads.
In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads