Re: move discant symbol

> > [...] > How can I move the discant symbol and the accordion pull symbol to avoid > them to stack on top of each other? > > [...] > > I just learned from Jean how to use \overlay and \translate-scaled > together to control exactly where text and glyphs are placed, and make them > scale with

move discant symbol

Sorry, trivial question: How can I move the discant symbol and the accordion pull symbol to avoid them to stack on top of each other? \version "2.25.2" #(use-modules (lily accreg)) %to use \discant pull = \markup {\musicglyph "accordion.pull" } \score { \fixed c'' { \discant "20" \tempo

Re: Separate dynamics from notes

%%% > > > > Otherwise it is possible to create music functions that replace notes > and rests with spacers or remove dynamics, but I can’t do that for you at > the moment. While they’re not difficult functions they’re not ”built-in”. > > > > The second question is also probably not

Re: frescobaldi themes

Ciao Valentin, Thank you for your kind msg! You wrote: [install multiple themes all at once in Frescobaldi] > I suppose the easiest way to be able to install multiple files would be to > slightly > tweak Frescobaldi’s code (which can easily be done on a distributed copy > as it is python). >

Re: Separate dynamics from notes

I have infinite esteem in cheerleader so if the message comes from one of them I will do all what them propose: - I will study what I can do with the edition engraver - and wait for your MWE :)) By the way, ahem what is a MWE? Grazie Kieren! g. On Fri, 28 Apr 2023 at 17:13, Kieren MacMillan

Re: Separate dynamics from notes

to go back to study the edition engraver :) g. On Thu, 27 Apr 2023 at 18:20, Robin Bannister wrote: > Gianmaria Lari wrote: > > > > This thing always seemed so inconvenient to me that I thought it was > > practically unusable. Or that there was some trick to maybe have > &

Re: frescobaldi themes

[midi player not visible in Frescobaldi] > Maybe it's just turned off? What if you enable it in Tools > MIDI > MIDI > player ? ahhh quelle honte ! My apologies, I didn't know you have to enable it. Thanks a lot Jean! gianmaria

Re: frescobaldi themes

and no more embedded midi player!!! I tried to have a look on the mailing list and on google but no one discusses this issue. Do you know anything about this? Thks, Gianmaria On Fri, 28 Apr 2023 at 10:52, Federico Bruni wrote: > > > Il giorno ven 28 apr 2023 alle 09:40:57 +0200, Gianm

frescobaldi themes

Hope this is not off topic. Is there any way in Frescobaldi to install a bunch of themes all at once (instead of passing trough Edit -> Preferences -> Fonts & Colors etc.) ? Thanks, Gianmaria

Re: Separate dynamics from notes

Fantastic Robin! I'll test it more in the following days. Anyway, couldn't it be of interest to others as well? Thanks a lot to everyone!!! Gianmaria On Thu, 27 Apr 2023 at 18:20, Robin Bannister wrote: > Gianmaria Lari wrote: > > > > This thing always seemed so inconvenient to me

Re: Separate dynamics from notes

Thank you Leo for your answers and help. > you’ll probably need to be a little more specific about the use case, > perhaps also supply example code. > Regarding my second question, let me try to be more clear I have a score. I want to write the dynamics using a separate variable. Suppose that

Separate dynamics from notes

First question Suppose I wrote this score: \version "2.25.2" rh = \fixed c' {c4\pp d\p e\f f\ff} \score { \new Staff \rh } Is there any "automatic" way to extract the dynamics in the score (maybe assigning it to a variable)? At the end I would like to easily transform the previous code in

Re: keep measures on the same line

Hello Jean, > Sometimes I want to keep some measures on the same line. To do this I use > \nobreaks and I set the fontsize manually by trial and error. Isn't there > an easier way? > > Before this group of measures, put > > \autoLineBreaksOff > > [] > Using \autoLineBreaksOff lilypond stops

keep measures on the same line

Sometimes I want to keep some measures on the same line. To do this I use \nobreaks and I set the fontsize manually by trial and error. Isn't there an easier way? Thank you, gianmaria

Re: \pushToTag and \appendToTag examples

> > > Nota bene: I didn't yet add any examples that take advantage of David new > > possibilities: > > Ah, but that was sort of the point. > Sure, I'm sorry :( I'll help with that too when I will be able to access this new feature. > P.S. I would have liked to add a screenshot of the generated

\pushToTag and \appendToTag examples

Following David Kastrup's suggestion, I wrote some hopefully simple examples for \pushToTag and \appendToTag. I paid the maximum attention to make this code simple and clear but I'm sure it contains millions of errors etc. etc. It's just a starting point. I hope it can be useful. Nota bene: I

Re: tags

Hello David, I've submitted a merge request > that will at > least make the following work for your purpose: > > \version "2.23.3" > music = {\tag#'here a a} > {\pushToTag #'here ~ \music } > [] > I don't like the sample code in the

Re: maple leaf rag mutopia

> > Replace \applyMusic #unfold-repeats with \unfoldRepeats ? > Yes, now it works fantastically :) Grazie! g.

maple leaf rag mutopia

Hello, I'm trying to engrave Maple Leaf Rag from mutopia. It has been written with LilyPond, version 2.14.2. I converted it using "Tools/Update with convert-ly" (in Frescobaldi) but when I try to engrave it I get this error message: Parsing...C:/Program Files

Re: tags

> How is { ~ } correct? ~ is not standalone music. > > Maybe it would be nice to get an error message when you try to use a wrong object with \pushToTag etc.

Re: tags

Ciao David, [] > At any rate, \pushToTag's documentation states: > >Sometimes you want to splice some music at a particular place in an > existing music expression. You can use ‘\pushToTag’ and ‘\appendToTag’ > for adding material at the front or end of the ‘elements’ of an

tags

Be patient with me. I expect this to generate {a~a} but it generates {a a} . Why? \version "2.23.2" music = {a \tag#'here a} {\pushToTag #'here ~ \music } The \displayLilyMusic output looks "correct". { { a4 \tag #'here { ~ } a4 } } * * * I also tried this \version "2.23.2" music = {a

Re: "compound music expression" to "music" expression"

On Sat, 24 Apr 2021 at 11:40, Aaron Hill wrote: > On 2021-04-23 11:32 pm, David Kastrup wrote: > > Gianmaria Lari writes: > > > >> Thank you Aaron and Jean, your code works! > >> > >> But I have some trivial questions. > >> If I write: > >>

Re: "compound music expression" to "music" expression"

This should be the good one that doesn't work :) \version "2.23.2" #(define (first-element music) (first (ly:music-property music 'elements))) { #(first-element #{ \chordmode {c} #}) } Ciao, g.

Re: "compound music expression" to "music" expression"

Ah!!! Sorry, I made many tests and I copied the wrong code. My apologies. g. On Sat, 24 Apr 2021 at 08:11, David Kastrup wrote: > Gianmaria Lari writes: > > > Thank you Aaron and Jean, your code works! > > > > But I have some trivial questions. > > If I wr

Re: "compound music expression" to "music" expression"

Thank you Aaron and Jean, your code works! But I have some trivial questions. If I write: \displayLilyMusic \chordmode {c} I get: { < c' e' g' >4 } It looks a good "compound music expression". But Aaron code and Jean code behave differently. Have a look here This does not work. \version

"compound music expression" to "music" expression"

How can I convert a "compound music expression" made of just *one* "music expression" to a music expression? So something that "removes" curly brackets. For example it should convert {} to Thanks, g.

Re: combining chords in chords

> > If the only purpose for using tags is to generate different octaves in the > midi and the display, it would be much easier to just change the octavation > of the clef. > > Nice escamotage Carl :)) But no, the visual representation and the midi output do not differ only in the octave. g.

Re: combining chords in chords

Thank you Aaron and Valentin for your help and your codes. It worked perfectly in my previous example. Is it possible to make it working also with tags? Here is a bit of information. In my code, I use tags to generate two different outputs, one for midi and one for layout. So my variables are

Re: combining chords in chords

Ciao Valentin, thanks for your code, it works and it is very simple. Before asking my question, I had tried a solution similar to yours, I used <>. Unfortunately it didn't work because I forgot to specify it also after \kc. Thanks for your help and the explanation. Best regards, g. On Thu,

Re: combining chords in chords

Dear Aaron, > How can I solve this? > > Here's a way that involves merging the elements of the two EventChords: > [...] that's great It seems to work perfectly. Thanks a lot Aaron!! Gianmaria

combining chords in chords

I have some variables, each containing one chord as in the following example: ja = 8 jb = 8 jc = 8 and some other variables combining them, like this: ka = <<\ja \jb>> kb = <<\ja \jc>> kc = <<\jb \jc>> This is a working example engraving \ka \kb and \kc: \version "2.23.2" ja = 8

Re: What usb keyboard to enter voices into lilypond? What other hardware and/or Software is indispensable?

> you plug it into your desktop via USB and it works? Or do I have to > install other software to make it working? > For windows no driver to install. You just plug in and enable the Frescobaldi midi input feature. Absolutely trivial. Ciao, g.

Re: What usb keyboard to enter voices into lilypond? What other hardware and/or Software is indispensable?

Ciao Bernhard, I have the "M-Audio Keystation Mini 32" that Knute suggests. I can confirm it works flawlessly with Frescobaldi (and Musescore). His small size makes it very practical. And it's cheap so if you decide to not use it, it should not be a big problem :) Ciao, g. On Mon, 22 Mar 2021

Re: organ - off topic

; "the church built around many organs" - I like your priorities! I got > in trouble once for similarly suggesting that the purpose of a cathedral > was to support the bell tower (we were in the ringing chamber at the time). > :-o > > > > On 01/10/2020 10:02, Lukas-F

organ - off topic

Sorry if I ask this question here. I do it as usual because I have a lot of consideration for the people who write on this group and I'm sure someone can help me. I'm curious to know if a pipe organ (mechanical) can have a sustain pedal and a sostenuto pedal like a piano. I had a look online but

Re: [OT] modify midi

llis wrote: > On 15/06/2020 12:18, Mark Knoop wrote: > > At 11:09 on 15 Jun 2020, Gianmaria Lari wrote: > >> Sometimes I would like to modify a bit the midi file generated by > >> Lilypond. What stops me from doing that is that in case I modify the > >>

[OT] modify midi

Sometimes I would like to modify a bit the midi file generated by Lilypond. What stops me from doing that is that in case I modify the lilypond source I lose all the work done on the midi and I have to do it again from scratch. So I was wondering if anyone knows a software that gives you the

Re: Staff.OttavaBracket.direction

On Thu, 11 Jun 2020 at 17:33, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > Hi Gianmaria, > Are you sure to want an *ottava bassa* on above the staff? > This could be pretty disturbing... > No, I'm not sure. I have no experience; in my particular case it just looked

Staff.OttavaBracket.direction

My apologies if the question is trivial. I would like to print the ottavaBracket up the staff but even if I specify the direction of ottava bracket it doesn't work. Here it is a not working example. \version "2.21.1" \fixed c'' { \override Staff.OttavaBracket.direction = #UP \ottava #-1 c d

Re: move object - accordion register

Thank you Pierre and Jamie for your kind help. The command you mentioned \markup\halign worked perfectly! Thanks a lot, g. On Wed, 10 Jun 2020 at 13:54, Jamie Beardslee wrote: > Use \halign to horizontally align markup. A positive value moves it to > the left (before), and a negative value

move object - accordion register

I would like to move the accordion register symbol on the left, before the c''. How can I do it? \version "2.21.1" #(use-modules (scm accreg)) { \discant "120" c'''4-232 } Thank you, gianmaria

Re: Tone cluster

> > \toneCluster f' ~ f'' ~ \toneCluster f' f'' > > should work. > Yes, it works :) Thanks Pierre! g.

Re: Tone cluster

Hello Klaus and Pierre, I tried to use your \toneCluster and it works perfectly for me. Now I tried to use \toneCluster with tie like this: \toneCluster f' f'' ~ \toneCluster f' f'' ... and it works well except it only add a single tie at the top. Is there any way to add a lower and upper

Re: italian list or forum

Ciao Federico, [...] As I'm seeing more and more italians here (and also on Frescobaldi > mailing list), I think it's the moment to create a new italian > "community place". > Please let me know if you are interested. > Interested. No preference regarding Mailing list on gnu.org or google

Re: Suggestion to make sharps and flats persistent

My apologies for the text formatting of my last mail. I wrote the message on my mobile phone and didn't notice the formatting issue. >

Re: Suggestion to make sharps and flats persistent

> [...]. That being said… > > Are not > > \relative f' > > and > > \fixed c''' > > just "feature requests for laziness with resulting opaqueness"? ;) [...] > We (well… modulo me LOL) don’t get this worked up about how \relative makes > cut-and-paste a nightmare. Why start now? ;)

Re: Suggestion to make sharps and flats persistent

Hello Paul, > [...]If I'm writing music in F, then I suggest that I be able to use *bF* > as a pitch instead of *bf*. The *F* would indicate that all subsequent *b*s > would be flattened until one is encountered with a different accidental or > until the end of the current music expression. It

Re: Remote Ensemble Playing

> > Does anyone have any idea how these people is able to do things like these? > > https://youtu.be/Sj4pE_bgRQI > https://youtu.be/3eXT60rbBVk > > [...] > > One possibility might be having one instrument play along with the > > conductor video, then have the next musician play along that video >

Re: Remote Ensemble Playing

Ciao Urs! On Wed, 1 Apr 2020 at 09:05, Urs Liska wrote: > Am Mittwoch, den 01.04.2020, 08:51 +0200 schrieb Gianmaria Lari: > > Off topic but very interesting :) > > Does anyone have any idea how these people is able to do things like these? > > https://youtu.be/Sj4pE_bgR

Re: Remote Ensemble Playing

Off topic but very interesting :) Does anyone have any idea how these people is able to do things like these? https://youtu.be/Sj4pE_bgRQI https://youtu.be/3eXT60rbBVk The only information I found is this:

Re: modaltranspose & scheme function

(iota 8) produces (0 1 2 3 4 5 6 7). > (iota 8 0 -1) would produce (0 -1 -2 -3 -4 -5 -6 -7). > oh, great! Thanks Aaron! g.

modaltranspose & scheme function

Long time ago with the help of the people in this forum I have been able to write (to collect) this simple code \version "2.19.82" \include "changePitch.ly" multiModal = #(define-music-function (scale patternRhytmic patternMelodic) (ly:music? ly:music? ly:music?) #{ #@(map(lambda (p)

Re: New release

Ciao Federico, I would be very glad to help. On Thu, 6 Feb 2020 at 17:06, Federico Bruni wrote: > I'm installing on Windows 7 after cleaning a previous very old version. > The default path is C:\Program Files (x86)\LilyPond > ok. > Gianmaria, can you test this issue? >

Re: New release

Hello Phil, I downloaded and I'm trying to install the windows version. Is it normal that 2.19.84 version tries to install itself it in the old folder "LilyPond2.19.83"? Have a look to the attached screenshot. Regards Gianmaria On Thu, 6 Feb 2020 at 14:40, Phil Holmes wrote: > We have just

Re: "\removeWithTag #'x {.....}" more concisely

Ciao Pierre, On Thu, 6 Feb 2020 at 08:52, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > Hi Gianmaria, > How about: rcl = \removeWithTag #'chordLetter \etc > Well, that exactly what I need! Great, thanks a lot. P.S. I have already seen the \etc command but never used and I

"\removeWithTag #'x {.....}" more concisely

I use very often the following instructions in my lilypond code \removeWithTag #'chordLetter {.} where chordletter is a tag I created. Is there any way to write it more concisely like \rcl {...} Thanks a lot, Gianmaria

Re: clusters (accordion)

> > I would like to engrave the cluster symbol in the attached image. > I have been able to do something that is similar. Here it is: \version "2.19.83" { \hide Rest \makeClusters { 8 8} r8 \makeClusters { 8 8} r8 \makeClusters { 8 8} r8 \makeClusters { 8 8} r8 \undo \hide Rest }

Re: beam and partial

Thank you Aaron and Martin. It's very clear. Best regards, g. On Tue, 28 Jan 2020 at 14:25, Aaron Hill wrote: > On 2020-01-28 4:52 am, Gianmaria Lari wrote: > > Just a curiosity. Why lilypond engrave this: > > > > \version "2.19.83" > > {\partial

beam and partial

Just a curiosity. Why lilypond engrave this: \version "2.19.83" {\partial 8*7 g8 8 8 8 8 8 8} like g8[ 8 8] 8[ 8 8 8] I would expect: g8[ 8 8 8] 8[ 8 8] Thanks, g.

clusters (accordion)

I would like to engrave the cluster symbol in the attached image. The excerpt is from the fifth movement of the Zolotaryov accordion kinder suite N1. I don't want to use exactly the same notation: if there is a better one (more modern/standard), that would be ok. Any suggestions? Thank you, g.

Re: $nota ^\markup {M} version 2.19 vs 2.21

On Tue, 26 Nov 2019 at 15:25, David Kastrup wrote: > Gianmaria Lari writes: > > > On Tue, 26 Nov 2019 at 14:14, David Kastrup wrote: > > > >> Thomas Morley writes: > >> > >> > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmar

Re: $nota ^\markup {M} version 2.19 vs 2.21

On Tue, 26 Nov 2019 at 14:14, David Kastrup wrote: > Thomas Morley writes: > > > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari > > : > >> > >> This code works. > >> > >> \version "2.21.0" > >> test = #(define

Re: $nota ^\markup {M} version 2.19 vs 2.21

On Tue, 26 Nov 2019 at 10:53, Thomas Morley wrote: > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari > : > > > > This code works. > > > > \version "2.21.0" > > test = #(define-scheme-function (nota) (ly:music?) > > #{ &g

$nota ^\markup {M} version 2.19 vs 2.21

This code works. \version "2.21.0" test = #(define-scheme-function (nota) (ly:music?) #{ $nota ^\markup {M} #}) {\test c} but it didn't in version 2.19.83. How I should modify it to make it working in 2.19.83? Thank you, g.

Re: tie & tag

Dear Aaron, you wrote: [] > \pushToTag and \appendToTag only work on things that have an elements > property. So that means this expression is valid but useless: > > \pushToTag #'here c' \tag #'here g' I tried to search "Element property" and I found this:

Re: tie & tag

Dear Aaron... > A \tag is not a location per se, but rather it marks the following bit > of music with some identifier. [.] Thanks a lot for your examples, now it's perfectly clear! I post here some other examples inspired by your code. I did my best to write the easiest as possible

Re: tie & tag

On Fri, 22 Nov 2019 at 18:53, Aaron Hill wrote: > On 2019-11-22 7:49 am, Gianmaria Lari wrote: > > I tried (again) with PushToTag with no success. And I don't understand > > why > > it doesn't work. Here it is the code: > > \pushToTag and \appendToTag only work on t

Re: tie & tag

\pushToTag #'tieTag ~ {\tag #'midiOut\tag #'tieTag {} \tag #'screenOut c' } {\tag #'midiOut\tag #'tieTag {} \tag #'screenOut c' } and then to: {c' c'} {~} Where is my mistake? Thank you, g. On Fri, 22 Nov 2019 at 14:01, Gianmaria Lari wrote: > Hello Aaron, > made some tests and I

Re: tie & tag

Hello Aaron, made some tests and I discovered where are the issues. Here is our working code (just a bit simplified): \version "2.21.0" \tagGroup #'(screenOut midiOut) nc = {\tag #'midiOut\tag #'screenOut c' } myScore = {\nc << \nc <>~ >> \nc} \keepWithTag #'screenOut \myScore \keepWithTag

Re: tie & tag

Ciao Aaron, you wrote: > > Here's something you can do in 2.19.83: > > > > > > \version "2.19.83" > > > > \tagGroup #'(screenOut midiOut) > > nc = {\tag #'midiOut \tag #'screenOut c' } > > nd = {\tag #'midiOut \tag #'screenOut d' } > > myScore = {\nc \nd \nc << \nd s~ >> \nd} >

Re: tie & tag

Consider this situation: \version "2.21.00" \tagGroup #'(screenOut midiOut) nc = {\tag #'midiOut \tag #'screenOut c' } nd = {\tag #'midiOut \tag #'screenOut d' } myScore = {\nc \nd \nc \nd~\nd} \score {\keepWithTag #'screenOut \myScore \layout{}} \score {\keepWithTag #'midiOut

Re: tie & tag

On Thu, Nov 21, 2019, 5:35 PM David Kastrup wrote: > Gianmaria Lari writes: > > > I would expect this code > > > > > > \version "2.21.00" > > test = {\tag #'first c' > > \tag #'second e'} > > \keepWithTag #'

tie & tag

I would expect this code \version "2.21.00" test = {\tag #'first c' \tag #'second e'} \keepWithTag #'first {\test~\test} \keepWithTag #'second {\test~\test} ... generates two scores c~c and e~e but it doesn't! It generates c c and e~e Why no ties in the first score? Any "fix"?

Re: acciaccatura & mis-predicted

Thank you Jacques and Harm for your help. I will try to use the previous version. Best regards g.

acciaccatura & mis-predicted

I'm sure this is a trivial issue but I need help to understand why this code... \version "2.21.0" { \acciaccatura cis'8 d'1 \acciaccatura cis'8 d'1 } ... generates this log: [] programming error: mis-predicted force, 108.120472 ~= 108.620856 continuing, cross fingers programming

Re: Tie multiple voice music contained in variable

Ciao Aaron, [] > And you can use tags if you need the tie to be conditional: > > > \version "2.19.83" > > multipleVoiceConditionalTie = \fixed c' { ><< { g4 \tag #'tie a~ \tag #'noTie a } \\ { e2 } >> > } > Yes, I didn't forget tags; but to me they are syntactically difficult to

Re: Tie multiple voice music contained in variable

Ciao Harm, P.S. My apologies if I included the images in the email and not attached it > it's for clarity. Please let me know if you lilypond email users always > prefer to attach images at the end of the messages. > > Please always attach and use plain text ;) > Well, I saw my beard well grown

Re: Tie multiple voice music contained in variable

Thank you! g. On Wed, 13 Nov 2019 at 11:16, Gianmaria Lari wrote: > > On Wed, 13 Nov 2019 at 10:01, Michael Käppler wrote: > >> Hi Gianmaria, >> Interesting, for me running 2.19.80 the first example does not compile, >> either. >> > > Yes, I vaguely

Re: Tie multiple voice music contained in variable

On Wed, 13 Nov 2019 at 10:01, Michael Käppler wrote: > Hi Gianmaria, > Interesting, for me running 2.19.80 the first example does not compile, > either. > Yes, I vaguely remember that version 2.21 manage differently ties/variable. And probably that was the reason why I decided to use it :) >

Tie multiple voice music contained in variable

The following code containing a tie between variables, compiles and works perfectly: \version "2.21.0" pa = {e'1} *{ \pa~\pa } * %here is the tie! Is there any way to do the same in case the variable contains two voices like in the following code? \version "2.21.0" pa = {<< {e'1}\\{c'1}>>} {

prall / mordent with accidentals

What's the standard way to engrave a prall/mordent with accidentals? I found online these two solutions but would like to know if there is anything more "standard". mordentsharp = \mordent _\markup { \tiny \sharp } {a2^\mordentsharp} mordentsharp = ^\markup \left-align \center-column {

Re: Two simultaneous mark events

On Sun, 19 May 2019 at 22:46, Simon Albrecht wrote: > On 18.05.19 18:58, Gianmaria Lari wrote: > > In the past I used some snippet I found on LSR giving the possibility > > to write multiple rehearsal marks, but I was wondering if there is a > > simpler way. Isn't

Two simultaneous mark events

I'm often in this situation: \version "2.21.0" fine = { \once \override Score.RehearsalMark #'break-visibility = #'#(#t #t #f) \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT \mark \markup \italic "Fine" } \fixed c' { c d e f \bar "|." \fine \break \mark A c c c c

Re: fixed vs relative

On Thu, 9 May 2019 at 21:32, David Wright wrote: > On Thu 09 May 2019 at 20:20:36 (+0200), David Kastrup wrote: > > Gianmaria Lari writes: > > > > > I saw the discussion about fixed vs relative few times in the lilypond > ml. > > > > > > I th

Re: fixed vs relative

On Thu, 9 May 2019 at 20:20, David Kastrup wrote: > Gianmaria Lari writes: > > > I saw the discussion about fixed vs relative few times in the lilypond > ml. > > > > I think it's a lot about personal taste and habit and personally I > decided > > to stick t

fixed vs relative

I saw the discussion about fixed vs relative few times in the lilypond ml. I think it's a lot about personal taste and habit and personally I decided to stick to fixed mainly because I find fixing mistakes in relative mode is much more annoying than writing in fixed way But what if the

Re: chord and chordChanges

On Thu, 9 May 2019 at 14:18, David Kastrup wrote: > Gianmaria Lari writes: > > >> > >> > >> \version "2.21.0" > >> << > >> \new Staff { > >> c'4 d' e' f' > >> \repeat volta 2 {c' d' e' f' | g'

Re: chord and chordChanges

> > > \version "2.21.0" > << > \new Staff { > c'4 d' e' f' > \repeat volta 2 {c' d' e' f' | g' a' b' c''} > } > \new ChordNames \with { chordChanges = ##t } { > g1 \once \unset chordChanges \repeat volta 2 {g1|1} > } > >> > Thank you David, this is what I wanted! In the

chord and chordChanges

Following code prints chord even if they don't change. \version "2.21.0" << \new Staff { c'4 d' e' f' \repeat volta 2 {c' d' e' f' | g' a' b' c''} } \new ChordNames { g1 \repeat volta 2 {g1|1} } >> To avoid to print chords always, I used \set chordChanges = ##t. but I

Re: fingering

Dear Robin you wrote: > [...] You should limit lilypond to one staff by saying > \new Staff << \myMusic \myFing >> > > > That looks better, but it is still not equivalent. > Try changing the s-2 to s_2: > the notehead and the fingering collide. > To avoid that you should also limit lilypond

Re: fingering

I found some solution that I post here to get some feedback and/or other suggestions. Here they are 4 different ways to add fingering to a musical expression: *1 Standard:* \version "2.21.0" \fixed c' {a-1 c' f'-\finger\markup\circle 3 a'-4} *2 Different context *(thanks Pierre

Re: fingering

Ciao Stephane! On Mon, 6 May 2019 at 11:23, Stephan Schöll wrote: > Despite of my newbie status on the list, let me ask back: > > What's your intention with separating dynamics, the notes and the > fingerings? > > If the separation is only for displaying purposes in a specific staff, I > would

Re: fingering

On Mon, 6 May 2019 at 11:16, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > Hi Gianmaria, > I suppose you'll have to create/modify your own contect, say > 'Fingerings, such as : > > \version "2.21.0" > myMusic = {a4 b c' d'} > myFing = {s4-1 s-2 s-3 s-4} > << >

fingering

I normally enter fingering instruction using the "note-digit" convention ( http://lilypond.org/doc/v2.18/Documentation/notation/inside-the-staff#fingering-instructions) like this: \version "2.21.0" {a4-1 b-2 c'-3 d'-4} This way of proceeding it's in my opinion the easiest and less error prone

Re: move rehearsal marks

Thank you Malte!! That's perfect! g. On Sun, 5 May 2019 at 08:36, Malte Meyn wrote: > > > Am 05.05.19 um 07:48 schrieb Gianmaria Lari: > > How I can move a bit on the left the rehearsal mark "A" to make it > > taking less vertical space? > > I’d use X-offset

move rehearsal marks

Sorry to ask this basic question. How I can move a bit on the left the rehearsal mark "A" to make it taking less vertical space? \version "2.21.0" { \ottava 1 a'''1 1 1 1 \break \mark A 1 1 1 1^3 \break } Thank you, g. ___ lilypond-user mailing

Re: tag issue

On Sat, 13 Apr 2019 at 13:06, Thomas Morley wrote: > Am Sa., 13. Apr. 2019 um 12:20 Uhr schrieb Gianmaria Lari > : > > > > Harm, if I understood corretly the code: > > > > \version "2.18.2" > > \tagGroup #'(testOne testTwo) > > > &g

Re: tag issue

Harm, if I understood corretly the code: \version "2.18.2" \tagGroup #'(testOne testTwo) music = { \tag #'testOne a \tag #'testTwo b } \keepWithTag #'testOne {\music~\music} is converted to: \keepWithTag #'testOne { \tag #'testOne a \tag #'testTwo b ~ \tag #'testOne a \tag

Re: tag issue

On Sat, 13 Apr 2019 at 11:41, Thomas Morley wrote: > Am Sa., 13. Apr. 2019 um 11:16 Uhr schrieb Gianmaria Lari > : > > > > I don't understand the following behaviour: > > > > \version "2.18.2" > > \tagGroup #'(testOne testTwo) > > > >

  1   2   3   4   5   6   >