On Wed, 2016-03-02 at 14:37 +, Graham King wrote:
> I'm trying to eradicate numerous "Impossible or ambiguous
> (de)crescendo in MIDI" errors from a large score...
Well, there's some, qualified, success to report: I've eliminated the
various, sometimes well-hidden, causes of these messages.
On Thu, 2016-03-17 at 22:51 +, Graham King wrote:
> On Wed, 2016-03-02 at 14:37 +, Graham King wrote:
> > I'm trying to eradicate numerous "Impossible or ambiguous
> > (de)crescendo in MIDI" errors from a large score...
> Well, there's some, qualified, success to report: I've eliminated the
Hello Graham,
On 17.03.2016 23:51, Graham King wrote:
# { c_\markup { \dynamic p \italic { dolce } } Looks like a dynamic,
walks like a dynamic, but doesn't quack like one. Replace with {
c-\omit\p_\markup { \dynamic p \italic { dolce } } Likewise for "meno
f" and many other cases.
# { c1\sf
On Fri, 2016-03-18 at 00:13 +0100, Simon Albrecht wrote:
> Hello Graham,
>
> On 17.03.2016 23:51, Graham King wrote:
> > # { c_\markup { \dynamic p \italic { dolce } } Looks like a dynamic,
> > walks like a dynamic, but doesn't quack like one. Replace with {
> > c-\omit\p_\markup { \dynamic p
On 05.03.2016 01:04, Graham King wrote:
On Fri, 2016-03-04 at 13:33 -0600, Cynthia Karl wrote:
>
I think I understand why these errors are generated. It would appear
that \fz is not intended to be used as a dynamic - it is not
mentioned in the NR. Nevertheless, is is defined as a dynamic scr
On Fri, 2016-03-04 at 13:33 -0600, Cynthia Karl wrote:
> >
>
> I think I understand why these errors are generated. It would appear that
> \fz is not intended to be used as a dynamic - it is not mentioned in the NR.
> Nevertheless, is is defined as a dynamic script in the LP file
> dynamic-
> Date: Wed, 02 Mar 2016 14:37:44 +
> From: Graham King
> To: LilyPond Users
> Subject: Impossible or ambiguous (de)crescendo in MIDI.
> Message-ID: <1456929464.11804.791.ca...@oberon.tremagi.org.uk>
> Content-Type: text/plain; charset="us-asciiā
>
> 2) The second problem arose when I fin
On 02.03.2016 21:21, Graham King wrote:
On Wed, 2016-03-02 at 14:37 +, Graham King wrote:
Is there a magic spell to soothe lilypond in these circumstances? It
might seem like nit-picking, but there are so many of these errors in
the score that they are obscuring other, more important, mess
On Wed, 2016-03-02 at 14:37 +, Graham King wrote:
> Is there a magic spell to soothe lilypond in these circumstances? It
> might seem like nit-picking, but there are so many of these errors in
> the score that they are obscuring other, more important, messages.
Brian Barker has kindly answer
I just noticed the last line of your post. Yes, a line number to the
source would be nice.
I don't know if this issue ever got into issue tracking for LilyPond. This
comment should be added if it did.
Knute Snortum
(via Gmail)
On Sat, May 31, 2014 at 6:55 AM, Knute Snortum wrote:
> This wa
This was discussed here:
http://lilypond.1069038.n5.nabble.com/MIDI-dynamics-parsing-error-tt162479.html#a162546
The long and the short of it was to put a dynamic mark in, like \mf, and
then \omit the text. There was some agreement that LilyPond should assume
a dynamic of mf or handle this bette
11 matches
Mail list logo