Got it.
On Mon, Nov 1, 2021 at 4:38 PM Jean Abou Samra wrote:
>
> Le 02/11/2021 à 00:08, Kenneth Wolcott a écrit :
> > That helps explain it! Thanks!
> >
> > But if I wanted to reproduce precisely what this arranger is doing, I
> > could just enter the pitches as written and just place a note to
Le 02/11/2021 à 00:08, Kenneth Wolcott a écrit :
That helps explain it! Thanks!
But if I wanted to reproduce precisely what this arranger is doing, I
could just enter the pitches as written and just place a note to
instruct the performer to do the ottava manually, correct?
Thanks,
Ken
Sure.
Le 01/11/2021 à 21:41, Kieren MacMillan a écrit :
Hi Harm,
attached code hacks Instrument.Y-offset.
This is a proof of concept, please test thoroughly before using it in serious
work.
Nice! This definitely solves the basic problem nicely.
Lukas sent me [off-list] a totally different
Got it! Thanks for your patience with me!
Ken
On Mon, Nov 1, 2021 at 4:07 PM Jean Abou Samra wrote:
>
> Le 02/11/2021 à 00:00, Kenneth Wolcott a écrit :
> > Hi Jean;
> >
> >Thanks for the tip.
> >
> >I'm using Lilypond 2.22.1.
> >
> >I now have the attava bracket beneath the notes
That helps explain it! Thanks!
But if I wanted to reproduce precisely what this arranger is doing, I
could just enter the pitches as written and just place a note to
instruct the performer to do the ottava manually, correct?
Thanks,
Ken
On Mon, Nov 1, 2021 at 3:57 PM Jean Abou Samra wrote:
>
>
Le 02/11/2021 à 00:00, Kenneth Wolcott a écrit :
Hi Jean;
Thanks for the tip.
I'm using Lilypond 2.22.1.
I now have the attava bracket beneath the notes using " \override
Staff.OttavaBracket.direction = #DOWN"
BTW, I'm looking at the NR for 2.22.1 and I see "ottava #X" where,
Hi Jean;
Thanks for the tip.
I'm using Lilypond 2.22.1.
I now have the attava bracket beneath the notes using " \override
Staff.OttavaBracket.direction = #DOWN"
BTW, I'm looking at the NR for 2.22.1 and I see "ottava #X" where,
apparently the "#" is no longer needed.
Is it possible
Le 01/11/2021 à 23:49, Kenneth Wolcott a écrit :
Hi Kieren & Carl;
Well, since you have already provided an MWE that shows it works as
documented, may I provide my full Lilypond code? It is only a halfway
completed Piano arrangement of "The Elephant" from the ""Carnival of
the Animals", by
On 11/1/21, 4:49 PM, "Kenneth Wolcott" wrote:
Hi Kieren & Carl;
Well, since you have already provided an MWE that shows it works as
documented, may I provide my full Lilypond code? It is only a halfway
completed Piano arrangement of "The Elephant" from the ""Carnival
Le 01/11/2021 à 23:20, Kenneth Wolcott a écrit :
How to force the placement of the ottava bracket to be below the
notes? (or above?)
Below: just \override the direction. Above: prior
to version 2.23.3, you had to use the lesser known
\overrideProperty (see
Ken,
Please show an example.
I assume you are using it wrong.
Always enter the sounding pitch in lilypond. In the Notation Reference, they
are showing you that if you don't change the pitch, an add an ottava, the note
will displace in the opposite direction of the ottava bracket, because the
Hi;
How to force the placement of the ottava bracket to be below the
notes? (or above?)
Thanks,
Ken Wolcott
Hi Ken,
> another question regarding ottava: why does Lilypond change the pitches?
>
> If the purpose of the ottava is to make it easier for the
> publisher/engraver/typesetter/performer to read the notes within the
> staff rather than lots of ledger lines above or below the staff, then
> why
Hi again;
another question regarding ottava: why does Lilypond change the pitches?
If the purpose of the ottava is to make it easier for the
publisher/engraver/typesetter/performer to read the notes within the
staff rather than lots of ledger lines above or below the staff, then
why does
Hi Harm,
> attached code hacks Instrument.Y-offset.
> This is a proof of concept, please test thoroughly before using it in serious
> work.
Nice! This definitely solves the basic problem nicely.
Lukas sent me [off-list] a totally different solution that was also excellent.
Maybe we can/should
Hi Kieren,
This should be very well doable with an engraver, similar to the engraver for
group delimiters. Optimally this should integrate with the Instrument name
engraver, so that the instrument name can behave differently depending on
whether the group name is present (e.g. a group
Am Mo., 1. Nov. 2021 um 15:35 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> Having struggled with this for almost a decade (see, e.g.,
> https://lists.gnu.org/archive/html/lilypond-user/2013-03/msg00314.html)… Is
> this something that could be handled really well with an engraver? Or at
>
Dear community,
I would like to do with arranger.ly something similar to
Key = { \key f \major }
music =
{ \Key c'4 d' e' f'2.}
artiA = { s2.( s) }
music = { \context Voice << {\music} {\artiA } >> }
I tried in in the following way, without success, unfortunately:
\version "2.22.1"
> On 1 Nov 2021, at 11:33, Thomas Scharkowski wrote:
>
> Am 31.10.2021 um 18:36 schrieb Hans Åberg :
>>
>>
>>> On 31 Oct 2021, at 11:43, Thomas Scharkowski
>>> wrote:
>>>
>>> Hi, I have installed this version on a fresh MacOS 12 and get this error
>>> message:
>>
>> I have made an
Hi all,
Having struggled with this for almost a decade (see, e.g.,
https://lists.gnu.org/archive/html/lilypond-user/2013-03/msg00314.html)… Is
this something that could be handled really well with an engraver? Or at least
a bunch of helpful syntactic sugar? Surely all of this manual work
The include file now works but the: \once\override
Score.RehearsalMark.break-visibility = ##(#t #f #f) \fine
doesn't. This message show up:
Starting lilypond-windows.exe 2.22.1 [include-all.ly]...
Processing
`C:/Users/mahan/AppData/Local/Temp/frescobaldi-8ijs0g1g/tmph11fyztr/include-all.ly'
Am Mo., 1. Nov. 2021 um 13:02 Uhr schrieb Mahanidhi :
>
> I forgot to add the \include file:
>
> \version "2.22.1"
> \language "english"
>
> show-barline = {\once \undo \hide Staff.BarLine \bar "|"} % to show bar line
>
> fine = {\once \override Score.RehearsalMark.self-alignment-X = #RIGHT \mark
I forgot to add the \include file:
\version "2.22.1"
\language "english"
show-barline = {\once \undo \hide Staff.BarLine \bar "|"} % to show bar line
fine = {\once \override Score.RehearsalMark.self-alignment-X = #RIGHT \mark
\markup { \italic \abs-fontsize #10 "Fine" }}
dcfine = {\once
Hello,
I have a problem with an \include code. The DC al fine is aligned to the bar
but the fine is not. At the same time I get this error:
programming error: file name not normalized:
\users\mahan\chinmoy-sangit\include\include-all.ly
Can someone help me? Thank you.
minimal code:
\version
> On 1 Nov 2021, at 11:33, Thomas Scharkowski wrote:
>
> Am 31.10.2021 um 18:36 schrieb Hans Åberg :
>>
>>
>>> On 31 Oct 2021, at 11:43, Thomas Scharkowski
>>> wrote:
>>>
>>> Hi, I have installed this version on a fresh MacOS 12 and get this error
>>> message:
>>
>> I have made an
Am 31.10.2021 um 18:36 schrieb Hans Åberg :
>
>
>> On 31 Oct 2021, at 11:43, Thomas Scharkowski
>> wrote:
>>
>> Hi, I have installed this version on a fresh MacOS 12 and get this error
>> message:
>
> I have made an installer using MacPorts directly on MacOS 12; see separate
> post.
>
>
Am Sa., 30. Okt. 2021 um 15:54 Uhr schrieb Thomas Morley
:
>
> Am So., 24. Okt. 2021 um 18:19 Uhr schrieb Aaron Hill
> :
> >
> > On 2021-10-24 8:05 am, Thomas Morley wrote:
> > > Am So., 24. Okt. 2021 um 16:35 Uhr schrieb Aaron Hill
> > >> Let me take a stab at converting the print routine to
While these suggestions are good suggestions, it's also important to note that
beam subdivision is incorrect in many instances.
See https://sourceforge.net/p/testlilyissues/issues/5547/
In case someone wants to take up that issue, it might be best to link to
the current issue collection
Hi Valentin,
Thanks for your perfect solution!!
best
ole
> Am 31.10.2021 um 21:52 schrieb Valentin Petzel :
>
> Hi Lukas, hi Ole,
>
> Getting the parentheses is quite a simple modification (just use parenthesize-
> stencil on the arrowhead stencil. But I think that using straight arrow lines
Hi Valentin,
Getting the parentheses is quite a simple modification (just use parenthesize-
stencil on the arrowhead stencil.
You're right. Sorry that I didn't bother to look that up yesterday,
thanks for stepping in.
But I think that using straight arrow lines
is more readable than the
30 matches
Mail list logo
