- Description has changed:
Diff:
~~~~
~~~~
- **assigned_to**: Dan Eble
- **Patch**: -->
- **Comment**:
I ran across some code that inspired head-scratching, and I believe it is
directly related to this issue. I can probably fix it. Here are my thoughts
for your review. Basically, in most cases, I don't think there is sufficient
reason to issue warnings.
crescendo with explicit dynamics (mf < f)
* at endpoints, use the specified dynamics
* between endpoints, interpolate
unspecified starting dynamic (... < f)
* use the most recent dynamic as the starting point
* at the start of the piece, use the default dynamic (issue #3945)
* between endpoints, interpolate
unspecified ending dynamic (mf < ...)
* at the ending point, use a volume that is a reasonable amount louder than the
starting volume (there appears to be code to do this already)
* between endpoints, interpolate
“impossible” crescendo (mf < p)
* perform as a crescendo with unspecified ending dynamic followed by an instant
change to the specified ending dynamic
mid-crescendo dynamics
* e.g. `<< { c'1\< c' c'\! } { s1 s\p s } >>`
* interpolate each interval separately as in cases above
* it might make sense to some people to warn about unexpected dynamics like p
in the middle of a crescendo from mf to f, but the engraver lays it out as
requested without complaining, so why not have a go at performing it too?
---
** [issues:#4048] Is Dynamic_performer’s understanding of (de)crescendo too
limited?**
**Status:** Accepted
**Created:** Sat Aug 02, 2014 10:45 AM UTC by Anonymous
**Last Updated:** Mon Jul 20, 2015 01:41 PM UTC
**Owner:** Dan Eble
*Originally created by:* *anonymous
*Originally created by:*
[[email protected]](http://code.google.com/u/115988136766997056421/)
On 02/08/14 18:36, Knute Snortum wrote:> Something that is seen a lot in 19th
and 20th century music is a crescendo
> or decrescendo without going to a specific dynamic. The performer is given
> the freedom to decide how much to change the dynamics. This causes an
> error message: "programming error: Impossible or ambiguous \(de\)crescendo in
> MIDI."
>
> %%% BEGIN
> \version "2.19.10"
>
> \score \{
> \relative c' \{
> c1 \p | c4 \< d e f | g \> f e d | c1 \p
> \}
> \layout \{\}
> \midi \{\}
> \}
> %%% END
>
> This error message should be a warning and give some line number to the
> offending code.
On 02/08/14 15:28, David Kastrup wrote:> Knute Snortum <[email protected]>
writes:
...
>
> That's not an actual programming error in pretty much all cases but
> rather an input problem probably deserving a warning. That alone should
> warrant fixing.
>
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
