OK I engraved my manuscript out  in full (only words and melody), then I
checked that the bars lined up with both the version of the manuscript with
repeats and the drum machine. All good.
It was worth the effort to find out that it is not the most efficient
method as the drum machine allows me to patch in sections.
That means is most logical using the manuscript with the repeats marked.
Not the manuscript in full. Because it is easier to recognize the repeats
and paste in the appropriate section of drums.
So back to having a collection of bar numbers at each repeat. Worth the
exercise to find out.

Thanks for your help. Graham



On Mon, Feb 25, 2013 at 6:58 PM, Graham.Okely <[email protected]>wrote:

> Thanks I have not tried \unfoldRepeats. Let's see how it goes....it
> appears to be for midi output. But that may be ok as the drum machine does
> take midi....so many ways to do this. When you are used to reading the
> score it might just be better to print it out once in full for creating a
> drum part against. Regards Graham
>
>
> On Mon, Feb 25, 2013 at 6:42 PM, Marc Hohl [via Lilypond] <[hidden 
> email]<http://user/SendEmail.jtp?type=node&node=141471&i=0>
> > wrote:
>
>> Am <a href="tel:25.02.2013%2011" value="+12502201311" 
>> target="_blank">25.02.2013
>> 11:40, schrieb Marc Hohl:
>>
>> > Am <a href="tel:25.02.2013%2011" value="+12502201311" 
>> > target="_blank">25.02.2013
>> 11:37, schrieb Graham.Okely:
>>
>> >> Thanks I can see that would work in rehearsals.
>> >>
>> >> Working up a drum line is easier if each bar gets a number
>> >> sequentially. But writing up the drum sequence is only required once.
>> >> (Usually) So I do not think writing up a fully expanded manuscript
>> >> for that is worth it. I found penciling in each repeat bar number
>> >> worked last time. Then just plug steps into the drum sequencer. I may
>> >> try the fully expanded manuscript yet.
>> >>
>> > If you use it for working with a sequencer, wouldn't it be better to
>> > process the lilypond file with \unfoldRepeats?
>> I just read that you already mentioned that option.
>>
>> Sorry for the noise.
>>
>> Marc
>>
>>
>> _______________________________________________
>> lilypond-user mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=141469&i=0>
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://lilypond.1069038.n5.nabble.com/Advice-on-bar-numbers-tp141364p141469.html
>>  To unsubscribe from Advice on bar numbers, click here.
>> NAML<http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> ------------------------------
> View this message in context: Re: Advice on bar 
> numbers<http://lilypond.1069038.n5.nabble.com/Advice-on-bar-numbers-tp141364p141471.html>
> Sent from the User mailing list 
> archive<http://lilypond.1069038.n5.nabble.com/User-f3.html>at Nabble.com.
>
> _______________________________________________
> lilypond-user mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to