Re: Changing volta number text

[Kieren MacMillan]

Hi Ralph,

> I have to admit, after learning from you that the documentation is accurate, 
> and spending some time examining the various examples in the documentation, I 
> think I could achieve what I want. It takes some real effort, and I think it 
> would be difficult for someone who has little experience with LilyPond. And 
> isn't that the point of the documentation?

Absolutely. My comment was meant as a [gentle] criticism of the documentation, 
not of you or other users. Even if it explicitly pointed out that one needs to 
*not use* the \repeat volta command, that would be [more] helpful!

> I think it would be helpful to include an appropriate example in the manual 
> repeat marks section of the documentation.

Given that the combination of the first three examples at 
<https://lilypond.org/doc/v2.21/Documentation/notation/long-repeats#manual-repeat-marks>
 is sufficient to solve your example, and the fourth example is almost exactly 
what you needed, what would a more appropriate example look like? Would that be 
in addition to the existing examples, or as a replacement to one of them?

The sheer size of the Lilypond docs is already pretty overwhelming; just adding 
more examples won’t necessarily make it easier for users.

> I guess I'll make a note of the solution!

Some syntactic sugar might be nice… I could imagine a function that took a list 
of string+moment pairs and “unfolded” a volta automagically. If my life ever 
calms down, maybe I’ll give that a try.

Best,
Kieren.
____

Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Changing volta number text

[Kieren MacMillan]

Hi Ralph,

> I think it would be helpful to either have a snippet that shows how to change 
> a "normal" volta number setup (i.e., change the numbers and/or add text), or 
> to add something to the documentation.

The documentation is accurate, if not entirely clear…  =)

This is what I got using 
<https://lilypond.org/doc/v2.21/Documentation/notation/long-repeats#manual-repeat-marks>:

%%
\version "2.21.0"
\include "english.ly"

test = {
  \time 3/4
  a'4 b' c' |
  b'4 c' d' |
  {
{
  \set Score.repeatCommands = #'((volta "1., 3."))
  e'4 f' g' |
}
{
  \set Score.repeatCommands = #'(end-repeat (volta "2."))
  d'4 c' b' |
}
{
  \set Score.repeatCommands = #'(end-repeat (volta "4."))
  g'4 a' b' |
  \set Score.repeatCommands = #'((volta #f))
}
  }
  c'1
}

\score {
  \test
}
%%%

Note that I deleted the \repeat volta command, but kept the bracketing of your 
\alternative block for readability.

Hope this helps!
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: LilyPond can't engrave 16 pages of music

[Kieren MacMillan]

Hi Reggie,

> I am trying to understand theoretically why this is failing. It's only 16
> pages. I am a minimalist composer so as a test I tried this extreme
> situation. But yet I don't quite agree rather that it's that extreme. It's
> only 16 pages and LilyPond crashes.

That looks like a [serious] bug to me. I’ve cc'ed the bug list.

Thanks!
Kieren.
________

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: MetronomeMark.break-align-symbols not heeded in custom context

[Kieren MacMillan]

Hi Simon,

This is why my ScoreMarks line looks like this:

  \context {
\type "Engraver_group"
\name ScoreMarks
markFormatter = #format-mark-box-alphabet
\consists "Axis_group_engraver"
\override VerticalAxisGroup.staff-affinity = #DOWN
\consists "Metronome_mark_engraver"
\override MetronomeMark.outside-staff-priority = #50
\override MetronomeMark.break-align-symbols =
  #'(left-edge staff-bar clef time-signature key-signature)
\override MetronomeMark.non-break-align-symbols =
  #'(paper-column-interface)
\consists "Mark_engraver"
\override RehearsalMark.outside-staff-priority = #100
\override RehearsalMark.break-align-symbols =
  #'(left-edge staff-bar clef time-signature key-signature)
\override RehearsalMark.self-alignment-X = #CENTER
\override RehearsalMark.extra-spacing-width = #'(-0.5 . 0.5)
\consists "Text_spanner_engraver"
\override TextSpanner.font-size = #2
\consists "Time_signature_engraver"
\omit TimeSignature
  }

Perhaps there's a better way of solving the problem, but this one works for me.

Hope that helps!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

[partcombine] partcombine can't handle simultaneous hairpins

[Kieren MacMillan]

Hi all,

I see this is still a problem, so I thought I'd post it to -bug.

Regards,
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.61"

musicA = {
  g'1\> R1\!
}
musicB = {
  b'1\> R1\!
}

\new Staff \partcombine \musicA \musicB
%%%  SNIPPET ENDS
________

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: problem with \partcombine and dynamics/hairpins

[Kieren MacMillan]

Hi Urs,

Thanks for the link/help. Tried to implement this, but there were a couple of 
problems (that I have no time to hunt down), so I backed it out. (This is 
definitely the right direction, though, as opposed to the baling-wire fix [due 
to Harm] that I’m using now…)

Hopefully one day, we can get \partcombine into really great shape.
It’s a wonderful tool, to the degree that it works.

Best,
Kieren.

On Sep 25, 2016, at 3:55 PM, Urs Liska  wrote:
> Hi Kieren,
> no time to really look into it. But in 
> https://git.openlilylib.org/bfsc/das-trunkne-lied/tree/master/library/ly/to-lilylib
>  are two "remove-" files that deal with this issue IIRC. Maybe they're if 
> help.
> Urs
________

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: problem with \partcombine and dynamics/hairpins

[Kieren MacMillan]

Harm (et al.),

Right after hitting “Send”, I realized the fix: ye olde empty chord!
The version below seems to work fine in both MWE and — at least, on first 
glance — in my RWS (real-world score).

Thanks!
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.48"

terminateHairpin =
#(define-music-function (ctx-name mus)(string? ly:music?)
#{ << $mus \context Voice = $ctx-name <>\! >> #})

endI = \terminateHairpin "one" \etc
endII = \terminateHairpin "two" \etc

musicA = {
 g'1\> \endI R1\!
}
musicB = {
 b'1\> \endII R1\!
}

\new Staff \partcombineII \musicA \musicB
%%%  SNIPPET ENDS


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: problem with \partcombine and dynamics/hairpins

[Kieren MacMillan]

Hi Harm,

> below a very bad workaround, found deep, deep in the quick n' dirty junk room.

Thanks for the attempt!

Works great on this MWE…
But in my real-world score, Lily’s long-standing \grace-timing “feature” (read: 
bug) comes crashing down.  =(

The hint/idea is possibly a good one, sufficient for my current triage needs — 
I’ll see if I can twist it to work without \grace.

Best,
Kieren.
____

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

problem with \partcombine and dynamics/hairpins

[Kieren MacMillan]

Hi all,

Apologies for the rapid repost/crosspost, but this feature/bug is keeping me 
from being able to put together a full score for a commission which is due 
ASAP. Does anyone have a viable** workaround for the issue demonstrated by the 
snippet, below?

Thanks,
Kieren.

** n.b. For me, “viable” does NOT include pulling all dynamics out of every 
part and putting them in separate dynamics variables to be simultaneous-ed in 
post-hoc…

>   SNIPPET BEGINS
> \version "2.19.46"
> 
> musicA = {
> g'1\> R1\!
> }
> musicB = {
> b'1\> R1\!
> }
> 
> \new Staff \partcombine \musicA \musicB
>   SNIPPET ENDS


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement: Take ‘master’ line thickness from a context property [was: Re: list of thicknesses…]

[Kieren MacMillan]

Hi Simon,

> <https://sourceforge.net/p/testlilyissues/issues/4760/>

Thanks for that!

Best,
Kieren.
____

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [feature-request] optional duration for temporary

[Kieren MacMillan]

Hi James,

> I have opened
> https://sourceforge.net/p/testlilyissues/issues/4658/

Thanks. (I’m getting a 404 error at the moment, but I assume that’s temporary.)

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Coda ahead of a line of its own

[Kieren MacMillan]

Hi all,

>>> There’s a better way — we should try to make it happen.
>> https://code.google.com/p/lilypond/issues/detail?id=3752
>> I'm not sure what it really intends to do...
> Have a \repeat coda command for repeats with coda,
> and a \repeat fine command for repeats with fine.

I agree 100% with David’s comment on that Google code page: it's really 
embarrassing that we don't have anything like that.

Best regards,
Kieren.
___

Kieren MacMillan, composer
www:  <http://www.kierenmacmillan.info>
email:  i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Skipping reminder accidentals in q

[Kieren MacMillan]

Hi David,

> At some point of time, one just has to accept that q is a shorthand.
> Once it becomes hard figuring out the proper semantics, we are leaving
> the shorthand realm.

Point taken…

But to imply that coming up with a logically consistent interpretation of each 
possibility is disingenuous. Here’s one obvious option:

   qrepeats the previous chord, with cautionary or forced accidentals not 
reindicated
   q!   repeats the previous chord, reindicating any forced accidentals
   q?   repeats the previous chord, reindicating any cautionary accidentals
   q!?   repeats the previous chord, reindicating any forced accidentals or 
cautionary accidentals.

So, in your specific examples:

> q!
> is going to be what?

The same output as

 

> q?
> is going to be what?

The same output as

 

Cheers,
Kieren.
_______

Kieren MacMillan, composer
www:  <http://www.kierenmacmillan.info>
email:  i...@kierenmacmillan.info


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Skipping reminder accidentals in q

[Kieren MacMillan]

Hi all,

> "chord repeats should not repeat forced/cautionary accidentals".  That’s 
> pretty straightforward.

Of course [because it’s 'common sense’], I agree this should be the default 
behaviour…
But I think it would be nice if there were still a way to override that, e.g., 
q! and q? to repeat the accidentals.

Cheers,
Kieren.
_______

Kieren MacMillan, composer
www:  <http://www.kierenmacmillan.info>
email:  i...@kierenmacmillan.info
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

random checkmarks appearing in output

[Kieren MacMillan]

Hello all,

For the last few [development] versions, I’ve found random checkmarks appearing 
in my scores:


Is anyone else having this problem?

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: vowel aligned lyrics - want to improve it

[Kieren MacMillan]

Hi Xavier,

> Someone on the French users mailing list would like to align lyrics
> on the first vowel.
> http://lilypond-french-users.1298960.n2.nabble.com/Alignement-des-paroles-sur-la-premiere-voyelle-td7579353.html
> 
> I found this thread but searching the LSR with the keyword "vowel"
> gives no result (and, of course, nothing about this in the doc).
> 
> 1. Could someone confirm me this is the latest version of the code for
> "vowel aligned lyrics" feature?
> 2. If it's effectively not on the LSR, could it be added?
> 3. It would be great to have "vowel aligned lyrics" directly in
> LilyPond; could this be added to the tracker as feature request?

Ultimately, it would be great to have two settings:
1. glyphs which "don't count" for width calculations (e.g., the LyricText 
"amazing—" should be centred as if it were just "amazing"); and,
2. glyphs which "don't count" for left-edge determination (e.g., all 
consonants, if you want vowel-aligned lyrics).

Just wanted to throw my feature request into this thread.  =)

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Positioning of "8" under clef symbol in G_8 clef

[Kieren MacMillan]

Hi!

I'm glad this is going forward.
Janek: please check placement with cue clefs, etc.: I've found the current 
implementation/workaround to be flawed in these cases.

Thanks,
Kieren.

On 2013-Apr-3, at 14:18, Xavier Scheuer wrote:

> On 3 April 2013 19:08, Janek Warchoł  wrote:
> >
> > Interestingly, this was discussed before; i've discovered some old
> > drafts of mine concerning it.  Also, i see that my work on rewriting
> > alignment interface would fit nicely with this stuff; i see now how
> > this should be achieved.  I can make a patch, but i'm busy; some
> > bounty would increase my motivation ;)  If at least 2 people will
> > pledge $5 each, i'll write a patch in the next few days - who's
> > interested?
> 
> Hi Janek,
> 
> I am not interested in this feature as I have never used a G_8 clef in
> the scores I engraved, but I would gladly pledge 2 times $5 to increase
> your motivation.  ;)
> 
> Please send me (privately) your bank account or any other information
> needed for the money transfer as your convenience.
> 
> Cheers,
> Xavier
> 
> -- 
> Xavier Scheuer 
> 


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: spacing with arpeggio

[Kieren MacMillan]

Hi all,

> Just be completely clear, appending \arpeggio as Thomas demonstrated
> (thanks, Thomas) not only "solves" it, it is actually the documented and
> correct usage of \arpeggio.
> 
> From the Notation Reference:
> 
> http://lilypond.org/doc/v2.17/Documentation/notation/expressive-marks-as-lines#arpeggio
> 
> where it says:
> 
> "An arpeggio on a chord (also known as a broken chord) is denoted by
> appending \arpeggio to the chord construct"
> 
> So, no bug here.

Makes sense — sorry for the noise!

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

spacing with arpeggio

[Kieren MacMillan]

Hi all,

This [reasonably-minimal] snippet shows a bug that's biting me a lot in my 
current engraving.

Thanks,
Kieren.
___

\version "2.17"
\language "english"

global = {
  \time 6/8
  \key d \dorian
  s8*6*2
}

pfNotesUpper = \relative a' {
  <<
{ \voiceOne
  8\arpeggio g a \arpeggio c d
  4.\arpeggio 4\arpeggio f'16 e
}
\new Voice { \voiceTwo
  d,4. c
   
}
  >>
}

pfNotesLower = \relative a {
  \clef bass
  <<
{ \voiceOne
  a8 d, e f4.
  e e
}
\new Voice { \voiceTwo
  \arpeggio 4\arpeggio g8
  4.\arpeggio \arpeggio
}
  >>
}

\score {
  \new PianoStaff = "pf" \with { connectArpeggios = ##t } <<
  \new Staff = "pfUpper" << \global \pfNotesUpper >>
  \new Staff = "pfLower" << \global \pfNotesLower >>
  >>
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: span bar not working any more?

[Kieren MacMillan]

Hi,

Just saw <http://code.google.com/p/lilypond/issues/detail?id=3203>.

Sorry for the noise.
Kieren.


On 2013-Mar-8, at 20:58, Kieren MacMillan  wrote:

> Hello all,
> 
> SpanBar isn't currently working as expected/documented: 
> <http://www.lilypond.org/doc/v2.17/Documentation/notation/displaying-staves#nested-staff-groups>
> 
> All the best,
> Kieren.
> ___
> lilypond-user mailing list
> lilypond-u...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

span bar not working any more?

[Kieren MacMillan]

Hello all,

SpanBar isn't currently working as expected/documented: 


All the best,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: MetronomeMark #'break-align-symbols sometimes fails

[Kieren MacMillan]

Hi!

> it appears MetronomeMark #'break-align-symbols fails
> with *every object* except time-signature.

This is a little frustrating, as it was part of a bounty fix from some time ago.

I understand the ultimate fix is [apparently] difficult — and Neil generously 
gave me a hack to tweak certain issues, especially at line breaks — but it 
would be nice to know what it would take to get MetronomeMark working as 
desired, once and for all.

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: grace synchronization

[Kieren MacMillan]

Hi all,

Well, here's an curious discovery: If you have a global variable 
"simultaneous-ed" into the Voice/Staff context(s), the "extra" skipped grace 
note MUST BE IN THE GLOBAL, not just explicitly placed in the other 
Voice(s)/Staff(s).

\version "2.13"

% skip in voice = fail
global = { \key a \major s1 \break s1 }
notesA = \relative {
  c1
  \acciaccatura { d8 } e1
}
notesB = \relative {
  c8 c c c c c c c
  \grace { s8 } d1
}
\score {
  << 
\new Staff << \global \notesA >>
\new Staff << \global \notesB >>
  >>
}

% skip in global = PASS
global = { \key a \major s1 \break \grace { s8 } s1 }
notesA = \relative {
  c1
  \acciaccatura { d8 } e1
}
notesB = \relative {
  c8 c c c c c c c
  d1
}
\score {
  << 
\new Staff << \global \notesA >>
\new Staff << \global \notesB >>
  >>
}

While that solves the problem in this minimal example, it doesn't in my piece 
(which includes multiple split voices, etc.).  =(
In other words, I'm still hoping we can make the whiole grace timing insanity 
go away…

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: grace synchronization

[Kieren MacMillan]

Hi Hans,

> I now got it working: just put in a grace note with a skip in the other staff.

I had already tried that in my score — doesn't fix the problem.

> However, when trying to use \bar ":||", like in the manual, then all sorts of 
> strange things happen.

=(
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

grace synchronization

[Kieren MacMillan]

Hello all, 

I'm running into a rather irritating grace synchronization problem — an 
acciaccatura in one voice is overriding an explicit page break — and so I 
wanted to know what it would take to fix the grace sync problem "once and for 
all".

I know of Issue 34 (and others) in the tracker, but here's my explicit 
question: What total bounty would cover a rewrite of the code so that grace 
note synchronization is not a concern at all for the user? I probably can't 
cover the whole thing, but knowing exactly the scope of the problem might lead 
others [who are equally frustrated by this issue] to chip in and get the fix 
funded.

Thanks!
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: MetronomeMark #'break-align-symbols sometimes fails

[Kieren MacMillan]

Hi all,

When this gets fixed, I'm happy to up my sponsorship by C$50 -- this has 
definitely turned out to be more work than it first appeared.

Thanks,
Kieren.

On 2010-Sep-26, at 08:43, Carl Sorensen wrote:

> 
> 
> 
> On 9/26/10 5:09 AM, "Xavier Scheuer"  wrote:
> 
>> Hi Jan!
>> 
>> No, I'm *not* obsessed with Tempo indications placement
>> (or maybe, am I?)...   ;-p
>> Actually this time the issue was reported on the French-speaking
>> mailing list, I'm just relaying it.
>> 
>> MetronomeMark #'break-align-symbols seems to fail with everything
>> (clef, left-edge, staff-bar, ...) except key-signature and
>> time-signature.
>> 
>> This (kind of) reopens issue #684, isn't it?
> 
> No, please make a new issue.  You have a new test file.
> 
> Thanks,
> 
> Carl
> 
> 
> ___
> lilypond-devel mailing list
> lilypond-de...@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
> 


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

collision bug?

[Kieren MacMillan]

Hi all,

There appear to be at least two collisions in this small snippet that are 
unsightly: the first flat and the preceding rest, and the second flat and the 
preceding ledger line.
Regression?

Thanks,
Kieren.


\version "2.13.25"
\include "english.ly"

thenotesI = \relative g' {
  g2( af)
}
thenotesII = \relative af {
  r8 af( df ef f2)
}

\score {
  \new Staff << \thenotesI \\ \thenotesII >>
}

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \concat + \line = unexpected behaviour [?]

[Kieren MacMillan]

Hi Dmytro,

> I've looked at formatting commands and decided to add this to tracker:
> http://code.google.com/p/lilypond/issues/detail?id=1100

Thanks!
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \concat + \line = unexpected behaviour [?]

[Kieren MacMillan]

Hi Werner,

>> i.e., in the snippet
>>   \markup { \line { pre \concat { a b c } post } }
>> the 'word-space should be overridden to not-zero, right?
> 
> The output should be
>  pre abc post
> Everything else is a bug IMHO.

I agree... and in this case, Lilypond does the right thing.

I'm just pointing out the inconsistency: Lilypond *should* IMHO give

\markup { \concat { pre \line { a b c } post } }  ==>  prea b cpost

but doesn't.

Regards,
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \concat + \line = unexpected behaviour [?]

[Kieren MacMillan]

Hi Neil,

> Yes.  \line stacks a set of markups horizontally, using 'word-space to
> set the space between adjacent markups.  If it's inside a \concat
> block, 'word-space is overridden to zero.

Okay, but I don't like it...  =\

Furthermore, why doesn't Lilypond behave consistently in this regard? i.e., in 
the snippet

   \markup { \line { pre \concat { a b c } post } }

the 'word-space should be overridden to not-zero, right?

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

\concat + \line = unexpected behaviour [?]

[Kieren MacMillan]

Hello all,

In the third line of this snippet, all whitespace (word spacing) is removed -- 
is this expected behaviour?

\version "2.13.21"
\markup { \line { in a line } }
\markup { \concat { pre "in a line" post } }
\markup { \concat { pre \line { in a line } post } }

Thanks,
Kieren.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request

[Kieren MacMillan]

Hi Carl,

> It seems to me that this is a bug; the fis' and the f' are not the same
> note, and therefore the note-heads should not be merged.

Yes, *that's* the bug (not the accidental handling).  =)

For the record, I [quickly] tried a number of shifting attempts, but couldn't 
duplicate the original sample -- both accidentals kept shifting with the 
left-most note column.

Cheers,
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request

[Kieren MacMillan]

Hi Phil,

> understood it to mean that when there are 2 notes in 2 voices but which have 
> the same fundamental note, only differing in an accidental, then LilyPond 
> doesn't support this.

Nope -- but we should adjust the documentation if it's unclear.

> I do have the chords set in different voices and it shows as in the attached 
> clip - it incorrectly makes the first note of the 2nd voice a natural.

That's a different issue:

\score {
  \new Staff <<
\new Voice { \voiceOne fis'8[ g'] }
\new Voice { \voiceTwo #(set-accidental-style 'voice) 8[ ] }
  >>
}

See 

 for more information.

Hope this helps!
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement request

[Kieren MacMillan]

Hi Phil,

> The attached image is how this appears in the Chappell version of "The 
> Mikado".

Your example isn't technically a situation where "the same note occurs with two 
different accidentals in the same chord" -- it has two different voices!

Cheers,
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Line breaks and text positioning

[Kieren MacMillan]

Hi Phil,

> I know it can be worked around with \break, but as a general rule it 
> shouldn't be necessary to do this.

Here's a snippet to consider:

\version "2.12.3"
#(set-global-staff-size 17)

\paper { indent = 0 }

\score {
  {
\clef "treble"
\time 4/4
\repeat "unfold" 31 { b'4 }
b'4^\markup { \normalsize \italic "Some text to test linebreaking 
calculation" }
\repeat "unfold" 40 { b'4 }
\bar "|."
  }
}

\score {
  {
\override Score.PaperColumn #'keep-inside-line = ##t
\clef "treble"
\time 4/4
\repeat "unfold" 31 { b'4 }
b'4^\markup { \normalsize \italic "Some text to test" }
\repeat "unfold" 40 { b'4 }
\bar "|."
  }
}

\score {
  {
\override Score.PaperColumn #'keep-inside-line = ##t
\clef "treble"
\time 4/4
\repeat "unfold" 31 { b'4 }
b'4^\markup { \normalsize \italic "Some text to test linebreaking" }
\repeat "unfold" 40 { b'4 }
\bar "|."
  }
}

\score {
  {
\override Score.PaperColumn #'keep-inside-line = ##t
\clef "treble"
\time 4/4
\repeat "unfold" 31 { b'4 }
b'4^\markup { \normalsize \italic "Some text to test linebreaking 
calculation" }
\repeat "unfold" 40 { b'4 }
\bar "|."
  }
}

I think the third example is a "bug": if the markup/tempo/rehearsalmark is 
going to cause the spacing to be so poor, the line should automagically break 
so that the item happens "mid-system" (like the last example).

Cheers,
Kieren.

> 
> --
> Phil Holmes
> 
> ___
> lilypond-user mailing list
> lilypond-u...@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: How to adjust the space between notes?

[Kieren MacMillan]

Hi Antheo,

> Yes a short sample would be nice but as it is a layout question it does not
> makes sense to shorten the code. Here is the code i wrote:
> http://old.nabble.com/file/p27667198/commons.ly commons.ly 
> http://old.nabble.com/file/p27667198/Introduction%2B-%2BSaint%2BSaens.ly
> Introduction+-+Saint+Saens.ly 

OK -- now I can see what's going on.  =)

1. If I'm not mistaken, you're trying to adjust not the overall spacing, but 
specific spacing choices/proportions based on note length. It's easy to match 
the length of the entire snippet to the desired output/example -- by tweaking 
common-shortest-duration -- but you want (e.g.) more space left for a dotted 
eighth than Lilypond's default. I believe this isn't controlled by 
"common-shortest-duration" only, but by other settings — I don't know the exact 
details, but I imagine there's a relatively easy way to set these proportions 
as you would like them. Maybe someone else can answer more completely.

2. The specific issue of the extra space given by the half-note looks like a 
bug to me. [Hence the cross-post to the bug list.]

Sorry I couldn't be of more assistance.
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Textual tempo markers in adjacent bars are stacked

[Kieren MacMillan]

Hi Xavier,

> As a workaroud I use this user-defined "TempoMark" command for textual
> tempo marks:
> 
> tempoMark = #(define-music-function (parser location markp) (string?)
> #{
>  \once \override Score.RehearsalMark #'self-alignment-X = #LEFT
>  \once \override Score.RehearsalMark #'break-align-symbols =
> #'(time-signature key-signature)
>  \once \override Staff.TimeSignature #'break-align-anchor-alignment = #LEFT
>  \once \override Score.RehearsalMark #'font-size = #1
>  \mark \markup { \bold $markp }
> #})

The problem with this "workaround" is that it uses RehearsalMark instead of 
MetronomeMark.
[I used to do this too, but have stopped because of this very problem.]
We really need to get MetronomeMark fixed.

Cheers,
Kieren.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

bug with LSR Item #233 (hairpin with centred dynamics)?

[Kieren MacMillan]

Hi all,

It appears that the snippet
   
does not respect the Staff fontSize (e.g., as set in a \with block).

1. What's the explanation?
2. What's a workaround?

Thanks,
Kieren.

[p.s. v2.13.8 if it matters…]

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: TrillSpanner does not extend over tied note

[Kieren MacMillan]

Hi Neil,


This has been fixed in 2.13.1.


Thanks! I'll see if the upgrade will handle my current score without  
regression.

Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

TrillSpanner does not extend over tied note

[Kieren MacMillan]

[Mac OS X 10.4.11]

Notice that the TrillSpanner does not extend through (i.e., include)  
the tied note, as expected/desired:


\version "2.12.2"
\paper { ragged-right = ##f }
trillBugMusic = \relative c'
{
  c1\startTrillSpan ~ |
  c4 c\stopTrillSpan\startTrillSpan ~ c c\stopTrillSpan 
\startTrillSpan ~ |

  c1\stopTrillSpan
}
\score { \trillBugMusic }

Cheers,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [repost] CR/LF regression in Mac OS X Lilypond editor

[Kieren MacMillan]

Hi Valentin,


this has now been added as
http://code.google.com/p/lilypond/issues/detail?id=643


Thanks!
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: beams

[Kieren MacMillan]

Hi James,


So is this a bug?


Looks like it...


or is there some way around this?


Did my solution (posted earlier) not work for you?
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

[repost] CR/LF regression in Mac OS X Lilypond editor

[Kieren MacMillan]

Hello all,

Has anyone else run into issues with the way the Lilypond editor (Mac  
OS X 10.4) handles CR/LF?


I don't remember exactly when, but starting at least five or six .01  
versions ago, anything I cut and paste from my Lilypond editor to  
(e.g.) my email would have no CR/LF left in them. [Still happens with  
2.11.49 -- I just checked.]


It was only an annoyance, until I (just) realised that many confusing  
errors I've been running into have been from Lily thinking that (e.g.)


% some comment   a4 b c d

was

% some comment a4 b c d

which, as you can imagine, are quite different!  =)

Regards,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

CR/LF regression in Lilypond editor

[Kieren MacMillan]

Hello all,

Has anyone else run into issues with the way the Lilypond editor (Mac  
OS X 10.4) handles CR/LF?


I don't remember exactly when, but starting at least five or six .01  
versions ago, anything I cut and paste from my Lilypond editor to  
(e.g.) my email would have no CR/LF left in them. [Still happens with  
2.11.49 -- I just checked.]


It was only an annoyance, until I (just) realised that many confusing  
errors I've been running into have been from Lily thinking that (e.g.)


% some comment
   a4 b c d

was

% some comment a4 b c d

which, as you can imagine, are quite different!  =)

Regards,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \relative doesn't work when using \parallelMusic

[Kieren MacMillan]

Hi Valentin,

Can't help you with \parallelMusic directly, but...


I would use everyday it if this was addressed


Don't forget that you can fake \parallelMusic by explicitly pushing  
notes into an existing Voice context -- see snippet, below, for an  
example.
It's not quite as pretty, but it accomplishes essentially the same  
thing.


Hope this helps!
Kieren.
___

\version "2.11.30"

theMusic = \relative c''
{
%% m. 1
\context Voice = "A"
<<
{
\voiceOne
\override Voice.NoteHead #'color = #red
a b c d
}
\new Voice = "B"
{
\voiceTwo
\override Voice.NoteHead #'color = #blue
a g f e
}
>>
%% m. 2
<<
\context Voice = "A" { a c c b }
\context Voice = "B" { a f f g }
>>
%% m. 3
<<
\context Voice = "A" { a f' e d }
\context Voice = "B" { a d, e f }
>>
}

\score
{
\theMusic
}



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Starting a Piano Staff with an appoggiatura (acciaccatura)?

[Kieren MacMillan]

Hi Joern,

Trying to start a PianoStaff with an appoggiatura or an  
acciaccatura seems broken.


Have you looked at the "Bugs" section at the bottom of the "Grace  
notes" section of the docs?


Hope this helps!
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Crescendo text too close to dynamic mark

[Kieren MacMillan]

Hi, Zoltán:


%% I'm not sure whether it's wrong or not, but I think that
%% the crescendo text is too close to the preceding dynamic mark.


Yes, but I doubt this will be classified as a bug, since the  
mechanism is not intended to solve the problem you're showing.


Perhaps this code will give you the result you want?

Best wishes,
Kieren.

p.s. Cross-posted to lilypond-user, in case the tip is helpful to  
others...

__

\version "2.11.23"

mfCrescText =
{
\setTextCresc
	\set crescendoText = \markup { \line { \dynamic "mf" \translate  
#'(0.5 . 0.15) \italic "cresc." } }

}

\paper { ragged-right = ##t }

\relative g'
{
\mfCrescText g2\< g2 | \repeat "unfold" 5 { g1 | \noBreak } g\fff |
}

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: average-spacing-wishes and note too close to barline

[Kieren MacMillan]

Hi, David:


Help would be appreciated.


You could modify the BarLine #'X-extent manually, e.g.

\version "2.11.23"
\paper{ ragged-right=##t indent = #0 }

blFix =
\override Score.BarLine #'space-alist = #'(
(time-signature . (extra-space . 0.75))
(custos . (minimum-space . 2.0))
(clef . (minimum-space . 1.0))
(key-signature . (extra-space . 1.0))
(key-cancellation . (extra-space . 1.0))
(first-note . (fixed-space . 1.3))
(next-note . (extra-space . 1.9)) ; Changed from the new default 0.9
(right-edge . (extra-space . 0.0)))

apFix = \override Score.AccidentalPlacement #'left-padding = #1.0

kmFix = \override Score.BarLine #'X-extent = #'(-1 . 1.2)

\new Score
{
  \new Staff \relative c'' {
R1 \bar ":|" 2 r2 \bar "|" 2 r2 | \break

\blFix
R1 \bar ":|" 2 r2 \bar "|" 2 r2 | \break

\apFix
R1 \bar ":|" 2 r2 \bar "|" 2 r2 | \break

\revert Score.BarLine #'space-alist
\revert Score.AccidentalPlacement #'left-padding

\kmFix
R1 \bar ":|" 2 r2 \bar "|" 2 r2 | \break
  }
}

Of course, this has to be done to each measure individually -- even  
in this small example, the fix for the first measure (which seems  
just about right to me) makes the second measure padding too large  
(IMO). In other words, a music function (Scheme) would be advisable,  
so all you would have to do is put (e.g.,)


\barPad #'(1 . 2)


My offer to contribute sponsorship for a solution still stands.


Ditto: with default settings, Lilypond shouldn't require *constant*  
tweaking in essentially *every* measure just to avoid collisions and  
other poor spacing concerns.  =(


Best regards,
Kieren.




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

cautionary accidental causes shift of lower accidental

[Kieren MacMillan]

Hello, all!

Attached is a snippet from a piano piece I'm engraving.

As you will see, the addition of a cautionary accidental in the upper  
part of the chord causes the lower (regular) accidental to shift  
unnecessarily.
I've included this on -list, to document the (i.e., my current)  
workaround.


Thanks!
Kieren.

p.s. You will also note the insufficient padding preceding the  
accidentals at the beginning of the second measure, but that's a  
different (ongoing) story...  ;-)

__

\version "2.11.23"  % Mac OS X 10.4.9
\include "english.ly"

theMusic = \relative
{
\key gf \major
8[--( -- -- ]--)
8[--( -- -- ]--)
8[--( -- -- ]--)
	8[--( -- \once \override Accidental #'X-extent =  
#'(1 . -1) -- ]--)

}

\paper { ragged-right = ##t }
\score { \theMusic }


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Accidentals too close to barline

[Kieren MacMillan]

Hi, David:

This is also (more of?) a problem with arpeggios, etc.

I think there should be a "measure-minimum-left-padding" (or  
whatever) value, to guarantee that the first object after the barline  
(or time or key sig, if present) maintains a certain distance from  
the prefatory objects.


I'd consider sponsoring it, maybe jointly, depending on how much it  
might cost.


I'm in for up to 100E.

Cheers,
Kieren.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Laissez vibrer direction

[Kieren MacMillan]

Hi, Marcus:

Until the bug is fixed, perhaps you can use #'rotation as a  
workaround option...?


Hope this helps!
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

melismas on tied notes not left-aligned

[Kieren MacMillan]

Hello, all --

Just noticed that melismas on tied notes are centered on notehead,  
whereas melismas on slurred notes are left-aligned (as expected)

I double-checked and they were both left-aligned in v2.8!

While we're here...  ;-)
Is there an easy way to (globally) set the X-alignment of (just) the  
first syllable of a melisma?


Thanks!
Kieren.

%%% BEGIN SNIPPET %%%

\version "2.9.17"

theMusic = \relative c'
{
c4 c ~ c8 c4 c8
c( d e d) c2
}

theWords = \lyricmode
{
Some word, __ then a long __ word.
}

\score
{
\new GrandStaff
<<
\new Staff << \theMusic >>
\addlyrics { \theWords }
>>
}

%%% END SNIPPET %%%


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Stem #'neutral-direction

[Kieren MacMillan]

Hi, Markus:

Thanks -- that solved it!
But can anyone explain why the default is for Voice *not* to \consist  
of the "Melody-engraver"??  =)


Thanks!
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Stem #'neutral-direction

[Kieren MacMillan]

Hello, all!

Is Stem #'neutral-direction not working as expected in 2.9.17? [See  
bug snippet, below.]


Thanks,
Kieren.

%%% BEGIN SNIPPET %%%

\version "2.9.17"

theMusic = \relative c''
{
\repeat "unfold" 16 { c4 b c b c b a g a b a b a g a b }
}

\score
{
\theMusic
}

\layout
{
\context
{
\Score
\override Stem #'neutral-direction = #'()
}
}

%%% END SNIPPET %%%


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Minimum padding after barlines for notes with accidentals?

[Kieren MacMillan]

Hi, Rick:


Yes, now I see it is happening on my left oriented string numbers, and
arpeggios too.  I think I'll wait for a more global fix from a  
developer,
(even if I have to try to do one of those complicated "call back"  
fixes),

rather than spend a week re-editing every measure and all future work.


I, too, would love a global fix! However, I've had too many time- 
sensitive engravings to get out the door (commisisons, etc.) in the  
meantime, so I went ahead with all the manual tweaks.



Maybe this post belongs on the bug list, pretty serious IMO.


I've cross-posted; we'll see what happens!  =)

Best,
Kieren.


Kieren MacMillan wrote:


Hi, Rick!


There is a problem with notes that both start a measure and have an
accidental. [...] I can't be the first one to notice it).


If you search the archives, you'll see that I've asked this question
a number of times.
And it's also true of other "left-side attachements", e.g.,  
arpeggios.


I've yet to receive a satisfactory response/solution/explanation.  =\

What I've been doing in the meantime is manually tweaking the X-
extent of the Accidental (or BarLine) to force the padding, e.g.

 \once \override Accidental #'X-extent = #'(-2 . 1) bs

It's definitely a time-consuming process, but I haven't found a
better solution -- if you find one, I'd greatly appreciate hearing
about it!  =)

Best,
Kieren.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




--
View this message in context: http://www.nabble.com/Minimum-padding- 
after-barlines-for-notes-with-accidentals--tf2265851.html#a6287966

Sent from the Gnu - Lilypond - User forum at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Cannot reset TupletNumber back to visible

[Kieren MacMillan]

Hi, Raphael!

I can't reproduce the bug you're talking about -- e.g., the following  
works as expected:


%%% BEGIN SNIPPET %%%

\version "2.8.5"

stuff =
{
\times 3/2 { g:8 d:8 }
\override TupletNumber #'transparent = ##t
\times 3/2 { g:8 d:8 }
\times 3/2 {
  \override TupletNumber #'transparent = ##f
  g:8 d:8
  \override TupletNumber #'transparent = ##t
}
\override TupletNumber #'transparent = ##t
\times 3/2 { g:8 d:8 }
\override TupletNumber #'transparent = ##f
}

\score
{
\stuff
}

%%% END SNIPPET %%%

Does this *not* output what you expect on your copy of Lilypond?

Best regards,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: ties in polyphony

[Kieren MacMillan]

Hi, Karim (et al.):

Starting from version 2.9.16-1 on both plateforms, linux (debian  
etch) and
Macosx PPC Tiger. some strange things are happening concerning ties  
that
are not produced on pdf nor in ps. It is happening Only when it is  
a two

voice thing. (If you remove one voice, the ties will be draw again).
THis is ok in version 2.9.15 and 14


I've noticed a bug that might be the same thing: I'm scrambling to  
finish a big choral commission, and lyrics are getting misaligned, etc.

I had to revert to 2.9.15...

Cheers,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

mutlti-voice alignment

[Kieren MacMillan]

Hello, all --

Any idea/explanation for why the alignment is off (between the fs and  
a) in the following example?

I can tweak it with a NoteColumn #'extra-offset, but I'd rather not...

Thanks,
Kieren.

%%%  CODE BEGINS
\version "2.9.15"
\include "english.ly"

theNotes = \relative
{
\key e \minor
<<  \\ fs8 >>
}

\score
{
\theNotes
}
%%%  CODE ENDS



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Bug when trying to use right-align in Composer, Header

[Kieren MacMillan]

Bonjour, Frédéric!

I am trying to put dates on a second line under the composer's  
name. Although it
works using \markup \center-align { "composer" \small  
"(-)" }, it
doesn't when I use \right-align instead. The result is two lines  
printed one on

another. Why is it like this?


Try this:

composer = \markup
{
\override #'(baseline-skip . 2.8)
	\column { \right-align { \fontsize #1 "Marty McFly" \fontsize #-1  
"(1985–1955)"  } }

}

Adjust the individual fontsize and baseline-skip values to your liking.

Best regards,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: tieWaitForNote

[Kieren MacMillan]

Hi, Han-Wen --


yes,  I think so


Great!


don't use 2.9.9-1 though, as it has an embarassing bug.


Oh, yeah, I ran into that one: I was on the subway with my laptop,  
minding my own business (and engraving a score), when all of a sudden  
my pants disappeared!  ;-)


Cheers,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: tieWaitForNote

[Kieren MacMillan]

Hi, Han-Wen (et al.):


Anyone know a fix or workaround?

upgrade to 2.9


Right now, I'm in the ever-increasing crunch of getting a chamber  
opera score composed, engraved, parted, and out the door...

The premiere is two weeks from tomorrow!!  =\
Is 2.9 stable and bug-free enough to trust for that gig?

Thanks,
Kieren.

p.s. Out of curiosity, does 2.9 fix the pedal brackets bug I found?  



p.p.s. Despite any hint of negativity from me -- due entirely to the  
stress I'm under right now -- Lilypond is working out remarkably well  
in this, the first truly major production in my post-all-those-other- 
engraving-apps era. Everyone who has seen my score(s) has gushed  
about the quality, and my tweak time must be less than a quarter of  
what it would have taken in any other app -- kudos to everyone on the  
Lilypond team!



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

tieWaitForNote

[Kieren MacMillan]

Hello, all --

Just wondering if I'm the only one running into this issue (q.v.,  
middle-line-B tie):


%%%  BUG SNIPPET BEGINS
\version "2.8.4"
\include "english.ly"
\relative c'
{
\time 12/8
\set tieWaitForNote = ##t
r8 cs[~ a'~ b~ e'~ gs,]~ 2.\laissezVibrer
\set tieWaitForNote = ##f
}
%%%  BUG SNIPPET ENDS




Anyone know a fix or workaround?

Thanks,
Kieren.___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Beaming Triplets

[Kieren MacMillan]

Hi, Trent:

Sorry -- didn't really comprehend the "buggy" nature of your  
email...  =\

Chalk it up to being deep in opera-composition mode.

Apologies,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Beaming Triplets

[Kieren MacMillan]

Hi, Trent:

Is this what you want?

%%%  CODE SNIPPET BEGINS
\paper
{
ragged-right = ##t
indent = 0\mm
}

\relative c''
{
c4 c4 c8 \times 2/3 { c16[ d e] }
}
%%%  CODE SNIPPET ENDS

Note how the [ goes after the first note you want included in the beam.

Best regards,
Kieren.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \paper within \score

[Kieren MacMillan]

Hi, Graham:

(I'm still not clear on \paper vs. \layout, since you _can_ have  
\layout outside of a \score )


Although this may confuse you more, the way I think of it is in Adobe  
terms:


\layout = story
	i.e., one contiguous block of presented material (in this case,  
usually music)


\paper = artboard
	i.e., the dimensions (and other details) of the page(s) on which all  
of the stories (\layouts) are outputted.


Hope this helps (and not hinders!).
Kieren.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond