Re: Tips for code reusability

2023-03-01 Thread Saul Tobin
I concur on entering all music in concert pitch. You may find the auto-transpose snippet from OpenLilyLib helpful ( https://github.com/openlilylib/oll-misc/tree/master/pitch), as you can simply write "\transposition bf" instead of wrapping all transposed blocks in "\transpose x y { }". This is

Re: Tips for code reusability

2023-03-01 Thread Wol
On 28/02/2023 22:02, TJ Kolev wrote: I would appreciate any suggestions for the above issues. Or comments on how I am putting together the whole score. I do a load of brass (and concert) band stuff. And because I play trombone I'm sensitive to transposition issues. So I always store my parts

Re: Tips for code reusability

2023-03-01 Thread TJ Kolev
I did try to do the first note trick, but obviously I didn't get the syntax right. Got it now. Didn't get to tags and quoting. Those look very promising. Will investigate. Thank you for the references! tjk :) On Tue, Feb 28, 2023 at 5:50 PM Saul Tobin wrote: > >

Re: Tips for code reusability

2023-02-28 Thread Saul Tobin
https://lilypond.org/doc/v2.24/Documentation/notation/writing-parts#quoting-other-voices may help with the second question. On Tue, Feb 28, 2023 at 5:08 PM TJ Kolev wrote: > Greetings, > > I've decided to notate a brass band piece from a paper copy into some > digital format that would be

Re: Tips for code reusability

2023-02-28 Thread Jean Abou Samra
Le mardi 28 février 2023 à 16:02 -0600, TJ Kolev a écrit : > Greetings, > I've decided to notate a brass band piece from a paper copy into some digital > format that would be easier to edit and transform Picked LilyPond and have > been using it with Frescobaldi. So far very happy with the