Re: aligning melisma and non-melisma lyrics across staves in the same system
2015-11-28 23:54 GMT+01:00 Kieren MacMillan : > If this snippet achieves "production-ready” status, I'll try to reply more detailed, as soon as I find the time. Pretty busy with non-LilyPond tasks this weekend... Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: aligning melisma and non-melisma lyrics across staves in the same system
Kieren MacMillan writes: >> Maybe affecting 'self-alignment-X is the wrong method at all, >> instead I could probably set 'X-offset. > > Perhaps someone else [with a more encyclopedic knowledge of the > back-end] can weigh in on that. I am (and always have been) a little > confused by the difference — and especially interaction — of these two > parameters. X-offset is the main property used for positioning a grob. Frequently it is set to a callback consulting self-alignment-X in order to arrive at some positioning. So changing self-alignment-X works as a tool for affecting those X-offset callbacks consulting it. If you override X-offset with a fixed value or a callback not looking at self-alignment-X, setting self-alignment-X ceases to have an effect. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Table of Contents: 2 problems
Thank you for the help I received with this problem.
I have finally had time to get back to the project, and have ended up with:
\paper {
inner-margin = 30\mm
outer-margin = 30\mm
print-page-number = ##f
tocTitleMarkup = \markup {
\vspace #10
\fontsize #6
\column {
\fill-line { \null "Contents" \null }
\vspace #2
}
}
tocItemMarkup = \markup \fontsize #5 \fill-line {
\override #'(line-width . 80)
\tocItemWithDotsMarkup
}
}
\markuplist \override #'(baseline-skip . 5) \table-of-contents
Lower down on the same page are a couple of paragraphs of text.
The table of contents is now much as I want it, although I am not keen
on the amount of space between the end of the row of dots and the
page-number itself - to me, it seems excessive. But this is a small
matter and I can live with it.
I dare say that the above markup could be more logically arranged: there
was a fair amount of trial and error that went on before I got a
successful result, even with the help from the list!
David
> I have not used a Table of Contents before, and I am having some
> difficulty in getting the result I want. I have 2 problems.
>
> 1) I would like to have a dotted line between the title and the page
> number in each line. But if I use
>
> tocItemMarkup = \tocItemWithDotsMarkup
>
> then there does not seem to be a way of formatting the text the way I
> want to (larger font etc.).
>
> As an alternative I have tried defining tocItemMarkup including
>
> \fill-with-pattern #1 #RIGHT .
>
> This results in a space between the dots
> and the page number; I get a similar result with
> \fill-with-pattern #1 #CENTER .
>
> 2) The table of contents appears at the top of a page which already has
> a couple of paragraphs of text on it. This page is defined as a
> separate \bookpart, and has its own \paper block setting a wider
> 'inner-margin' and 'outer-margin' than I use for the actual scores.
>
> I would like the table of contents to have wider margins still, but a
> second \paper block on the same page does not work, and changing
> 'indent' effectively only increases the right margin. I have tried
> experimenting with a \hspace before and after the contents of the line,
> e.g.
>
> tocItemMarkup = \markup \fontsize #5 \fill-line {
> \hspace #1 { \fill-with-pattern #1 #RIGHT .
> \fromproperty #'toc:text \fromproperty #'toc:page } \hspace #1 }
>
> but this just doesn't work. (Please forgive my feeble attempts at using
> markup, which I still find rather cryptic!)
>
> David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Introducing "LilyPond HTML Live Score"
Hello all, I've been developing a tool which is at a very early stage now, but I humbly guess you should like the idea. Check this very simple page and click the "play" button (or you can click any note or rest). http://www.mathieudemange.fr/lilypond-html-live-score-demo/ There's a public repository for the tool here : https://gitlab.com/sigmate/lilypond-html-live-score And the score used in the demo is a transcription I made which is a free score (CC-BY-SA) available on this repo : https://gitlab.com/sigmate/transcription-pools-vibes-solo Looking forward to hear your feedback! Cheers, Mathieu ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Introducing "LilyPond HTML Live Score"
This seems like it might be exceedingly cool, but I'm running into a
problem. When running make-live-score.sh I get this:
Drawing systems...
Layout output to `score-page-1.svg'...
Layout output to `score-page-2.svg'...
Layout output to `score-page-3.svg'...
Success: compilation successfully completed
Adding #score id to tag...
sed: can't read score.svg: No such file or directory
Injecting events timing data into score.svg...
Traceback (most recent call last):
File "injector.py", line 6, in
svg = ET.parse("score.svg")
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
source = open(source, "rb")
IOError: [Errno 2] No such file or directory: 'score.svg'
Injecting score.svg into index.html...
I'm really not sure what I should be doing. I changed the name of my
original Lilypond file to score.ly and the svg files are all correct
but the index.html file still plays your original demo.
On Sun, Nov 29, 2015 at 10:08 AM, Mathieu Demange
wrote:
> Hello all,
>
> I've been developing a tool which is at a very early stage now, but I humbly
> guess you should like the idea. Check this very simple page and click the
> "play" button (or you can click any note or rest).
>
> http://www.mathieudemange.fr/lilypond-html-live-score-demo/
>
> There's a public repository for the tool here :
>
> https://gitlab.com/sigmate/lilypond-html-live-score
>
> And the score used in the demo is a transcription I made which is a free
> score (CC-BY-SA) available on this repo :
>
> https://gitlab.com/sigmate/transcription-pools-vibes-solo
>
> Looking forward to hear your feedback!
>
> Cheers,
>
> Mathieu
>
>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Introducing "LilyPond HTML Live Score"
Ow! That's because I clearly didn't except anyone to try the script
that quick :D It's not fail-proof, yet, but here are some hints (before
all this gets managed automatically):
- make sure you adapt the paper format so that your score fits into one
single page (see the \paper block in the original score.ly file)
- adapt the Javascript code in the index.tpl file (lines 80, 81, 82) to
the audio files you want to use (if any)
Thanks for you interest! The tool is currently at an early stage of
development (more like a proof-of-concept actually). There's still quite
a lot of work to do :)
Yours,
Mathieu
Le 2015-11-29 20:10, David Bellows a écrit :
This seems like it might be exceedingly cool, but I'm running into a
problem. When running make-live-score.sh I get this:
Drawing systems...
Layout output to `score-page-1.svg'...
Layout output to `score-page-2.svg'...
Layout output to `score-page-3.svg'...
Success: compilation successfully completed
Adding #score id to tag...
sed: can't read score.svg: No such file or directory
Injecting events timing data into score.svg...
Traceback (most recent call last):
File "injector.py", line 6, in
svg = ET.parse("score.svg")
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in
parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in
parse
source = open(source, "rb")
IOError: [Errno 2] No such file or directory: 'score.svg'
Injecting score.svg into index.html...
I'm really not sure what I should be doing. I changed the name of my
original Lilypond file to score.ly and the svg files are all correct
but the index.html file still plays your original demo.
On Sun, Nov 29, 2015 at 10:08 AM, Mathieu Demange
wrote:
Hello all,
I've been developing a tool which is at a very early stage now, but I
humbly
guess you should like the idea. Check this very simple page and click
the
"play" button (or you can click any note or rest).
http://www.mathieudemange.fr/lilypond-html-live-score-demo/
There's a public repository for the tool here :
https://gitlab.com/sigmate/lilypond-html-live-score
And the score used in the demo is a transcription I made which is a
free
score (CC-BY-SA) available on this repo :
https://gitlab.com/sigmate/transcription-pools-vibes-solo
Looking forward to hear your feedback!
Cheers,
Mathieu
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Introducing "LilyPond HTML Live Score"
> Ow! That's because I clearly didn't except anyone to try the script that
> quick :D
Ha! I've been looking for something like this for a while. There's
another out there but I've had no luck getting it working and I think
it's been abandoned.
> - make sure you adapt the paper format so that your score fits into one
> single page (see the \paper block in the original score.ly file)
> - adapt the Javascript code in the index.tpl file (lines 80, 81, 82) to the
> audio files you want to use (if any)
Ok, I switched to a score that uses only one page.
I changed line 80 to reflect the name of the piece ("name").
I changed line 82 to point to the correct ogg file ("name.ogg").
I'm not sure what to do with line 81:
A) If I change it to "name.m4a" then everything seems to compile
and the score is shown in index.html but there's no sound or
animation.
B) If I comment out that line then I get the score and the music
but no animation. So close!
So I'm almost there!
And I would very much like to include this in a super huge project I'm
working once it reaches maturity and to that end I'll help out
wherever I can (though I'm not much of a programmer).
Thanks!
Dave
On Sun, Nov 29, 2015 at 12:03 PM, Mathieu Demange
wrote:
> Ow! That's because I clearly didn't except anyone to try the script that
> quick :D It's not fail-proof, yet, but here are some hints (before all this
> gets managed automatically):
>
> - make sure you adapt the paper format so that your score fits into one
> single page (see the \paper block in the original score.ly file)
> - adapt the Javascript code in the index.tpl file (lines 80, 81, 82) to the
> audio files you want to use (if any)
>
> Thanks for you interest! The tool is currently at an early stage of
> development (more like a proof-of-concept actually). There's still quite a
> lot of work to do :)
>
> Yours,
>
> Mathieu
>
>
> Le 2015-11-29 20:10, David Bellows a écrit :
>>
>> This seems like it might be exceedingly cool, but I'm running into a
>> problem. When running make-live-score.sh I get this:
>>
>> Drawing systems...
>> Layout output to `score-page-1.svg'...
>> Layout output to `score-page-2.svg'...
>> Layout output to `score-page-3.svg'...
>> Success: compilation successfully completed
>> Adding #score id to tag...
>> sed: can't read score.svg: No such file or directory
>> Injecting events timing data into score.svg...
>> Traceback (most recent call last):
>> File "injector.py", line 6, in
>> svg = ET.parse("score.svg")
>> File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
>> tree.parse(source, parser)
>> File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
>> source = open(source, "rb")
>> IOError: [Errno 2] No such file or directory: 'score.svg'
>> Injecting score.svg into index.html...
>>
>> I'm really not sure what I should be doing. I changed the name of my
>> original Lilypond file to score.ly and the svg files are all correct
>> but the index.html file still plays your original demo.
>>
>> On Sun, Nov 29, 2015 at 10:08 AM, Mathieu Demange
>> wrote:
>>>
>>> Hello all,
>>>
>>> I've been developing a tool which is at a very early stage now, but I
>>> humbly
>>> guess you should like the idea. Check this very simple page and click the
>>> "play" button (or you can click any note or rest).
>>>
>>> http://www.mathieudemange.fr/lilypond-html-live-score-demo/
>>>
>>> There's a public repository for the tool here :
>>>
>>> https://gitlab.com/sigmate/lilypond-html-live-score
>>>
>>> And the score used in the demo is a transcription I made which is a free
>>> score (CC-BY-SA) available on this repo :
>>>
>>> https://gitlab.com/sigmate/transcription-pools-vibes-solo
>>>
>>> Looking forward to hear your feedback!
>>>
>>> Cheers,
>>>
>>> Mathieu
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ChordNames: Brandt & Roemer exceptions
Hello all, Here's the first step towards a comprehensive Brandt & Roemer chord-naming include file. I’ve attached both the exceptions/markup include file (ChordNames-brandtroemer.ly) and a "test suite” score file (ChordNames-brandtroemer-test.ly). There are still lots of things I know how to implement and must do so (e.g., encapsulate redundant/shared/common markup situations into functions), and things I don’t yet know how to implement but must figure out soon (e.g., how to accomplish B&R’s “fraction” notation for polytonal chords). In the meantime, I would love to hear comments, suggestions, etc. on what I have so far. Thanks. Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ChordNames-brandtroemer.ly Description: Binary data ChordNames-brandtroemer-test.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Gounod - Le Rendez Vous
On 22/11/15 22:27, tisimst wrote: I think there was a misunderstanding about the voicing in Valse 2. The beamed groups should NOT be in \voiceOne. They should be in \oneVoice. That should clean up the space taken up by their respective slurs, too. Hi, Abraham. Fixed those issues now. I think now I understood it correctly. Please look into [1] best, Alberto [1] https://github.com/ambs/music/blob/master/Gounod/LeRendezVous/suite.pdf ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ChordNames: Brandt & Roemer exceptions
p.s. Thanks to Tim McNamara for the root-namer Scheme function! (Full documentation and credits will be added to the entire file before it "goes public”…) On Nov 29, 2015, at 4:32 PM, Kieren MacMillan wrote: > Hello all, > > Here's the first step towards a comprehensive Brandt & Roemer chord-naming > include file. I’ve attached both the exceptions/markup include file > (ChordNames-brandtroemer.ly) and a "test suite” score file > (ChordNames-brandtroemer-test.ly). > > There are still lots of things I know how to implement and must do so (e.g., > encapsulate redundant/shared/common markup situations into functions), and > things I don’t yet know how to implement but must figure out soon (e.g., how > to accomplish B&R’s “fraction” notation for polytonal chords). > > In the meantime, I would love to hear comments, suggestions, etc. on what I > have so far. > > 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: Gounod - Le Rendez Vous
Hell, Simon On 23/11/15 00:03, Simon Albrecht wrote: The last measure of the Introduction actually has only two quarters (the half note isn’t dotted), to be complemented by the immediately following upbeat for Valse 1. I need your help with this. Although I got it working for the upper voice, it is failing for the lower voice: I am using: R1*1/2 And getting: intro.ly:97:5: warning: barcheck failed at: 1/2 | R1*1/2 \bar "|." Of course the upper measure is gis2 and it doesn't complain there. It seems that you intentionally replaced -! by -. in Valse 1, however the original uses them distinctly and I’d stick with that. Thanks for the note. I didn't really notice (and in fact I am not sure what that means, musically speaking, but I will find that out) The hairpins in Valse 4 should stop at the third beat, I think. Not sure what you mean with that one. It would probably be better English to begin the Credits sentence with ‘Thanks to…’. Fixed! You’re welcome – and thanks for pointing to this delightful piece :-) No, thank you for your help. Working version at https://github.com/ambs/music/blob/master/Gounod/LeRendezVous/suite.pdf Alberto ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Gounod - Le Rendez Vous
Alberto, On Sunday, November 29, 2015, Alberto Simões-2 [via Lilypond] < ml-node+s1069038n184252...@n5.nabble.com> wrote: > > > On 22/11/15 22:27, tisimst wrote: > > I think there was a misunderstanding about the voicing in Valse 2. The > > beamed groups should NOT be in \voiceOne. They should be in \oneVoice. > > That should clean up the space taken up by their respective slurs, too. > > Hi, Abraham. > > Fixed those issues now. I think now I understood it correctly. > Please look into [1] > > best, > Alberto > > [1] > https://github.com/ambs/music/blob/master/Gounod/LeRendezVous/suite.pdf > It still looks like my comments didn't come across, or perhaps you haven't yet committed those changes, because I'm still seeing the beamed groups with the stems up where they don't (shouldn't?) be. I'll take a look at the file later and try to send you more specifics. Thanks, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Gounod-Le-Rendez-Vous-tp183419p184255.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rehearsal mark/tempo collision
On 27.11.2015 21:10, Craig Dabelstein wrote: Any idea how I can prevent the rehearsal marks from being pushed upwards by the tempo indication, and get the tempo marks to be moved a little to the right. Another way: \once\override MetronomeMark.self-alignment-X = #-0.2 or the like. Yours, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Gounod - Le Rendez Vous
On 29/11/15 21:49, tisimst wrote: Alberto, On Sunday, November 29, 2015, Alberto Simões-2 [via Lilypond] <[hidden email] > wrote: On 22/11/15 22:27, tisimst wrote: > I think there was a misunderstanding about the voicing in Valse 2. The > beamed groups should NOT be in \voiceOne. They should be in \oneVoice. > That should clean up the space taken up by their respective slurs, too. Hi, Abraham. Fixed those issues now. I think now I understood it correctly. Please look into [1] best, Alberto [1] https://github.com/ambs/music/blob/master/Gounod/LeRendezVous/suite.pdf It still looks like my comments didn't come across, or perhaps you haven't yet committed those changes, because I'm still seeing the beamed groups with the stems up where they don't (shouldn't?) be. I'll take a look at the file later and try to send you more specifics. Yes, I have missed the pull. Should be fixed now, together with some other fixes Simon suggested. Alberto ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is there a similar command to LaTeX's \vfill?
On 29.11.2015 03:07, Joshua Nichols wrote:
I'm looking to force a \markup{} after a score block to the bottom of
the page for a project I am in. In LaTeX, this looks like \vfill,
which forces the next bit of text/content to the bottom of the page.
Is there something like it in LilyPond?
No, unfortunately not.
I made the same request three years ago:
Re: Gounod - Le Rendez Vous
On 29.11.2015 22:45, Alberto Simões wrote: Hell, Simon On 23/11/15 00:03, Simon Albrecht wrote: The last measure of the Introduction actually has only two quarters (the half note isn’t dotted), to be complemented by the immediately following upbeat for Valse 1. I need your help with this. Although I got it working for the upper voice, it is failing for the lower voice: I am using: R1*1/2 And getting: intro.ly:97:5: warning: barcheck failed at: 1/2 | R1*1/2 \bar "|." Of course the upper measure is gis2 and it doesn't complain there. Full-bar rests automatically perform a barcheck at their beginning and at their close. The latter obviously fails here, because the rest doesn’t span an entire bar. So you should be using r2 here. It seems that you intentionally replaced -! by -. in Valse 1, however the original uses them distinctly and I’d stick with that. Thanks for the note. I didn't really notice (and in fact I am not sure what that means, musically speaking, but I will find that out) Describing the difference between these in performing is a difficult task, but they are usually used distinctively and so we should allow performers to make sense of this distinction instead of hiding it away – regardless of what it actually means. The hairpins in Valse 4 should stop at the third beat, I think. Not sure what you mean with that one. in a nutshell: s2\> s4\! instead of s2.\> s\! And I have yet another suggestion: It works as is, but LilyPond would have more freedom to make good linebreaks if you insert \bar "" at appropriate places in the introduction’s cadenza. Yours, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rehearsal mark/tempo collision
Thanks Lilyponders. These ideas are really helpful. Craig On Mon, 30 Nov 2015 at 07:57 Simon Albrecht wrote: > On 27.11.2015 21:10, Craig Dabelstein wrote: > > Any idea how I can prevent the rehearsal marks from being pushed > > upwards by the tempo indication, and get the tempo marks to be moved a > > little to the right. > > Another way: \once\override MetronomeMark.self-alignment-X = #-0.2 or > the like. > > Yours, Simon > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Introducing "LilyPond HTML Live Score"
2015-11-29 19:08 GMT+01:00 Mathieu Demange : > Hello all, > > I've been developing a tool which is at a very early stage now, but I humbly > guess you should like the idea. Check this very simple page and click the > "play" button (or you can click any note or rest). > > http://www.mathieudemange.fr/lilypond-html-live-score-demo/ > > There's a public repository for the tool here : > > https://gitlab.com/sigmate/lilypond-html-live-score > > And the score used in the demo is a transcription I made which is a free > score (CC-BY-SA) available on this repo : > > https://gitlab.com/sigmate/transcription-pools-vibes-solo > > Looking forward to hear your feedback! Very cool! I don’t quite have a use for it at the moment, but I very well might soon. Starred the GitLab project, so I keep an eye on it … -- Peter Crighton | Musician & Music Engraver based in Mainz, Germany http://www.petercrighton.de ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: grace notes MIDI playback
Hi all,
I found a workaround for my problem and I am sharing it here. If I define
these in the beginning of the score and use the articulate.ly script, the
grace notes will behave as I expect:
#(define ac:defaultGraceBackwardness 0)
#(define ac:defaultGraceFactor 1)
Example:
\include "articulate.ly"
\version "2.19.28"
grace on beat and no compression
#(define ac:defaultGraceBackwardness 0) % default 1, meaning it goes back in
time
#(define ac:defaultGraceFactor 1) % compression factor
A = \relative c'' {e2 \grace {dis32[ e, a' bes,]} ees,4 \grace {dis'32}
ees,4}
B = {\clef bass c,4 c, c, c,}
\markup {"score"}
\score {
<<
\new Staff \A
\new Staff \B
>>
\layout {}
}
\markup {"playback"}
\score {
<<
\new Staff \articulate \A
\new Staff \B
>>
\layout {}
\midi {}
}
Producing:
and: example.mid
Cheers,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/grace-notes-MIDI-playback-tp184215p184263.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ChordNames: Brandt & Roemer exceptions
Oh, don't give me credit for that! It was sent to me by another list member a few years back as the pop-chords.ly file. > On Nov 29, 2015, at 3:42 PM, Kieren MacMillan > wrote: > > p.s. Thanks to Tim McNamara for the root-namer Scheme function! > (Full documentation and credits will be added to the entire file before it > "goes public”…) > >> On Nov 29, 2015, at 4:32 PM, Kieren MacMillan >> wrote: >> >> Hello all, >> >> Here's the first step towards a comprehensive Brandt & Roemer chord-naming >> include file. I’ve attached both the exceptions/markup include file >> (ChordNames-brandtroemer.ly) and a "test suite” score file >> (ChordNames-brandtroemer-test.ly). >> >> There are still lots of things I know how to implement and must do so (e.g., >> encapsulate redundant/shared/common markup situations into functions), and >> things I don’t yet know how to implement but must figure out soon (e.g., how >> to accomplish B&R’s “fraction” notation for polytonal chords). >> >> In the meantime, I would love to hear comments, suggestions, etc. on what I >> have so far. >> >> 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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ChordNames: Brandt & Roemer exceptions
2015-11-30 0:04 GMT+01:00 Noeck : > Hi Kieren, > > as a guitar player, I am used to not having standards in chord notation > (the German note names confusion (H=B) being one of the constant issues > with that). So please forgive my ignorance when talking about consistent > systems of chord notation like Brandt-Roemer. > > I was interested in a direct comparison to the current style. That's why > I created the attachment from your testing code. > red = Lilypond's default style > black = your Brandt-Roemer style > green = differences I noticed (only once) > > My personal take is: nice and understandable. I like the sizes of > accidentals and the consistent font size for numbers. I am not used to > these diminished chords, the minor and the major 7 notation. > > Two questions: > 1. Why is Cm69 (ly) = C6/9 (BR)? Where is the "MI" gone? Is it kind of > implied? I don't see it. > > 2. (I almost don't dare to ask, but) in your code, could the "MI" for > minor be configurable such that the BR style can be used but with 'm' > for minor? (For ignorants who want to break with a standard.) > > Thanks for your work in any case! > > Cheers, > Joram Well, I really have no time atm, but is Joram's pdf really what Brandt&Roemer propose?? Looking at the chord no 5 and 6 of this pdf I'd read the symbol's as e-major with added lowered 6th and f-major with added sharpened 6th. -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ChordNames: Brandt & Roemer exceptions
Hi Harm, > is Joram's pdf really what Brandt&Roemer propose?? The black and green are, I believe, exactly what B&R propose. > Looking at the chord no 5 and 6 of this pdf I'd read the symbol's as > e-major with added lowered 6th and f-major with added sharpened 6th. Their system is hardly a standard. That being said, it has many attractive qualities — not the least of which is that it is far more consistent than any other I’ve ever come across. As to these particular examples… In the B&R system, all scale-degree alterations must be in parentheses; hence nobody familiar with their notation/system could possibly confuse F#6, i.e., an F# major triad with added [major] 6th degree, for F(#6), i.e., an F major triad with sharpened 6th scale degree. And that would be even before the glyph positioning, which further reduces possible ambiguity. I’m not suggesting anyone implement this system if they don’t want to. I’m simply asking for commentary on *my* Lilypond implementation of the system as defined by B&R. I’m hoping the example file, once it’s finished and properly vetted by the Pond, will form the basis of any number of chord name exception files (including, hopefully, one which is more standard than either B&R or Lilypond’s Ignatzek default). Cheers, 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: Is there a similar command to LaTeX's \vfill?
Hi Joshua (et al.),
Search the archives for put-mm.
I use it all the time for exactly the purpose you describe.
Hope that helps!
Kieren.
On Nov 29, 2015, at 5:02 PM, Simon Albrecht wrote:
> On 29.11.2015 03:07, Joshua Nichols wrote:
>> I'm looking to force a \markup{} after a score block to the bottom of the
>> page for a project I am in. In LaTeX, this looks like \vfill, which forces
>> the next bit of text/content to the bottom of the page. Is there something
>> like it in LilyPond?
>
> No, unfortunately not.
> I made the same request three years ago:
>
Re: ChordNames: Brandt & Roemer exceptions
Hi Joram, Thanks for the helpful response! > I was interested in a direct comparison to the current style. That's why > I created the attachment from your testing code. > red = Lilypond's default style > black = your Brandt-Roemer style > green = differences I noticed (only once) Very nice — thanks for doing that. > My personal take is: nice and understandable. I like the sizes of > accidentals and the consistent font size for numbers. Excellent. I would like to implement kerning, if possible. Otherwise, I felt like I had found good basic sizes, relations, and spacing — glad to hear you agree! > Two questions: > 1. Why is Cm69 (ly) = C6/9 (BR)? Where is the "MI" gone? Is it kind of > implied? I don't see it. ERROR! =) Thanks for catching that; I will fix it immediately. > 2. (I almost don't dare to ask, but) in your code, could the "MI" for > minor be configurable such that the BR style can be used but with 'm' > for minor? (For ignorants who want to break with a standard.) Once a complete B&R example is done, I will be seeing how many of the elements can be parameterized. Certainly, the minor indicator would be one (and one of the easier ones, at that). Stay tuned. > Thanks for your work in any case! My pleasure. Thanks for the feedback. Best, 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
