On Mon, Jun 29, 2020 at 4:10 PM Trevor wrote:
>
> Hi Carl
>
> >This notation will greatly simplify some of the choral music I set in
> >the past year. I forgot about the discussion on the lists, and so
> >didn't use it even though it was available. Thanks for making it work
> >
> I always use t
Carl Sorensen writes:
> David,
>
> This notation will greatly simplify some of the choral music I set in
> the past year. I forgot about the discussion on the lists, and so
> didn't use it even though it was available. Thanks for making it work
>
> Aaron,
>
> I think this is a useful enough wr
Hi Carl
This notation will greatly simplify some of the choral music I set in
the past year. I forgot about the discussion on the lists, and so
didn't use it even though it was available. Thanks for making it work
I always use the satb.ly template for almost all of my choral music (see
A1 B
Am Sa., 20. Juni 2020 um 17:18 Uhr schrieb Ralph Palmer
:
>
> On Sat, Jun 20, 2020 at 6:28 AM Karlin High wrote:
>>
>> On 6/20/2020 7:37 AM, Thomas Morley wrote:
>> > I'd say we need more people for LSR-work.
>> >
>> > Furthermore, some time ago I started to upgrade LSR to 2.20, but had
>> > to st
On Mon, Jun 29, 2020 at 3:44 PM David Kastrup wrote:
>
> Aaron Hill writes:
>
> > On 2020-06-29 2:17 pm, David Kastrup wrote:
> >> \voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
> >> which is ugly enough as it is [...]
> >
> > Does not seem that ugly to me, but I suppose one could enc
Aaron Hill writes:
> On 2020-06-29 2:17 pm, David Kastrup wrote:
>> \voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
>> which is ugly enough as it is [...]
>
> Does not seem that ugly to me, but I suppose one could encapsulate it
> via the ever-handy \etc:
>
>
> \version "2.20.0"
>
On 2020-06-29 2:17 pm, David Kastrup wrote:
\voices 1,3,4,2 << \soprano \\ \alto \\ \tenor \\ \bass >>
which is ugly enough as it is [...]
Does not seem that ugly to me, but I suppose one could encapsulate it
via the ever-handy \etc:
\version "2.20.0"
soprano = { c''4 }
alto = { a'4 }
Pierre Perol-Schneider writes:
> Le lun. 29 juin 2020 à 22:31, David Kastrup a écrit :
>
>>
>> Just keep most stuff in the main voice, like
>>
> ...
>
>> \voices "main", 2 << { g4 f\) } \\ a,2 >>
>
> ...
> WTF???
> 'just discovered that \voices is in the 2.20 learning manual...
> One word: bravo
Le lun. 29 juin 2020 à 22:31, David Kastrup a écrit :
>
> Just keep most stuff in the main voice, like
>
...
> \voices "main", 2 << { g4 f\) } \\ a,2 >>
...
WTF???
'just discovered that \voices is in the 2.20 learning manual...
One word: bravo.
Cheers,
Pierre
Sorry, forgot the list...
Lukas-Fabian Moser schrieb am Mo., 29. Juni 2020, 22:08:
> Hi David,
>
> I can't figure out how to get the tie between the G's, without breaking
>> the double stops in the first measure into two separate voices, and so
>> breaking their stems. Can someone show me how t
David Zelinsky writes:
> I've done some reasonably complicated things in Lilypond, but still have
> lots to learn. My current conundrum is to typeset the attached snippet.
> I can't figure out how to get the tie between the G's, without breaking
> the double stops in the first measure into two s
On Mon, 29 Jun 2020 at 21:37, David Zelinsky wrote:
>
> I've done some reasonably complicated things in Lilypond, but still have
> lots to learn. My current conundrum is to typeset the attached snippet.
> I can't figure out how to get the tie between the G's, without breaking
> the double stops i
I've done some reasonably complicated things in Lilypond, but still have
lots to learn. My current conundrum is to typeset the attached snippet.
I can't figure out how to get the tie between the G's, without breaking
the double stops in the first measure into two separate voices, and so
breaking t
Pierre,
Yet the voice shift command has a “\once”.
Mark
From: Pierre Perol-Schneider [mailto:pierre.schneider.pa...@gmail.com]
Sent: Monday, June 29, 2020 12:21 AM
To: Mark Stephen Mrotek
Cc: Leo Correia de Verdier ;
jasm...@gmail.com; lilypond-user
Subject: Re: trouble with alignm
Thanks for this insightful clarification. I'll just take care not to apply
it to the first or last bar on a staff. A minimum of 3 bars per staff
should not be a real limitation.
Regards,
Aberforth D
On Mon, 29 Jun 2020 at 16:46, Lukas-Fabian Moser wrote:
> Hi,
>
> > No, I was applying it to the
Hi,
No, I was applying it to the 2nd system. If I put the command
\showMultiRests before the first bar of any system, it seems to have
no effect, but it works fine when I put it before any other bar on the
staff. As I rarely have just 1 bar on a staff this should not be a
problem in practice.
Thanks :) I'm John, not Bert. Bert is just the guy who hosts a site with
some good guitar stuff on it.
On Mon, Jun 29, 2020 at 3:17 AM Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> Hi Bert and welcome to the list.
> It's nice to see you here!
> Here's a template that may hel
Thanks Lukas-Fabian,
This is perfect and it will be very helpful in many situations. Regarding
your question: No, I was applying it to the 2nd system. If I put the
command \showMultiRests before the first bar of any system, it seems to
have no effect, but it works fine when I put it before any oth
Am 29.06.2020 um 10:36 schrieb Michael Käppler:
The file 'lily-21179cd9-1.eps' is there, indeed. How is this supposed to
work?
Do I have to specify manual includes somewhere?
Sorry for the noise, I found out that I have to specify --pdf when invoking
lilypond-book, because
texi2pdf uses 'pdfla
Hi,
Am 29.06.20 um 14:41 schrieb Aberforth D - Instrumentals:
It works although it doesn't seem to work when applied to the first
bar on the staff, but I guess it's good enough.
Do you mean that the staff is not removed in the first system? That's
just the difference between \RemoveEmptyStave
Thanks Pierre,
It works although it doesn't seem to work when applied to the first bar on
the staff, but I guess it's good enough.
I would still be grateful if somebody could answer my second question
because it might be useful in specific circumstances. Namely, how to hide a
redundant staff when
Hi Pierre,
Using tags is pretty much the only way to achieve this from one source, but
you would still need different functions for Voice and TabVoice (unless you
combine them + tagging into one function, which might be useful, but
unflexible.
Valentin
signature.asc
Description: This is a dig
Hi Valentin,
Le lun. 29 juin 2020 à 13:30, Valentin Petzel a écrit :
...
> But the hard part would be getting Staff Notation and TabStaff-Notation
> right at the same time, because you usually want to notate this like this
>
Or similar to this. So you would need different functions for Tabnotat
Hi Lukas,
You might want to set restrainOpenStrings to #t in case the sounding pitch is
in fact an open
string (else minimumFret would be ignored), see appended file.
The order requirement to string tuning is most likely a bug, I guess Lilypond
tries to
minimize the used fret by traversing th
Hi Valentin,
1) Yes. Without my mistake it calculates on which fret the sounding note would
be, thus placing the note head onto the correct string. I’m sorry for that.
Yes - thanks much! Now it works as expected (at least by me):
If
i) #pitch is the pitch of an open string (as defined with \
Hello Carl,
They can be, although I had to correct a little mistake where I forgot to
replace 12 from my testing with the actual fret. You just need to be aware
that this will revert any \set minimumFret = ? done before as long as lilypond
cannot mask context properties. Also it might be a good
Hi Lukas,
I’m sorry, I messed that up. It should say
(calc-harmonic-pitch (fret->pitch (number->string fret))
I did my intropections with that using fret=12, and then I forgot to change
that when copying. See the attached file for the correction.
About your points:
1) Yes. Without my mistake
Hi,
How about:
\version "2.20.0"
\language "english"
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
%% => http://lsr.di.unimi.it/LSR/Item?id=312
showMultiRests = {
\set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-in
Hi all,
I'm trying to integrate Lilypond snippets into Texinfo files.
Consider the 'Texinfo' example from the 'Usage' manual, which you can find
here:
http://lilypond.org/doc/v2.21/Documentation/usage/lilypond_002dbook-templates
With this example in lybook-texinfo.tely, I do
lilypond-book --outp
Hello,
I'm currently working on a piano-vocal score for an opera. I'm using a
Frenched score layout so empty staves are removed from the systems. I
usually aim for 12 to 14 staves on a page. If necessary I am willing to
accept a minimum of 10 and a maximum of 15 staves, but I try to avoid that.
I
Hi Harm,
Le lun. 29 juin 2020 à 09:59, Thomas Morley a
écrit :
> Hi Pierre,
>
> I've now approved it as
> lsr.di.unimi.it/LSR/Item?u=1&id=1116
> with some slight changes.
>
> I deleted another instance of \hideNotes and changed
> \once\override Staff.Clef.space-alist =
> #'((key-canc
Am So., 28. Juni 2020 um 09:37 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Harm,
>
> Le sam. 27 juin 2020 à 10:39, Thomas Morley a
> écrit :
> ...
>>
>> Some Remarks:
>> (a) Your override
>> \once\override Staff.TimeSignature.space-alist =
>> #'((first-note . (fixed-space . 0)))
>> will
Hi Mark,
Le lun. 29 juin 2020 à 01:29, Mark Stephen Mrotek a
écrit :
> Leo,
>
> Yes, thank you.
> In measure 2, how to align the c4. with the e2.
> In measure 3, why does "\mergeDifferentlyDottedOn" not apply to the g8 and
> the g4?
>
> Mark
>
It's because of the voice shifting (try \shiftOff).
Hi Bert and welcome to the list.
It's nice to see you here!
Here's a template that may help you.
For barrés, see http://lsr.di.unimi.it/LSR/Item?id=952
HTH,
Cheers,
Pierre
PS. I'd strongly advise you to work with de v2.20:
http://lilypond.org/download.html
Le dim. 28 juin 2020 à 22:53, a écrit :
34 matches
Mail list logo
