>
> I got inclusion of the original init file working with the following code.
> IMHO it feels like a very crude hack. Is there a scheme function that would
> include a LilyPond file in the current context?
>
> Code:
>
> $(ly:parser-include-string
> (format #f "\\include \"~a\""
>(string-appe
Hi Aura,
I haven't had a chance to look at your code. Your project sounds
interesting – I'll try to make some time.
The exporter writes output to stdout.
>
> I have a few questions/problems:
>
> 1) First of all, is this a good strategy at all or would there be a better
> way
> to make LilyPond ru
>
>
>1. get-outfile-name returns the base name, with no file extension. I
>need to retrieve the output format set by the command line options (
>--format).
>2. This doesn't handle MIDI properly. MIDI scores, even when in the
>same book, are output to different files, and the abo
These are questions I've had to consider as I work on Emacs
lilypond-ts-mode, and I suspect are relevant to lots of tooling projects.
Since output file names and locations are potentially set via arbitrary
Scheme code, it's not feasible to do this reliably without actually running
the LilyPond bin
>
> This looks very interesting, thanks! Could you provide a short video
> (i.e., a screen capturing session) that demonstrates the
> functionality? I guess we would all benefit from seeing this 'in
> action' :-)
>
Great idea! Here is a quick demo:
https://www.youtube.com/watch?v=IFtCpMpOM1o
Sa
Hi all,
One of the longstanding workflow limitations of LilyPond is the difficulty
of inserting or removing measures, stemming from an inability to navigate
"vertically" through a score's music input code (i.e. cycling through the
same rhythmic position in different parts). I've been working with
Hi Kieren,
As you may know, properties that formerly accepted moments have been
changed to accept numbers instead. Convert-ly handles this, but it looks
like you have some Scheme code that manipulates at least one such property,
and it is hitting an error when it tries to compare a simple number u
If you look at LilyPond's code for initializing Guile in main.cc, you'll
see that LilyPond by default turns off automatic compilation of Guile code,
I'm guessing for empirical performance reasons. If you set the environment
variable GUILE_AUTO_COMPILE=1, I wonder if the warning will go away because
>
> I think it is unfair to put this burden on us developers
> for the 2.25.xx series.
Fair enough. I was mainly thinking it could be worthwhile for the
developers' sake to reduce the number of email threads from users taken by
surprise when their code stops working. A fair amount of time seems t
>
> Isn't that the reason that the changes documentation is written in the
> first place...to warn users about upcoming changes? So an extra warning
> in the email would be redundant, and this warning would also fade into
> the background? (by the way, I don't think that comparatively a _lot_ of
>
I guess I should add that I can see one use case where the replacements
might be unwanted, and that is when a text font is used that specifically
contains nice looking accidentals, such as Nepomuk. That is a use case that
should be supported, but IMO it shouldn't take precedence over the behavior
w
>
> While it is rather innocuous in this particular case it might be
> extremely frustrating for beginners to find out why LilyPond does
> this.
>
I'm not sure I follow your thought process. What is it that you worry would
be confusing to beginners? Genuine question. Is it something about
accident
>
> Do you think this isn't prominently enough? If so, how could this be
> improved?
>
I think that as with many warnings, the fact that it's always there leads
to it fading into the background for many readers, particularly as they
learn from experience that for *most* code, *most* of the time,
>
> if you have reasonable ideas how such API changes could be
> communicated better I am sure people would love to hear them and if
> feasible
> incorporate them.
IMO one relatively simple change would be to add a note to the release
announcement email mentioning that users should expect to need
>
> Instead of the old interface use this deprecated new interface,
> instead of just: Use the same interface, but you will need to add a type
> conversion.
The deprecated properties aren't intended for end users to write in their
code. New human written code should use the non-deprecated names a
I don't want to speak for Dan, but I believe the objective is to get user
code moved over to actually using exact rationals rather than moments for
these properties, not just to allow the use of exact rationals in addition
to moments.
It's worth pointing out that there were extended discussions on
LilyPond has never guaranteed backward compatibility of its API between
versions, except for minor versions of the same stable release. It's
usually the case that between any given two versions only a small subset of
code requires changes, but you should always assume that when upgrading to
a new L
Here's what I have in my stylesheet:
\paper {
#(add-text-replacements!
`(("♭" . ,(markup #:fontsize -1 #:text-flat))
("♮" . ,(markup #:fontsize -1 #:text-natural))
("♯" . ,(markup #:fontsize -1 #:text-sharp))
))
}
The fontsize adjustment might be out of date. I saw there w
Why not add global text replacements substituting the accidental markups in
place of the Unicode characters? Personally I prefer to type and read
within my code the Unicode accidentals but I'd always want the output to
use Emmentaler.
On Mon, Feb 3, 2025, 1:36 AM Werner LEMBERG wrote:
>
> >> How
Probably what you want is \omit Clef or \override Clef.break-visibility = #
all-invisible, so that it doesn't take up space, not just that it's hidden.
I would expect removing the engraver to have surprising results, since even
if a clef isn't printed, Lilypond still needs to know how to assign pit
Why is convert-ly.py located inside your project directory? That is likely
the source of your issues. My recommendation is delete your Lilypond 2.24
installation and revert any manually moved or copied libraries or scripts,
then download Lilypond 2.24 again, extract it, and move the entire folder
a
I mean, \applyContext kind of does accept an optional "which context"
argument in that you can write \context Foo { \applyContext ... } to run
code in a context different than the current one. I'm not sure if it's
specifically used this way in official docs, but there is an example here
https://ext
Yes indeed! I've been casually following the development and it looks like
it was a lot of work to migrate the codebase to current library versions.
Many thanks to all involved!
Saul
On Fri, Jan 17, 2025, 6:13 PM Simon Albrecht wrote:
> Hi Federico, Knute and everyone,
>
> On 16.01.25 11:04, Fe
It's very difficult to troubleshoot without narrowing down the code causing
the error, but look for grobs where the typesetting depends on line
breaking, especially cross-staff grobs.
On Fri, Jan 10, 2025 at 1:04 PM Richard Shann
wrote:
> In a large file a programming error message is emitted:
>
Hm. This is *supposed* to be the situation where \override
DynamicText.X-align-on-main-noteheads = ##t (which is the default actually)
saves the day. And if the \sf is attached directly to the chord, it does.
But when it's in a different staff context, it doesn't do anything, since
DynamicText lack
Frederic,
Maybe have a look at autotranspose from OpenLilyLib:
https://github.com/openlilylib/oll-misc/tree/master/pitch. You may find it
more intuitive.
Saul
Saul
On Sat, Jan 4, 2025, 10:58 AM David Kastrup wrote:
> Frédéric writes:
>
> > I have some music written for instruments in ut. So
wrote:
> Am Di., 31. Dez. 2024 um 20:02 Uhr schrieb H. S. Teoh via LilyPond
> user discussion :
> >
> > On Tue, Dec 31, 2024 at 01:55:28PM -0500, Saul Tobin wrote:
> > >Did you run convert-ly from HEAD?
> >
> > I just tried it, the only differe
Did you run convert-ly from HEAD?
On Tue, Dec 31, 2024, 1:53 PM H. S. Teoh via LilyPond user discussion <
lilypond-user@gnu.org> wrote:
> Hi,
>
> I'm testing out the latest git HEAD version of lilypond with an
> orchestral score, and I'm getting this error:
>
> -
> Parsing...ERROR: In
Would it work to run in the global scope the same function that initializes
the units within output-def modules?
On Sun, Dec 29, 2024, 11:38 AM David Kastrup wrote:
> Timothy Lanfear writes:
>
> > On 29/12/2024 12:57, Richard Shann wrote:
> >> Is there a way of writing
> >>
> >> \override #'(li
I haven't had time to play with your code but I notice that you're
using grob::always-vertical-skylines-from-stencil. That really should only
be used for grobs that can calculate their stencil without knowing line
breaks. Instead use grob::unpure-vertical-skylines-from-stencil, which you
can find i
I mean should MMRs actually use centered-spanner-interface? MMRs are after
all spanners that are centered between spacing-pair. It looks to me like
the C++ code for MMRs does exactly the same offset calculation
as centered-spanner-interface::calc-x-offset, though not all in one place.
On Tue, Dec
I could be hallucinating but I think I remember seeing someone post an
attempt at an engraver that handles chromatically altered unisons. Might be
worth searching back.
On Sat, Dec 7, 2024 at 8:40 PM William Rehwinkel via LilyPond user
discussion wrote:
> Dear Knute,
>
> Here is the best that I
Variables can be rebound.
On Tue, Dec 3, 2024, 2:52 AM Raphael Mankin wrote:
>
>
> On 02/12/2024 18:00, Saul Tobin wrote:
> > Hi Raphael,
> >
> > Lilypond variables exist in the same namespace, with the exception that
> > output-def blocks like paper and la
Hi Raphael,
Lilypond variables exist in the same namespace, with the exception that
output-def blocks like paper and layout are Scheme modules. Lilypond
include just literally inserts the text if the included file.
Saul
On Sun, Dec 1, 2024, 3:16 PM Raphael Mankin wrote:
> What is the scope of
Why is your NullVoice inside a Devnull? The whole point of allowing Score
to explicitly accept NullVoice is to put NullVoice directly in your score
at the same level as your ChordNames. Anything you put inside Devnull will
disappear into a black hole.
On Sun, Nov 10, 2024 at 1:48 PM Walt North wr
First of all, I just want to say I love almost everything about this, and
especially I love the Hermann Hesse reference!
I am quite curious what you mean by saying you use Lilypond to write
poetry. Do you mean that you use Guile Scheme to generate the text and use
Lilypond to typeset it as top lev
Peter, it appears to me that you asked an identical question several months
ago and received an answer with detailed information on the license for all
the fonts included by default in Lilypond. Is there something different
about your question now from what you asked in August?
On Sun, Oct 20, 202
Not an answer to the question, but an observation: in my experience, these
messages tend to indicate calculations that are a significant performance
hit to the score compilation time. Do you notice whether the piece you are
working on with a lot of cross staff beaming is notably slower to compile
t
As far as I'm aware, one of the shortcomings of Lilypond's handling of text
is that it only does one pass to calculate the size of markups. If the size
of the actual text can vary dynamically, it won't be reflected in the
layout. This is an issue, for example, if the page header contains the
center
If it has to be a music expression transformation, the way I would approach
this would be:
1. Reverse the music expression
2. Use fold-some-music to simply drop every element until we hit a
rhythmic event that isn't a multimeasure rest
3. *cons* onto the head of the remaining expressio
Texinfo isn't too hard to figure out, so no worries about that part. It's
just a matter of time and energy to write it up. Until I'm properly settled
in my new place and have my home office set up here, about all I have the
bandwidth for is quick replies on the list. Hopefully it won't take too
muc
I just meant that it might not be obvious that the syntax given for
changing the value of pre-existing alist keys also works to add arbitrary
new keys to the alist. It also might not be obvious that in this case,
custom key-value pairs added to property-defaults.fonts will function
properly as text
One additional tip that isn't explicit in the documentation:
property-defaults.fonts is just an alist, so you can use the same syntax in
the \paper block to define custom font families in addition to the standard
'serif 'sans and 'typewriter.
On Tue, Oct 8, 2024 at 5:08 PM Federico Bruni wrote:
The easiest way to handle this is to continue one of the voices into the
unison section and use \oneVoice.
On Tue, Oct 8, 2024, 12:38 PM Cameron Hall wrote:
> I'm trying to add dynamics to a part that splits into two, then goes
> back into a unison section. The problem is that the crescendo star
It might be easier to get the output you want by modifying the spacing of
the VerticalAxisGroup created by the Lyrics context.
On Sat, Oct 5, 2024, 11:19 AM Knute Snortum wrote:
> On Sat, Oct 5, 2024 at 7:51 AM Walt North wrote:
>
>> For example I was hoping to change the system system spacing
It's almost certainly feasible to write a script to run within an editor
that would use Lilypond itself to parse the duration of the music
expression and insert, lengthen, or shorten material at a specified point
within it — given some rigid but typical assumptions about the structure of
the input
Hi David,
Unfortunately, this just is a significant workflow shortcoming of composing
in Lilypond. For me, it is outweighed by the workflow benefits of Lilypond,
the most important of which is that, since the files are all plain text, it
enables me to use Git to manage my composition projects.
Wh
Hi Cameron,
I'm sure others on this list may have differing opinions, but personally my
strong advice is to simply enter the music for each part verbatim in a
single variable, with one measure per line. Using variables and quotes for
themes played repeatedly or by many instruments seems like it wi
Score {
> \new Staff
> <<
> <<
> \new NullVoice = "verseA" { \break \verseLyricsMelody }
> \new Lyrics \lyricsto "verseA" { \verseOneLyrics }
> >>
> >>
> }
>
> \new Score {
> \new Staff
>
.)?
NullVoice is defined with both Staff and Voice as aliases. I would have
assumed this meant that it could be used anywhere that Staff could be used.
Saul
On Fri, Sep 20, 2024 at 10:25 PM Saul Tobin
wrote:
> The easiest way to get the staff not to appear would be to put NullVoice
> inside a
rics \lyricsto "verse" { \verseOneLyrics }
> >>
> <<
> \new NullVoice = "verseB" { \break \verseLyricsMelody }
> \new Lyrics \lyricsto "verseB" { \verseOneLyrics }
>
> >>
>
>
>
> }
>
>
>
> On 9/20/
My understanding is that Devnull is not intended for alignment of lyrics
because it does not have the necessary engraver to create the invisible
grobs used for alignment. It appears to me in your example that actually
the lyrics are just being spaced evenly without alignment to anything.
Nullvoice
You might find it more convenient to define the output PDF filename
directly within Lilypond. See:
https://lilypond.org/doc/v2.24/Documentation/notation/output-file-names or
for 2.25
https://lilypond.org/doc/v2.25/Documentation/notation/output-file-names.
On Sun, Sep 15, 2024 at 5:18 PM Stu McKenz
I believe this stems from using $ rather than #, since this will insert
literally c' and cause the apostrophe to be parsed twice. I'm away from my
computer right now so can't actually test the example.
Saul
On Fri, Sep 13, 2024, 10:58 AM Yoshiaki Onishi wrote:
> Dear LilyPond Community,
>
> In
ound and not worth the effort.
> On 9/2/2024 8:48 PM, Saul Tobin wrote:
>
> I believe that this should simply work, though I haven't tried it myself.
>
> Saul
>
> On Mon, Sep 2, 2024 at 6:31 PM Walt North wrote:
>
>> Is it possible to remove empty tabstaff lines similar to removing empty
>> staff lines using\RemoveAllEmptyStaves?
>>
>>
It might be possible, but I think it would require some fairly advanced
customization. The function \partCombine creates Voices that it uses, and
TabStaff uses TabVoices. Whether there would be issues beyond that, I'm not
sure.
Saul
On Mon, Sep 2, 2024 at 6:42 PM Walt North wrote:
> Is it possi
I believe that this should simply work, though I haven't tried it myself.
Saul
On Mon, Sep 2, 2024 at 6:31 PM Walt North wrote:
> Is it possible to remove empty tabstaff lines similar to removing empty
> staff lines using\RemoveAllEmptyStaves?
>
>
>
> I suppose it would make sense to have an additional main section in the
> Docs
> explaining how LilyPond (the software) works, as opposed to LilyPond (the
> description language).
>
> This could feature things like $, #, #@ and whatever, how the parser works,
> how translation and engravers wor
Just responding to one piece of this: the NullVoice context was created
specifically for the use case of rhythmically aligning lyrics to invisible
notes. Devnull, as you discovered, just sends musical events into a black
hole. It might be worth another attempt with your existing approach, but
using
Hi Jaime,
Text strings count as markups, so any property that accepts input in the
form \markup { ... } will also accept it in the form "...".
Saul
On Thu, Aug 22, 2024 at 8:56 PM Jaime wrote:
> There is a "Types of properties" table at
> https://lilypond.org/doc/v2.25/Documentation/learning/t
Try with G_ instead of _.
This change happened a while ago (
https://gitlab.com/lilypond/lilypond/-/commit/a9fef9dee1399c24505d2f74623c9d15bb306ff7)
but old code continued working with _ until a recent version. I'm not sure
exactly why.
In any case, seems like this still needs to be updated in th
Hello friends,
I’ve found that one of the more cumbersome tasks in Lilypond is engraving
chromatic music for concert harp. When entering markups manually for each
pedal change, it’s difficult to achieve clean and consistent formatting,
and very easy to make errors. I’d like to share my solution to
Jean, please don't apologize for the constraints on your time. You
contribute so much to the project and the community. Your efforts are
appreciated.
On Sat, Jul 8, 2023 at 8:11 PM Jean Abou Samra wrote:
> Le samedi 08 juillet 2023 à 17:44 +1000, Vaughan McAlley a écrit :
>
> When a staff-switch
Hooray! I can finally compile my whole symphony draft on Windows! Thanks
devs for all the work that went into this.
On Sat, Jun 24, 2023 at 6:42 AM Jonas Hahnfeld via LilyPond user discussion
wrote:
> We are happy to announce the release of LilyPond 2.25.6. This is termed
> a development release
A practical follow up question: what is currently the largest repertoire of
publicly available Lilypond scores? Ideally, something like the complete
Bach chorales or Mozart piano sonatas.
On Wed, Mar 29, 2023 at 3:43 PM Saul Tobin
wrote:
> I've seen some examples of other people succe
this button On the upper left corner. when i asked for clarification
>> instead of admitting it was mistaken it said it was white and next to
>> another button. Twice it doubled down before admitting it was wrong.
>>
>> On Wed, Mar 29, 2023, 6:44 PM Saul Tobin
>> wrot
I've seen some examples of other people succeeding in getting ChatGPT with
GPT4 to compose simple music in other text based music formats. I've had
limited success getting it to output Lilypond code. It is able to correctly
structure the code with a score block, nested contexts, and appropriately
n
Is your idea to have a second engraver at the Voice level to prepare the
events? You should be able to have an engraver listen to the event and
modify it before it's listened by the Staff level engraver, as long as they
are \consist'ed in the right order.
On Mon, Mar 20, 2023, 1:40 PM Valentin Pet
That really only addresses the full score, not the parts, since in the
parts multiple movements share the same bookpart.
On Sun, Mar 12, 2023 at 5:19 PM Jean Abou Samra wrote:
> Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit :
>
> For what it's worth my use case was
this has worked fine for me.
On Sun, Mar 12, 2023 at 4:45 PM Jean Abou Samra wrote:
> Le dimanche 12 mars 2023 à 16:34 -0700, Saul Tobin a écrit :
>
> A slightly nicer syntax to workaround this limitation is to use the
> function:
> parserDefine =
> #(define-void-f
A slightly nicer syntax to workaround this limitation is to use the
function:
parserDefine =
#(define-void-function (name val)(symbol? scheme?)
(ly:parser-define! name val))
Then instead of var = { ... } you can write \parserDefine var { ... }.
I believe this was posted on the list a few yea
Hard disagree on plain text emails.
I didn't really have a strong opinion re the whole discussion about message
boards vs. email, but IMO the world has moved on to rich text email with
embedded media. I think the reliance on plain text email as the standard
for this mailing list detracts significa
I concur on entering all music in concert pitch. You may find the
auto-transpose snippet from OpenLilyLib helpful (
https://github.com/openlilylib/oll-misc/tree/master/pitch), as you can
simply write "\transposition bf" instead of wrapping all transposed blocks
in "\transpose x y { }". This is part
https://lilypond.org/doc/v2.24/Documentation/notation/writing-parts#quoting-other-voices
may help with the second question.
On Tue, Feb 28, 2023 at 5:08 PM TJ Kolev wrote:
> Greetings,
>
> I've decided to notate a brass band piece from a paper copy into some
> digital format that would be easier
Surprised to see that the http versions of those pages are accessible.
Shouldn't they redirect to https?
On Sat, Feb 18, 2023 at 12:13 PM Jonas Hahnfeld via LilyPond user
discussion wrote:
> On Sat, 2023-02-18 at 14:43 -0500, Shane Brandes wrote:
> > That is great, but where can one find a list
Channel wrap around can also occur if you assign midi channels per Voice
and instantiate more than 16 Voice contexts, for example if you have used
\new Voice at the beginning of each polyphonic passage.
On Sat, Feb 18, 2023, 7:04 AM wrote:
> On 17 Feb 2023 at 19:11, Jean Abou Samra wrote:
>
> >
Many users have old projects on very old versions of Lilypond, and
sometimes you just want to make a small edit, not update your whole project
to use the new version. It's important for documentation to be available.
On Mon, Feb 13, 2023, 8:41 AM Kevin Cole wrote:
> On Mon, Feb 13, 2023 at 11:33
This seems more or less equivalent to religiously putting
\resetRelativeOctave at the beginning of every phrase IMO.
On Sat, Feb 11, 2023 at 2:15 PM Simon Albrecht
wrote:
> On 10/02/2023 19:22, Saul Tobin wrote:
> > What is the reasoning behind having smaller relative blocks?
>
&g
The downsides seem to me like they would be very specific to a given user's
workflow.
On Sat, Feb 11, 2023 at 6:53 AM Kieren MacMillan <
kie...@kierenmacmillan.info> wrote:
> Hi Saul,
>
> > What is the reasoning behind having smaller relative blocks? Generally I
> structure my variables as a sing
What is the reasoning behind having smaller relative blocks? Generally I
structure my variables as a single \relative block per variable and just
use \resetRelativeOctave at the beginning of every passage.
On Fri, Feb 10, 2023 at 3:09 AM Simon Albrecht
wrote:
> Hi Darren,
> On 10/02/2023 11:46,
ChoirStaff <<
\new Staff << \marks \A >>
>>
\new ChoirStaff <<
\new Staff << \marks \B >>
>>
>>
Maybe I'm missing a way to do this while keeping the mark engravers in the
ChoirStaff context.
Saul
On Thu, Feb 9, 2023 at 1:29
Hi Simon,
Is there a reason to have the marks in a child context rather than just a
simultaneous music variable?
Saul
On Wed, Feb 8, 2023 at 10:24 AM Simon Albrecht
wrote:
> Hello everyone,
>
> I am working on a large score with several ChoirStaves and want to have
> BarNumbers and Marks in th
Hi all,
Just want to let everyone know, auto-transpose in OpenLilyLib now has
automatically inserted key signatures.
https://github.com/openlilylib/oll-misc/tree/master/pitch/auto-transpose
Please let me know if you run into any bugs using it.
Saul
up on Google
search results for Lilypond questions, at least for me.
On Wed, Feb 1, 2023 at 2:12 AM Jean Abou Samra wrote:
> Saul,
>
>
> Le 1 févr. 2023 à 04:16, Saul Tobin a écrit :
>
> The fourth example engraver here:
>
> https://extending-lilypond.readthedocs.io
The fourth example engraver here:
https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example
Running this code in 2.24 crashes on initializing the engraver with In
procedure ly:spanner-set-bound!: Wrong type argument in position 3
(expecting Item): ().
I believe this may be a case where you need to use \applyOutput, as
documented here:
https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#tweaking-grobs-during-translation
.
On Tue, Jan 31, 2023 at 5:57 PM Ahanu Banerjee
wrote:
> I am trying to modify the color of the l
On Tue, Jan 31, 2023 at 1:32 PM Jean Abou Samra wrote:
> On 31/01/2023 22:07, Saul Tobin wrote:
> > I have a few questions:
> > 1. How to achieve horizontal alignment and avoid vertical overlap of
> RehearsalMarks and MetronomeMarks at the beginning of a system, or when
>
ot;foo"
s1
\textMark "foo"
s1
}
music = \relative c'' {
bf4 a c b
bf4 a c b
bf''4 a,, c b
bf4 a c b
}
\score {
<<
\new MarkLine \global
\new StaffGroup <<
\new Staff << \global \music >>
\new Staff
IMO deduplication wouldn't really be semantically contradictory, because
the goal of allowing multiple simultaneous marks is to allow for multiple
*different* marks at the same moment. And you could always have a context
property to switch deduplication on/off.
The scheme evaluation challenges see
Hi all,
I'm in the process of updating my scores from 2.18 to 2.24 (yes I skipped a
bunch of versions), and I'm trying to understand the intended use of the
new types of marks.
Take the following small example:
\version "2.24.0"
\language "english"
markGroup = \with {
\consists Mark_engraver
case.
On Thu, Jan 26, 2023 at 6:10 PM Andrew Bernard
wrote:
> What if you don't have any rests?
>
>
> Andrew
>
>
> On 27/01/2023 1:00 pm, Saul Tobin wrote:
> >
> > Attached is a snippet that keeps track of these instructions and
> > automatically prints
Hi all,
I have always felt one of the more annoying proofreading tasks for
instrumental music is ensuring that technique instructions such as mutes
are properly cancelled.
Attached is a snippet that keeps track of these instructions and
automatically prints reminder text after a set number of mea
ld seem to require the ability to
"listen ahead" or "listen behind" to all the events happening at the same
moment. Is that even possible?
On Thu, Jan 19, 2023 at 5:48 PM Saul Tobin
wrote:
> Hi all,
>
> I managed to add functionality to the auto-transpose engraver
Hi all,
I managed to add functionality to the auto-transpose engraver snippet from
OLL so that it prints key signatures at transposition changes. It also
doesn't do so if the transposition change is only octave transposition.
The one thing I'd like to fix is the behavior when an actual key change
Doesn't "Night Fantasies" by Elliott Carter use an extremely obscure
structural polyrhythm? Not an actual irrational meter but similar idea.
On Tue, Jan 17, 2023 at 4:47 PM H. S. Teoh via LilyPond user discussion <
lilypond-user@gnu.org> wrote:
> On Tue, Jan 17, 2023 at 07:08:41PM -0500, David Ze
ially
thought but I'm just as confused.
On Tue, Jan 17, 2023 at 1:15 PM Jean Abou Samra wrote:
> Le 17/01/2023 à 10:10, Saul Tobin a écrit :
> > What I can't figure out is why when my autoKeysigEngraver broadcasts a
> > KeyChangeEvent, it gets picked up by t
I've been tinkering with the auto-transpose engraver from OLL, trying to
automatically print key signatures if the transposition has been changed.
In the original code it looks like the plan was to have the engraver
broadcast a KeyChangeEvent, but when I tried that it ended up in an
infinite loop o
Lilypond ships with a text font as well as a music font. I agree that I
suspect that currently Lilypond's text font does not actually define these
Unicode music characters, so it falls back on the OS to find them. Why not
just add copies of Emmentaler glyphs to the Lilypond text fonts for
character
al in a piece of text came up in the future. You could
> definitely make the text using lilypond accidentals look right by
> changing the font size of either the text or the accidental, it's just a
> matter of the size and alignment.
>
> -William
>
> On 1/15/23 01:05, Saul Tob
Surprisingly, typing the Unicode characters for accidental symbols does not
produce the same font output as using the markup commands:
<<
\new Staff {
c'1^"B♭"
c'1^"C♯"
c'1^"D♮"
}
\new Staff {
c'1^\markup { B \flat }
c'1^\markup { C \sharp }
c'1^\markup { D \natural }
1 - 100 of 180 matches
Mail list logo
