Re: Transposing an entire score

On Tue, Nov 7, 2017 at 1:25 PM, Simon Albrecht wrote: > On 07.11.2017 20:13, Flaming Hakama by Elaine wrote: > >> Looks like all you'll need to do is change one file: >> parts/01-ego_flos_campi.ly >> >> replace all instances of "\relative"

Re: ly:load (LSR 785)

On 07.11.2017 09:56, David Kastrup wrote: ly:load is not at fault here. This LSR redefines basics of LilyPond's operation, then reloads some of its internals. That's completely messed up. You can probably say something like #(define define-session-public define) before the load in order to

Re: Transposing an entire score

On 07/11/17 19:13, Flaming Hakama by Elaine wrote: > > -- Forwarded message -- > From: peter.gam...@homecall.co.uk > To: lilypond-user@gnu.org > Cc: > Bcc: > Date: Tue, 07 Nov 2017

Re: Transposing an entire score

On 07.11.2017 20:13, Flaming Hakama by Elaine wrote: Looks like all you'll need to do is change one file: parts/01-ego_flos_campi.ly replace all instances of  "\relative" with "\transpose a, c \relative" Why? That would only make sense if you used the same

Re: Removing/hiding "clutter"

On 07.11.2017 17:19, SoundsFromSound wrote: Maybe try: \override Script.transparent = ##t That would essentially remove them...does that help? If you abolutely need to retain the spacing, that’s a good idea, else just \omit Script or its verbose alias \override Script.stencil = ##f Best,

Re: Transposing an entire score

> -- Forwarded message -- > From: peter.gam...@homecall.co.uk > To: lilypond-user@gnu.org > Cc: > Bcc: > Date: Tue, 07 Nov 2017 16:54:12 + > Subject: Transposing an entire score > I have a piece of choral music written in 7 parts. It's around 80 bars > long. > It's in the key

Re: Transposing an entire score

On 11/7/2017 11:54 AM, peter.gam...@homecall.co.uk wrote: I have a piece of choral music written in 7 parts. It's around 80 bars long. It's in the key of F major, which is too low for my choir. I'd like to transpose it up 3 semitones to A flat major. I'm new to Lilypond and the syntax gives me

Re: Transposing an entire score

Am 07.11.2017 um 17:54 schrieb peter.gam...@homecall.co.uk: I have a piece of choral music written in 7 parts. It's around 80 bars long. It's in the key of F major, which is too low for my choir. I'd like to transpose it up 3 semitones to A flat major. I'm new to Lilypond and the syntax gives

Re: Transposing an entire score

peter.gam...@homecall.co.uk writes: > I have a piece of choral music written in 7 parts. It's around 80 bars long. > It's in the key of F major, which is too low for my choir. > I'd like to transpose it up 3 semitones to A flat major. > I'm new to Lilypond and the syntax gives me nightmares. I

Re: "Guide notes"

Am 07.11.2017 um 16:45 schrieb David Wright: Thanks for the replies. I did try specifying a chord, but the "pitch" parameter won't take it. That’s because I didn’t know that you wanted chords … Of course it’s possible to specify a chord, see the following code. There’s only one reason I

Re: Removing/hiding "clutter"

On Tue 07 Nov 2017 at 17:36:17 (+0100), David Kastrup wrote: > David Kastrup writes: > > > David Wright writes: > > > >> I print a fair amount of SATB a cappella on four staves, > >> but on the side I produce a two-stave version without > >> lyrics,

Re: Removing/hiding "clutter"

David Kastrup writes: > David Wright writes: > >> I print a fair amount of SATB a cappella on four staves, >> but on the side I produce a two-stave version without >> lyrics, printed like an English hymnbook with stems up >> and down to distinguish

Re: Removing/hiding "clutter"

David Wright writes: > I print a fair amount of SATB a cappella on four staves, > but on the side I produce a two-stave version without > lyrics, printed like an English hymnbook with stems up > and down to distinguish parts. It's to make it simpler > for people to

Re: Removing/hiding "clutter"

David Wright wrote > I print a fair amount of SATB a cappella on four staves, > but on the side I produce a two-stave version without > lyrics, printed like an English hymnbook with stems up > and down to distinguish parts. It's to make it simpler > for people to play bits on the piano. > > To

Re: Removing/hiding "clutter"

David Wright wrote > I print a fair amount of SATB a cappella on four staves, > but on the side I produce a two-stave version without > lyrics, printed like an English hymnbook with stems up > and down to distinguish parts. It's to make it simpler > for people to play bits on the piano. > > To

Re: "Guide notes"

On Wed 01 Nov 2017 at 16:51:19 (+0100), Malte Meyn wrote: > > > Am 01.11.2017 um 16:03 schrieb David Wright: > >I've sung (strictly, not sung) a great many of these > >without knowing what they're officially called. > >I've created this one with what looks like an awful > >hack. Is there a

Removing/hiding "clutter"

I print a fair amount of SATB a cappella on four staves, but on the side I produce a two-stave version without lyrics, printed like an English hymnbook with stems up and down to distinguish parts. It's to make it simpler for people to play bits on the piano. To make it easier to see the notes, I

Re: create more horizontal space per

I was able to achieve a fairly good output with only breaks. I added a system to system spacing change to make it look better. \version "2.18.2" \relative { \time 3/8 cis''16 r8. gis8 \time 5/8 \tuplet 3/2{ c![ e,] r8} \tuplet 3/2{ c' ees, r8} r8 \bar "||" \time 4/4 \once \override

Re: ly:load (LSR 785)

Simon Albrecht writes: > Hello everybody, > > I am very grateful to have found > – it’s amazing to just > have a readymade solution for that available. > > Downloading the file and compiling works fine with 2.18.2, however >