PianoStaff and StaffGroup brackets are truncating single line DrumStaff at top left of staff system.

Hi, I want to create a StaffGroup that includes a single line Staff or DrumStaff at the top. I am having the problem that the left most measure bar line and the brackets of each staff system are being truncated down to the staff line of the single staff. I have tried a workaround by making a

Re: PianoStaff and StaffGroup brackets are truncating single line DrumStaff at top left of staff system.

dfro writes: > Hi, > > I want to create a StaffGroup that includes a single line Staff or > DrumStaff at the top. I am having the problem that the left most > measure bar line and the brackets of each staff system are being > truncated down to the staff line of the single staff. > > I have tried

Re: PianoStaff and StaffGroup brackets are truncating single line DrumStaff at top left of staff system.

Am 22.03.2018 um 15:22 schrieb David Kastrup: I am not fixing the awful things your mail program did to your code (consider using an attachment instead). Off-topic: To me it seems as if it was your mail program that did awful things. Mine displays the code (including long lines) correctly.

Re: PianoStaff and StaffGroup brackets are truncating single line DrumStaff at top left of staff system.

Hi Malte, > Mine displays the code (including long lines) correctly. Same here. And the archive (http://lists.gnu.org/archive/html/lilypond-user/2018-03/msg00571.html) looks okay as well. Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣

Merging paper blocks

Hi all, some time ago I got assistance for merging layout blocks that were stored in a list. The code I used (and which works, although I don't fully understand it) is something like this: ((layout-diffs (append-map (lambda (output-def) (lset-difference equ

Is lilypond suitable for big composition projects?

That may seem like a stupid question, but I've been using LilyPond with Frescobaldi for a year and a half, but I start to ask myself if it is as efficient as if I had used another tool like Musescore. I explain: I don't have at all a powerful computer, and I think that an essential feature that I

Is lilypond really suitable for composing?

That may seem like a stupid question, but I've been using LilyPond with Frescobaldi for a year and a half, but I start to ask myself if it is as efficient as if I had used another tool like Musescore. I explain: I don't have at all a powerful computer, and I think that an essential feature that I

Add interval to selection - Frescobaldi snippet

Hi there! I am looking for a Frescobaldi snippet/functionality (Pyhthon script I assume) that would add an interval to a selected note (or selection of notes/chords). Something similar to the transpose function that is integrated, but adding the transposition to existing music to form a chord. Fo

Re: PianoStaff and StaffGroup brackets are truncating single line DrumStaff at top left of staff system.

On Thu 22 Mar 2018 at 10:53:49 (-0400), Kieren MacMillan wrote: > Hi Malte, > > > Mine displays the code (including long lines) correctly. > > Same here. And the archive > (http://lists.gnu.org/archive/html/lilypond-user/2018-03/msg00571.html) looks > okay as well. The message was sent with th

Re: Is lilypond suitable for big composition projects?

Composition tactics are a very individual to a persons habits and skill sets. I use LilyPond for composing intermittently. If it is in my head and needs to be set down it is useful. If I am actively trying to work something out; I work with paper and pencil or pen, as nothing beats that for efficie

Re: Is lilypond suitable for big composition projects?

Hi Jonas, If every compilation is taking that long, maybe you are compiling several movements each time? In case you are, you can comment out the parts of the music that you are not working with to make the whole thing more agile, I do this with multi-movement works. Unfortunately I can't offer y

Re: Is lilypond suitable for big composition projects?

In my opinion, Lilypond is excellent for writing sheet music, but not very good for composing. I usually use MuseScore or Qtractor for composing, then (manually) convert it to Lilypond to make sheet music. On 03/22/18 16:35, Jonas Daverio wrote: > That may seem like a stupid question, but I've b

Re: Is lilypond suitable for big composition projects?

Jonas Daverio writes: > That may seem like a stupid question, but I've been using LilyPond with > Frescobaldi for a year and a half, but I start to ask myself if it is as > efficient as if I had used another tool like Musescore. > > I explain: I don't have at all a powerful computer, and I think

Re: Is lilypond suitable for big composition projects?

Stefano Troncaro wrote > Hi Jonas, > > If every compilation is taking that long, maybe you are compiling several > movements each time? In case you are, you can comment out the parts of the > music that you are not working with to make the whole thing more agile, I > do this with multi-movement wo

Re: Tie/Accidental Collision

@Kieren > But I would suggest not having the Stem whiteout affect the StaffSymbol… > It's probably enough just to write > I'm sorry, I do not understand this, it seems that I'm missing some important information. Could you elaborate a bit? Maybe use the \shape function? > I thought that \shape

Re: Is lilypond really suitable for composing?

On Thu, 2018-03-22 at 08:08 -0700, jtruc34 wrote: > That may seem like a stupid question, but I've been using LilyPond > with > Frescobaldi for a year and a half, but I start to ask myself if it is > as > efficient as if I had used another tool like Musescore. > > I explain: I don't have at all a

Re: Is lilypond suitable for big composition projects?

Am 22.03.2018 um 17:31 schrieb jtruc34: Yes, I'm already using the trick \set Score.skipTypesetting = ##f, but it is not so convenient. You could look into these two packages: https://github.com/openlilylib/partial-compilation (which is unfortunately totally undocumented, but you can have a l

Re: Is lilypond really suitable for composing?

-- Forwarded message -- > From: Jonas Daverio > To: lilypond-user@gnu.org > Subject: Is lilypond suitable for big composition projects? > That may seem like a stupid question, but I've been using LilyPond with > Frescobaldi for a year and a half, but I start to ask myself if it i

Re: Is lilypond suitable for big composition projects?

Am 22.03.2018 um 16:35 schrieb Jonas Daverio: That may seem like a stupid question, but I've been using LilyPond with Frescobaldi for a year and a half, but I start to ask myself if it is as efficient as if I had used another tool like Musescore. My answer tends to be "no". While I usually en

Re: Is lilypond suitable for big composition projects?

On 3/22/2018 10:35 AM, Jonas Daverio wrote: I've been using LilyPond with Frescobaldi for a year and a half, but I start to ask myself if it is as efficient as if I had used another tool like Musescore. The Musescore features that show and play notes as they are entered are very nice. I can s

Re: Tie/Accidental Collision

2018-03-22 17:33 GMT+01:00 Stefano Troncaro : > @Kieren >> >> Maybe use the \shape function? > > > I thought that \shape didn't work inside chords? Hi, you may be interested in this thread: http://lilypond.1069038.n5.nabble.com/Lilypond-ignores-some-shape-commands-in-chords-td210858.html Cheers,

Re: Add interval to selection - Frescobaldi snippet

2018-03-22 16:22 GMT+01:00 aeoleandust : > Hi there! > > I am looking for a Frescobaldi snippet/functionality (Pyhthon script I > assume) that would add an interval to a selected note (or selection of > notes/chords). Something similar to the transpose function that is > integrated, but adding the

Re: Is lilypond really suitable for composing?

I've been using lilypond for a much shorter time, but my impression is that lilypond excels when you know exactly what you want to input. It's also difficult to work on different parts of the score unless you set up some sort of system to break the piece into smaller chunks. So I've been doing mor

Re: Is lilypond suitable for big composition projects?

On 23 March 2018 at 03:24, Stefano Troncaro wrote: > Hi Jonas, > > If every compilation is taking that long, maybe you are compiling several > movements each time? In case you are, you can comment out the parts of the > music that you are not working with to make the whole thing more agile, I > d

Re: Tie/Accidental Collision

Hi Stefano, >> But I would suggest not having the Stem whiteout affect the StaffSymbol… >> It's probably enough just to write > I'm sorry, I do not understand this, it seems that I'm missing some important > information. Could you elaborate a bit? Hmmm… When I first compiled your code, the Stem

Re: Is lilypond really suitable for composing?

On Fri, 23 Mar 2018, 08:08 Nathan Sprangers, wrote: > I've been using lilypond for a much shorter time, but my impression is > that lilypond excels when you know exactly what you want to input. It's > also difficult to work on different parts of the score unless you set up > some sort of system t

get current bar number

Hi All, I would like to be able to get the current bar number context property so that I can do something with it (like printing it in markup for example). I have tried the following scheme function: (ly:context-property 'Score 'currentBarNumber) but it errors out, telling me that Score is not a

Re: Tie/Accidental Collision

Hi Harm, that's *so *useful to me, thank you so much for stepping in and sharing that conversation!!! I really think that information should be available in the tie-column-interface section

Re: Is lilypond really suitable for composing?

I have always found that nothing beats plain pencil and sheets of staff paper, until I have the basic piece fairly complete. For me, it's clearly faster to make even a second draft on paper than to move at that point to LP and continue from there. I consider fast "hand writing" on staff paper to be

Re: get current bar number

Hi Kevin, yes, you need to get a context object. If you want to use it inside some music expression \applyContext is the key: doSomething = \applyContext #(lambda (context) (display (ly:cont