Re: Lilypond

[Valentin Petzel]

Hi Laurent,

It is correct that all notes belonging to the same chord do have the same duration (though it is possible to change the note head for some notes to that of a different duration). Note that this behaviour is something you get from pretty much all notation softwares. If you want to notate parallel lines of different rhythm you should look into the handling of voices, see here https://lilypond.org/doc/v2.22/Documentation/notation/multiple-voices or even the whole section in the manual about simultaneous notes:

https://lilypond.org/doc/v2.22/Documentation/notation/simultaneous-notes

Generally I’d suggest you to read chaper 1 of the manual, as this will cover most of the basic requirements you’ll have.

Cheers,

Valentin

Am Sonntag, 18. September 2022, 16:22:02 CEST schrieb pagani laurent:

> Hi Valentin,

>

> I have macported Frescobaldi and started to play with it.

> I don’t find it very explicit for the errors, and while it complains there

> are errors it still displays the result (more or less). The really positive

> point is indeed to show the notes between the pdf and the .ly. It has also

> the advantage to not duplicate the pdf file like Lily does each time one

> compiles. One has quickly 10 or 20 copies of the same file opened in

> Preview… Unlike Latex editors (texstudio, or texshop e.g.), it does not

> have the list of reserved words/commands in lateral menus to retrieve

> quickly something you don’t remember. But I guess there are not so many

> things to remember at the end though I find some combinations a bit tricky.

>

> I met another problem which is that Lily forces chords to have the same

> duration for all notes. Maybe it is because I have not read the advanced

> manual yet. From what I’ve learned until now, I tried to guess a way out

> like : < c2 {e4 r}> but it does not work. It is possible ? It is very

> common to have notes of different durations running in parallel in the same

> staff.

>

> Best

> Laurent

>

> PS: Thanks for the file.

>

> > Le 18 sept. 2022 à 16:06, Valentin Petzel <valentin@petzel.at> a écrit :

> >

> > Hi Laurent, Hi Pierre,

> >

> > usually using Bar checks is the way to go, but this does have its own

> > limitations. E.g. if we misspell

> >

> > \time 3/4 c2 d4 |

> >

> > as

> >

> > \time 3/4 c2 d1 |

> >

> > this will not throw an error. Of course we could make use of bar number

> > checks. But then, bar number checks only work if you know what bar you are

> > in, and bar checks only work if you know what time signature you’re in.

> >

> > But it is not hard to add additional checks. The appended file defines a

> > pseudoengraver that checks for each placed rhythmic head if there is

> > sufficient remaining space left in the measure and issues a warnign

> > otherwise.

> >

> > Cheers,

> > Valentin

> >

> > Am Sonntag, 18. September 2022, 11:15:20 CEST schrieb Pierre Perol-Schneider:

> >> Hi Laurent, Hi Jan,

> >> @Laurent, see:

> >> https://lilypond.org/doc/v2.22/Documentation/notation/bars.html#bar-and-b

> >> ar-> number-checks e.g.: \version "2.22.0"

> >> { c' e' g' e'1 | <e e''' e''>2 <e e''' e''> }

> >> Cheers,

> >> Pierre

> >>

> >> Le dim. 18 sept. 2022 à 11:02, Jan Nieuwenhuizen <janneke@gnu.org> a écrit :

> >>> pagani laurent writes:

> >>>

> >>> Can someone answer Laurent?

> >>>

> >>>> Hi Jan,

> >>>>

> >>>> Sorry to disturb you (possibly I should have gone to some forum but

> >>>> this is so fundamental for me that if the answer is no, I won’t use

> >>>> Lilypond, so I don’t want to bother entering the forum if it is to

> >>>> leave it immediately).

> >>>>

> >>>> I am having a look at Lilypond and I have a very simple question :

> >>>> I wrote a very simple test score :

> >>>>

> >>>> \version "2.22.0"

> >>>> {

> >>>> c' e' g' e'1 <e e''' e''>2

> >>>> }

> >>>>

> >>>> and the compilation ran without error :

> >>>>

> >>>> Traitement de « /Users/laurent/Desktop/test.ly »

> >>>> Analyse...

> >>>> Interprétation en cours de la musique...

> >>>> Pré-traitement des éléments graphiques...

> >>>> Détermination du nombre optimal de pages...

> >>>> Répartition de la musique sur une page...

> >>>> Dessin des systèmes...

> >>>> Conversion à « test.pdf »...

> >>>> Compilation menée à son terme, avec succès.

> >>>>

> >>>> However, there is an obvious error : the e’1.

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Does this mean that Lilypond will not report such errors when writing

> >>>> a score ? That would be worrysome because that means that after having

> >>>> written tons of pages, one has to go through the final product to

> >>>> check for such errors and then locate them in the input file (I guess

> >>>> there is no such interface as with some Latex editor where the pdf and

> >>>> the latex are linked so that clicking on the pdf text, you are

> >>>> directed to the corresponding latex code) which might not be very

> >>>> obvious. If this is explained further in the manual, just tell me to

> >>>> read the manual completely but again I won’t embark in this long task

> >>>> if it is to give up at the end...

> >>>>

> >>>> Thanks

> >>>> Laurent

> >>>>

> >>>>

> >>>>

> >>>> It’s tough to make predictions- especially about the future.

> >>>> Yogi Berra

> >>>

> >>> --

> >>> Jan Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://lilypond.org

> >>> Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com

> >

> > <measure-length-warning.ly>

>

> Vieux dicton des pharaons ”si tu rames, cesse !”

> Le Canard Enchaîné

signature.asc
Description: This is a digitally signed message part.