Re: Organization of the piese part by part, not staff by staff

2019-01-11 Thread Mats Bengtsson
On 2019-01-10 21:19, Павел Буданов wrote: Hello everybody! This case is usually used: we are instancing staffs, voices and putting notes into them. This is simply example: \new GrandStaff <<  \new Staff \rightHand   \new Staff \leftHand >> But I want to organizate the piece in other case. For

Re: Organization of the piese part by part, not staff by staff

2019-01-11 Thread Павел Буданов
Thank you for the answers. I learned everything I needed11.01.2019, 03:37, "Saul Tobin" :Fundamentally, the data model of Lilypond is horizontal, even when you delve into the guts of how the program works (iterators, streams, engravers). My advice is to embrace that and adapt your workflow and

Re: Organization of the piese part by part, not staff by staff

2019-01-10 Thread Saul Tobin
Fundamentally, the data model of Lilypond is horizontal, even when you delve into the guts of how the program works (iterators, streams, engravers). My advice is to embrace that and adapt your workflow and thinking to take advantage of Lilypond's strengths, rather than fighting against it. In my

Re: Organization of the piese part by part, not staff by staff

2019-01-10 Thread Valentin Villenave
On 1/10/19, Павел Буданов wrote: > And I will add this music to score block: > \refren \bar "||" \episodeA \refren \episodeB > Is this case possible? If so, how to implement it correctly, where is the > documentation written about it? Greetings Pavel, at its heart, LilyPond very much encourages

Organization of the piese part by part, not staff by staff

2019-01-10 Thread Павел Буданов
Hello everybody!This case is usually used: we are instancing staffs, voices and putting notes into them. This is simply example:\new GrandStaff << \new Staff \rightHand  \new Staff \leftHand>>But I want to organizate the piece in other case. For example, I want to engrave any rondo. In first, I