Thank you Ben and Leonardo!
I tried Joshua Armenta's proposed fix. I don't think it actually changed
anything. I still got the same ghostscript error after I tried the
procedure.
% cd /usr/local/share/doc
myusername@myhostname % ls -al | grep ghost
lrwxr-xr-x 1 myusername admin54 Nov 11
> I wonder whether it is expected that this simple input
>
> ```
> { c' }
> \midi{}
> ```
>
> doesn't create a MIDI file.
Yes. Otherwise you could not do
```
\midi { global MIDI settings ... }
fooMusic = ...
\score { \fooMusic \layout { } }
\score { \unfoldRepeats \fooMusic \midi { } }
b
> I'm having the same problem.There's already a thread about this:
> [https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html](https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html)
> Joshua Armenta posted a solution, something to do with Ghostscript, but I
> coul
>> I wonder whether it is expected that this simple input
>>
>> ```
>> { c' }
>> \midi{}
>> ```
>>
>> doesn't create a MIDI file.
>
>
> Yes. [...]
Thanks. I'll add this information to the NR.
Werner
Hi List,
sigh … here we go again. I apologize in advance for my client, a hobbyist
composer who thinks entirely in terms of cutting and pasting, moving things
around manually, and not in terms of how to notate anything clearly. Here
goes:
He has a song for soprano, baritone, and piano. The song h
PS - you know what? I'm sorry: I'm making this guy's work much more
complicated than it needs to be. This is really just a song for single
voice and piano; I'll notate it that way and leave it to him to work out
with the performers who sings which verse in which language. Sorry for the
trouble!
A
I think this sounds like a use case for a long text preface explaining what is
to be performed in what order and why, just notating everything on a treble
clef and doing manual octavations in the midi file. Maybe writing a reminding
1S,2B: or such (not sure I got it completely right from your ex
Thanks. I'll add this information to the NR.
Right now, the NR says the following (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html). What do you think needs to be clarified?
To create a MIDI ou
> Thanks. I'll add this information to the NR.
>
>
> Right now, the NR says the following
> (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html).
> What
> do you think needs to be clarified?
>
> To create a MIDI output file from a LilyPond input file, insert
> a\mid
Kevin Cole wrote:
I would like to use F. Bb and Am as the "real" chords and append "(C)",
"(F)" and "(Em)" as text.
This may help:
https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00416.html
Cheers,
Robin
I have the following in my \paper block. I want to eliminate the page number
on page 1. I have 'print-first-page-number = ##f' but the oddHeaderMarkup is
overriding it. Is there a way around this? Some sort of conditional?
Thanks,
David
\paper {
print-page-number = ##t
first-page-num
Werner LEMBERG writes:
> +A @code{@bs{}midi} block outside of @code{@bs{}score} does
> +@emph{not} create a MIDI file.}
MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered inside of a \sco
On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote:
> We are happy to announce the release of LilyPond 2.25.10.
And here are the binaries with Guile 3.0, built using
https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and
https://gitlab.com/lilypond/lilypond/-/merge_requests/2170 :
htt
Hi David,
On Sun, Nov 12, 2023 at 7:18 AM bobr...@centrum.is
wrote:
> I have the following in my \paper block. I want to eliminate the page
> number on page 1. I have 'print-first-page-number = ##f' but the
> oddHeaderMarkup is overriding it. Is there a way around this? Some sort of
> conditi
> MIDI settings can be changed globally (or in a book or bookpart), but
> the generation of an actual MIDI file is only triggered when a \midi
> block is encountered inside of a \score .
Thanks for the idea and wording.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2171
Werner
Hello,
(Note: Lilypond v. 2.24.2, in Linux.)
I am setting a group of pieces; each piece is in its own score block. I
want each score to start on a new page, and the final page in each score to
have a ragged-last-bottom, so that the systems are evenly spaced - these
are duets, and I like no more
Hi Alasdair,
On Sun, Nov 12, 2023 at 8:47 AM Alasdair McAndrew wrote:
> How can I force each score with a book to have a last ragged bottom, and
> each score beginning on a new page?
>
Might try putting each score into a \bookpart section. When I put multiple
scores into a single PDF that's ho
Thanks, Michael - that looks like the perfect answer. Typical of me, I
seem to have explored every page in the documentation except for that one.
Thanks again,
Alasdair
On Mon, 13 Nov 2023, 1:04 am Michael Werner, wrote:
> Hi Alasdair,
>
> On Sun, Nov 12, 2023 at 8:47 AM Alasdair McAndrew
> w
Thanks Micheal!
The '\unless \on-first-page' was what I went with on the first try. It was the
magic sauce.
-David
- Original Message -
> From: "Michael Werner"
> To: "bobroff"
> Cc: "Lillypond Users Mailing List"
> Sent: Sunday, November 12, 2023 1:09:05 PM
> Subject: Re: pageNumbe
On 2023-11-12 14:31, Werner LEMBERG
wrote:
MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered inside of a \score .
Thanks fo
Hi all,
I managed to place a fermata above a barline, I even managed to place it
correctly at the end of the line, but now I would like to place a
fermata sign below the barline (and rotate it 180°) too (in the
bassvoice of a choir staff group) - simplified example:
\version "2.24.0"
\relati
Dear Johannes,
If you change "ufermata" to "dfermata" and insert "\tweak direction
#DOWN" before "\mark" that should get you what you want.
Thanks,
-William
\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility =
#end-of-line-visible \tweak direction
Am 12.11.2023 um 17:10 schrieb William Rehwinkel:
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility =
#end-of-line-visible \tweak direction #DOWN \mark \markup {
\musicglyph #"scripts.dfermata" } \bar "||" e2
}
thx William for the quick response, always an amazing
I see, thanks for the update.
I found a solution to this problem here:
https://www.reddit.com/r/lilypond/comments/vozo9z/comment/ieibg4j/ does
this do what you were hoping for?
-William
Pasted below in-case this link goes away...
\version "2.25.7"
\score {
\new PianoStaff
<<
Hi Johannes,
On Sun, Nov 12, 2023 at 11:01 AM Johannes Roeßler wrote:
> Hi all,
>
> I managed to place a fermata above a barline, I even managed to place it
> correctly at the end of the line, but now I would like to place a fermata
> sign below the barline (and rotate it 180°) too (in the bassv
ah, even more elegant - didn't find it during my search... thx, Michael!
Hi Johannes,
On Sun, Nov 12, 2023 at 11:01 AM Johannes Roeßler wrote:
Hi all,
I managed to place a fermata above a barline, I even managed to
place it correctly at the end of the line, but now I would like to
Hi Michael,
doesn't work well with a choirstaff though..
twoWayFermata = {
\once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
\once \set Staff.caesuraTypeTransform = ##f
\caesura ^\fermata _\fermata
}
music = {
f'1 \twoWayFermata
R1
f'2 \twoWayFermata f'2
R1
b'1 \tw
Hi Johannes,
On Sun, Nov 12, 2023 at 11:44 AM Johannes Roeßler wrote:
> Hi Michael,
>
> doesn't work well with a choirstaff though..
>
No, it doesn't, does it. I missed the part in your original post where you
mentioned the choir staff bit. With a GrandStaff the span bar counts as a
single bar
this works perfectly, Michael, saved it to my snippets :)
thx again!
J
upFermata = {
\once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
\once \set Staff.caesuraTypeTransform = ##f
\caesura ^\fermata
}
downFermata = {
\once \set Staff.caesuraType = #'((underlying-bar-line . "
Jonas Hahnfeld wrote:
On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote:
We are happy to announce the release of LilyPond 2.25.10.
And here are the binaries with Guile 3.0, built using
https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and
https://gitlab.com/lilypond/lilypond/-/m
On 2023-11-12 17:37, Michael Werner
wrote:
Hi Johannes,
On Sun, Nov 12, 2023 at
11:01 AM Johannes Roeßler
wrote:
Hi all,
> Le 12 nov. 2023 à 19:14, Robin Bannister a écrit :
>
> If I take the code of LSR1098 [1] , without the demo part,
> Guile3 errors the input-warning call:
>
> GNU LilyPond 2.25.10 (running Guile 3.0)
> Processing `1.ly'
> Parsing...
> 1.ly:38:2: error: Guile signaled an error for the express
On Sat, 11 Nov 2023 at 19:38, Jonas Hahnfeld via LilyPond user discussion <
lilypond-user@gnu.org> wrote:
> We are happy to announce the release of LilyPond 2.25.10. This is
> termed a development release, but these are usually reliable for
> testing new features and recent bug fixes. However, if
> Is there a way to quickly see at a glance the changes in a new version? I know
> there is https://lilypond.org/doc/v2.25/Documentation/changes/index and
> although the listing in categories surely has its upsides, I preferred the old
> method of just listing it all in reverse chronological order,
Thank you, Jean, that makes sense and will help.
all the best,
Abe
On Sun, Nov 12, 2023 at 12:53 AM Jean Abou Samra wrote:
> I'm having the same problem.There's already a thread about this:
> https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html
> Joshua Armenta posted a solu
> “_” needs to be replaced with “G_”. Already in Guile 2, but Guile 3 checks for
> it more eagerly.
Fixed in LSR.
signature.asc
Description: This is a digitally signed message part
On Sun, 12 Nov 2023 at 22:08, Jean Abou Samra wrote:
> Is there a way to quickly see at a glance the changes in a new version? I
> know there is https://lilypond.org/doc/v2.25/Documentation/changes/index and
> although the listing in categories surely has its upsides, I preferred the
> old method
This is my first time using quasi-mensural notation for modern notation
readers (going for medieval look, not historical accuracy).
If you haven't gagged at that, I'd like some help on a few items.
Here's how the original starts ... (IMSLP260656 p48)
InDulciJubilo1910
And this is my approxima
On Sun, Nov 12, 2023 at 6:01 AM Robin Bannister wrote:
> Kevin Cole wrote:
>
> > I would like to use F. Bb and Am as the "real" chords and append "(C)",
> > "(F)" and "(Em)" as text.
>
> This may help:
> https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00416.html
>
> Cheers,
> Robin
Th
I'm into this!
1) Not sure on this one- you need to override the notehead in a \note {2}
markup somehow since there's not a dedicated glyph for that.
2) I think that's as close as you get with Emmantaler. You can see the list
of clefs here:
https://lilypond.org/doc/v2.24/Documentation/notation/cle
Hi,
I thought I'd give the Emacs Lilypond mode a try-out. I like Emacs and have
used it a lot for coding and writing in LaTeX in my past career. (No editor
wars please, VIM is good too but I'm less familiar with it!)
I store my Includes file in a directory ~/Lilypond/includes but Lilypond
mode ca
On Mon, Nov 13, 2023 at 02:45:26PM +1100, Laurie Savage wrote:
>I store my Includes file in a directory ~/Lilypond/includes but
>Lilypond mode cannot locate them even if I specify a full file name e.g
>\include
>"/home/Laurie/Lilypond/includes/jazzchords.ily"
>I set this in my ~
42 matches
Mail list logo