Header block instrument name problem
Win.XP / Version 2.10.20
Having trouble to include \flat in instrument name in the \header block i.e.
:-
\header {
instrument = "Trumpet in B"\flat
}
I've tried this and other arrangements but with no luck to print the flat
symbol. Any ideas please.
Regards, Alan
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.11/909 - Release Date: 20/07/2007
4:39 p.m.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Colliding fret-diagrams
It's much easier to provide a relevant answer to your question if you
include a small example .ly file that illustrates your problem.
Also, don't forget to tell what LilyPond version you use.
How do you typeset the fret diagrams? Do you attach them to note like
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
or do you typeset them as a Lyrics line
\new Lyrics { \markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;" ... }
or do you use the new (but still undocumented) FretBoards context
which was introduced in version 2.10 (see the NEWS link in the
documentation for 2.10 for an example)?
The answer will be different in the three different cases.
In the first case, it should work to use \fatText, as is illustrated in
the following example:
\version "2.10.0"
\relative c { \fatText c8^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
c^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;" |
}
\layout{ragged-right = ##t }
If you want to increase the spacing even further, the answer
is different if you use version 2.10.x or the experimental 2.11.x.
/Mats
Quoting Rob Duncan <[EMAIL PROTECTED]>:
I'm trying to notate some rapid chord changes with \fret-diagram but the
diagrams are overlapping each other. Presumably this is because the widths
of the chord diagrams aren't affecting the layout of the melody notes that
I'm attaching the \fret-diagrams to. What is the best way to remedy this?
I think I want something like \fatText, but perhaps there's a better way.
Can anyone suggest something?
Thanks,
Rob.
--
View this message in context:
http://www.nabble.com/Colliding-fret-diagrams-tf4117742.html#a11710164
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
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Header block instrument name problem
>
> Having trouble to include \flat in instrument name in the \header block i.e.
> :-
>
> \header {
> instrument = "Trumpet in B"\flat
> }
Try that instead:
instrument = \markup{ "Trumpet in B"\small\flat }
Best,
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Header block instrument name problem
If you read the section on "Creating titles" in the manual it tells you
that you can use any "Text markup" commands, for example
\header{
instrument = \markup{ Trumpet in B \flat }
}
If you don't like the vertical alignment, search the mailing list
archives or read the "Overview of Text markup commands" section to
figure out yourself how to fine-tune it.
/Mats
Quoting alanvw <[EMAIL PROTECTED]>:
Win.XP / Version 2.10.20
Having trouble to include \flat in instrument name in the \header block i.e.
:-
\header {
instrument = "Trumpet in B"\flat
}
I've tried this and other arrangements but with no luck to print the flat
symbol. Any ideas please.
Regards, Alan
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.11/909 - Release Date: 20/07/2007
4:39 p.m.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Need help with this simple lyric
Quoting peterwinson <[EMAIL PROTECTED]>: Mats, how do you do this in Jedit. I've tried to find out but still have not figured it out. Do you need the Lilytool plugin for jedit? I've never used Jedit myself, but a quick look in the Jedit manual reveals that there is a full section devoted to "Character encodings" which should answer your question. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating music with Scheme - can this be done in a simpler way?
On 11/07/07, Neil Puttock <[EMAIL PROTECTED]> wrote:
> Hi Neil,
>
> Thanks for your solution! It works fine on its own, but I'm having
> trouble using it for something like
>
> \applyMusic #transform {
> << \pedalMotif { c } { s4-\< s2. s4-\! } >>
> }
>
> which fails to compile:
>
> GNU LilyPond 2.10.25
> Processing `test.ly'
> Parsing...ERROR: Wrong type (expecting pair): ()
>
A solution would be to place the function inside the polyphonic section,
i.e.
<< { \applyMusic #transform {
\pedalMotif { g, }
}
} \\ { s4-\< s2. s4-\! }
>>
or
<< { \applyMusic #transform {
\pedalMotif { g, }
}
}
\new Voice { s4-\< s2. s4-\! }
>>
Regards,
Neil
I added my original music function to the LSR; it's not the most
beautiful code but it is the easiest to use I think.
http://lsr.dsi.unimi.it/LSR/Item?id=302
--
Groeten,
Alard.
Ceterum censeo MS Word esse delendam.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating music with Scheme - can this be done in a simpler way?
2007/7/21, Alard de Boer <[EMAIL PROTECTED]>: I added my original music function to the LSR; it's not the most beautiful code but it is the easiest to use I think. Thanks; approved. Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Tip: defining new contexts ... starting from existing contexts
Hi,
The following is a short write-up on how to define new contexts
starting from existing contexts. The tip augments 9.2.7 "Defining new
contexts" which explains how to define new contexts starting from
scratch.
Consider the following red-and-blue score.
%%% EX 1 %%%
\version "2.11.26"
\new Score <<
\new Staff \with {
\override NoteHead #'color = #red
\override Stem #'color = #red
} {
c'4 c'4 c'4 c'4
}
\new Staff \with {
\override NoteHead #'color = #blue
\override Stem #'color = #blue
} {
c'4 c'4 c'4 c'4
}
>>
%%% EX 1 %%%
The red-and-blue score in example 1 instantiates two separate staves,
reddens the with-block of the first staff, and then turns the
with-block of the second staff blue.
This approach works great but mixes formatting directives and note
entry together. Maybe externalizing our overrides will give us a
cleaner inputfile.
9.2.6 "Changing context default settings" tells us how change contexts
globally. But this approach is unavailable to us here.
%%% EX 2 %%%
\version "2.11.26"
\layout {
\context {
\Staff
\override NoteHead #'color = #red
\override Stem #'color = #red
\override NoteHead #'color = #blue
\override Stem #'color = #blue
}
}
\new Score <<
\new Staff {
c'4 c'4 c'4 c'4
}
\new Staff {
c'4 c'4 c'4 c'4
}
>>
%%% EX 2 %%%
We can't override the global staff context to be both red and blue.
When we try, the interpreter overwrites our red overrides with our
blue overrides. Our red-and-blue score comes out only blue.
Instead, we've got two different types of staff. So we define two new contexts.
9.2.7 "Defining new contexts" tells us how to define new contexts from
scratch. But the default staff context does an awful lot of work. And
defining new staff contexts from scratch is a pain.
%%% EX 3 %%%
\version "2.11.26"
\layout {
\context {
\type "Engraver_group"
\name "RedStaff"
\consists "Output_property_engraver"
\consists "Bar_engraver"
\consists "Font_size_engraver"
\consists "Volta_engraver"
\consists "Separating_line_group_engraver"
\consists "Dot_column_engraver"
\consists "Staff_collecting_engraver"
\consists "Ottava_spanner_engraver"
\consists "Clef_engraver"
\consists "Key_engraver"
\consists "Time_signature_engraver"
\consists "Ledger_line_engraver"
\consists "Staff_symbol_engraver"
\consists "Collision_engraver"
\consists "Rest_collision_engraver"
\consists "Accidental_engraver"
\consists "Piano_pedal_engraver"
\consists "Piano_pedal_align_engraver"
\consists "Instrument_name_engraver"
\consists "String_number_engraver"
\consists "Axis_group_engraver"
\consists "Figured_bass_engraver"
\consists "Figured_bass_position_engraver"
\consists "Script_row_engraver"
localKeySignature = #'()
createSpacing = ##t
ignoreFiguredBassRest = ##t
instrumentName = #'()
shortInstrumentName = #'()
\defaultchild "Voice"
\accepts "Voice"
\accepts "CueVoice"
\override NoteHead #'color = #red
\override Stem #'color = #red
}
\context {
\type "Engraver_group"
\name "BlueStaff"
\consists "Output_property_engraver"
\consists "Bar_engraver"
\consists "Font_size_engraver"
\consists "Volta_engraver"
\consists "Separating_line_group_engraver"
\consists "Dot_column_engraver"
\consists "Staff_collecting_engraver"
\consists "Ottava_spanner_engraver"
\consists "Clef_engraver"
\consists "Key_engraver"
\consists "Time_signature_engraver"
\consists "Ledger_line_engraver"
\consists "Staff_symbol_engraver"
\consists "Collision_engraver"
\consists "Rest_collision_engraver"
\consists "Accidental_engraver"
\consists "Piano_pedal_engraver"
\consists "Piano_pedal_align_engraver"
\consists "Instrument_name_engraver"
\consists "String_number_engraver"
\consists "Axis_group_engraver"
\consists "Figured_bass_engraver"
\consists "Figured_bass_position_engraver"
\consists "Script_row_engraver"
localKeySignature = #'()
createSpacing = ##t
ignoreFiguredBassRest = ##t
instrumentName = #'()
shortInstrumentName = #'()
\defaultchild "Voice"
\accepts "Voice"
\accepts "CueVoice"
\override NoteHead #'color = #blue
\override Stem #'color = #blue
}
\context {
\Score
\accepts RedStaff
\accepts BlueStaff
}
}
\new Score <<
\new RedStaff {
c''4 c''4 c''4 c''4
}
\new BlueStaff {
c'4 c'4
Re: Tip: defining new contexts ... starting from existing contexts
2007/7/21, Trevor Bača <[EMAIL PROTECTED]>: The following is a short write-up on how to define new contexts starting from existing contexts. The tip augments 9.2.7 "Defining new contexts" which explains how to define new contexts starting from scratch. Looks great (I've often been looking for such a tip in the past). I'll make a patch soon. Thanks, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Need help with this simple lyric
how do you do this [ UTF-8 encoding ] in Jedit. "utilities" > "Global Options "> "general" Choose UTF-8 in "Default character encoding" Gilles ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Need help with this simple lyric
Gilles, so I have the character encoding as UTF-8. How do I insert a special character like U+2720 (maltese cross) in Jedit? Gilles THIBAULT wrote: > > >> how do you do this [ UTF-8 encoding ] in Jedit. > > > "utilities" > "Global Options "> "general" > > Choose UTF-8 in "Default character encoding" > > Gilles > > > > > ___ > 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/Need-help-with-this-simple-lyric-tf4104956.html#a11728370 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: Need help with this simple lyric
Quoting peterwinson <[EMAIL PROTECTED]>: Gilles, so I have the character encoding as UTF-8. How do I insert a special character like U+2720 (maltese cross) in Jedit? Exactly the same way as you do in any other program. Either copy/paste from some other document or use the "Character Palette" or "Character Set" program on your computer (see http://lists.gnu.org/archive/html/lilypond-user/2007-07/msg00451.html for details regarding Windows or http://lists.gnu.org/archive/html/lilypond-user/2007-07/msg00469.html for Mac. There's also a similar utility on most Linux distributions). /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
