> Attatched is a version or act1.ly, act1_.ly, that puts the final movement in
> its own score block. I know you may not want to put each movement in its own
> score, but lilypond expects this by default and notice how all the problems
> associated with doing it as you have it set up disappear.
On 16-Apr-05, at 7:34 AM, Stephen wrote:
The problem appears when you put all the movements together **under
the same score**. I consider this to be a midi bug. If you put each
movement in its own score, all your engraving problems would disapear,
the movements would appear as they do in the sep
.
Stephen
- Original Message -
From: "Karl Hammar" <[EMAIL PROTECTED]>
To:
Sent: Saturday, April 16, 2005 3:01 PM
Subject: Re: removing unwanted accidentals
Karl,
The problem appears when you put all the movements together **under the
same
score**. I consider this to be a m
I can't think of a situation where anyone except a beginner who didn't
understand the philosopy behind lllypond would want to use a
"no-accidental" style. OTOH it is useful to have workarounds for bugs.
\noAccidental seems ideal for this. It is not as cumbersome as having to
change the accidental-s
> Citerar Stephen <[EMAIL PROTECTED]>:
>
> > I think we want Lilypond to continue to follow standard practive. If we give
> > users the ability to violate those rules then total novices will start
> > making mistakes.
>
> We don't have to document the feature in a way such that novices will be ab
x27;t been very helpful to you so far, but I think this is all useful
> advice, germane to your project.
>
> Stephen
>
> - Original Message -
> From: "Karl Hammar" <[EMAIL PROTECTED]>
> To:
> Sent: Friday, April 15, 2005 12:59 PM
> Subject: Re
> Citerar Karl Hammar <[EMAIL PROTECTED]>:
...
> > > \version "2.4.0"
> > >
> > > #(define-public (print-+100-text-callback grob)
> > > (let* ( ;(text (ly:grob-property grob 'text))
> > > (text (number->string (+ 100 (string->number (ly:grob-property
> > grob
> > > 'text)
> > >
Citerar Stephen <[EMAIL PROTECTED]>:
> I think we want Lilypond to continue to follow standard practive. If we give
> users the ability to violate those rules then total novices will start
> making mistakes.
We don't have to document the feature in a way such that novices will be able
to
use it.
> Stephen
>
> - Original Message -
> From: "Erik Sandberg" <[EMAIL PROTECTED]>
> To: "Stephen" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>;
> Sent: Thursday, April 14, 2005 3:49 PM
> Subject: Re: removing unwanted accidentals
Citerar Karl Hammar <[EMAIL PROTECTED]>:
>
> > On Friday 15 April 2005 10.56, Karl Hammar wrote:
> > > [EMAIL PROTECTED]:
> > > > It also changes the numbering of all subsequent bars. I don't know the
> > > > author's intent in this case (I didn't write that snippet), but I
> guess
> > > > it cou
so far, but I think this is all useful
advice, germane to your project.
Stephen
- Original Message -
From: "Karl Hammar" <[EMAIL PROTECTED]>
To:
Sent: Friday, April 15, 2005 12:59 PM
Subject: Re: removing unwanted accidentals
>*No*, the forget does not work for:
act
> On Friday 15 April 2005 10.56, Karl Hammar wrote:
> > [EMAIL PROTECTED]:
> > > It also changes the numbering of all subsequent bars. I don't know the
> > > author's intent in this case (I didn't write that snippet), but I guess
> > > it could be something like an attaca movement.
> >
> > Yes. Th
> >*No*, the forget does not work for:
> act 1, aria 13, bar 6 Violin II: the b is shown with natural
> act 1, aria 13, bar 11 Violin I: the f is shown with natural
> Elsewhere yes, but not for theese two notes.>
>
> When I print out Score13, neither of these errors are present, even if I add
*No*, the forget does not work for:
act 1, aria 13, bar 6 Violin II: the b is shown with natural
act 1, aria 13, bar 11 Violin I: the f is shown with natural
Elsewhere yes, but not for theese two notes.>
When I print out Score13, neither of these errors are present, even if I add
the line:
#(se
To: "Stephen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
Sent: Thursday, April 14, 2005 3:49 PM
Subject: Re: removing unwanted accidentals
On Thursday 14 April 2005 21.31, Stephen wrote:
Given all the options for automatic accidentals: voice, modern,
modern-voice, piano, n
On Friday 15 April 2005 10.56, Karl Hammar wrote:
> [EMAIL PROTECTED]:
> > It also changes the numbering of all subsequent bars. I don't know the
> > author's intent in this case (I didn't write that snippet), but I guess
> > it could be something like an attaca movement.
>
> Yes. The bigger pictur
\minor \music04
\key c \minor \music05
and the key-engraver only shows the key signature when it *changes*.
I tried hack around in lily/key-engraver.cc and doing things like
if (scm_is_eq (last, key)) return, found no solution.
...
>
> Erik
>
> > - Original Message -
(this example I gave is not realistic, but the below example suggests that it
may happen that you want to tweak accidentals in unexpected ways, e.g. due to
other bugs)
Erik
> - Original Message -
> From: "Erik Sandberg" <[EMAIL PROTECTED]>
> To:
> Sent: Mon
way to suppress the bar number at that bar.
However, I fixed it by setting the accidental style to 'forget'. See? there
is already a way to do it.
Stephen
- Original Message -
From: "Erik Sandberg" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 11, 2005 3:53 PM
Sub
Hi,
There seems to be a need for a way to notate that a single note should _not_
have an accidental displayed, something like a 'force-no-accidental'
property.
I think there was a discussion about this over a year ago, without a
conclusion. Now there have been 2 or 3 (implicit) requests for it
20 matches
Mail list logo
