Re: Nested transposition

2021-03-13 Thread Lukas-Fabian Moser
Am 13.03.21 um 02:16 schrieb Valentin Petzel: As far as I know transpose should only really be used with absolute pitches, as it would be quite impossible to do it otherwise. Think of it like this: Say we are in relative mode and have c' f. Then f will be above c. If you then do c' \transpose f a

Re: Nested transposition

2021-03-13 Thread Silvain Dupertuis
I have nearly always used relative pitches. I always use variables to build up the music in a logical way. Transpose always worked right for me. As for enharmonic transposition, it does work well Here is an example :  m = \relative c' { \key des \major des4 es f as des2. r4}  \score {    {   

Re: Nested transposition

2021-03-13 Thread Valentin Petzel
I'm sorry, I worded that badly. I did not mean the note C#, but the scale or harmonic concept of C# major, that is, C#, D#, E#, F#, G#, A#, B#. While C# can be reached in C major, it usually belongs harmonically to A major or A dom major, which is quite close to C major. But Db major is quite co

Re: Nested transposition

2021-03-13 Thread ebenezer
I don't have the expertise of the rest of you, but the first thing I did with Lilypond was give \relative the elbow. It just seemed like a nightmare way to compose. Ditto duration persistence. All for the sake of saving a few keystrokes? Re: the manuals/guides where \relative is introduced as

move Full Measure Rest up

2021-03-13 Thread Orm Finnendahl
Hi, in the following snippet the whole measure rest in the upper voice collides with the des in the lower voice an needs to be moved up: 8<--- \version "2.19" << { R1 } \\ { aes'2 bes'4 c''4 | %40 bes'4 des'4 ges'4 f'4 | %41

move Full Measure Rest up

2021-03-13 Thread Orm Finnendahl
Hi, the example in the previous mail was inconsistent with the mail text, so here again: In the following snippet the whole measure rest in the upper voice collides with the des in the lower voice an needs to be moved up: 8<--- \version "2

solved: move Full Measure Rest up

2021-03-13 Thread Orm Finnendahl
Hi, I found it, sorry for the noise! 8<--- \version "2.19" << \override MultiMeasureRest.staff-position = #8 { R1 } \\ { aes'2 des''4 c''4 } >> 8<--- Using a note name with \rest w

Re: move Full Measure Rest up

2021-03-13 Thread Phil Holmes
See http://lilypond.org/doc/v2.23/Documentation/notation/writing-rests#full-measure-rests - "Selected snippets". On 13/03/2021 13:48, Orm Finnendahl wrote: Hi, in the following snippet the whole measure rest in the upper voice collides with the des in the lower voice an needs to be moved up:

Strange behaviour of chord names?

2021-03-13 Thread Christian Masser
Hey all! Just had a curious case concerning chord names. Typesetting a small jazz piece and - as always - wanted to keep my file tidy, so I put the chords for the solo-section in a variable as they are the same for every solo. But somehow Lilypond seems to make a difference, if one inserts the res

Re: Nested transposition

2021-03-13 Thread Kieren MacMillan
Hi Elaine, > That may be so, but you likely pay for it every day by typing out extra > commas and apostrophes. My music entry is done 99% by MIDI input, so I type almost no commas or apostrophes. ;) Cheers, Kieren. Kieren MacMillan, composer (he/him/his) ‣ web

Re: Strange behaviour of chord names?

2021-03-13 Thread Aaron Hill
On 2021-03-13 6:11 am, Christian Masser wrote: [...] mySoloChordsA = \chords { c1 f g c } [...] I think you want \chordmode, not \chords, when defining the variables. \chords { ... } is shorthand for \new ChordNames \chordmode { ... } if I recall. -- Aaron Hill

Re: Strange behaviour of chord names?

2021-03-13 Thread Christian Masser
Ah, that explains it. Thank you very much, Aaron! Am Sa., 13. März 2021 um 16:02 Uhr schrieb Aaron Hill < lilyp...@hillvisions.com>: > On 2021-03-13 6:11 am, Christian Masser wrote: > > [...] > > mySoloChordsA = \chords { > > c1 f g c > > } > > [...] > > I think you want \chordmode, not \chords

New Sphinx extension for including Lilypond

2021-03-13 Thread Kevin Cole
In case you missed it: -- Forwarded message - From: Shengyu Zhang Date: Sat, Mar 13, 2021 at 10:31 AM Subject: [sphinx-users] Another new extension for including Lilypond To: sphinx-users About ten years ago, Wei-Wei Guo wrote a lilypond extension[1], it is useful but a little

Re: Nested transposition

2021-03-13 Thread Peter Toye
My experience is exactly the opposite. I use the computer keyboard for input, and as most of the music is for piano, which spans several octaves outside the staves, absolute entry is a serious PITA. For vocal music, there aren't usually many wide skips, so again relative notation uses fewer keys

Re: Nested transposition

2021-03-13 Thread Carl Sorensen
On 3/13/21, 7:21 AM, "lilypond-user on behalf of Kieren MacMillan" wrote: My music entry is done 99% by MIDI input, so I type almost no commas or apostrophes. ;) Can you tell me how you do your MIDI input? I'd like to do that, but I don't have a good workflow for it. Thanks,

MIDI input [was Re: Nested transposition]

2021-03-13 Thread Kieren MacMillan
Hi Carl! >> My music entry is done 99% by MIDI input, so I type almost no commas or >> apostrophes. > Can you tell me how you do your MIDI input? I'd like to do that, but I don't > have a good workflow for it. 1. I use Frescobaldi. 2. I’ve set keyboard shortcuts (F18 and F19) for starting and

Re: Nested transposition

2021-03-13 Thread David Wright
On Sat 13 Mar 2021 at 11:18:52 (+0100), Lukas-Fabian Moser wrote: > Am 13.03.21 um 02:16 schrieb Valentin Petzel: > > As far as I know transpose should only really be used with absolute pitches, > > as it would be quite impossible to do it otherwise. Think of it like this: > > Say we are in relativ

Re: Nested transposition

2021-03-13 Thread David Wright
On Sat 13 Mar 2021 at 09:21:07 (-0500), Kieren MacMillan wrote: > Hi Elaine, > > > That may be so, but you likely pay for it every day by typing out extra > > commas and apostrophes. > > My music entry is done 99% by MIDI input, so I type almost no commas or > apostrophes. > ;) I'm happy to se