Re: LilyPond 2.23.6 released

2022-02-17 Thread Thomas Scharkowski
I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. Thomas > Am 17.02.2022 um 00:45 schrieb Jean Abou Samra : > > Le 16/02/2022 à 15:37, Thomas Scharkowski a écrit : >> Hi all, >> >> I installed this ver

Naming midi files

2022-02-17 Thread Mark Probert
Hi. If I have a book that is structured something like below, then LP produces two midi files: foo.midi and foo-1.midi. Is there a way I can coerce the names into "bar.midi" and "baz.midi" within LP? Or is this something best down externally? Thanks again ..mark. -- foo.ly \include "bar.

Re: Slur in different voices

2022-02-17 Thread Leo Correia de Verdier
Hi Mark! Generally I work around this using hidden notes or notes with hidden stems. In your example I think you want a tie rather than a slur (since it’s a held note), but they both work in the same way with regard to voices. In your example it could look like: \version "2.22" lowerA = \new

Re: Naming midi files

2022-02-17 Thread Michael Gerdau
If I have a book that is structured something like below, then LP produces two midi files: foo.midi and foo-1.midi. Is there a way I can coerce the names into "bar.midi" and "baz.midi" within LP? Or is this something best down externally? [example code snipped] RTFM: https://lilypond.org/doc/v

Re: Naming midi files

2022-02-17 Thread Michael Gerdau
It’s not that simple, since in the example all the scores are in the same book. It is that simple. Put the score in one book and the midis separate books and done. Or that is how I understand the manual. Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on r

Re: Naming midi files

2022-02-17 Thread Leo Correia de Verdier
It’s not that simple, since in the example all the scores are in the same book. > 17 feb. 2022 kl. 09:58 skrev Michael Gerdau : > >> If I have a book that is structured something like below, then LP >> produces two midi files: foo.midi and foo-1.midi. >> Is there a way I can coerce the names into

Re: Naming midi files

2022-02-17 Thread Mark Probert
You wrote: >> It’s not that simple, since in the example all the scores are in the >> same book. > > It is that simple. > Put the score in one book and the midis separate books and done. > My understanding is a \midi{} block is contained within a \score{} block. The structure I have is \book

Re: Naming midi files

2022-02-17 Thread Xavier Scheuer
On Thu, 17 Feb 2022 at 09:37, Mark Probert wrote: > > > Hi. > > If I have a book that is structured something like below, then LP > produces two midi files: foo.midi and foo-1.midi. > > Is there a way I can coerce the names into "bar.midi" and "baz.midi" > within LP? Or is this something best down

Re: Naming midi files

2022-02-17 Thread Leo Correia de Verdier
You would have to structure your files and variables differently, for instance something like (in pseudocode): — foo.ly \include "bar.ily" \include ”baz.ily” \book { \bookpart { \header { title = "Bar One" } \score { \barMusic \layout{} } } \bookpart {

Re: Naming midi files

2022-02-17 Thread Lukas-Fabian Moser
Folks, Am 17.02.22 um 11:48 schrieb Xavier Scheuer: > If I have a book that is structured something like below, then LP > produces two midi files: foo.midi and foo-1.midi. > > Is there a way I can coerce the names into "bar.midi" and "baz.midi" > within LP? Or is this something best down externa

2,23,6 markFormatter change?

2022-02-17 Thread Paul Scott
2.23.6 I have been using the following definition for many years: CircleNumberMark = {   \set Score.markFormatter = #format-mark-circle-numbers } I now get: warning: cannot find property type-check for `markFormatter' (translation-type?).  perhaps a typing error? from one score where I may

Re: 2,23,6 markFormatter change?

2022-02-17 Thread Jean Abou Samra
> Le 17/02/2022 18:09, Paul Scott a écrit : > > > 2.23.6 > > I have been using the following definition for many years: > > CircleNumberMark = { > \set Score.markFormatter = #format-mark-circle-numbers > } > > I now get: > > warning: cannot find property type-check for `markFormatter' > (tra

Ossia at the first line of a PianoStaff

2022-02-17 Thread Knute Snortum
I have another problem that I'd love help with. (Sorry for all the questions lately.) The piece of music I'm working on is a piano piece with several ossia bars. I've been researching how to do this and I've come across a problem I can't fix. If the ossia bar is the first bar of a new line, the

Red dot before all notes

2022-02-17 Thread Rajesh Baskar
Hi, I'm trying to get a red dot placed before each note. I have tried using \tweak and \set fingeringOrientations = #'(left) \finger  \markup \with-color "#FF"  "." But nothing seems to give the desired results. The below image is what I'm trying to get. \version "2.22.0" \include "en

Re: Red dot before all notes

2022-02-17 Thread Jean Abou Samra
Hi, One thing you may not be aware of is that when you reply to an existing thread, the reply appears in the same thread for others, even if you change the title. I saw your message under "Box around MeasureCounter". It is better to start a new topic instead. Le 17/02/2022 à 19:21, Rajesh Baska

Re: Ossia at the first line of a PianoStaff

2022-02-17 Thread Jean Abou Samra
Le 17/02/2022 à 19:01, Knute Snortum a écrit : I have another problem that I'd love help with. (Sorry for all the questions lately.) The piece of music I'm working on is a piano piece with several ossia bars. I've been researching how to do this and I've come across a problem I can't fix. If

Re: LilyPond 2.23.6 released

2022-02-17 Thread Jean Abou Samra
Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit : I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. You did see all the logging output with warnings about 'possibly unbound variables' and stuff?

Re: Naming midi files

2022-02-17 Thread David Wright
On Thu 17 Feb 2022 at 21:43:09 (+1100), Mark Probert wrote: > [ ] wrote: > >> It’s not that simple, since in the example all the scores are in the > >> same book. > > > > It is that simple. > > Put the score in one book and the midis separate books and done. > > > My understanding is a \midi{} b

Re: Possible bug: Grace note at the beginning makes instrumentName disappear?

2022-02-17 Thread Valentin Petzel
Hello Thomas, in your case using a with block is definitely the best option. One can also solve such issues by adding a skip column before the main beat like this \new Staff << {\set Staff.instrumentName = #"abc" \grace s} \new Voice \grace c c >> which can be useful with stuff like tempo in a

Splitting voices

2022-02-17 Thread E Appeldoorn
I have a score consisting of 5 strings. Near the end all instrument voices (except the bass) split into two. The top voice being a solo, and the bottom one the rest. I have managed this for one voice, but can't figure out how to add second violin, viola, and cello in the same manner, then addin

Re: Splitting voices

2022-02-17 Thread Lukas-Fabian Moser
Hi Erik, I have a score consisting of 5 strings. Near the end all instrument voices (except the bass) split into two. The top voice being a solo, and the bottom one the rest. I have managed this for one voice, but can't figure out how to add second violin, viola, and cello in the same manner,

Re: Add text to score without affecting spacing

2022-02-17 Thread Jean Abou Samra
Le 16/02/2022 à 15:26, Kieren MacMillan a écrit : Hi Aaron, There are a number of grobs that normally have no visual representation. You could attach your content there This is really clever! Can you imagine *any* possible downside to this approach? I think it depends on the use case. For

Re[2]: Splitting voices

2022-02-17 Thread E Appeldoorn
Thanks Lukas, I would never have figured that out. -- Origineel bericht -- Van: "Lukas-Fabian Moser" Aan: "E Appeldoorn" ; "Lilypond" Verzonden: 17-2-2022 22:08:09 Onderwerp: Re: Splitting voices Hi Erik, I have a score consisting of 5 strings. Near the end all instrument voices (

Re: Add text to score without affecting spacing

2022-02-17 Thread Jean Abou Samra
Le 10/02/2022 à 01:08, Kieren MacMillan a écrit : \markup \with-dimensions-from \null "foobar" By the way: pedantically, I would recommend \markup \with-dimensions #empty-interval #empty-interval "foobar" or \markup \with-dimensions-from \stencil #empty-stencil "foobar" or \markup \with-outli

Re: Add text to score without affecting spacing

2022-02-17 Thread Valentin Petzel
Hello Jean, thank you for that insight. I have been using \with-dimension #'(0 . 0) #'(0 . 0) on RehearsalMark grobs so far. The use case here is generation of playing animation. Basically I am using an engraver to print information about the current position into the score, which is then outpu

Re: Naming midi files

2022-02-17 Thread Mark Probert
Thank you, everyone, especially to David for the study code. All this info is greatly appreciated! .. mark.

Re: Add text to score without affecting spacing

2022-02-17 Thread Kieren MacMillan
Hi Jean, > By the way: pedantically, I would recommend Thanks for that. > Basically, \null leads to point-stencil, which has > the extent '(0 . 0) on both axes -- a single-point > interval. That's small, but not totally empty. > empty-interval is '(+inf.0 . -inf.0) which is truly > empty, and th

Re: Ossia at the first line of a PianoStaff

2022-02-17 Thread Knute Snortum
On Thu, Feb 17, 2022 at 11:32 AM Jean Abou Samra wrote: > > Le 17/02/2022 à 19:01, Knute Snortum a écrit : > > I have another problem that I'd love help with. (Sorry for all the > > questions lately.) > > > > The piece of music I'm working on is a piano piece with several ossia > > bars. I've be

Re: Ossia at the first line of a PianoStaff

2022-02-17 Thread Jean Abou Samra
Le 18/02/2022 à 00:43, Knute Snortum a écrit : On Thu, Feb 17, 2022 at 11:32 AM Jean Abou Samra wrote: Thanks, that gets rid of the brace. Is there any way to get rid of the bar span that connects the ossia staff to the piano staff? Alright, I was too focused on the bracket. I'm tired, so I

Re: Add text to score without affecting spacing

2022-02-17 Thread Jean Abou Samra
Le 17/02/2022 à 22:58, Kieren MacMillan a écrit : Hi Jean, By the way: pedantically, I would recommend Thanks for that. Basically, \null leads to point-stencil, which has the extent '(0 . 0) on both axes -- a single-point interval. That's small, but not totally empty. empty-interval is '(+in

Re: Ossia at the first line of a PianoStaff

2022-02-17 Thread Knute Snortum
On Thu, Feb 17, 2022 at 4:01 PM Jean Abou Samra wrote: > > Le 18/02/2022 à 00:43, Knute Snortum a écrit : > > On Thu, Feb 17, 2022 at 11:32 AM Jean Abou Samra wrote: > > Thanks, that gets rid of the brace. Is there any way to get rid of > > the bar span that connects the ossia staff to the piano