Hello again,
This has me stumped. I've been digging for hours.
\version "2.21.7"
global = {
\skip 1*24
\mark \default
\skip 1*12
\mark \default
\skip 1*12
}
music = \relative c'' {
\compressMMRests
R1*48
}
\new Staff <<
Are you talking about reimplementing LilyPond from scratch?
I'm happy with Scheme, as a programmer. It's the Guile implementation
that causes the performance issue with Guile 2, not the Scheme
languages. Perhaps it's just that with advanced tools one requires
advanced knowledge. As with anythi
On 2020-10-18 11:45 pm, Andrew Bernard wrote:
OK. So, how do you tell it legato? Slurs? I am new to this area. And
of course the visual output with rests is not musically correct, is it
(not that it matters).
The documentation for \articulate is within the script itself. See this
excerpt:
%
On 2020-10-19 12:00 am, Adam Griggs wrote:
Hello again,
This has me stumped. I've been digging for hours.
\version "2.21.7"
global = {
\skip 1*24
\mark \default
\skip 1*12
\mark \default
\skip 1*12
}
music = \relative c'' {
\compress
Am So., 18. Okt. 2020 um 21:47 Uhr schrieb Kevin Barry :
>
> Hi Bart,
>
> I'm away from my computer so I can't verify what I'm about to say, but I
> think that once a note is beamed it is actually the beam that controls the
> lengths of the stems. I think you need to override the Beam's positions
Just my two cents to this comment:
> switch to another, easier to read and write extension language. Someone
> suggested Lua, for example, which would be a good candidate it seems
I don’t know about Lua, but as a non-programmer, I spent many days getting in
grips with Scheme. The result were ver
Did the trick, thank you very much!
On Mon, 19 Oct 2020, 16:13 Aaron Hill, wrote:
> On 2020-10-19 12:00 am, Adam Griggs wrote:
> > Hello again,
> >
> > This has me stumped. I've been digging for hours.
> >
> >\version "2.21.7"
> >
> >global = {
> > \skip 1*24
> > \mark \d
Hi Jacques,
I split my replies to address different aspects separately.
This one about scheme/guile
Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu :
> Some aspects of the current state of the Lily implementation are a bit
> saddening:
> - Scheme is not easy to read nor write f
About issue 34
Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu :
> LilyPond can be characterized the following way, please excuse any important
> omission or error:
> - the implementation is one-pass, meaning that the work done when
> handling a file goes straight from the char
Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu :
> We often have to add things such as short skips and cadenzas to avoid having
> so-called events at the exact same time moment in the score.
> This is illustrated by \HiddenMeasureAndBarLine in the attached file:
> commenting its use out
Thanks! The "showIt" / "hideIt" functions were exactly what I was looking
for.
Hello,
I wanted to ask if there's a way to prevent
showLastLength/Score.skipTypesetting from showing tempo and time signature
(and header information if possible).
Regards,
Martín.
--
www.martinrinconbotero.com
Le 19/10/2020 à 17:32, Martín Rincón Botero a écrit :
Hello,
I wanted to ask if there's a way to prevent
showLastLength/Score.skipTypesetting from showing tempo and time
signature (and header information if possible).
Regards,
Martín.
Hi,
I don't know an obvious way to do this, though yo
Hello Jean,
thank you for your answer. It’s not a critical thing, but since I moved all my
workflow to Python to be able to use its automating capabilities for producing
Lilypond files, today I started using OLL’s partial compilation together with a
couple of subprocesses that are run at the en
Hi all,
I am trying to define a variable on the command line that I can use within
the .ly file. I've tried both
-e "(define-public part 1)"
and
-e "(define part 1)"
In the .ly file, I have a Scheme expression
#(if (= part 0)
(define partName "")
(define partName (string-append "S" part)
In the example shown below, notice that the slur is incorrectly pointing
upward, and "crashing" into the tuplet bracket. It only happens with both
the slur and the beam present. With slur only or beam only, it engraves
correctly.
Is this a known issue? Should I be coding it differently? The code u
Le 19/10/2020 à 23:14, Dave Seidel a écrit :
Hi all,
I am trying to define a variable on the command line that I can use
within the .ly file. I've tried both
-e "(define-public part 1)"
and
-e "(define part 1)"
In the .ly file, I have a Scheme expression
#(if (= part 0)
Le 19/10/2020 à 23:43, Marc Shepherd a écrit :
In the example shown below, notice that the slur is incorrectly
pointing upward, and "crashing" into the tuplet bracket. It only
happens with both the slur and the beam present. With slur only or
beam only, it engraves correctly.
Is this a known
Jacques Menu writes:
> Hello folks,
>
> Sorry, this message is rather long…
>
>
> I’ve been wondering what design decisions would be made, should
> someone start a project like LilyPond today, with the years-long
> experience we have behind us in this field.
>
> LilyPond can be characterized the
Thanks Jean! I need to read more carefully!
On Mon, Oct 19, 2020 at 5:45 PM Jean Abou Samra wrote:
>
> Le 19/10/2020 à 23:14, Dave Seidel a écrit :
>
> Hi all,
>
> I am trying to define a variable on the command line that I can use within
> the .ly file. I've tried both
>
> -e "(define-public pa
On 2020-10-19 2:45 pm, Jean Abou Samra wrote:
You can ignore the warning that shows up
(https://gitlab.com/lilypond/lilypond/-/issues/3613).
You can avoid the warning by using the @ syntax:
eval-scope.ly
\version "2.20.0"
#(format #t "\nvalue = ~s"
(false-if-exception (@ (guile-use
The reason the tuplet is up, is that — in the actual music, there is a
lower voice, so the tuplet *has to be* up. I left out the lower voice in my
example, because it is not relevant to the behavior I am asking about.
In the real score, I have not overridden the tuplet and slur direction.
With the
Interesting. I don't understand the '@' syntax -- been trying to look it up
but so far to no avail.
Here's what I ended up with:
#(begin
(use-modules (guile-user))
(if (not(symbol? 'part))
(define part 0)
)
(if (= part 0)
(define partName "")
(define partName (string-append
More succinct:
#(begin
(use-modules (guile-user))
(if (not(defined? 'part))
(define partName "")
(define partName (string-append "S" (number->string part)))
)
)
though the warning still prints, but that's not a big deal for me.
On Mon, Oct 19, 2020 at 10:23 PM Dave Seidel wrote:
On 2020-10-19 7:51 pm, Dave Seidel wrote:
More succinct:
#(begin
(use-modules (guile-user))
(if (not(defined? 'part))
(define partName "")
(define partName (string-append "S" (number->string part)))
)
)
partName =
#(or (false-if-exception (format #f "S~d" (@ (guile-user) pa
On 2020-10-19 7:51 pm, Dave Seidel wrote:
More succinct:
#(begin
(use-modules (guile-user))
(if (not(defined? 'part))
(define partName "")
(define partName (string-append "S" (number->string part)))
)
)
To be even more succinct, observe the following:
Avoid negated predica
26 matches
Mail list logo
