Re: Re: conditional formatting

[Dmytro O. Redchuk]

On Tue 05 Oct 2010, 20:51 Vicente Solsona wrote:
> On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser
>  wrote:
> >Dmytro's suggestion looks more promising, though I haven't been
> >able to generate code that does the job so far. When I code
Well, i guess that your checks was far to simple for your case; actually you
need something like this:

 - i need staff, lyrics and chords:
- then staff is "Staff", lyrics is "Lyrics", chords is "Chords"
 - i need lyrics and chords:
- then staff is "Devnull", those two are the same
 - etc-etc

If you have a "container" (StaffGroup) the task is even more complicated .-)
(manual says that "Devnull" can not contain other contexts)

Sorry, i've not tested _all_ this; actually, yes, there are other, much
more simple ways. Sorry!! :-)
 
> that looks very interesting and can be very useful if you find the way.
Well, this may be useful in very rare cases, i think (when i "really-really
want" to specify "result" in a command line or like this -- when i, for some
other reason, want to deal with _the only_ "master" source file).

-- 
  Dmytro O. Redchuk
  Bug Squad

  Be careful! These are some commonly used abbreviations:
   • LM -- Learning Manual
   • NR -- Notation Reference
   • IR -- Internal Reference

  Look at LilyPond’s documentation to find more.

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

What's with WebLily?

[Father Gordon Gilbert]

Someone on this list pointed out that there was WebLily available, so I
thought I'd check it out.  But when I've tried to create an account to use
it, I keep getting "Sign In is temporarily unavailable."  Can someone help?

Thanks,

Gordon+

-- 
Fr. Gordon Gilbert
Penetanguishene, ON
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \tempo

[Mario Moles]

Good solution! 
Thank you so match!
In data mercoledì 06 ottobre 2010 01:17:59, hai scritto:
> On Tue, 05 Oct 2010 22:27:40 +0200, Mario Moles 
> 
> wrote:
> > Hi lilyponders!
> > How i can for \tempo=40-42 ?
> > Cheers!
> 
> use markups. I guess you mean something like this:
> 
> \tempo \markup {
>\concat {
>   \general-align #Y #DOWN \note #"4" #1
>  " = 40-42"
>}
> }
> 
> did you look in the manual? there's a pretty similar example there.
> 
> greetings,
> 
> Vicente

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

Re: Problems with segnos and codas

[Robert Urmann]

You mean something like:
--- snip ---
\version "2.12.3"
\relative {
r2 r4 
\override Score.RehearsalMark #'Y-offset = #2
\once \override Score.RehearsalMark #'self-alignment-X = #RIGHT
\mark \markup { \vcenter "D.S." \hspace #1 \musicglyph #"scripts.segno" 
}

\stopStaff s2. \hideNotes g4 ~ \unHideNotes \startStaff

\once \override Score.RehearsalMark #'self-alignment-X = #LEFT
\mark \markup { \musicglyph #"scripts.coda" \vcenter "Coda" }
g2 r
}
--- snap ---
?

To fake two RehearsalMarks to appear at the same time I add a grace note spacer 
between them:

\mark "AA" grace { s16 } \mark "AB"

Best, Robert

Am 05.10.2010, 13:32 Uhr, schrieb Tim Rowe :


I have a coda immediately following a D.S., and have tried to mark it
up as follows:
  
\override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
\override Score.RehearsalMark #'self-alignment-X = #RIGHT
\mark \markup {"D.S " \musicglyph #"scripts.segno"}
  |
\override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
\override Score.RehearsalMark #'self-alignment-X = #LEFT
\mark \markup {\musicglyph #"scripts.coda" "Coda "} |
  g2 r2 |
(To be honest, they're just magic incantations I god from snippets,
and I have no real understanding of what they're doing).

That has two problems. The most significant is that it doesn't work at
all -- I get a warning that there are two simultaneous mark events,
and it junks the second, so I don't get the coda mark.

The one that you can't tell from the little bit that I've included
there is that the starting g of the coda should be tied over from the
"to coda" bar, so it should have a tie going into it.

Where am I going wrong? Is there an easy way to fix these problems?

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

Re: \header place in \score block (doc & syntax clarification)

[Marc Mouries]

thanks for pointing this out. I only look at the log if the compiler fails.

> it seems uncritical, and so Lily continues compiling. Should it abort?

I find it more handy to have the header located at the beginning of the 
score rather than at the end. Furthermore, If lilypond can compile 
correctly whatever place the header is in the scope part, i'd say why 
printing a warning and why not allowing it?



On 10/5/2010 7:06 PM, RobUr wrote:

Did you notice Lily's log? It complains about the bad \header placement!
But it seems uncritical, and so Lily continues compiling. Should it 
abort?


Best, Robert

Am 05.10.2010, 15:09 Uhr, schrieb Antheo :



would somebody mind clarifying?


Antheo wrote:



The documentation here
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Introduction-to-the-LilyPond-file-structure#Introduction-to-the-LilyPond-file-structure 



says: "A \score block must always contain just one music expression, 
and

this must appear immediately after the \score command."
and: "these three commands – \header, \layout and \midi – are special:
unlike many other commands which begin with a backward slash (\) 
they are

not music expressions"

Which implies that the \header must be placed after the music 
expression.

However, I found that with version 2.12, the lilypond accepts that the
header is placed before as well.

\version "2.12.3"
\score {
  \header { piece = "lilypond compiles a score where header is placed
before the music expression"}
  { c'4 a b c' }
  \layout { }
}

If lilypond compiles the file, I'd assume the documentation needs to be
updated???
Would you mind clarifying?

 http://old.nabble.com/file/p29878274/test%2Bheader%2Bplace.ly
test+header+place.ly










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

OT Tzur Ma'oz

[dadadharma @dslextreme.com]

This is Off Topic, but I don't know where else to turn...

I'm looking for a basic, out-of-copyright four-part harmony version of
Tzur Ma'oz that I can transcript in Lilypond for my singing group
(Shape Note).

I could not find any on the "Sheet Music Wiki"



Also, we had a discussion at Barbershop Chorus last night about our
Christmas song list. Not a "Holiday Song list" -- only Christian songs
were there.

That's a big problem in West Los Angeles.

Barbershop -- we wanna sing the barbershop cord maybe 30% of the song
(by duration; we tend to hold it out), maybe 60% of the song.

Does anybody know about a crash-course (simple guidelines) for goyish
song leaders who need to arrange Hannukah songs? What are the
harmonies & choirly effects that need to be achieved?

Any thoughtful essays on what "interfaith" means -- not in terms of
highly-trained, virtuoso choirs, but grass-roots community singing?

Virtuosos can pull off any stunt, of course.

But at the grass-roots -- not just a different musical species or
genre or family or tribe...

Maybe as different as invertebrates from vertebrates?

David Olson
Culver City, California

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

Re: Problems with segnos and codas

[Carl Sorensen]

On 10/5/10 4:22 PM, "Tim Rowe"  wrote:

> On 5 October 2010 17:23, Xavier Scheuer  wrote:
> 
>> Yes, indeed, this is a really annoying issue.
>> This kind of "LilyPond limitation" make me feel upset sometimes.
> 
> I hardly dare ask whether there's any way to get the midi playback to
> follow the segnos and codas :-/

Short answer: No.

Longer answer: Write each piece of music as a separate variable, then use a
different \score for the print layout and the midi file.

LilyPond midi was not created as a performance midi, but as a proofhearing
midi.  And we currently don't really have anybody working on the midi part,
as far as I know.

Thanks,

Carl


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

Re: minor inconsistency in \paper-settings?

[Carl Sorensen]

On 10/5/10 1:47 PM, "James Wilkinson"  wrote:

> On 10/3/10 3:45 PM, Carl Sorensen wrote:
> 
>> It would seem desirable to have a warning message when a non-existent
>> property is set in a \paper{} block.
> 
> Why not whenever a non-existent property is set anywhere?

We already do it when a non-existent property is set using \set.

Thanks,

Carl


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

Re: Problems with segnos and codas

[Tim Rowe]

On 5 October 2010 17:23, Xavier Scheuer  wrote:

> The only real workaround that I found is LSR #575
> http://lsr.dsi.unimi.it/LSR/Item?id=575

That seems to be what I need, thanks. When I shuffle it around for my
score, though, the return to 4/4 is visible, so I've missed something.
I could live with it as it is (it is the start of a coda, after all),
but it would be nice to fix. What hides it in the sample you linked?

-- 
Tim Rowe

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

Re: \tempo

[Vicente Solsona]

On Tue, 05 Oct 2010 22:27:40 +0200, Mario Moles   
wrote:

Hi lilyponders!
How i can for \tempo=40-42 ?
Cheers!


use markups. I guess you mean something like this:

\tempo \markup {
  \concat {
 \general-align #Y #DOWN \note #"4" #1
" = 40-42"
  }
}

did you look in the manual? there's a pretty similar example there.

greetings,

Vicente


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

Re: \header place in \score block (doc & syntax clarification)

[RobUr]

Did you notice Lily's log? It complains about the bad \header placement!
But it seems uncritical, and so Lily continues compiling. Should it abort?

Best, Robert

Am 05.10.2010, 15:09 Uhr, schrieb Antheo :



would somebody mind clarifying?


Antheo wrote:



The documentation here
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Introduction-to-the-LilyPond-file-structure#Introduction-to-the-LilyPond-file-structure

says: "A \score block must always contain just one music expression, and
this must appear immediately after the \score command."
and: "these three commands – \header, \layout and \midi – are special:
unlike many other commands which begin with a backward slash (\) they  
are

not music expressions"

Which implies that the \header must be placed after the music  
expression.

However, I found that with version 2.12, the lilypond accepts that the
header is placed before as well.

\version "2.12.3"
\score {
  \header { piece = "lilypond compiles a score where header is placed
before the music expression"}
  { c'4 a b c' }
  \layout { }
}

If lilypond compiles the file, I'd assume the documentation needs to be
updated???
Would you mind clarifying?

 http://old.nabble.com/file/p29878274/test%2Bheader%2Bplace.ly
test+header+place.ly






--
--
http://www.lilypondforum.de/


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

Re: Problems with segnos and codas

[Tim Rowe]

On 5 October 2010 17:23, Xavier Scheuer  wrote:

> Yes, indeed, this is a really annoying issue.
> This kind of "LilyPond limitation" make me feel upset sometimes.

I hardly dare ask whether there's any way to get the midi playback to
follow the segnos and codas :-/

-- 
Tim Rowe

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

Re: Re: conditional formatting

[Marten Visser]

At 20:51 05/10/2010, you wrote:

On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser 
wrote:

Hi Vincente, thanks for the suggestion. However, I do not only want to
delete a music expression (which can be tagged), but an entire staff,
namely the tabStaff. I wouldn't know how to create code removing a staff
by tagging it.


you're right. I thought that what you requested could be done with tags
because I once did something similar and there were tags involved.

but I've looked in my file again and found an alternative and perhaps
simpler
way which you may find useful: the trick is to use two different \book
sections;
then Lilypond generates two pdfs in one move, so you don't need to specify
any
condition at all:

%8<--
%
% input file tst.ly generates tst.pdf for the piccolist and tst-1.pdf for
the guitarist

\version "2.12.3"

piccolo = \relative c'' {
c d e f
}

guitar = \relative c' {
a b c d
}

staffPiccolo = \new Staff {
\piccolo
}

staffGuitar = \new Staff
{
\guitar
}

staffTabGuitar = \new TabStaff
{

\guitar
}

\book
{
% creates tst.pdf for the piccolist
<<
\staffPiccolo
\staffGuitar
>>
}

\book
{
% creates tst-1.pdf for the guitarist
<<
\staffPiccolo
\staffGuitar
\staffTabGuitar
>>
}

%8<--

I hope I've understood you better this time :)


Dmytro's suggestion looks more promising, though I haven't been able to
generate code that does the job so far. When I code


that looks very interesting and can be very useful if you find the way.

greetings,

Vicente


Thanks for this suggestion. Indeed I do want to generate both scores, 
so it looks like a perfect solution. :)


--Marten



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

Re: conditional formatting

[Marten Visser]

At 19:03 05/10/2010, you wrote:
I can't really use Scheme (other than find and replace), so maybe 
this doesn't solve what you need, but what about creating separate 
variables with the staves that you want and simply commenting an 
appropriate \score ? i.e.,

\version "2.12.3"

piccolo = \relative a' { a c' a e' e c a e }

instrument = { a, c' a e' e c' a e'}

instrumentTab = {
  a,4\5 c'\2 a\3 e'\1
  e\4 c'\2 a\3 e'\1
}

withTabs = \new StaffGroup <<
   \new Staff \instrument
   \new TabStaff \with { instrumentName = lute } \instrumentTab
>>

withoutTabs = \new StaffGroup <<
   \new Staff \with { instrumentName = piccolo } \piccolo
   \new Staff \with { instrumentName = lute } \instrument
>>

%\score { \withTabs }
\score { \withoutTabs }


Hi, thanks for thinking with me. This indeed is a solution. The 
preceding discussion focusses on the use of Devnull as a solution, 
but indeed you may define two different contents for the \score block.


Scheming along, the example in the previous posts may be changed as 
below. Select the apropriate makeFor to obtain the desired output. 
When guitar is selected, a tabstaff will be displayed in addition.


Problem solved, thanks frogs!
(apart from what seems to be a bug when you put tablature into a Devnull)

--Marten

===
%{
Example of optional TabStaff with scheme functions and 
variable \score block

%}

\version "2.13.32"

makeFor = #'choir
makeFor = #'piano
%makeFor = #'guitar

myContainer =
#(if (eq? makeFor 'choir)   "ChoirStaff" "PianoStaff")


upperMelody = \relative c'' {
  c4 bes d c
}

lowerMelody = \relative c' {
  a4 g bes a
}

Tablature = \simultaneous { % Combine both voices for Tablature
\override TabStaff.Stem #'transparent = ##t % Makes stems transparent
\override TabStaff.Beam #'transparent = ##t % Makes beams transparent
<< \context TabVoice=TabVoiceA { \upperMelody} >>
<< \context TabVoice=TabVoiceB { \lowerMelody} >>
}

OptionalTabStaff =
#(if (eq? makeFor 'guitar)
#{ \new TabStaff << \Tablature >> #}
#{ #})


\score {
  <<
\new \myContainer <<
\new Staff
{
\set Staff.instrumentName = #(symbol->string makeFor)
<<
\upperMelody
>>
}
  \new Staff {
  \lowerMelody
}
>>
\OptionalTabStaff
>>
}
===



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

Re: anybody understand the instrumentCueName docs?

[Keith E OHara]

On Tue, 05 Oct 2010 02:05:00 -0700, Trevor Daniels wrote:


Keith E OHara wrote Tuesday, October 05, 2010 7:18 AM



   \new CueVoice \with {
 instrumentCueName = "ob."
   } \new Voice {
[ . . . ]

this example does not create a new Voice _within_ the CueVoice - it
creates it in parallel with it, both within a Staff context.


Yep. But from the grammar alone, one would think it works like
  \new Staff \with {instrumentName=#"oboe"}
  \new Voice { a b c d }

Trevor Daniels wrote:


If voice or cuevoice contexts are created, explicitly or implicitly,
in music which is passed to \addQuote the cue notes are not extracted
correctly. A \set command will implicitly create a voice.

But, just for the record, we may safely \set properties in the *existing* Voice,
within a music expression that we intend to quote.


You can get round this by using tags.

  [ . . . ]

  \tag #'cue  \set CueVoice.instrumentCueName = "ob."


Now that should work, scaled to a full score. We need to tag this anyway to clean "ob." 
and the like from the score. (killCues lets the labels live.) The snippet I said I liked does the 
same, except using Voice.instrumentCueName="ob."

It is a long way, however, from the examples in the documentation, to these 
solutions.

I am leaning toward suggesting dropping instrumentCueName in favor of simple 
\markup, once I check a few things.
-Keith


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

\tempo

[Mario Moles]

Hi lilyponders!
How i can for \tempo=40-42 ?
Cheers!
-- 
oiram/bin/selom
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: minor inconsistency in \paper-settings?

[James Wilkinson]

On 10/3/10 3:45 PM, Carl Sorensen wrote:


It would seem desirable to have a warning message when a non-existent
property is set in a \paper{} block.


Why not whenever a non-existent property is set anywhere?

++

Jimmy Wilkinson| Professor Emeritus of Computer Science
ji...@cs.cofc.edu  | The College of Charleston
(843) 953-8160 | Charleston  SC29424
http://www.cs.cofc.edu/~jimmy

If there is one word to describe me, that word would have to be 
"profectionist".

Any form of incompitence is an athema to me.
Metathesis??? Don't ax me.
Just between you and I, the grammar used by Americans are getting worse.
I can only help but wonder what the cause of this might be.
It just ceases to amaze me how it could be the case, but mostly I could 
care less.

.. boat storage under house with wench ..
I won't get into specifics because that was between he and I

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

Lilypond-book margins

[Christopher Meredith]

Does anyone know what to put in the lytex file to produce a PDF that is
8.5x5.5 ( half US letter)?

[Sent from my Google Nexus One]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: conditional formatting

[Vicente Solsona]

On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser   
wrote:
Hi Vincente, thanks for the suggestion. However, I do not only want to  
delete a music expression (which can be tagged), but an entire staff,  
namely the tabStaff. I wouldn't know how to create code removing a staff  
by tagging it.


you're right. I thought that what you requested could be done with tags
because I once did something similar and there were tags involved.

but I've looked in my file again and found an alternative and perhaps  
simpler
way which you may find useful: the trick is to use two different \book  
sections;
then Lilypond generates two pdfs in one move, so you don't need to specify  
any

condition at all:

%8<--
%
% input file tst.ly generates tst.pdf for the piccolist and tst-1.pdf for  
the guitarist


\version "2.12.3"

piccolo = \relative c'' {
c d e f
}

guitar = \relative c' {
a b c d
}

staffPiccolo = \new Staff {
\piccolo
}

staffGuitar = \new Staff
{
\guitar 
}

staffTabGuitar = \new TabStaff
{

\guitar 
}

\book
{
% creates tst.pdf for the piccolist
<<
\staffPiccolo
\staffGuitar
>>
}

\book
{
% creates tst-1.pdf for the guitarist
<<
\staffPiccolo
\staffGuitar
\staffTabGuitar 
>>
}

%8<--

I hope I've understood you better this time :)

Dmytro's suggestion looks more promising, though I haven't been able to  
generate code that does the job so far. When I code


that looks very interesting and can be very useful if you find the way.

greetings,

Vicente


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

Re: conditional formatting

[James Bailey]

I can't really use Scheme (other than find and replace), so maybe this doesn't 
solve what you need, but what about creating separate variables with the staves 
that you want and simply commenting an appropriate \score ? i.e.,
\version "2.12.3"

piccolo = \relative a' { a c' a e' e c a e }

instrument = { a, c' a e' e c' a e'}

instrumentTab = {
  a,4\5 c'\2 a\3 e'\1
  e\4 c'\2 a\3 e'\1
}

withTabs = \new StaffGroup <<
   \new Staff \instrument
   \new TabStaff \with { instrumentName = lute } \instrumentTab
>>

withoutTabs = \new StaffGroup <<
   \new Staff \with { instrumentName = piccolo } \piccolo
   \new Staff \with { instrumentName = lute } \instrument
>>

%\score { \withTabs }
\score { \withoutTabs }


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

Re: Re: Re: conditional formatting

[Marten Visser]

At 11:08 05/10/2010, you wrote:

On Mon 04 Oct 2010, 23:11 Marten Visser wrote:
> Dmytro's suggestion looks more promising, though I haven't been able
> to generate code that does the job so far. When I code
>
> ==
> \new Devnull
> <<
> \TablatureNotes
> >>
> ==
>
> I still get an empty tabStaff and two tabstaffs below it for both
> voices in the \TablatureNotes. Replacing "Devnull" by "TabStaff", I
> get one tabstaff with both voices combined. I guess Devnull is not a
> manner to suppress printing the staff.

Sorry, i've not tested this much.

Which lilypond version do you use? That sample was tested (a bit,-) with
2.13.35, latest development so far. Well.. this works with 2.12 too, ive tried
just now.

First of all -- i'm not sure that this is the best (or even smart at all) way
to do "this" (and i am still not sure that i understood what's needed,-)

Anyway, please take a look -- this example produces ChoirStaff with two staves
if makeFor equals 'choir and produces single staff with \lowerMelody if
makeFor equals anything else.

How far this from a required result?

%--8<---
makeFor = #'choir

#(define myContainer (if (eq? makeFor 'choir)
 "ChoirStaff"
 "Devnull"))

#(define upperStaff (if (eq? makeFor 'choir)
"Staff"
"Devnull"))

upperMelody = \relative c'' {
  c4 bes d c
}

lowerMelody = \relative c'' {
  a4 g bes a
}

\score {
  \new \myContainer <<
\new \upperStaff <<
  \upperMelody
>>
\new Staff {
  \lowerMelody
}
  >>
}
%--8<---

I'm just interesting .-)

Playing with lilypond gives me a lot of fun and some experience, which can be
used later, for my own needs.

Or, if this is more convenient for you, could you post a small example ---
what you've tried and it wasn't work as desired?

Thanks.

--
  Dmytro O. Redchuk
  Bug Squad


Hello again,

I compiled your example, but it didn't compile without errors. I did 
get the results you got, however.


I changed your code to obtain what I expected your code to produce:

==
%{
Example of variable stafftype with scheme funtions
%}

\version "2.13.32"

makeFor = #'piano
%makeFor = #'choir

%#(define myContainer (if (eq? makeFor 'choir)
% "ChoirStaff"
% "Devnull"))
myContainer =
#(if (eq? makeFor 'choir) "ChoirStaff" "PianoStaff")

%#(define upperStaff (if (eq? makeFor 'choir)
%"Staff"
%"Devnull"))
upperStaff =
#(if (eq? makeFor 'choir) "Staff" "Devnull")

upperMelody = \relative c'' {
  c4 bes d c
}

lowerMelody = \relative c'' {
  a4 g bes a
}

\score {
  \new \myContainer <<
\new \upperStaff
{
\set Staff.instrumentName = \myContainer
<<
  \upperMelody
>>
}
\new Staff {
  \lowerMelody
}
  >>
}
==

By setting the instrumentName to \myContainer I checked what was 
actually happening. In your example an unrecoverable error occurred. 
The above example is bug-free in the \version used.


I'll try to work this to a code for omitting the tablature staff, and 
post it here.


--Marten 



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

Re: Problems with segnos and codas

[Xavier Scheuer]

On 5 October 2010 13:32, Tim Rowe  wrote:
>
> I have a coda immediately following a D.S., and have tried to mark it
> up as follows:
>  
>    \override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
>    \override Score.RehearsalMark #'self-alignment-X = #RIGHT
>    \mark \markup {"D.S " \musicglyph #"scripts.segno"}
>  |
>    \override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
>    \override Score.RehearsalMark #'self-alignment-X = #LEFT
>    \mark \markup {\musicglyph #"scripts.coda" "Coda "} |
>  g2 r2 |
> (To be honest, they're just magic incantations I god from snippets,
> and I have no real understanding of what they're doing).
>
> That has two problems. The most significant is that it doesn't work at
> all -- I get a warning that there are two simultaneous mark events,
> and it junks the second, so I don't get the coda mark.
>
> The one that you can't tell from the little bit that I've included
> there is that the starting g of the coda should be tied over from the
> "to coda" bar, so it should have a tie going into it.
>
> Where am I going wrong? Is there an easy way to fix these problems?

Yes, indeed, this is a really annoying issue.
This kind of "LilyPond limitation" make me feel upset sometimes.

The only real workaround that I found is LSR #575
http://lsr.dsi.unimi.it/LSR/Item?id=575

Unfortunately this is really a _dirty_ workaround.
I hope that further LilyPond improvements (like the use of #anchor) would
help handle far better this kind of situations.

http://code.google.com/p/lilypond/issues/detail?id=824
http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg00544.html

Cheers,
Xavier

-- 
Xavier Scheuer 

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

Re: hspace in cm?

[Xavier Scheuer]

On 27 September 2010 16:54, Robin Bannister  wrote:
>
> Well, I've had Lilypond on the back burner for a while, so I'm a bit rusty.
> By swapping the X and Y of mm-feed you get horizontal millimeters:
>
> #(define-markup-command (mm-hgap layout props amount) (number?)
> (let ((o-s (ly:output-def-lookup layout 'output-scale)))
>  (ly:make-stencil "" (cons 0 (abs (/ amount o-s))) '(0 . 0) )))
>
> \markup \line { "first" "next" "last" }
> \markup \line { \mm-hgap #20 "first" \mm-hgap #20 "next" \mm-hgap #20 "last"
> }
>

Thank you Robin for your kind reply.

I'm sorry I have no "stable" internet connection at the moment...  :-C
(or when I too rarely have Internet I have not LilyPond...).

I'll test it and look into it ASAP, thanks again.


On 3 October 2010 21:24, Neil Puttock  wrote:
>
> OK, though I hope first you've tried to do it yourself; I'm pretty
> sure it's within your capabilities.  :)

I wish it would!

It seems simple when you get the "ready-to-use" command.  ;-D
Actually I did not even understand I would have to define my own
Scheme command!  So I played with the "normal"  \hspace  command.
;-p

I am really scared when I have to deal with that kind of Scheme stuffs!
I'm learning about it by modifying existing Scheme code I can found on the LSR
or within LilyPond's mailing lists.  So basically I am working by comparison and
by trial-and-error based on pre-existing code but I am not yet really able to
"make the jump" and define my own commands because there are still a lot
of things I do not understand clearly speaking of Scheme code.

I must be lacking some "basic programming knowledge".
Unfortunately my scheduled does not allow me to begin studying various
programming languages right now.  So I'll keep on doing odd jobs.
That said, I am always very grateful when a talented developer gives me a
good, ready-to-use solution.  :)

Thanks a lot.

Cheers,
Xavier

-- 
Xavier Scheuer 

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

Re: Problems with segnos and codas

[Gilles Sadowski]

On Tue, Oct 05, 2010 at 09:26:52AM -0500, Tim McNamara wrote:
> While this doesn't solve the problem (somebody else seems to have
> done that), it'd sure be nice if using marks for segno and coda
> would be a lot more user friendly- like
> 
> g1\segno
> 
> g1\coda

That would not solve the problem because we want those to be associated with
the bar line (i.e. a single setting for a whole score, not one per staff).

> [...] although both coda and segno are
> probably more properly associated with a bar line than with a beat,
> unlike a fermata.

Indeed.

> And it would be nice if the problem with manual breaks and codas
> could be fixed.  There is no reason for the coda mark to be forced
> to the beginning of the next line if a \break is present.  The mark
> should be rendered where it is placed.

I guess that the problem is that a bar line is a bar line, even if visually
splitted over two staves.


Best,
Gilles

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

Re: Problems with segnos and codas

[Tim McNamara]

While this doesn't solve the problem (somebody else seems to have  
done that), it'd sure be nice if using marks for segno and coda would  
be a lot more user friendly- like


g1\segno

g1\coda

perhaps as one can with g1\fermata, although both coda and segno are  
probably more properly associated with a bar line than with a beat,  
unlike a fermata.


And it would be nice if the problem with manual breaks and codas  
could be fixed.  There is no reason for the coda mark to be forced to  
the beginning of the next line if a \break is present.  The mark  
should be rendered where it is placed.


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

How to set different bar number format every nth bar?

[Marc Mouries]

 I'd like to have bar numbers printed on every bar with the first bar 
number of each line bigger.
I'd like to find if there is any way to set different bar number format 
with a function rather than inline with the music.

I'd like to avoid to reset the bar number format for each staff like:

\score {
% set the size of the first bar number larger
  \override Score.BarNumber #'font-size = #-2
  c d e f | % 1st measure
  % 5th other measures on the same staff
  \override Score.BarNumber #'font-size = #-4
 g a b c | c d e f | g a b c | c d e f | g a b c |
  % and so on...
}

I've seen Neil's music function to set the visibility of the bar number 
every odd measure but don't think this can be reused to set the font size.


links to documentation i may have missed or scheme functions are welcome.

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

\header place in \score block (doc & syntax clarification)

[Marc Mouries]

 The documentation here 
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Introduction-to-the-LilyPond-file-structure#Introduction-to-the-LilyPond-file-structure


says: "A \score block must always contain just one music expression, and 
this must appear immediately after the \score command."
and: "these three commands – \header, \layout and \midi – are special: 
unlike many other commands which begin with a backward slash (\) they 
are not music expressions"


Which implies that the \header must be placed after the music 
expression. However, I found that with version 2.12, the lilypond 
accepts that the header is placed before as well.


\version "2.12.3"
\score {
\header { piece = "lilypond compiles a score where header is placed 
before the music expression"}

{ c'4 a b c' }
\layout { }
}

If lilypond compiles the file, I'd assume the documentation needs to be 
updated???

Would you mind clarifying?

-Marc

\version "2.12.3"
\score {
  \header { piece = "lilypond compiles a score where header is placed before the music expression"}
  \new Staff { c'4 a b c' }
  \layout { }
}

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

Re: Problems with segnos and codas

[Gilles Sadowski]

Hi.

> You're trying to put 2 rehearsal marks on the same bar line.  Does
> something like:
> 
>  { r4 r r 
>\override Score.RehearsalMark #'self-alignment-X = #CENTER
>\mark \markup {"D.S " \musicglyph #"scripts.segno" "   "
> \musicglyph #"scripts.coda" "Coda "}
>  |
>  g2 r2 |
> }
> 
> do what you want?

In many cases, that won't do since what usually happens is that "D.C."
must appear at the last bar, then there is a "\break" and the next line is
the coda (with the "scripts.coda" sign).

The workaround which I use is to put the "D.C." \mark one bar earlier with
a "#LEFT" alignment (so it looks like it is on the last bar, albeit not
aligned on the end of it).

Indeed it's strange that LilyPond cannot write both marks even if they are
not on the same line.


Best,
Gilles

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

Re: anybody understand the instrumentCueName docs?

[Reinhold Kainhofer]

Am Dienstag, 5. Oktober 2010, 15:07:34 schrieb Trevor Daniels:
> Keith
> 
> If voice or cuevoice contexts are created, explicitly or implicitly,
> in music
> which is passed to \addQuote the cue notes are not extracted
> correctly.

Yes, unfortunately, quoting music with more than one voice (explicitly or 
implicitly created) uses the notes of the **SECOND** created voice, not of the 
first voice... That's a known bug:
http://code.google.com/p/lilypond/issues/detail?id=1214

Cheers,
Reinhold
-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org


signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to set different bar number format every nth bar?

[Antheo]

Is that something not possible?


Antheo wrote:
> 
> I'd like to avoid to do:
> 
> \score {
> % set the size of the first bar number larger
>   \override Score.BarNumber #'font-size = #-2
>   c d e f | % 1st measure
>   % 5th other measures on the same staff
>   \override Score.BarNumber #'font-size = #-4
>  g a b c | c d e f | g a b c | c d e f | g a b c | 
>   % and so on...
> }
> 
> I've seen Neil's music function to set the visibility of the bar number
> every odd measure but don't think this can be reused to set the font size.
> 
> links to documentation i may have missed or scheme functions are welcome.
> 
> 
> Antheo wrote:
>> 
>> 
>> I'd like to have bar numbers printed on every bar with the first bar
>> number of each line bigger.
>> I'd like to find if there is any way to set different bar number format
>> with a function rather than inline with the music.
>> 
>> -Marc
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>> 
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/How-to-set-different-bar-number-format-every-nth-bar--tp29834921p29887176.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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

Re: \header place in \score block (doc & syntax clarification)

[Antheo]

would somebody mind clarifying?


Antheo wrote:
> 
> 
> The documentation here
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/Introduction-to-the-LilyPond-file-structure#Introduction-to-the-LilyPond-file-structure
> 
> says: "A \score block must always contain just one music expression, and
> this must appear immediately after the \score command."
> and: "these three commands – \header, \layout and \midi – are special:
> unlike many other commands which begin with a backward slash (\) they are
> not music expressions"
> 
> Which implies that the \header must be placed after the music expression.
> However, I found that with version 2.12, the lilypond accepts that the
> header is placed before as well.
> 
> \version "2.12.3"
> \score {
>   \header { piece = "lilypond compiles a score where header is placed
> before the music expression"}
>   { c'4 a b c' }
>   \layout { }
> }
> 
> If lilypond compiles the file, I'd assume the documentation needs to be
> updated???
> Would you mind clarifying?
> 
>  http://old.nabble.com/file/p29878274/test%2Bheader%2Bplace.ly
> test+header+place.ly 
> 

-- 
View this message in context: 
http://old.nabble.com/%5Cheader-place-in-%5Cscore-block-%28doc---syntax-clarification%29-tp29878274p29887153.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


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

Re: anybody understand the instrumentCueName docs?

[Trevor Daniels]

Keith

If voice or cuevoice contexts are created, explicitly or implicitly, 
in music
which is passed to \addQuote the cue notes are not extracted 
correctly.
A \set command will implicitly create a voice.  You can get round 
this
by using tags.  Here's how I would code your example.  I prefer to 
keep

the context structure and the music quite separate.

Trevor


oboe = \relative c''' {
 g1
 g4 r8 e16 f e4 d
}
\addQuote "oboe" { \oboe }

violin = \relative c'' {
 g4. b8 a4 g4
 \tag #'cue  \set CueVoice.instrumentCueName = "ob."
 \cueDuring #"oboe" #UP { R1 }
 g4. b8 d2
}
\addQuote "v" { \removeWithTag #'cue { \violin } }

timpani = \relative c' {
 r2
 \set CueVoice.instrumentCueName = "vln"
 \cueDuring #"v" #UP { r2 }
 g4 r4 r2
 \set CueVoice.instrumentCueName = "vln"
 \cueDuring #"v" #UP { s2 }
 d'2
}

\score {
 <<
   \new Staff <<
 \new CueVoice
 \new Voice \violin
   >>
   \new Staff <<
 \new CueVoice
 \new Voice \timpani
   >>
 >>
}




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

Re: font size for numbers on easyHeadOn with number

[MING TSANG]

Thanks, your code is perfect. 

1.  I applied the suggested code (snippet) to my original .ly code I encounter 
lilypond abend. I also do CMD lilypond and the result is the same - "lilypond 
has encountered a problem and needs to close..."  I have desk check the code.
2.  Is there anyway to run lilypond in debug mode? I wish lilypond will tell me 
which line is the culprit. 

3.  I run lilypond with -d,--safe and it complains about "wrong type argument 
in 
position 1 ( expecting symbol): (unquote safe)

Here is the jedit console message for 1.  "Lilypond has encountered a problem 
and need to close ..."

This is a console shell for running LilyPond and related commands. Enter %help 
to see the available special commands.
> %lilypond %args "C:\Documents and 
>Settings\Administrator\Desktop\LILY_POND\more-love-to-thee.ly"
正在處理 ‘C:/Documents and 
Settings/Administrator/Desktop/LILY_POND/more-love-to-thee.ly’
分析中...
Interpreting music... 
Interpreting music... 
Processing time: 64 seconds










From: Carl Sorensen 
To: MING TSANG 
Cc: "lilypond-user@gnu.org" 
Sent: Sun, October 3, 2010 3:44:57 PM
Subject: Re: font size for numbers on easyHeadOn with number




On 9/29/10 9:42 AM, "MING TSANG"  wrote:

> Carl,
> 
> I took your code and added multi midi output for voice parts.  Everything
> seems working perfectly.  However I applied the template to my .ly code I
> cannot produce desire result.
> 

I'm sorry to be so slow in getting back to you.  It's been a busy week.

I ran your code, and got an error message that indicated the parser was
looking for more information (which was slightly different from your error).

I looked in the Notation Reference, section 3.1.5, and it shows \layout
blocks at top-level, rather than inside a \score block.  So I moved your
\layout block out of the \score block and into the top-level.  Then the file
ran perfectly -- .pdf output and 3 .midi outputs.

HTH,

Carl

P.S. If it were my code, I'd take \timeKey out of the Voice contexts, and
put it into the Staff contexts, since that's where the time signature is
determined.  I've done it in the code below.


\version "2.13.34"
\header {
  title = "主阿我要更愛你：More Love To Thee"
}
#(define Ez_numbers_engraver
  (list
(cons 'acknowledgers
  (list
  (cons 'note-head-interface
(lambda (engraver grob source-engraver)
  (let* ((context (ly:translator-context engraver))
  (tonic-pitch (ly:context-property context 'tonic))
  (tonic-name (ly:pitch-notename tonic-pitch))
  (grob-pitch
  (ly:event-property (event-cause grob) 'pitch))
  (grob-name (ly:pitch-notename grob-pitch))
  (delta (modulo (- grob-name tonic-name) 7))
  (note-names
  (make-vector 7 (number->string (1+ delta)
(ly:grob-set-property! grob 'note-names
note-names
#(set-global-staff-size 18)
EzNum = {
 \easyHeadsOn
\override Staff.StaffSymbol #'staff-space = #2.25
\override Staff.StaffSymbol #'line-thickness = #1.25
\override Staff.NoteHead #'font-size = #+2.75
\override Staff.Clef #'font-size = #+2.25
\override Staff.TimeSignature #'font-size = #+2.25
\override Staff.Accidental #'font-size = #+2.25
\override Voice.NoteHead #'font-size = #0
}

\paper  {
%#(set-global-staff-size (* 5.8 mm))
  indent = #(* mm 0)
  line-width = #(* mm 180)
  interscoreline = 2.\mm
  between-system-space = 36\mm
  ragged-bottom = ##t

}

\include "english.ly"
TimeKey = { \time 4/4  \key bf  \major  }
SopMusic  = \relative c' {
%\easyHeadsOn
d'4. d8 ef8 d8 c8 bf8 |%bar 17
bf2 a2 |%bar 18
\label #'lastPage
  }
AltoMusic  = \relative c' {
%\easyHeadsOn
\override NoteHead #'color = #blue
f4. f8 g8 f8 ef8 d8 |%bar 17
f2 ef2 |%bar 18
}
TenorMusic = \relative c  {
%\easyHeadsOn
bf'4. bf8 bf bf bf bf | bf2 c2 |%bar 17-18
}
BassMusic  = \relative c  {
%\easyHeadsOn
\override NoteHead #'color = #red
bf4. bf8 bf bf bf bf | d2 f2 |%bar 17-18
}

PianoRHand = \relative c' {
4.^( 8 8 8 8 8 |
%bar 17
2 2) |%bar 18
}
PianoLHand = \relative c {
8 d'8_\markup{con Ped} f bf f bf f bf |%bar 17
8 f'' bf f  a' c a |%bar 18
}

\layout {
  \context {
\Voice
\consists \Ez_numbers_engraver
  }
}

\score {
  \new GrandStaff = "GrandStaff_score" <<
\new ChoirStaff <<
  \new Staff <<
\override Score.BarNumber #'break-visibility = #'#(#

Re: Problems with segnos and codas

[Phil Holmes]

- Original Message - 
From: "Tim Rowe" 

To: "Lilypond-User Mailing List" 
Sent: Tuesday, October 05, 2010 12:32 PM
Subject: Problems with segnos and codas



I have a coda immediately following a D.S., and have tried to mark it
up as follows:
 
   \override Score.RehearsalMark #'break-visibility = 
#begin-of-line-invisible

   \override Score.RehearsalMark #'self-alignment-X = #RIGHT
   \mark \markup {"D.S " \musicglyph #"scripts.segno"}
 |
   \override Score.RehearsalMark #'break-visibility = 
#begin-of-line-invisible

   \override Score.RehearsalMark #'self-alignment-X = #LEFT
   \mark \markup {\musicglyph #"scripts.coda" "Coda "} |
 g2 r2 |
(To be honest, they're just magic incantations I god from snippets,
and I have no real understanding of what they're doing).

That has two problems. The most significant is that it doesn't work at
all -- I get a warning that there are two simultaneous mark events,
and it junks the second, so I don't get the coda mark.

The one that you can't tell from the little bit that I've included
there is that the starting g of the coda should be tied over from the
"to coda" bar, so it should have a tie going into it.

Where am I going wrong? Is there an easy way to fix these problems?

--
Tim Rowe


You're trying to put 2 rehearsal marks on the same bar line.  Does something 
like:


 { r4 r r 
   \override Score.RehearsalMark #'self-alignment-X = #CENTER
   \mark \markup {"D.S " \musicglyph #"scripts.segno" "   " \musicglyph 
#"scripts.coda" "Coda "}

 |
 g2 r2 |
}

do what you want?

--
Phil Holmes



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

Problems with segnos and codas

[Tim Rowe]

I have a coda immediately following a D.S., and have tried to mark it
up as follows:
  
\override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
\override Score.RehearsalMark #'self-alignment-X = #RIGHT
\mark \markup {"D.S " \musicglyph #"scripts.segno"}
  |
\override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
\override Score.RehearsalMark #'self-alignment-X = #LEFT
\mark \markup {\musicglyph #"scripts.coda" "Coda "} |
  g2 r2 |
(To be honest, they're just magic incantations I god from snippets,
and I have no real understanding of what they're doing).

That has two problems. The most significant is that it doesn't work at
all -- I get a warning that there are two simultaneous mark events,
and it junks the second, so I don't get the coda mark.

The one that you can't tell from the little bit that I've included
there is that the starting g of the coda should be tied over from the
"to coda" bar, so it should have a tie going into it.

Where am I going wrong? Is there an easy way to fix these problems?

-- 
Tim Rowe

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

Re: instrument names for grandstaves

[RobUr]

Obviously it's not intended to group RhythmicStaves in GrandStaves.
The solution is to use ordinary StaffGroups and overriding the  
systemStartDelimiter. Could be like this:

--- snip ---

\version "2.13.35"

\score {
\new StaffGroup
<<
\new StaffGroup = "group I" \with {
\consists "Instrument_name_engraver"
instrumentName = "group 1"
shortInstrumentName = "g1"
systemStartDelimiter = #'SystemStartBrace
} <<
\new RhythmicStaff = "test I" {
\set RhythmicStaff.instrumentName = "test 1"
\set RhythmicStaff.shortInstrumentName = "t1"
c4 c c c | \break c c c c
}
\new RhythmicStaff = "test II" {
\set RhythmicStaff.instrumentName = "test 2"
\set RhythmicStaff.shortInstrumentName = "t2"
c4 c c c | \break c c c c
}
>>

\new StaffGroup = "group II" \with {
\consists "Instrument_name_engraver"
instrumentName = "group 2"
shortInstrumentName = "g2"
systemStartDelimiter = #'SystemStartBrace
} <<
\new RhythmicStaff = "test III" {
\set RhythmicStaff.instrumentName = "test 3"
\set RhythmicStaff.shortInstrumentName = "t3"
c4 c c c | \break c c c c
}
\new RhythmicStaff = "test IV" {
\set RhythmicStaff.instrumentName = "test 4"
\set RhythmicStaff.shortInstrumentName = "t4"
c4 c c c | \break c c c c
}
>>
>>

\layout { }
}
--- snap ---

Best, Robert

Am 05.10.2010, 09:47 Uhr, schrieb 胡海鹏 - Hu Haipeng :


Hello,
  I'd like to engrave some percussion sections for separate players. The  
groups have their name for player numbers, and the individual rhythmic  
staves indicate names of instruments. However, even though I include the  
engraver, the file attached doesn't generate group names into the pdf. I  
know this because I converted the pdf into text. Could anyone point out  
what's wrong?

Regards
Haipeng





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

Re: My kingdom for a lilypond server

[Valentin Villenave]

On Mon, Oct 4, 2010 at 4:17 PM, Mike Blackstock
 wrote:
> Ha ha - a real 'groaner' if intentional pun.
>>
>> dedicated server (our current one only had 512Mo RAM, if memory serves

Wasn't even intentional. Neither was using Mo instead of "MB", for
that matter :-)

Nice catch!

Cheers,
Valentin

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

Re: LyricTie: Different font used from 2.12 to 2.13?

[Phil Holmes]

Thanks.  Submitted as 
http://code.google.com/p/lilypond/issues/detail?id=1294


--
Phil Holmes


- Original Message - 
From: "RobUr" <16...@golden-ears.de>

To: 
Sent: Tuesday, October 05, 2010 10:02 AM
Subject: Re: LyricTie: Different font used from 2.12 to 2.13?


Sure, forgot it in the hassle ... there's nothing unusual:

--- snip ---
\version "2.13.35"

\relative c' {
r4^"2.13.35 (uses “MS-Gothic”)" f e d | c2 c
}

\addlyrics { Buon gior -- no~al mon -- do. }
--- snap ---

Best, Robert

Please could you post the LilyPond snippet that you use to generate this 
example.


--
Phil Holmes


- Original Message - From: "RobUr" <16...@golden-ears.de>
To: 
Sent: Tuesday, October 05, 2010 7:43 AM
Subject: LyricTie: Different font used from 2.12 to 2.13?


Dear all,

everything was fine with LyricTies, until I came up with a score (say:
lyrics in this score) when trying the current Lily devel.
What happened? In 2.12.3: all lyric ties have been placed beautifully
where they have to be – starting right at the bottom right corner of the
left letter and ending right at the bottom left corner of the following
letter. On Mac OS X Tiger, Lily 2.12.3 (and before) resp. 
Pango/FontConfig

has chosen "Helvetica" to borrow this special char from. Great – fits
excellent!

NOW on the same machine – same OS, same hardware (sorry, can't change 
that

much, it's a MacBook), no re-install ever since Lily 11.x lived here (may
I call this "stable"?) – now Lily 2.13.34 upwards finds "MS-Gothic" to be
tied to lyrically!!! It's not for the font, but for the way Mr U+203F is
invoked: suddenly the glyph is much more narrow, it starts beneath the
vertical center of the letter and ends halfway the wordspace, leaving the
same gap before the following letter, where it was intended to stop.

So WHY do Lily 2.12 and 2.13 on the SAME MACHINE choose different 
(system)

fonts for the lyric tie? I greped all Lily-containers for "Helvetica" or
"MS-Gothic" to discover a new preference for the new font, but without
success. Is it Pango to make the choice on its own leaving Lily back with
baddest spacing? Please, compare the clips and see, how ugly it's now on
Mac OS X :(( I've found some code to modify the lyric tie spacing, but
that's just a solution for my local machine, not suitable to give away 
...


Setup: LP 2.12.3 and 2.13.11–35 on Mac OS X (10.4.11 Intel)

Regards,
Robert
--
http://www.lilypondforum.de/
http://www.lilypondforum.de/index.php?action=profile;u=170






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




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


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

Re: Re: conditional formatting

[Dmytro O. Redchuk]

On Mon 04 Oct 2010, 23:11 Marten Visser wrote:
> Dmytro's suggestion looks more promising, though I haven't been able
> to generate code that does the job so far. When I code
> 
> ==
> \new Devnull
> <<
> \TablatureNotes
> >>
> ==
> 
> I still get an empty tabStaff and two tabstaffs below it for both
> voices in the \TablatureNotes. Replacing "Devnull" by "TabStaff", I
> get one tabstaff with both voices combined. I guess Devnull is not a
> manner to suppress printing the staff.

Sorry, i've not tested this much.

Which lilypond version do you use? That sample was tested (a bit,-) with
2.13.35, latest development so far. Well.. this works with 2.12 too, ive tried
just now.

First of all -- i'm not sure that this is the best (or even smart at all) way
to do "this" (and i am still not sure that i understood what's needed,-)

Anyway, please take a look -- this example produces ChoirStaff with two staves
if makeFor equals 'choir and produces single staff with \lowerMelody if
makeFor equals anything else.

How far this from a required result?

%--8<---
makeFor = #'choir

#(define myContainer (if (eq? makeFor 'choir)
 "ChoirStaff"
 "Devnull"))

#(define upperStaff (if (eq? makeFor 'choir)
"Staff"
"Devnull"))

upperMelody = \relative c'' {
  c4 bes d c
}

lowerMelody = \relative c'' {
  a4 g bes a
}

\score {
  \new \myContainer <<
\new \upperStaff <<
  \upperMelody
>>
\new Staff {
  \lowerMelody
}
  >>
}
%--8<---

I'm just interesting .-)

Playing with lilypond gives me a lot of fun and some experience, which can be
used later, for my own needs.

Or, if this is more convenient for you, could you post a small example ---
what you've tried and it wasn't work as desired?

Thanks.

-- 
  Dmytro O. Redchuk
  Bug Squad

  Be careful! These are some commonly used abbreviations:
   • LM -- Learning Manual
   • NR -- Notation Reference
   • IR -- Internal Reference

  Look at LilyPond’s documentation to find more.

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

Re: anybody understand the instrumentCueName docs?

[Trevor Daniels]

Keith E OHara wrote Tuesday, October 05, 2010 7:18 AM

   I cannot find a way to use the documentation examples for 
cueDuring with instrumentCueName in a real score.
I'm thinking of writing up and submitting replacement examples, 
based on a snippet from the LSR.  First I'd like to see if I just 
missed the point of the existing examples.


1) The third example in "Formatting cue notes" seems to try to 
create a Voice inside a CueVoice:

   \new CueVoice \with {
 instrumentCueName = "ob."
   } \new Voice {
 \cueDuring #"oboe" #UP { R1 }
 g4. b8 d2
   }
First, the Internals Ref says CueVoice is not supposed to enclose 
other Contexts


The CueVoice context is just a Voice context with a smaller font 
size, stem length,
etc, so there should be no problem including another Voice within 
it.  But in fact
this example does not create a new Voice _within_ the CueVoice - it 
creates it

in parallel with it, both within a Staff context.  No problem here.

Second, I cannot figure out how to extend this to longer music 
with more parts.  For example, I tried to let a third voice quote 
a longer sequence of music containing the segment above (attached 
CueName.ly) and cannot see a way to structure the changing voices 
to allow quoting from anywhere in the sequence.


This is undeniably tricky.  I think the problem is that quoting 
parts only works
reliably when the quoted part contains only one voice.  There is a 
warning
that only the first voice is selected, but I suspect it may be more 
serious
than that.  Moving the \set instrumentCueName into the Voice 
context,
as you suggest, will change the time when the CueVoice context is 
created
and this may be why it then works.  But that is not the root cause 
of the
problem, so I would not want to change the documentation until this 
is

properly understood.

Trevor



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

Re: LyricTie: Different font used from 2.12 to 2.13?

[RobUr]

Sure, forgot it in the hassle ... there's nothing unusual:

--- snip ---
\version "2.13.35"

\relative c' {
r4^"2.13.35 (uses “MS-Gothic”)" f e d | c2 c
}

\addlyrics { Buon gior -- no~al mon -- do. }
--- snap ---

Best, Robert

Please could you post the LilyPond snippet that you use to generate this  
example.


--
Phil Holmes


- Original Message - From: "RobUr" <16...@golden-ears.de>
To: 
Sent: Tuesday, October 05, 2010 7:43 AM
Subject: LyricTie: Different font used from 2.12 to 2.13?


Dear all,

everything was fine with LyricTies, until I came up with a score (say:
lyrics in this score) when trying the current Lily devel.
What happened? In 2.12.3: all lyric ties have been placed beautifully
where they have to be – starting right at the bottom right corner of the
left letter and ending right at the bottom left corner of the following
letter. On Mac OS X Tiger, Lily 2.12.3 (and before) resp.  
Pango/FontConfig

has chosen "Helvetica" to borrow this special char from. Great – fits
excellent!

NOW on the same machine – same OS, same hardware (sorry, can't change  
that

much, it's a MacBook), no re-install ever since Lily 11.x lived here (may
I call this "stable"?) – now Lily 2.13.34 upwards finds "MS-Gothic" to be
tied to lyrically!!! It's not for the font, but for the way Mr U+203F is
invoked: suddenly the glyph is much more narrow, it starts beneath the
vertical center of the letter and ends halfway the wordspace, leaving the
same gap before the following letter, where it was intended to stop.

So WHY do Lily 2.12 and 2.13 on the SAME MACHINE choose different  
(system)

fonts for the lyric tie? I greped all Lily-containers for "Helvetica" or
"MS-Gothic" to discover a new preference for the new font, but without
success. Is it Pango to make the choice on its own leaving Lily back with
baddest spacing? Please, compare the clips and see, how ugly it's now on
Mac OS X :(( I've found some code to modify the lyric tie spacing, but
that's just a solution for my local machine, not suitable to give away  
...


Setup: LP 2.12.3 and 2.13.11–35 on Mac OS X (10.4.11 Intel)

Regards,
Robert
--
http://www.lilypondforum.de/
http://www.lilypondforum.de/index.php?action=profile;u=170






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




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

Re: LyricTie: Different font used from 2.12 to 2.13?

[Phil Holmes]

Please could you post the LilyPond snippet that you use to generate this 
example.


--
Phil Holmes


- Original Message - 
From: "RobUr" <16...@golden-ears.de>

To: 
Sent: Tuesday, October 05, 2010 7:43 AM
Subject: LyricTie: Different font used from 2.12 to 2.13?


Dear all,

everything was fine with LyricTies, until I came up with a score (say:
lyrics in this score) when trying the current Lily devel.
What happened? In 2.12.3: all lyric ties have been placed beautifully
where they have to be – starting right at the bottom right corner of the
left letter and ending right at the bottom left corner of the following
letter. On Mac OS X Tiger, Lily 2.12.3 (and before) resp. Pango/FontConfig
has chosen "Helvetica" to borrow this special char from. Great – fits
excellent!

NOW on the same machine – same OS, same hardware (sorry, can't change that
much, it's a MacBook), no re-install ever since Lily 11.x lived here (may
I call this "stable"?) – now Lily 2.13.34 upwards finds "MS-Gothic" to be
tied to lyrically!!! It's not for the font, but for the way Mr U+203F is
invoked: suddenly the glyph is much more narrow, it starts beneath the
vertical center of the letter and ends halfway the wordspace, leaving the
same gap before the following letter, where it was intended to stop.

So WHY do Lily 2.12 and 2.13 on the SAME MACHINE choose different (system)
fonts for the lyric tie? I greped all Lily-containers for "Helvetica" or
"MS-Gothic" to discover a new preference for the new font, but without
success. Is it Pango to make the choice on its own leaving Lily back with
baddest spacing? Please, compare the clips and see, how ugly it's now on
Mac OS X :(( I've found some code to modify the lyric tie spacing, but
that's just a solution for my local machine, not suitable to give away ...

Setup: LP 2.12.3 and 2.13.11–35 on Mac OS X (10.4.11 Intel)

Regards,
Robert
--
http://www.lilypondforum.de/
http://www.lilypondforum.de/index.php?action=profile;u=170






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




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

instrument names for grandstaves

[胡海鹏 - Hu Haipeng]

Hello,
  I'd like to engrave some percussion sections for separate players. The groups 
have their name for player numbers, and the individual rhythmic staves indicate 
names of instruments. However, even though I include the engraver, the file 
attached doesn't generate group names into the pdf. I know this because I 
converted the pdf into text. Could anyone point out what's wrong?
Regards
Haipeng


 \version "2.13.35"

\score {
  \new StaffGroup <<
\new GrandStaff = "group I"\with { \consists "Instrument_name_engraver" } <<
  \set GrandStaff.instrumentName = "group 1"
  \set GrandStaff.shortInstrumentName = "g1"
  \new RhythmicStaff = "test I" {
\set RhythmicStaff.instrumentName = "test 1"
\set RhythmicStaff.shortInstrumentName = "t1"
c4 c c c | \break c c c c
  }
  \new RhythmicStaff = "test II" {
\set RhythmicStaff.instrumentName = "test 2"
\set RhythmicStaff.shortInstrumentName = "t2"
c4 c c c | \break c c c c
  }
>>
\new GrandStaff = "group II" \with { \consists "Instrument_name_engraver" } <<
  \set GrandStaff.instrumentName = "group 2"
  \set GrandStaff.shortInstrumentName = "g2"
  \new RhythmicStaff = "test III" {
\set RhythmicStaff.instrumentName = "test 3"
\set RhythmicStaff.shortInstrumentName = "t3"
c4 c c c | \break c c c c
  }
  \new RhythmicStaff = "test IV" {
\set RhythmicStaff.instrumentName = "test 4"
\set RhythmicStaff.shortInstrumentName = "t4"
c4 c c c | \break c c c c
  }
>>
  >>
  \layout { }
}



i.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

LyricTie: Different font used from 2.12 to 2.13?

[RobUr]

Dear all,

everything was fine with LyricTies, until I came up with a score (say:  
lyrics in this score) when trying the current Lily devel.
What happened? In 2.12.3: all lyric ties have been placed beautifully  
where they have to be – starting right at the bottom right corner of the  
left letter and ending right at the bottom left corner of the following  
letter. On Mac OS X Tiger, Lily 2.12.3 (and before) resp. Pango/FontConfig  
has chosen "Helvetica" to borrow this special char from. Great – fits  
excellent!


NOW on the same machine – same OS, same hardware (sorry, can't change that  
much, it's a MacBook), no re-install ever since Lily 11.x lived here (may  
I call this "stable"?) – now Lily 2.13.34 upwards finds "MS-Gothic" to be  
tied to lyrically!!! It's not for the font, but for the way Mr U+203F is  
invoked: suddenly the glyph is much more narrow, it starts beneath the  
vertical center of the letter and ends halfway the wordspace, leaving the  
same gap before the following letter, where it was intended to stop.


So WHY do Lily 2.12 and 2.13 on the SAME MACHINE choose different (system)  
fonts for the lyric tie? I greped all Lily-containers for "Helvetica" or  
"MS-Gothic" to discover a new preference for the new font, but without  
success. Is it Pango to make the choice on its own leaving Lily back with  
baddest spacing? Please, compare the clips and see, how ugly it's now on  
Mac OS X :(( I've found some code to modify the lyric tie spacing, but  
that's just a solution for my local machine, not suitable to give away ...


Setup: LP 2.12.3 and 2.13.11–35 on Mac OS X (10.4.11 Intel)

Regards,
Robert
--
http://www.lilypondforum.de/
http://www.lilypondforum.de/index.php?action=profile;u=170<><>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user