No problem Ken. Sorry about that, I made the following example: (note
that this would not play in midi playback)
\version "2.22.2"
shMordentUp = \markup { \center-column {\musicglyph "scripts.mordent"
\musicglyph "accidentals.sharp" }}
shMordentDo = \markup { \center-column {\musicglyph
Hi William;
Thank you, now I have a meaning.
What remains (that I did not specify) is how to engrave this?
Thanks,
Ken
On Mon, Jun 27, 2022 at 8:51 PM William Rehwinkel
wrote:
>
> That symbol means that the lower note is sharped. So it would be g-f#-g
> instead of g-fnatural-g. See
>
Hi William;
Looks like I need to read more slowly :-) I see now that my
question was indeed precisely covered in the documentation.
Thank *you*. :-)
Ken
On Mon, Jun 27, 2022 at 9:29 PM William Rehwinkel
wrote:
>
> No problem Ken. Sorry about that, I made the following example: (note
> that
Hi Andrew;
The screenshot is from 8notes.com:
https://www.8notes.com/school/pdf/piano/bach_six_1.pdf (attached)
Thanks,
Ken
On Mon, Jun 27, 2022 at 8:58 PM Andrew Bernard
wrote:
>
> Are you referring to BWV 933-938 6 Kleine Praludien? If so, I see no
> such passage in any of the preludes.
Are you referring to BWV 933-938 6 Kleine Praludien? If so, I see no
such passage in any of the preludes.
What source are you engraving from?
I am a harpsichordist so I can fairly confidently say this is not a rare
notation and all it would mean is that the mordent is to the F sharp not
F
That symbol means that the lower note is sharped. So it would be g-f#-g
instead of g-fnatural-g. See
https://music.stackexchange.com/questions/86043/would-an-accidental-in-a-mordant-still-be-effective-for-the-whole-measure
On 6/27/22 23:13, Kenneth Wolcott wrote:
Hi;
I'm trying to
Hi;
I'm trying to engrave a Piano arrangement of JS Bach, Six Little
Preludes, Nr 1, where the left hand notes have a strange thing I've
never seen before, a mordent on top of a sharp sign.
I've never seen these symbols together in this manner.
I have a screenshot attached.
Thanks,
Ken
Am Mo., 27. Juni 2022 um 13:23 Uhr schrieb Jean Abou Samra :
>
>
>
> Le 27/06/2022 à 12:12, Thomas Morley a écrit :
> > Hi,
> >
> > https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
> > access header-entries for use in arbitrary markup.
> > Alas it's limited to $defaultheader.
>
Jean Abou Samra writes:
> When you say "tackle the resulting parser conflicts", that means
> "add precedences to solve them by making interpretation choices",
> not "solve them in a way that always does what the user might intend",
> right? As I understand it, there is a shift/reduce conflict on
Hi Jacques,
On 27/06/2022 22:13, Jacques Menu wrote:
Does anyone know of some way to generate spiccato articulations in the scores
produced by Lily?
what would you expect that to look like?
{ a'4-! }
maybe?
Best, Simon
Hi David,
On 27/06/2022 21:07, David Kastrup wrote:
Before looking for a possible following `=`
LilyPond has to have made a decision what type the token/expression
coming before that has. It cannot look at the type of a #... expression
before deciding to look for `=` but it can (and will) look
Hi Jean,
On 27/06/2022 20:37, Jean Abou Samra wrote:
Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values halved/doubled). Unfortunately
\tempo isn’t affected by
Le 28/06/2022 à 00:15, David Kastrup a écrit :
David Kastrup writes:
Jean Abou Samra writes:
Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values
halved/doubled).
David Kastrup writes:
> Jean Abou Samra writes:
>
>> Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
>>> Hello everyone,
>>>
>>> I’m trying to encode a piece such that I can switch whether or not
>>> durations will be shifted (note values
>>> halved/doubled). Unfortunately \tempo isn’t affected
> On 27 Jun 2022, at 22:28, Jacques Menu wrote:
>
> Hello folks,
>
> Does anyone know of some way to generate spiccato articulations in the scores
> produced by Lily?
>
> Thanks for your help!
>
> JM
Google leads me to
Hello folks,
Does anyone know of some way to generate spiccato articulations in the scores
produced by Lily?
Thanks for your help!
JM
Jean Abou Samra writes:
> Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
>> Hello everyone,
>>
>> I’m trying to encode a piece such that I can switch whether or not
>> durations will be shifted (note values
>> halved/doubled). Unfortunately \tempo isn’t affected by
>> \shiftDurations (that
Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values halved/doubled). Unfortunately
\tempo isn’t affected by \shiftDurations (that would be a sensible
feature request,
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values halved/doubled). Unfortunately
\tempo isn’t affected by \shiftDurations (that would be a sensible
feature request, right?), so I tried this:
%%%
Oh, no. This is what is needed. I just haven't come across the proposed algorithm of the program. I need to try it out.27.06.2022, 14:35, "Jean Abou Samra" :Le 27/06/2022 à 12:22, Лысов Дмитрий a écrit : It is interesting. There is something to think about.Since you say this, I suppose you are not
Aaron Hill writes:
> On 2022-06-27 6:18 am, Jean Abou Samra wrote:
>> The LSR runs LilyPond 2.22 and you have 2.18. You need to upgrade
>> LilyPond. Frescobaldi makes it easy to use several versions in
>> parallel.
>
> As far as I can see, the LSR only notes the current version in
> Contributing
On 2022-06-27 6:18 am, Jean Abou Samra wrote:
The LSR runs LilyPond 2.22 and you have 2.18. You need to upgrade
LilyPond. Frescobaldi makes it easy to use several versions in
parallel.
As far as I can see, the LSR only notes the current version in
Contributing [1].
[1]:
Le 27/06/2022 à 13:26, mark damerell a écrit :
It came from:
%% http://lsr.di.unimi.it/LSR/Item?id=328
Here is part of it:
% First version, with a single argument, i.e. the
% syntax is \triplet{ c d e }
triplet = #(define-music-function (music) (ly:music?)
#{ \tuplet 3/2 $music #})
It came from:
%% http://lsr.di.unimi.it/LSR/Item?id=328
Here is part of it:
% First version, with a single argument, i.e. the
% syntax is \triplet{ c d e }
triplet = #(define-music-function (music) (ly:music?)
#{ \tuplet 3/2 $music #})
\score{
\relative c'{
c4 \triplet {c d e}
}
}
Le 27/06/2022 à 12:22, Лысов Дмитрий a écrit :
It is interesting. There is something to think about.
Since you say this, I suppose you are not completely satisfied with this
solution. What could be better about it?
Jean
Le 27/06/2022 à 12:12, Thomas Morley a écrit :
Hi,
https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
access header-entries for use in arbitrary markup.
Alas it's limited to $defaultheader.
Although there is a comment to add/access other headers like from
\score, \bookpar
It is interesting. There is something to think about.27.06.2022, 09:48, "Jean Abou Samra" :Le 26/06/2022 à 20:25, Лысов Дмитрий a écrit : Thanks. That's not bad. Probably, the insertion of the \markup block in \score should not be done. Then you will get one midi file. Still, it is more
Hi,
https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
access header-entries for use in arbitrary markup.
Alas it's limited to $defaultheader.
Although there is a comment to add/access other headers like from
\score, \bookpar explicit \book, I found no way to do so.
I tried to
Le 26/06/2022 à 20:25, Лысов Дмитрий a écrit :
Thanks. That's not bad. Probably, the insertion of the \markup block
in \score should not be done. Then you will get one midi file. Still,
it is more convenient to listen to individual midi files.
1. It is usually more convenient if you move
29 matches
Mail list logo
