Re: Handbell mallets
On 2018-12-14 10:46 pm, Aaron Hill wrote:
Creating a custom articulations is probably the best option, however
you can also easily redefine the stencil for an existing one:
\version "2.19.82"
% handbell mallet
hbm = \tweak stencil #(lambda (grob)
(grob-interpret-markup grob #{ \markup \combine
\raise #1 \musicglyph #"scripts.stopped"
\musicglyph #"scripts.staccato"
#})) \stopped
{ f'8-+-. [ f''-+-. ] f'\hbm [ f''\hbm ] }
It's been too long since I played bells, so I don't remember the
conventions anymore. But if it is desired that the mallet symbol be
inverted when it appears below a note, here is a modification to the
code above that will take into account direction:
\version "2.19.82"
% handbell mallet
hbm = \tweak stencil #(lambda (grob)
(let ((dir (ly:grob-property grob 'direction)))
(grob-interpret-markup grob #{ \markup \combine
\raise #dir \musicglyph #"scripts.stopped"
\musicglyph #"scripts.staccato"
#}))) \stopped
{ f'8-+-. [ f''-+-. ] f'\hbm [ f''\hbm ] b'4^\hbm b'_\hbm }
-- Aaron Hill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Handbell mallets
On 2018-12-14 9:58 pm, Rick Kimpel wrote:
All,
In handbell music, there is an articulation for playing the bell with
a mallet while it is on the table. It looks like a "stopped" symbol
near the note head, with a "staccato" articulation just beyond that. I
can get reasonable results for notes near the top and bottom of the
staff, but when I have something like
{f8'-+-.[ f''-+-.]}
one of the two will always look bad. Ideally, the + will be in the
staff near the note head. Any ideas on how to achieve this without
tweaking each articulation? I have half a mind to just use staccato
and a note in the score.
https://www.handbellworld.com/images/HandbellNotation/MalletWithHandbellOnTable.jpg
Creating a custom articulations is probably the best option, however you
can also easily redefine the stencil for an existing one:
\version "2.19.82"
% handbell mallet
hbm = \tweak stencil #(lambda (grob)
(grob-interpret-markup grob #{ \markup \combine
\raise #1 \musicglyph #"scripts.stopped"
\musicglyph #"scripts.staccato"
#})) \stopped
{ f'8-+-. [ f''-+-. ] f'\hbm [ f''\hbm ] }
-- Aaron Hill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Handbell mallets
All,
In handbell music, there is an articulation for playing the bell with a mallet
while it is on the table. It looks like a "stopped" symbol near the note head,
with a "staccato" articulation just beyond that. I can get reasonable results
for notes near the top and bottom of the staff, but when I have something like
{f8'-+-.[ f''-+-.]}
one of the two will always look bad. Ideally, the + will be in the staff near
the note head. Any ideas on how to achieve this without tweaking each
articulation? I have half a mind to just use staccato and a note in the score.
https://www.handbellworld.com/images/HandbellNotation/MalletWithHandbellOnTable.jpg
Thanks,
Rick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Why is spacing wrong before command?
Hi Reggie, Reggie wrote > Why > are the first 3 measures adjusted when the newspacing comes after? The \newSpacingSection command only ensures that there are two separate sections which can have their own spacing. If you want, you can independently tweak them with overrides. The second section from the example mainly consists of 16th notes and therefore has a wider spacing. In the first section, the amount of 16th notes in the whole section is very small, so spacing is narrower because there are mainly 8th notes. So the overall effect is that \newSpacingSection prevents the first section being widened because of the 16ths in the last bar. Cheers, Klaus -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Harm,
> Any idea how to tackle:
> (1) ligatures
> \lyricmode { f -- i }
Can you give me a real world situation — in a "regular" score (i.e., with
notes) — in which you would want both a ligature *and* chords on both elements
of the ligature? I can’t comprehend what that would look like…
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Johan, > Libre/Open Office has a nifty plugin called ChordTransposer that makes it > possible to type in chords easily and obtain the right alignment for the > chords (and, as the name suggests, you get transpositions too). Nice! I’ll have to look into that for inspiration. > It works by attaching individual frames to the text to put the chords in. > Change the text and the chords shift accordingly. Clever! But obviously that isn’t how I’ll want (need) to make it work in Lilypond. > And it can convert from and to ChordPro. That would be a great feature for my LilyChordPro framework. Thanks! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
On Fri, 14 Dec 2018 11:27:13 -0500, Kieren MacMillan wrote: > And yet many, many people I know use it (or LibreOffice). ;) Libre/Open Office has a nifty plugin called ChordTransposer that makes it possible to type in chords easily and obtain the right alignment for the chords (and, as the name suggests, you get transpositions too). It works by attaching individual frames to the text to put the chords in. Change the text and the chords shift accordingly. And it can convert from and to ChordPro. -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Johan, > Interesting to encounter MSWord as apparent trendsetter... It is about the > worst tool for producing lead sheets. And yet many, many people I know use it (or LibreOffice). ;) My point was simply that the "short syllables with [many and/or long] chords" isn’t a Lilypond-only problem. > The approach seen in many ChordPro tools, is to space the syllables so > [C#dim]a[Fm]li[G]ve will get you something similar to (monospace text > ahead): > >C#dim Fm G >a-li-ve Totally. I would imagine Lilypond can do that with [relative] ease, since it already does it with [relative] ease when notes are present. Thanks, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Why is spacing wrong before command?
Here is my code I do not understand why newspacing would have any effect on
previous notes and measures why not just what comes after? Like in the user
manual. Page here
http://lilypond.org/doc/v2.19/Documentation/notation/new-spacing-section Why
are the first 3 measures adjusted when the newspacing comes after?
\relative c'
{
\time 2/4
c4 c8 c
c8 c c4 c16[ c c8] c4
\newSpacingSection
\time 4/16
c16[ c c8]
}
\relative c'
{
\time 2/4
c4 c8 c
c8 c c4 c16[ c c8] c4
\time 4/16
c16[ c c8]
}
attach.png
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
On Fri, 14 Dec 2018 08:49:33 -0500, Kieren MacMillan wrote: > > (2) short syllables, both with chords > > This is an issue even in Microsoft Word, Interesting to encounter MSWord as apparent trendsetter... It is about the worst tool for producing lead sheets. The approach seen in many ChordPro tools, is to space the syllables so [C#dim]a[Fm]li[G]ve will get you something similar to (monospace text ahead): C#dim Fm G a-li-ve -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with accidentals.ly and Lilypond 2.19.82
Hi Thomas,
your analysis has been very good.
I have almost solved the issue.
I just don't know what's the glyph name for the SEMI-SHARP and SEMI-FLAT
In the following code, I should add the ones for SEMI-SHARP and SEMI-FLAT.
Do you know what's the name of the glyph? I already tried (e.g. SEMI-SHARP)
"accidentals.semi-sharp", "accidentals.semisharp" and "accidentals.sharp.semi".
They didn't work, but it might be a problem of refreshing.
Best
Luca
arrowGlyphs = #`(
(,DOUBLE-SHARP . "accidentals.doublesharp")
(,SHARP-RAISE . "accidentals.sharp.arrowup")
(,SHARP. "accidentals.sharp")
(,SHARP-LOWER . "accidentals.sharp.arrowdown")
(,NATURAL-RAISE . "accidentals.natural.arrowup")
( 0. "accidentals.natural")
(,NATURAL-LOWER . "accidentals.natural.arrowdown")
(,FLAT-RAISE . "accidentals.flat.arrowup")
(,FLAT . "accidentals.flat")
(,FLAT-LOWER . "accidentals.flat.arrowdown")
(,DOUBLE-FLAT . "accidentals.flatflat")
)
From: Thomas Morley
Sent: 13 December 2018 23:20
To: Luca Danieli
Cc: David Kastrup; lilypond-user
Subject: Re: Problem with accidentals.ly and Lilypond 2.19.82
Am Do., 13. Dez. 2018 um 23:11 Uhr schrieb Luca Danieli :
> What it did was to replace the line #(ly:parser-set-note-names parser
> pitchnames)
> with #(ly:parser-set-note-names pitchnames)
convert-ly, correctly applied, would have done it for you ;)
> So I have got the same problem of before. Some accidentals are replaced with
> a X. Don't know how to solve it.
Well, first I made an experiment.
I included your code and tried to compile the most simple:
{ ceseh1 }
With 2.18.2 and 2.19.82 (converted)
In both version I get:
warning: Could not find glyph-name for alteration -3/4
2.18.2 is done with this warning
2.19.82 additionally prints some dummy accidental
> Am I the only one to have this problem?
Likely, but I have a hard time imagening your file ever worked:
Obviously you took
http://lsr.di.unimi.it/LSR/Item?id=786
and changed it.
But while defining your pitchnames in 'arrowedPitchNames', you use
alterations like
(* FLAT 3/2)
(/ FLAT 2)
(/ SHARP 2)
(* SHARP 3/2)
There is no corresponding entry in 'arrowGlyphs' for those alterations, though.
Thus LilyPond-2.19.82 does not find any accidental-glyph to print,
warns you and (to make it more obvious) it prints the dummy instead.
Create additional entries in 'arrowGlyphs' for the alterations listed
above and it should work.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Spam] Re: Status and future of abc2ly
On Fri 14 Dec 2018 at 17:32:59 (+1100), Andrew Bernard wrote: > I was so disappointed with the complete mess the current abc2ly makes of > Irish tunes from the vast repository at thesession.org that I started > looking into this. The others mentioned that using abc2xml and then using > musixxml2ly supplied with lilypond is the way forward. I found this to be > logical, from the programming point of view of using a single intermediary > interface (MusicXML), and it works great, except for messed up header > blocks, which I just delete and hand edit. Those strings ought to be amenable to machine recoding as they're most likely UCS-2 or UTF-16. (Obviously bear in mind that you have to take into account the byte-ordering.) Otherwise, from what you have printed, you could write an editing script to detect the string "^@ and then delete every other character until you reach ^@" (or are about to delete a space) and treat that extra ^@ following the space. Post-processing with a script would save a lot of handiwork. Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Harm,
> I don't have a clue how to deal with those issues, but I'd love to be
> proofed wrong.
>
> Any idea how to tackle:
>
> (1) ligatures
> \lyricmode { f -- i }
This is a fringe case in my world, so I’m happy to cross that bridge when (if?)
all other problems are solved.
> (2) short syllables, both with chords
This is an issue even in Microsoft Word, so we’ll have to come up with whatever
solution one would have come up with in Microsoft Word (e.g., shifting the
chord names).
Right now, I’m just trying to get a simple example working perfectly. =)
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Multiple tempos at the same time and midi playback?
Sorry - email got cut! Thanks DJF for your detailed example... I really appreciate it. Yes I am very new to LilyPond and still reading the latter parts of the user manuals. But from what you say, it seems like at least visually LilyPond can accomplish a score with different metronome marks for each instrument - and that is a great starting point for me! By the way, what GUI would you suggest me to use where I can type in the sourcecode and listen to playback without compiling a midi file each time? For the simultaneous midi playback of different metronomes, if (whichever) GUI you suggest to me is an open source progect, then I could try with the help of an experienced programmer to code an option for simultaneous tempi playback. It's been three years since I wrote my last piece for orchestra (using Sibelius) which is no longer accessible for the blind. And out of frustration from not being able to compose since, I started developing a new accessible notation software that did support simultaneous tempi playback. Unfortunately just when things were getting hot my programmer walked out on me. So that's how I thankfully discovered LilyPond which might be a solution for me. But at least from that experience I know that (some way or another) simultaneous playback of different tempi can be possible. Thank you very much again people, and any other suggestion/ tip is super appreciated! Best day, Yakir On 12/14/18, Yakir Arbib wrote: > Hi All, > > Thank you very much for your help and suggestions! > > On 12/14/18, Carl Sorensen wrote: >> >> >> On 12/13/18, 5:33 AM, "Yakir Arbib" wrote: >> >> Hi All, >> >> >> My name is Yakir and I'm a pianist / composer based in Paris. >> >> I am very new to LilyPond, so please pardon me if my question is >> annoying or redundant. >> >> I write modern classical music in which each instrument has its' own >> separate tempo. My question is, do you think it's possible to write >> something like that in LilyPond using separate tempo commands for >> each >> staff? >> >> I'm pretty sure you will not be able to accomplish this easily in >> LilyPond. >> It is probably possible by using scaled durations. >> >> Lilypond's basic timing is done in beats. Beats are grouped into >> measures. >> The timing is not done in seconds, or minutes. >> >> So if you want to have one staff at 4/4 and a tempo of 60, with another >> staff at 4/4 and a tempo of 120, you'll probably need to scale the >> durations >> of all the notes in the 120 staff by two, and probably fake the time >> signature (that is, set the time signature to say, 4/2 but display it as >> 4/4). And when you do that, you'll need to reset the beaming rules. >> >> So I think it's doable, but not easily. >> >> HTH, >> >> Carl >> >> >> > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Multiple tempos at the same time and midi playback?
Hi All, Thank you very much for your help and suggestions! On 12/14/18, Carl Sorensen wrote: > > > On 12/13/18, 5:33 AM, "Yakir Arbib" wrote: > > Hi All, > > > My name is Yakir and I'm a pianist / composer based in Paris. > > I am very new to LilyPond, so please pardon me if my question is > annoying or redundant. > > I write modern classical music in which each instrument has its' own > separate tempo. My question is, do you think it's possible to write > something like that in LilyPond using separate tempo commands for each > staff? > > I'm pretty sure you will not be able to accomplish this easily in LilyPond. > It is probably possible by using scaled durations. > > Lilypond's basic timing is done in beats. Beats are grouped into measures. > The timing is not done in seconds, or minutes. > > So if you want to have one staff at 4/4 and a tempo of 60, with another > staff at 4/4 and a tempo of 120, you'll probably need to scale the durations > of all the notes in the 120 staff by two, and probably fake the time > signature (that is, set the time signature to say, 4/2 but display it as > 4/4). And when you do that, you'll need to reset the beaming rules. > > So I think it's doable, but not easily. > > HTH, > > Carl > > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Am Fr., 14. Dez. 2018 um 04:09 Uhr schrieb Kieren MacMillan
:
>
> Hello all,
>
> I’m trying to develop a Lilypond lyrics+chords [only] framework, and am
> trying to understand the "cleanest" possible starting point.
>
> The final goal: Given a set of lyrics (either with “inline” durations, or
> durations contained in a melody variable) and a set of chords (with
> durations), Lilypond should automatically output a lyric+chord sheet similar
> to what can be seen in the attached screenshot.
Hi Kieren,
here:
https://lists.gnu.org/archive/html/lilypond-user/2018-12/msg00147.html
I expressed my doubts it will ever work.
I don't have a clue how to deal with those issues, but I'd love to be
proofed wrong.
Any idea how to tackle:
(1) ligatures
\lyricmode { f -- i }
(2) short syllables, both with chords
<<
\new ChordNames \chordmode { c:7 g:13 }
\new Lyrics \lyricmode { I -- o }
>>
?
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
