Re: 4 hands piano pieces book

[Jacques Menu Muzhic]

Hello Alberto,

You’ll find attached an example, a reduction from one of my actual scores. I 
hope it’s not too big, but I needed to keep if of some length to show the idea.
The dimming of sections of the « dessus » is because the soloists will take 
over one after the other (they’re oboists).

You can place all score-wide stuff such as double bars, time specifications, 
modulations, irregular measures and annotations that are to appear in every 
instrumental part as well as in the director score (see « Harpeges » at bar 33) 
in the « controle » part.


Of interest are multiRestWitBarNumbers, contributed by someone on this list. I 
appreciate the automatic display of the bar number at the beginning and end of 
multirests:

multiRestWitBarNumbers =
#(define-music-function (parser location dur)(ly:duration?)
   (let ((display-bar-num #{
     \once\override Score.BarNumber.break-visibility = ##(#f #t #t)
           #}))
     #{
       $display-bar-num
       %%% Choose R $dur for control part check,
       %%% then switch to s $dur for score printout
       s $dur
       $display-bar-num
     #}))

and the following:

    \score {
%%% Choose \new Staff to see the staff and check its correctness,
%%% then switch to \new Dynamics to hide the control staff
      \new StaffGroup <<
        \new Dynamics {
          %\new Staff {
          \Controle
        }
        \ViolonsStaff
        \HauboisStaff
        \BassonsStaff
        \BasseStaff
      >>


These variables:

myBreak = { \break }
%myBreak = { }

myPageBreak = {\pageBreak}
%myPageBreak = {}

are used to switch between:
        - the original breaks from the score I started from, for cross-checking
        - the regular mode in which LP will take care of them for better layout
This is more straightforward as using tags, but this is not your concern in the 
OP of course.


One thing I’d like to be able to do is to change these variables’ value for the 
instrumental parts, but I didn’t find a way to to that in the current 
book/bookpart architecture. Any hint is welcome…


Hope this helps!

JM

ControlPartExample.ly
Description: Binary data

> Le 8 mai 2016 à 19:14, Alberto Simões <address@hidden> a écrit :
> 
> 
> 
> On 08/05/16 18:13, Jacques Menu Muzhic wrote:
>> Hello,
>> 
>> Would dynamics parts dedicated to breaks and pageBreaks, stored in 
>> variables, be useful? They might contain only spacer rests and such breaks, 
>> and be used by Piano I and Piano II parts.
>> 
>> I use this satisfactorily to produce director and musicians parts, with the 
>> same breaks in the first drafts to facilitate cross checking of the LP input 
>> code.
>> 
> 
> Do you have any "small" example I could use for inspiration?
> Thanks
> 
>> One would still have to place things in the right order in the input file to 
>> build the left and right pages, of course.
>> 
>> JM
>> 
>>> Le 8 mai 2016 à 17:16, Urs Liska <address@hidden> a écrit :
>>> 
>>> 
>>> 
>>> Am 8. Mai 2016 16:39:56 MESZ, schrieb "Alberto Simões" <address@hidden>:
>>>> 
>>>> 
>>>> On 08/05/16 15:37, Jean-Charles Malahieude wrote:
>>>>> 
>>>>> Has anyone tried to build it as one markup with three columns (left
>>>>> pianist, the binding, and right pianist) on an A3-landscape sheet?
>>>>> The only problem would be the page numbering…
>>>> 
>>>> That could always be done later... use pdfjam or the like to crop the
>>>> A3
>>>> pages in A4 pages, and use latex to add headers/footers to all pages.
>>>> It
>>>> might work.
>>>> 
>>>> But not sure how to create columns in lilypond :-)
>>> 
>>> I don't think that would help at all. The initial problem is getting the 
>>> page breaks in sync.
>>> Once you've achieved that (presumably by manually adding page breaks) you 
>>> can easily create two separate pdfs and use an external tool to create the 
>>> bound volume.
>>> 
>>> One thing I just start thinking of: you can use openLilyLib's break package 
>>> to ease your workflow.  This allows you to specify breaks as one single 
>>> list. Then you can apply that break list to both scores. You still have to 
>>> do the page breaking manually but have a clean interface to it.
>>> 
>>> I can't look into it right now as I'm on the train ...
>>> 
>>> 
>>> Best
>>> Urs
>>> 
>>>> 
>>>> Thanks
>>> 
>>> --
>>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
>>> 
>>> _______________________________________________
>>> lilypond-user mailing list
>>> address@hidden
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>