On Tue, Jan 31, 2023 at 9:49 PM Ahanu Banerjee
wrote:
> That's certainly an interesting approach. Reminds me of the old SCORE
> system. But unless I misunderstood your suggestion, it becomes rather
> inconvenient and inefficient for larger scores, particularly if changes
> have to be made to the
On Tue, Jan 31, 2023 at 9:41 PM Michael Werner wrote:
> ...
> \version "2.24.0"
> \language "english"
>
> music = { g8 g g g }
> upArticulation = { g8 g-\upbow g g }
> downArticulation = { g8 g-\upbow g g }
>
> <<
> \new Dynamics
> \upArticulation
> \new Staff
> \music
> \new Dynamics
> \downArti
I suppose there are different definitions for what a "bug" is. I said it
was not one because it is obviously intended behavior—I figured my use case
is a bit unusual so was not surprised by this. But if it can be treated as
a bug and additional functionality can be added in a future version, that
w
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): ().
On 01/02/2023 03:51, Ahanu Banerjee wrote:
> It's obviously not a bug. Jean, thanks for pointing out where the relevant
> instruction is.
>
> What would be the easiest way to modify this behavior for a single score?
It's a bit of a weird thing to do, but you could consider
\version "2.24.0"
On 01/02/2023 03:59, kie...@kierenmacmillan.info wrote:
> Hi all,
>
>> I would personally consider that a bug!
>> script-engraver.cc:
>>
>> void
>> Script_engraver::listen_articulation (Stream_event *ev)
>> {
>> /* Discard double articulations for part-combining. */
>> for (vsize i = 0; i < s
Hi all,
I would personally consider that a bug!
script-engraver.cc:
void
Script_engraver::listen_articulation (Stream_event *ev)
{
/* Discard double articulations for part-combining. */
for (vsize i = 0; i < scripts_.size (); i++)
if (scm_is_eq (get_property (scripts_[i].event_, "articulatio
It's obviously not a bug. Jean, thanks for pointing out where the relevant
instruction is.
What would be the easiest way to modify this behavior for a single score?
Thanks,
-Ahanu
On Tue, Jan 31, 2023, 21:37 Jean Abou Samra wrote:
> On 01/02/2023 03:34, kie...@kierenmacmillan.info wrote:
> > H
That's certainly an interesting approach. Reminds me of the old SCORE
system. But unless I misunderstood your suggestion, it becomes rather
inconvenient and inefficient for larger scores, particularly if changes
have to be made to the notes later down the line, i.e., having to modify
multiple sets
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
Hi Ahanu,
I would split things out into some variables, and put the articulations
into separate contexts. I find it makes things much easier to keep track
of. For example:
\version "2.24.0"
\language "english"
music = { g8 g g g }
upArticulation = { g8 g-\upbow g g }
downArticulation = { g8 g-\u
On Wed, Feb 01, 2023 at 03:37:47AM +0100, Jean Abou Samra wrote:
> On 01/02/2023 03:34, kie...@kierenmacmillan.info wrote:
> > Hi Ahanu,
> >
> >> g_\upbow ^\upbow g g % fails
> >
> > I would personally consider that a bug!
>
> script-engraver.cc:
>
> void
> Script_engraver::listen_articulation
On 01/02/2023 03:34, kie...@kierenmacmillan.info wrote:
> Hi Ahanu,
>
>> g_\upbow ^\upbow g g % fails
>
> I would personally consider that a bug!
script-engraver.cc:
void
Script_engraver::listen_articulation (Stream_event *ev)
{
/* Discard double articulations for part-combining. */
for (
Hi Ahanu,
g_\upbow ^\upbow g g % fails
I would personally consider that a bug!
As for a "solution", what about this?
<< g_\upbow \\ <>^\upbow >>
Not *that* much better than your hack… but maybe a little better?
Kieren.
I'm trying to put the same articulation both above and below one note. (My
document has one set of bowings above the staff and an alternate set below
the staff, and occasionally they both need the same marking.)
The workaround I currently have is creating a second voice, which is a bit
of a pain.
I am trying to modify the color of the ledger lines for a single note. My
understanding is that I need to use \stopStaff and \startStaff for this.
However, doing so causes the staff lines to be discontinuous. This rounds
the ends of the staff lines surrounding the point at which the staff is
stoppe
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
> musical objects push the
Fantastic! Thanks again.
On Tue, Jan 31, 2023 at 7:28 PM Jean Abou Samra wrote:
> On 01/02/2023 01:23, Ahanu Banerjee wrote:
> > Is it possible to have one of the arguments rely on a property of
> another argument?
> >
> > In my example, I want the default value for "parenColor" to be the same
>
On 01/02/2023 01:23, Ahanu Banerjee wrote:
> Is it possible to have one of the arguments rely on a property of another
> argument?
>
> In my example, I want the default value for "parenColor" to be the same as
> the color of the "parenItem":
>
> \version "2.24"
> \language "english"
> altPare
Is it possible to have one of the arguments rely on a property of another
argument?
In my example, I want the default value for "parenColor" to be the same as
the color of the "parenItem":
\version "2.24"
\language "english"
altParen = #(define-music-function
(parenColor parenSize parenItem)
Thanks! I had no idea that that resource existed.
Appreciate all your help.
-Ahanu
On Tue, Jan 31, 2023 at 7:08 PM Jean Abou Samra wrote:
> On 01/02/2023 01:04, Ahanu Banerjee wrote:
> > Is it possible to specify default values for a function to use when
> arguments are missing? In the example
On 01/02/2023 01:04, Ahanu Banerjee wrote:
> Is it possible to specify default values for a function to use when arguments
> are missing? In the example below, I want the default font size to be -4 and
> the default color to be blue without having to specify it each time, but I
> also want the a
Is it possible to specify default values for a function to use when
arguments are missing? In the example below, I want the default font size
to be -4 and the default color to be blue without having to specify it each
time, but I also want the ability to change those values in rare cases.
\version
I realized that the duplication is actually not an issue when using a
MarkLine context, since it isn't collecting the events from multiple
contexts, it's just listening to the event from the MarkLine itself. I
guess I'll just stick with this way of doing things.
\version "2.24.0"
\language "englis
Hello Stephan,
this can be done quite nicely:
\version "2.24.0"
partFine = {
% Offset bar line to mitigate slightly wider stencil of |. barline
\once\override Staff.BarLine.X-offset = #0.41
\bar "||"
}
notesI = \relative c' {
c1^\markup "1." c
\partFine
}
notesII = \relative c' {
e
On 31/01/2023 23:06, Steve Carlock wrote:
> Jean,
>
> Thank you for approving my email - I did subscribe using the website and
> confirmed the email (and have logged into my account page successfully) prior
> to sending my email to the list. Maybe I was impatient and needed to wait a
> day for
Jean,
Thank you for approving my email - I did subscribe using the website and
confirmed the email (and have logged into my account page successfully)
prior to sending my email to the list. Maybe I was impatient and needed to
wait a day for the account setup to completely process.
Thank you all f
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
On 31/01/2023 22:33, Jean Abou Samra wrote:
> Uh, why did I just write this already? The latter wouldn't
> be a problem. assign_event_once uses "equal?" The former,
> with procedures, is indeed a problem.
>
> Sorry for the noise.
Looking a bit more into define-markup-commands.scm, this
will occu
On 31/01/2023 22:32, 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
>> musical objects push them away from
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
> musical objects push them away from the staff as in measure 3? I have to say
> I thi
The tie ~ and number 1 in measure 3 are in the wrong order, the tie should
come after the number.
What happens is that Lilypond, when it sees a pitch or duration alone
interprets it as a new note, with the missing pitch or duration carried over
from the previous note. So g~1 becomes a g with
Hi all
I happened to typeset a few canons from several sources the last days.
Let's assume we have a 3-voiced canon. I observed that they look
somewhere between how one would set 3 parallel voices/staves and a
single-voice tune running through 3 lines with a \break after every
"line of lyrics".
Hi Steve,
welcome to the group!
In your third measure, Instead of
g~1
you should write
g1~
Your sequence means the following:
- g without a duration uses the last duration specified, i.e. whole note
from the measure before.
- ~ produces a tie to the following note.
- 1 without a pitch p
Hello,
Welcome to this list. I had to approve your message manually
because you are not subscribed to the list yet. Please fix this
by subscribing on https://lists.gnu.org/mailman/listinfo/lilypond-user
On 31/01/2023 22:04, Steve Carlock wrote:
> New Lilypond user here. The following code is no
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
New Lilypond user here. The following code is not working as I expect:
\version "2.24.0"
\language "english"
\score {
<<
\new Staff {
\key d \major
\time 4/4
\relative c' {
1 | 1 | g~1 | g2 2 |
}
}
>>
\layout { }
}
I expect to see 4 measures with ties between me
Hi Jean,
The solution you gave me works very good for whole notes. But if the
notes have stems then the stems are not removed. Please look at the
LilyPond like below.
\version "2.22.0" \language english boxify = #(define-music-function
(grob-path) (key-list?) (define proc (grob-transformer '
Thanks David for your detailed explanation.
On 1/31/2023 7:15 AM, David Wright wrote:
On Mon 30 Jan 2023 at 20:52:05 (-0800), Rajesh Baskar wrote:
You can see in
the mage attached that Lilypond generates them a bit differently. The
line dividing the two measures is thicker
You'll also notice t
Thanks Jean, that was a simple solution, and sorry for my ignorance.
On 1/30/2023 9:10 PM, Jean Abou Samra wrote:
On 31/01/2023 05:52, Rajesh Baskar wrote:
Hello Experts,
I'm facing a unique issue or it would be because of my limited knowledge of
Lilypond. I have 2 identical Lilypond files, t
On Mon 30 Jan 2023 at 20:52:05 (-0800), Rajesh Baskar wrote:
>
> You can see in
> the mage attached that Lilypond generates them a bit differently. The
> line dividing the two measures is thicker
You'll also notice that the stems of the last note in each measure are
apparently thicker than the ot
>> {
>> e1\< | g''1\breakDynamicSpan\ff |
>> }
>
> I'll eventually submit a patch to fix that.
This is now
https://gitlab.com/lilypond/lilypond/-/merge_requests/1829
Werner
Thank you very much!
Am Dienstag, 31. Jänner 2023, 15:42:39 CET schrieb Jean Abou Samra:
> On 31/01/2023 15:07, Valentin Petzel wrote:
> > Hello Jean,
> >
> > this does not work on 2.24. Do you happen to know what changed to make
> > this
> > work on 2.25?
>
> commit 86cdf5a56d123f3b1145e3eaba09
On 31/01/2023 15:07, Valentin Petzel wrote:
> Hello Jean,
>
> this does not work on 2.24. Do you happen to know what changed to make this
> work on 2.25?
commit 86cdf5a56d123f3b1145e3eaba09805d6e43453e
Author: Jean Abou Samra
Date: Tue Oct 4 21:57:10 2022 +0200
Make StaffSymbol.line-po
On 22/01/2023 21:06, Jean Abou Samra wrote:
> If you are interested in translating this into another language,
> please let me know. The translation is done in .po files, like
> most translation workflows (but not the one for the official
> documentation).
There is now a complete French translat
On 30/01/2023 22:45, Stefan E. Mueller wrote:
> This works for me, but I wonder if the vertical position of the individual
> tablature lines could be accessed and used for the positioning of the
> letters instead of doing things by hand.
Yes, it's possible. Try
\version "2.25.1"
% doesn't exis
Hello Jean,
this does not work on 2.24. Do you happen to know what changed to make this
work on 2.25?
Am Dienstag, 31. Jänner 2023, 14:48:26 CET schrieb Jean Abou Samra:
> On 30/01/2023 22:45, Stefan E. Mueller wrote:
> > This works for me, but I wonder if the vertical position of the individual
Hello Stefan (also Federico),
is there a particular reason you are using font Arial instead of simply using
markup command \sans?
This is a slightly more robust approach (not requiring manual positioning),
using a markup command
#(define-markup-command (tuning-column layout props tunings) (lis
48 matches
Mail list logo
