t; wrote:
>>
>>> Dear community,
>>> while compiling a certain file after upgrading to version 2.24.4 I get
>>> strange two error messages:
>>> The first one is:
>>>
>>>> ~/partituren/vorlagen/rhythmen.ly:233:9: programming error: cyclic
;> Dear community,
>> while compiling a certain file after upgrading to version 2.24.4 I get
>> strange two error messages:
>> The first one is:
>>
>>> ~/partituren/vorlagen/rhythmen.ly:233:9: programming error: cyclic
>>> dependency: calculation-in-progres
On Thu, Mar 6, 2025 at 5:02 AM Stefan Thomas
wrote:
> Dear community,
> while compiling a certain file after upgrading to version 2.24.4 I get
> strange two error messages:
> The first one is:
>
>> ~/partituren/vorlagen/rhythmen.ly:233:9: programming error: cyclic
>>
Dear community,
while compiling a certain file after upgrading to version 2.24.4 I get
strange two error messages:
The first one is:
> ~/partituren/vorlagen/rhythmen.ly:233:9: programming error: cyclic
> dependency: calculation-in-progress encountered for Stem.direction
> rvp = {
>
One workaround you might try is to print your PDF as PDF.
I do not know if it works, but it is simple to try...
Maybe the new PDF output would stop displaying your strange decolorations
I have done that for another unrelated problem I had on PDF's...
Silvain
Le 14.11.24 à 17:46, Mats Bengts
On 2024-11-14 13:35, Mats-Olof Liljegren wrote:
Hello! I have a strange issue that’s a bit off-topic, perhaps. When I
render to PDF, everything looks fine on my computer and in printouts.
But when I import the PDF into ForScore on iPad, I get strange
discolorations. See the attached image
Liljegren <mailto:m...@e-pro.se>> wrote:
> >
> > Hello! I have a strange issue that’s a bit off-topic, perhaps. When I
> > render to PDF, everything looks fine on my computer and in printouts. But
> > when I import the PDF into ForScore on iPad, I get strange discol
lying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."
Today's Topics:
1. Strange pdf render (Mats-Olof Liljegren)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://li
On Thu, 14 Nov 2024 at 13:37, Mats-Olof Liljegren wrote:
>
> Hello! I have a strange issue that’s a bit off-topic, perhaps. When I
render to PDF, everything looks fine on my computer and in printouts. But
when I import the PDF into ForScore on iPad, I get strange discolorations.
See the at
At 13:35 14/11/2024 +0100, Mats-Olof Liljegren wrote:
But when I import the PDF into ForScore on iPad, I get strange
discolorations. See the attached image.
See
http://forscore.co/kb/why-are-there-blue-rectangles-on-certain-pages/ .
I trust this helps.
Brian Barker
On Thu, 10 Oct 2024 10:06:03 -0700
Knute Snortum wrote:
> On Thu, Oct 10, 2024 at 9:27 AM Lucas Cavalcanti
> wrote:
>
> > Put brackets before and after the "repeat unfold 3". Don't know what
> > causes this bug, but it still happens in version 2.25.19.
> >
> > %%
> > \fixed c'' {
> > \repeat
On Fri, 11 Oct 2024, Peter Chubb wrote:
> The syntax of repeat is:
>\repeat TYPE MUSIC ALTERNATIVES
> So when you have:
>\repeat volta 2 {
> \repeat unfold {}
> \alternative {
> }
>}
> The alternatives are attached to the unfolded repeat, and get unfolded.
That's the
>>>>> "Cameron" == Cameron Hall writes:
Cameron> I've run into a strange problem that I think may be a bug. In
Cameron> this MWE, I have a repeat with alternate endings. However,
Cameron> the "\repeat unfold 3 { c1 }" is causing the volta bra
On Thu, Oct 10, 2024 at 9:27 AM Lucas Cavalcanti
wrote:
> Put brackets before and after the "repeat unfold 3". Don't know what
> causes this bug, but it still happens in version 2.25.19.
>
> %%
> \fixed c'' {
> \repeat volta 2 {
> {\repeat unfold 3 { c1 }}
> \alternative { \volta 1 { d
de out. de 2024 às 13:21, Cameron Hall
escreveu:
> I've run into a strange problem that I think may be a bug. In this MWE,
> I have a repeat with alternate endings. However, the "\repeat unfold 3
> { c1 }" is causing the volta brackets to disappear for some reason.
I've run into a strange problem that I think may be a bug. In this MWE,
I have a repeat with alternate endings. However, the "\repeat unfold 3
{ c1 }" is causing the volta brackets to disappear for some reason. If
I instead write out "c1 c1 c1", it works as expected. If
> I mean… technically, it’s correct…
Thanks.
> but yuck.
:-)
> If I were customizing the name, I would probably have it say
> Em(addb4). At the very least it should say Emsusb4.
As chord names noob I have no opinion to that. I just wanted to
ensure that MR !2335 produces correct results, e
Hi Werner,
I mean… technically, it’s correct… but yuck.
If I were customizing the name, I would probably have it say Em(addb4).
At the very least it should say Emsusb4.
— Kieren
__
My work day may look different than your work day. Please do not feel
> I tried the following
>
> ```
> \version "2.25.16"
>
> chord = \chordmode { c4:6-^1 }
>
> <<
> \new ChordNames \chord
> \chordmode { \chord }
> >>
> ```
>
> and got the attached result. The displayed chord name looks weird
> to me, but I'm no expert for Jazz chords... Is it correct? If no
I tried the following
```
\version "2.25.16"
chord = \chordmode { c4:6-^1 }
<<
\new ChordNames \chord
\chordmode { \chord }
>>
```
and got the attached result. The displayed chord name looks weird to
me, but I'm no expert for Jazz chords... Is it correct? If not, how
should it be displ
Please consider this example.
```tex
\version "2.25.11"
music = {
c'1
\tempo "T-note" c'1
}
\markup { time-signature }
{
\override Score.MetronomeMark.break-align-symbols =
#'(time-signature)
\music
}
\markup { time-signature, key-signature }
{
\override Score.MetronomeMark.break
Thanks for the explanation! I was not aware of the previous behavior and
that was very confusing.
And I guess I was not expecting alternatives to work with /unfold/
either but that makes sense.
On 2023-09-26 23:53, David Kastrup wrote:
Stéphane SOPPERA writes:
I observed a strange behavior
Stéphane SOPPERA writes:
> I observed a strange behavior with a /repeat unfold/ inside a /repeat
> volta/ with /alternatives/. See the attached /bug_repeat__ok.ly/ for
> full source.
>
> Using Lilypond 2.24.1:
>
> \repeat volta 2 {
> %% Here we repeat th
Hi,
I observed a strange behavior with a /repeat unfold/ inside a /repeat
volta/ with /alternatives/. See the attached /bug_repeat__ok.ly/ for
full source.
Using Lilypond 2.24.1:
\repeat volta 2 {
%% Here we repeat three times the same music.
* \relative { c'4
Second time sending this, but this time via "Reply all" for the list.
Pardon the spam.
How's this?
\version "2.25.8"
\relative c'' {
\mergeDifferentlyHeadedOn
\once \omit Staff.TimeSignature
<<
{2}
\\
{<
\tweak duration-log #1
c e>8[ g' g, g']}
>>
}
On Mon, 25 Sept
Hi everyone!
as the code mentioned below, when i try to engraving, the root note of the
chord are not same as upper note. how to solve this problem?
the aim:
problem:
code:
\relative c'' {
\mergeDifferentlyHeadedOn
\time 4/8
<<
{2}
\\
{8 [g'8]}
>>
}
best regards!
pening, but if this happened to me,
> I'd be looking for an earlier tweak or override which hadn't been cancelled.
>
> Paul
>
>
> From: Jin Choi
> To:
> Sent: 15/08/2023 23:11
> Subject: strange detached beam issue
>
> I have a section of piano music where
Paul
From: Jin Choi
To:
Sent: 15/08/2023 23:11
Subject: strange detached beam issue
I have a section of piano music where two voices start in the treble clef and
subsequently move down into the bass clef. When the right hand moves down, the
beam stays in the treble clef unattac
Yes, I noted that the problem doesn’t occur in my snippet. I will try to add
things to it until I can get it to happen. In my full text, I have just had it
happen again, in a similar passage where both parts leave the upper stave.
Forcing a voice to “hold open” the staff again fixes it for me.
It should be noted that on 2.25.7 this doesn't happen on my machine, and
the beam renders correctly (after running convert-ly on your snippet, it
didn't change anything).
-William
On 8/15/23 18:11, Jin Choi wrote:
I have a section of piano music where two voices start in the treble clef and
I solved the issue, but still don’t understand why it happened.
Apparently, when both voices leave the top staff, the staff or some context or
something just goes away at that point, even though it’s in use later? I just
added a third parallel voice that sits in the top staff and s1*4 to hold it
I have a section of piano music where two voices start in the treble clef and
subsequently move down into the bass clef. When the right hand moves down, the
beam stays in the treble clef unattached to anything:
When I try to isolate this section, the problem does not occur. I am mystified
as
>
> Try
>
> \version "2.24.1"
>
> \new Staff {
> \relative c {
> \easyHeadsOn
> \override NoteHead.font-name = "Ubuntu"
> \override NoteHead.stem-attachment =
> #(lambda (grob)
> (if (eqv? UP (ly:grob-property (ly:grob-object grob 'stem)
> 'direction))
> '
nt, the stems are positioned in the
> middle.
> In 2.22 I used to solve this with "override NoteHead.stem-attachment", but now
> in 2.24 this makes it even more strange.
>
> For the example below I use the Ubuntu font as everyone has it, but my
> personal choice is &q
Head.stem-attachment", but
now in 2.24 this makes it even more strange.
For the example below I use the Ubuntu font as everyone has it, but my
personal choice is "Dephunked BRK"
I also get this warning: *none of note heads `noteheads.s' or `noteheads.d'
found*
Please help
On 30/01/2023 22:26, Immanuel Asmus wrote:
> Hello Jean,
>
> actually, I /did/ subscribe. I wonder why my subscription was unsuccessful. I
> just tried again.
It didn't work this time either. I approved your message again.
Did you receive the confirmation email after filling the subscription
for
Hello Jean,
actually, I /did/ subscribe. I wonder why my subscription was
unsuccessful. I just tried again.
I finally found the cause of this error: It seems I checked only the
paper variables of my main document and Wetterlied.ly, whereas I didn’t
llok carefully into the other tqo source fi
On Mon, Jan 30, 2023 at 9:34 AM Jean Abou Samra wrote:
> Hello Immanuel,
>
> Welcome to this list. For your information, I had to approve your message
> manually as a list administrator because you are not subscribed to the list
> yet. Please fix this by subscribing on
> https://lists.gnu.org/mai
Dear Immanuel,
Sorry, I’m having trouble finding what would be the problem from the
provided snippets. Could you please reduce the files to a minimum
working example that we can compile that reproduces the problem? This
might help find what is the problem. In my experience when this kind of
t
Hello Immanuel,
Welcome to this list. For your information, I had to approve your message
manually as a list administrator because you are not subscribed to the list
yet. Please fix this by subscribing on
https://lists.gnu.org/mailman/listinfo/lilypond-user (note that once
subscribed, you can
Dear community,
I’ve been using lilypond for a fair amount of time, and even though I
sometimes use non-standard notation, I’ve never had any problem finding
a solution. Until now.
It’s my first time typesetting a song cycle I wrote. I want (as what I
understand is recommended) to typeset ev
>> It was diagnosed as a bug in the font (!), not in LilyPond.
>
> Yes, I saw the issue. That's extraordinarily weird.
It's not.
> It is one of the fonts installed with Microsoft Office so maybe this
> should be reported to Microsoft.
Newer versions of this font have it fixed. For example, 'Ti
On Mon, 2 Jan 2023 at 16:11, Jean Abou Samra wrote:
> Le 02/01/2023 à 14:31, Jean Abou Samra a écrit :
> > Le 31/12/2022 à 18:23, Sven Axelsson a écrit :
> >> I sent the font file to you privately.
> >
> > Thanks, I opened
> >
> > https://gitlab.com/lilypond/lilypond/-/issues/6508
>
>
> It was di
Le 02/01/2023 à 14:31, Jean Abou Samra a écrit :
Le 31/12/2022 à 18:23, Sven Axelsson a écrit :
I sent the font file to you privately.
Thanks, I opened
https://gitlab.com/lilypond/lilypond/-/issues/6508
It was diagnosed as a bug in the font (!), not in LilyPond.
OpenPGP_signature
Descri
Le 31/12/2022 à 18:23, Sven Axelsson a écrit :
I sent the font file to you privately.
Thanks, I opened
https://gitlab.com/lilypond/lilypond/-/issues/6508
OpenPGP_signature
Description: OpenPGP digital signature
>
> > > I have just updated my sheet music archive to LilyPond 2.24.0.
> > It went
> > > well, but I am seeing a strange font encoding problem.
> > >
> > > I have installed LilyPond on a Mac M1 running MacOS 13.1 with
> > Ho
Le 31/12/2022 à 17:11, Sven Axelsson a écrit :
On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote:
Le 31/12/2022 à 14:56, Sven Axelsson a écrit :
> Hi list,
>
> I have just updated my sheet music archive to LilyPond 2.24.0.
It went
> well, but I am seei
On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote:
> Le 31/12/2022 à 14:56, Sven Axelsson a écrit :
> > Hi list,
> >
> > I have just updated my sheet music archive to LilyPond 2.24.0. It went
> > well, but I am seeing a strange font encoding problem.
> >
>
Le 31/12/2022 à 14:56, Sven Axelsson a écrit :
Hi list,
I have just updated my sheet music archive to LilyPond 2.24.0. It went
well, but I am seeing a strange font encoding problem.
I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew
which builds from source using Guile
Hi list,
I have just updated my sheet music archive to LilyPond 2.24.0. It went
well, but I am seeing a strange font encoding problem.
I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew
which builds from source using Guile 3.0.
Running this code
\version "2.24.0"
Moving things to the staff context fixed both issues. Thanks a lot!
--Galen
On Mon, Aug 29, 2022 at 5:10 PM Aaron Hill wrote:
> On 2022-08-29 4:03 pm, Galen Hazelwood wrote:
> > I don't see what other event it could be talking about. I don't know if
> > this is an actual problem, or my understa
On 2022-08-29 4:03 pm, Galen Hazelwood wrote:
I don't see what other event it could be talking about. I don't know if
this is an actual problem, or my understanding of lilypond isn't good
enough yet.
It is an unbreakable beam that is blocking things. Your \override for
Beam.breakable applies
> On 17 Nov 2021, at 13:42, Robert Schmaus wrote:
>
> Dear Ponderers,
>
> I was just about to quickly write down a sheet of music, nothing fancy at
> all, when all of a sudden I got an exception. This is the full ly code (and I
> can’t make it any shorter for the reasons explained below):
>
Quick Update: The exception did indeed disappear after entering some more
music. Header is also no problem anymore …
I just hope, it stays like this when I get to the end of the music …
> On 17. Nov 2021, at 13:37, Robert Schmaus wrote:
>
> Dear Ponderers,
>
> I was just about to quickly wr
This compiled fine for me on lilypond 2.23.3, except for the warning about the
empty ChordNames.
On lilypond 2.20 I got an error message similar to yours (without the filename
weirdness), but it compiled fine if I commented out the ChordNames line or
typed something into its music expression. I
Dear Ponderers,
I was just about to quickly write down a sheet of music, nothing fancy at all,
when all of a sudden I got an exception. This is the full ly code (and I can’t
make it any shorter for the reasons explained below):
\version "2.20.0"
\header {
title = "Sinfonia No. 2 C-Dur"
See melismaBusyProperties in
http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable
On 13/11/2021 13:54, Bernhard Kleine wrote:
Hi, I feel lost. The text should go to every note in the example.
However the brackets behave as slurs /t
I am showing a part of the completed score. The problem was not the
beaming but the text distribution in the original example.
AutobeamingOff was correct for the First line , the line with the
beamExceptions took care of the eigths and the corresponding text in the
second line.
Kind regards
Hello Bernhard,
I think you’re tackling the wrong problem. First of all you can use manual
beaming without \autoBeamOff. But then your manual beams appear to be only
nescessary because 3/4 time sets a so called beaming exception for eigth
notes, so instead of 8[ 8] 8[ 8] 8[ 8] you have 8[ 8 8 8
Add a line
\set melismaBusyProperties = #'()
to the global variable.
Thanks a lot
Bernhard
Am 13.11.2021 um 15:09 schrieb Phil Holmes:
See melismaBusyProperties in
http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable
On 13/11/
I found the solution: add a line
Am 13.11.2021 um 15:09 schrieb Phil Holmes:
See melismaBusyProperties in
http://lilypond.org/doc/v2.23/Documentation/notation/common-notation-for-vocal-music#multiple-notes-to-one-syllable
On 13/11/2021 13:54, Bernhard Kleine wrote:
Hi, I feel lost. The text
Bernhard Kleine writes:
> Hi, I feel lost. The text should go to every note in the
> example. However the brackets behave as slurs /ties. This is
> unexpected. Where is the error?
>
> Kind regards Bernhard
>
> \version "2.21.1"
> \language "deutsch"
> \header {
> title = "Im Haslachtal"
> tag
Hi, I feel lost. The text should go to every note in the example.
However the brackets behave as slurs /ties. This is unexpected. Where is
the error?
Kind regards Bernhard
\version "2.21.1"
\language "deutsch"
\header {
title = "Im Haslachtal"
tagline = "Satz: Bernhard Kleine 2021"
}
\pape
On Wed, Nov 3, 2021 at 11:03 AM Paolo Prete wrote:
>
> Instead of suppressing the warning, given that LilyPond adds an invisible
> "auxiliary" stem to the whole notes, for creating the tremolo beam,
> I think it should be better to explicitly set the stems on both notes,
> according to the beam'
"lower" \lower
>>
}
%%%
On Wed, Nov 3, 2021 at 3:48 PM Knute Snortum wrote:
> On Wed, Nov 3, 2021 at 5:44 AM Paolo Prete wrote:
> >
> > Hello,
> >
> > I'm experiencing strange beams on cross-staff tremolos on whole notes.
> > The beam in t
Thanks for your reply, but unfortunately the value of Beam.gap depends on
how long is the measure, then it requires to be set only after a definitive
score and with a trial and error procedure...
BTW, I wonder if these issues are reported as known bugs in the ML
On Wed, Nov 3, 2021 at 4:17 PM Masa
sitions is
needed.
Akikazu
On 2021/11/03 23:48, Knute Snortum wrote:
On Wed, Nov 3, 2021 at 5:44 AM Paolo Prete wrote:
Hello,
I'm experiencing strange beams on cross-staff tremolos on whole notes.
The beam in the below snippet: 1) is not placed at the middle of the two notes
and 2
On Wed, Nov 3, 2021 at 5:44 AM Paolo Prete wrote:
>
> Hello,
>
> I'm experiencing strange beams on cross-staff tremolos on whole notes.
> The beam in the below snippet: 1) is not placed at the middle of the two
> notes and 2) it is too close to the ledger lines.
>
>
Hello,
I'm experiencing strange beams on cross-staff tremolos on whole notes.
The beam in the below snippet: 1) is not placed at the middle of the two
notes and 2) it is too close to the ledger lines.
Is this expected?
Is there a way to fix 1) + 2) without \tweak(ing)?
than
in and best regards.
>>
>> Jun
>>
>> <20210727 for lilypond-user.zip>
>>
>>> 2021/07/27 0:22、Jean Abou Samra のメール:
>>>
>>> Le 26/07/2021 à 15:58, 田村淳 a écrit :
>>>> Hello!
>>>>
>>>> I’m about to finish on
st.
> “parenthesized_dynamics.ily” code is from LSR, I recall.
>
> Thanks again and best regards.
>
> Jun
>
> <20210727 for lilypond-user.zip>
>
>> 2021/07/27 0:22、Jean Abou Samra のメール:
>>
>> Le 26/07/2021 à 15:58, 田村淳 a écrit :
>>> H
and best regards.
Jun
<>
> 2021/07/27 0:22、Jean Abou Samra のメール:
>
> Le 26/07/2021 à 15:58, 田村淳 a écrit :
>> Hello!
>>
>> I’m about to finish one project but I’ve encountered a very strange problem.
>> I have no idea where to start looking into. And
Le 26/07/2021 à 15:58, 田村淳 a écrit :
Hello!
I’m about to finish one project but I’ve encountered a very strange problem. I
have no idea where to start looking into. And I don’t think I can produce a
tiny example easily.
This is the first 2 pages of 25-page harpsichord part:
[attachment 1
Ah, that explains it. Thank you very much, Aaron!
Am Sa., 13. März 2021 um 16:02 Uhr schrieb Aaron Hill <
lilyp...@hillvisions.com>:
> On 2021-03-13 6:11 am, Christian Masser wrote:
> > [...]
> > mySoloChordsA = \chords {
> > c1 f g c
> > }
> > [...]
>
> I think you want \chordmode, not \chords
On 2021-03-13 6:11 am, Christian Masser wrote:
[...]
mySoloChordsA = \chords {
c1 f g c
}
[...]
I think you want \chordmode, not \chords, when defining the variables.
\chords { ... } is shorthand for \new ChordNames \chordmode { ... } if I
recall.
-- Aaron Hill
Hey all!
Just had a curious case concerning chord names. Typesetting a small jazz
piece and - as always - wanted to keep my file tidy, so I put the chords
for the solo-section in a variable as they are the same for every solo. But
somehow Lilypond seems to make a difference, if one inserts the res
John,
This is a known issue.
To compensate place a spacer grace in each of the other voices/staves.
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of John Burt
Sent: Friday, July 24, 2020 11:31 AM
To: lilypond-user
Subject: Strange
, July 24, 2020 at 12:31 PM
To: lilypond-user
Subject: Strange behavior with grace notes
When the first notes of a piece are grace notes, if there are other voices, or
other staves in the piece, the grace note is set in a separate bar, and then
the time signature and key are printed again. I
When the first notes of a piece are grace notes, if there are other voices,
or other staves in the piece, the grace note is set in a separate bar, and
then the time signature and key are printed again. I notice the same thing
with appoggiatura and accacciatura. I tried to make this example as minim
"John Schlomann" writes:
> define-macro works perfectly for me, even though the Guile manual seems to
> somewhat disparage its use.
Well, it's not the modern Scheme way but at the current point of time
LilyPond works best with Guile 1.8.
--
David Kastrup
nd-User Mailing List'
> Subject: Re: Strange error from define-syntax
>
> "John Schlomann" writes:
>
> > Thank you, David, for your quick response. I'm not sure what you mean by
> > "stick to macros". I thought define-syntax was the way to define
"John Schlomann" writes:
> Thank you, David, for your quick response. I'm not sure what you mean by
> "stick to macros". I thought define-syntax was the way to define a macro.
> What am I missing?
define-macro and defmacro apparently.
--
David Kastrup
On 5/28/20, John Schlomann wrote:
> Thank you, David, for your quick response. I'm not sure what you mean by
> "stick to macros". I thought define-syntax was the way to define a macro.
> What am I missing?
I think David may have been referring to LilyPond macros; have a look
at that for example:
2020 11:54 AM
> To: John Schlomann
> Cc: 'Lilypond-User Mailing List'
> Subject: Re: Strange error from define-syntax
>
> "John Schlomann" writes:
>
> > Dear Ponders & Schemers,
> >
> >
> >
> > I wanted to try creating a simple
"John Schlomann" writes:
> Dear Ponders & Schemers,
>
>
>
> I wanted to try creating a simple Scheme macro. I've never done this before,
> so I may well be going about it all wrong, but the error I get doesn't make
> sense.
>
>
>
> Here is a minimal non-working example:
>
>
>
> \version "2.
Dear Ponders & Schemers,
I wanted to try creating a simple Scheme macro. I've never done this before,
so I may well be going about it all wrong, but the error I get doesn't make
sense.
Here is a minimal non-working example:
\version "2.20.0"
#(use-modules (ice-9 syncase))
On Fri 10 Apr 2020 at 09:58:57 (+0200), Michael Gerdau wrote:
> > When working with addlyrics it was outside the \new staff construct like
> > here:
> >
> > tenorVoicePart = \new Staff \with {
> > instrumentName = "Tenor"
> > midiInstrument = "choir aahs"
> > } { \clef "treble_8" \tenorVoice }
On Thu 09 Apr 2020 at 18:41:40 (+0200), Noeck wrote:
> Am 09.04.20 um 18:18 schrieb Bernhard Kleine:
> > This would be worth mentioning in the manual!
>
> glad it works. What exactly would you mention in the manual?
>
> 1) How to use the \lyricsto construct? It is explained here:
>
> https://lil
> When working with addlyrics it was outside the \new staff construct like
> here:
>
> tenorVoicePart = \new Staff \with {
> instrumentName = "Tenor"
> midiInstrument = "choir aahs"
> } { \clef "treble_8" \tenorVoice }
> \addlyrics { \verseVoice }
>
> Now, it is within
>
> Soprano = \new Sta
When working with addlyrics it was outside the \new staff construct like
here:
tenorVoicePart = \new Staff \with {
instrumentName = "Tenor"
midiInstrument = "choir aahs"
} { \clef "treble_8" \tenorVoice }
\addlyrics { \verseVoice }
Now, it is within
Soprano = \new Staff \with {
instrumentN
Am 09.04.20 um 18:18 schrieb Bernhard Kleine:
> This would be worth mentioning in the manual!
Hi Bernhard,
glad it works. What exactly would you mention in the manual?
1) How to use the \lyricsto construct? It is explained here:
https://lilypond.org/doc/v2.20/Documentation/notation/common-no
Am 09.04.2020 um 17:18 schrieb Noeck:
>
> Am 09.04.20 um 17:04 schrieb Bernhard Kleine:
>> \new Lyrics \lyricsto „SI“
> Did you copy that verbatim or use the correct "normal quotes":
>
> \new Lyrics \lyricsto "SI"
>
> Just to rule out that simple problem.
>
> Joram
This is what is there :
Sopran
Am 09.04.20 um 17:04 schrieb Bernhard Kleine:
> \new Lyrics \lyricsto „SI“
Did you copy that verbatim or use the correct "normal quotes":
\new Lyrics \lyricsto "SI"
Just to rule out that simple problem.
Joram
this results in an error: the output is in the appendix.
Preprocessing graphical objects...
programming error: No spring between column 0 and next one
continuing, cross fingers
programming error: No spring between column 0 and next one
continuing, cross fingers
programming error: didn't find
Replace \addlyrics... by \new Lyrics \lyricsto „SI“...
Kind regards,
Michael
Mobil gesendet
> Am 09.04.2020 um 15:03 schrieb Bernhard Kleine :
>
> I have the following extract from Mendelssohn Bartholdy. I noticed that
> the parentheses in measure seven were not respected and the text was
> w
I have the following extract from Mendelssohn Bartholdy. I noticed that
the parentheses in measure seven were not respected and the text was
wrongly applied. When eleminating the line " \new Voice = "SII" {
\voiceTwo \SopranoVoiceII }" the text was correct. Please can you
explain and propose a rem
On 2020-03-30 16:10, Eby Mani wrote:
Thank you Aaron.
Malte, can you explain why you have mentioned \partial 8*7 is not
needed ?.
Probably since Malte uses the latest stable version, 2.20, which handles
these things much better than what was done in version 2.18. Try it out
and you should
On 2020-03-28 7:57 am, Malte Meyn wrote:
You don’t need this \partial 8*7. In fact it’s better to omit it for
correct autobeaming and bar checks. (Your code gives a bar check
warning.)
Odd, there should not be any bar check failures.
But I did not have access to my local LilyPond installation,
Am 28.03.20 um 15:30 schrieb Aaron Hill:
Would something like this work?
\version "2.20.0"
{
\time 4/4
\partial 8*7 | b'2 4. \bar "||"
You don’t need this \partial 8*7. In fact it’s better to omit it for
correct autobeaming and bar checks. (Your code gives a bar check warning.
On 2020-03-28 6:27 am, Eby Mani wrote:
I'm trying to typeset some Victorian choral music with some strange
time changes that switch between. Attached samples.
e.g.
eg1, 4.5th beat of 4/4 time it goes to pickup bar (\partial 8) of 6/8
time.
eg2, On the 5th beat of 6/8 time it goes to picku
1 - 100 of 794 matches
Mail list logo
