Re: registering a composition

I am replying here in the middle of the thread, because I decided to opt for an open source license after reading the considerations in this email. The source is available here: https://github.com/fpetrogalli/trr Thank you Valentin for "opening the can of worms". It's been very informative. I

Re: Adding a line break on \breve note

Here it goes; VerseOne = \lyricmode { \set stanza = "1." \override LyricText.self-alignment-X = #LEFT \markup \override #'(line-width . 66) \column { \line { Lorem ipsum dolor sit amet, consectetuer adipiscing elit.+ } \fill-line { \null "Etiam

GitLab access

On 2020-05-26 4:13 pm, Valentin Villenave wrote: It may indeed be more useful if added to the NR; I’ve just written a patch with that mind: https://gitlab.com/lilypond/lilypond/-/merge_requests/91 BTW Xavier, if you have a GitLab account and whish to gain access to the tracker and patch

Re: Hide a particular bar number

Hi Nikita, Please check: http://lilypond.org/tiny-examples.html How about: \version "2.20.0" { c'1 \once\omit Score.BarNumber \break \cadenzaOn 1 \cadenzaOff \bar "" \break 1 } HTH, Cheers, Pierre Le mar. 26 mai 2020 à 23:25, Nikita Sorokine a écrit : > Hello! > > I have a long bar

Re: Some new tutorials in Spanish

On 5/26/20, Francisco Vila wrote: > I'd like to share my last attempt of a series of ultra-fast tutorials in > Spanish. That’s great! (At least, I’m sure it is :-) BTW, if you have an account on GitLab, feel free to let us know so that you can be added and gain access to the tracker, merge

Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.

On 5/26/20, Xavier Scheuer wrote: > I have used several times the technique mentioned on this list and > documented only in the regression test ‘divisi-staves.ly’. It may indeed be more useful if added to the NR; I’ve just written a patch with that mind:

Re: Identify included files

On Tue 26 May 2020 at 13:06:50 (-0400), Fr. Samuel Springuel wrote: > > On 26 May, 2020, at 12:09 PM, Timothy Lanfear wrote: > > > > Maybe this code can give some hints on how to decide if midi is being > > produced. > > That’s the first code I’ve seen that’s been able to definitively show

Re: Some new tutorials in Spanish

El 26/5/20 a las 22:29, Caio Barros escribió: That's very nice, Francisco. I think this is a very important thing for the LilyPond community to have. I found that you took very seriously the "ultra-fast" part. Sometimes I feel it is too fast. For instance when you begin to explain the clefs

Hide a particular bar number

Hello! I have a long bar (cadenza) in my score and I would like to prevent the number of this particular bar to be printed. Thanks in advance, Nikita

Re: vertical spacing - distance staff and group

Dear Hans van Eck, you can add this to the \with block of your altoSaxPart: \override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #30 The following overview could have helped you to find the right command: https://joramberger.de/files/LilypondSpacing.pdf Best, Joram

vertical spacing - distance staff and group

Spacing question: does anyone know how you can change the vertical spacing between the Altsax and the Piano? (lift it a bit) I tried all kind of edits copied from the manual but I could only change the spacing inside the piano-group. How do you do that? Thanks, Hans van Eck code: \paper {

Re: Adding a line break on \breve note

Ok, I see, that my request was not described well enough. So, what I want to achieve is visible on picture: Thank for advices. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: Some new tutorials in Spanish

Em ter., 26 de mai. de 2020 às 14:08, Francisco Vila escreveu: > Hello, > > I'd like to share my last attempt of a series of ultra-fast tutorials in > Spanish. > > I realize they are not useful at all for experienced users (obviously) > and maybe also not that useful for absolute novices. But

Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.

On 5/26/20, Lib Lists wrote: > For example, I'd start with the concertmaster's part, then duplicate > it and edit it to generate the music the second soloist, then the > other soloists, then desks, divisi and so on. Greetings, I wouldn’t recommend to “duplicate” any code. As Xavier said, you can

Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.

Hi, thanks for your answer. During the past days I've been looking at this same technique, the only problem is that I cannot find a way to merge the different voices into one, for example in the first system. In an ideal world, I'd like to have the ability to tell Lilypond that a certain passage

Re: Getting started with Scheme

On 5/26/2020 12:06 PM, antlists wrote: On 23/05/2020 11:37, Kevin Barry wrote: OK. Is there a common way to accomplish the old Start -> Run -> type in the name of a program? If you just want to run a program that's in your search path, it's been the same since Windows 7 or even earlier - -R.

Some new tutorials in Spanish

Hello, I'd like to share my last attempt of a series of ultra-fast tutorials in Spanish. I realize they are not useful at all for experienced users (obviously) and maybe also not that useful for absolute novices. But it's been fun doing them, and I'll hopefully cover the basic features of

Re: Identify included files

> On 26 May, 2020, at 12:09 PM, Timothy Lanfear wrote: > > Maybe this code can give some hints on how to decide if midi is being > produced. That’s the first code I’ve seen that’s been able to definitively show when a midi file is being produced. Thank you. Now, there is the issue of it

Re: Getting started with Scheme

On 23/05/2020 11:37, Kevin Barry wrote: My copy of windows doesn’t have a*Start* menu: so that’s another instruction that is meaningless. OK. Is there a common way to accomplish the old Start -> Run -> type in the name of a program? Windows 10 has a (sort of) start menu - click on the

Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.

On Tue, 26 May 2020 at 18:12, Lib Lists wrote: > > [...] > > However, I know that \partcombine doesn't accept more than two voices, > so I guess I cannot (hypothetically) combine all the voices together > and let Lilypond sort out when the voices contain the same or > different materials and

Re: Are Lilyponds beams thick enough?

On 5/26/20, 1:14 AM, "David Kastrup" wrote: writes: >> Hello Valentin, >> >> For an unknown reason (at least unknown to me), LilyPond's default >> beam-thickness is 0.48 staff spaces. > > 0.5 would likely result more often in beam thicknesses getting rounded > up sometimes, down at other

Orchestral strings, how to organise score and parts for divisi, solos, desks etc.

Hello everybody, a long-time user here, never been a power user though, but I'm back to Lilypond after quite many years. I'm considering the possibility of notating a future orchestral project using Lilypond. As I never used it for anything bigger than chamber music, I'm learning how to organise a

Re: Identify included files

On 26/05/2020 16:15, Fr. Samuel Springuel wrote: I’ve already accounted for this in my most recent version of parse-only.ly. It’s not as straight forward as ly:source-files but by looking at (ly:get-option 'backend), (ly:get-option 'aux-files), (ly:parser-output-name) and (ly:output-formats),

Re: Identify included files

> On 26 May, 2020, at 6:18 AM, Matt Wallis wrote: > > For C/C++, there is an excellent discussion of the issues about automatically > producing dependencies and dealing with them in make: > > http://make.mad-scientist.net/papers/advanced-auto-dependency-generation/ > > I think much of this is

Re: Getting started with Scheme

Hi John Thanks for this. It's good to know it works for someone. I'll keep on trying. Paul On Sat, 23 May 2020 at 15:35, John Schlomann wrote: > Paul, > > I'm a Windows 10 user. (I'm hoping to get my Linux system rebuilt one of > these days.) I currently use LilyPond 2.20.0. > > My

Re: Adding a line break on \breve note

Le mar. 26 mai 2020 à 12:34, Frimlik a écrit : > Actually, as I can see, the first verse is split into 4 lines, I'd like to > have only 2 lines split by the '+' sign. > Simply change the line lenght, e.g.: VerseOne = \lyricmode { \set Lyrics.stanza = "1." \override

Re: Adding a line break on \breve note

Am Di., 26. Mai 2020 um 12:34 Uhr schrieb Frimlik : > > Actually, as I can see, the first verse is split into 4 lines, I'd like to > have only 2 lines split by the '+' sign. > Idea with vertical offset is interesting. > > > > -- > Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html >

Re: Are Lilyponds beams thick enough?

Am Dienstag, den 26.05.2020, 13:18 +0200 schrieb Valentin Petzel: > Hello other Valentin, hello David, hello Torsten. > > The 0.55ss is taken to mimick the 1958 Bärenreiter edition, although > I would > rather take a slightly thinner Beam with slightly reduced height. And > it > depends

Re: Adding a line break on \breve note

Actually, as I can see, the first verse is split into 4 lines, I'd like to have only 2 lines split by the '+' sign. Idea with vertical offset is interesting. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: Identify included files

> Le 15 mai 2020 à 18:03, Fr. Samuel Springuel a écrit : > >> On 15 May, 2020, at 3:43 AM, Valentin Villenave wrote: >> >> On 5/15/20, Fr. Samuel Springuel wrote: >>> Before I start writing a script to do this, is there an existing tool which >>> will identify all the `\include` files that a

Re: AW: Are Lilyponds beams thick enough?

On 5/26/20, David Kastrup wrote: > 0.5 would likely result more often in beam thicknesses getting rounded > up sometimes, down at other times, making for an uneven look after > digitisation. You’re right in theory, but that doesn’t sound like a convincing argument within the LilyPond ideological

Re: AW: Are Lilyponds beams thick enough?

writes: > Hello Valentin, > > For an unknown reason (at least unknown to me), LilyPond's default > beam-thickness is 0.48 staff spaces. 0.5 would likely result more often in beam thicknesses getting rounded up sometimes, down at other times, making for an uneven look after digitisation. --

AW: Are Lilyponds beams thick enough?

Hello Valentin, For an unknown reason (at least unknown to me), LilyPond's default beam-thickness is 0.48 staff spaces. The common standard, however, seems to be 0.5 staff spaces (Finale, Sibelius, Dorico, ...) and, most importantly, Elaine Gould ("Behind Bars") suggests 0.5 staff spaces.