On Fri, Feb 10, 2023 at 10:48 AM Mark Knoop wrote:
>
>
> At 10:38 on 10 Feb 2023, Knute Snortum wrote:
> > I have run into something in LilyPond that's annoying -- it probably
> > doesn't rise to the level of bug. When you have two notes in
> > different octaves but "on the same level" because of
At 10:38 on 10 Feb 2023, Knute Snortum wrote:
> I have run into something in LilyPond that's annoying -- it probably
> doesn't rise to the level of bug. When you have two notes in
> different octaves but "on the same level" because of an ottava, the
> accidental is repeated. This makes sense lo
I have run into something in LilyPond that's annoying -- it probably
doesn't rise to the level of bug. When you have two notes in
different octaves but "on the same level" because of an ottava, the
accidental is repeated. This makes sense logically because they are
not the same note, but it doesn
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,
On 2023-02-10 15:20, Johannes Roeßler wrote:
Hi Group,
I would like to align markups above my staff - I checked the page
regarding vertical spacing and found
"\override TextScript.outside-staff-padding = #3" but this just raised
all markups but still unaligned
\override TextScript.outsi
On 2023-02-10 7:12 am, Michael Werner wrote:
On Fri, Feb 10, 2023 at 9:49 AM Johannes Roeßler wrote:
thx to both Michaels :)
looks like an idea, but when I compile your source, I get a little
drift
between
"diminuendo" and "poco"
Best regards
Johannes
Huh. I hadn't noticed that when I w
I don't know why this works, but try this:
\new Dynamics \with {
\override TextScript.Y-offset = -0.5
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #4
}
--
Knute Snortum
On Fri, Feb 10, 2023 at 7:13 AM Michael Werner wrote:
> On Fri, Feb 10, 2023 at
On Fri, Feb 10, 2023 at 9:49 AM Johannes Roeßler wrote:
> thx to both Michaels :)
>
> looks like an idea, but when I compile your source, I get a little drift
> between
> "diminuendo" and "poco"
>
> Best regards
> Johannes
>
Huh. I hadn't noticed that when I was testing it here. But now I go lo
> looks like an idea, but when I compile your source, I get a little drift
> between
> "diminuendo" and "poco"
I think that's an issue with the outline (skyline?) handling of the
font. Letters a and p seem to have problems but not always (according to
my tests).
I suspect a bug. Jean or David
thx to both Michaels :)
looks like an idea, but when I compile your source, I get a little drift
between
"diminuendo" and "poco"
Best regards
Johannes
On Fri, Feb 10, 2023 at 9:21 AM Johannes Roeßler wrote:
Hi Group,
I would like to align markups above my staff - I checked the pag
On Fri, Feb 10, 2023 at 9:21 AM Johannes Roeßler wrote:
> Hi Group,
>
> I would like to align markups above my staff - I checked the page
> regarding vertical spacing and found
>
> "\override TextScript.outside-staff-padding = #3" but this just raised all
> markups but still unaligned
>
> \overri
Hi Group,
I would like to align markups above my staff - I checked the page
regarding vertical spacing and found
"\override TextScript.outside-staff-padding = #3" but this just raised
all markups but still unaligned
\override TextScript.outside-staff-priority = ##f didn't help either...
A
Hi Darren,
On 10/02/2023 11:46, Darren Ng wrote:
\ghostNoteWhichDoesNotActuallyAppear { c,,, }
I think what you want here is \resetRelativeOctave.
The best solution depends on many factors around your workflow and the
setup of your project, but generally it is recommendable to split things
Thanks for reiterating. I was being dense when replying and have since
figured out the same, was just meaning to reply again and then saw your
message :)
Thanks for the help and all the best!
Simon
On 10/02/2023 00:02, Saul Tobin wrote:
I think the reason is that the mark engravers belong to t
I want to achieve the following:
(1) $a is respects $x as its "startpitch"
(2) $b is respects $x as its "startpitch"
(3) removing A has no effect on B
\relative $x {
%{A%} { $a ... }
%{B%} { $b ... }
}
In the example above: (1)=ok (2)=fail (3)=fail
\relative $x {
%{A%} \relativ
Great, thanks both! Exactly what I need :-)
K
--
Roosna & Flak - Contemporary Dance & Music
Web: roosnaflak.com
Code: {github,gitlab}.com/kflak
Mastodon: @k...@sonomu.club
On 9 Feb 2023 21:12, Valentin Petzel wrote:
>Hello Jean,
>
>One could even get rid of the direction parameter and instead
16 matches
Mail list logo
