On Mon, 14 Nov 2016 16:57:08 +0100
Mojca Miklavec wrote:
> I would find it useful if the following example:
>
> \relative c'' {
> c1 \mark \default
> c1 \mark \default
> c1 \mark #8
> c1 \mark \default
> c1 \mark \default
> }
>
> was extended to also
Hi Andrew
Thanks, I'm Cc-ing the list
Il giorno mar 15 nov 2016 alle 1:43, Andrew Bernard
ha scritto:
Have run your files. Again, under 2.19.50 on Linux Mint (derived from
Ubuntu) the program does not crash.
Since the slur is what is calling the Bezier curve
Good morning everyone,
> On 15 Nov 2016, at 02:30, Andrew Bernard wrote:
> I know lilypond strives to do as much good layout as it can without requiring
> tweaks, but this seems a step too far.
I can fully agree with the first part of your statement - for my needs,
Hi Robert,
If you play with all the tie details settings, the only one that makes a
difference is this:
\override Tie.details.horizontal-distance-penalty-factor = 0 (from
default 10)
So there must be some subtle horizontal spacing issue at work that seems
wrong to me.
Andrew
Hi Robert,
I for one don't think lilypond should be making decisions for you about tie
direction based on an idea of sequenced phrases. I know lilypond strives to
do as much good layout as it can without requiring tweaks, but this seems a
step too far. There is nothing mentioned about this in the
Am 14.11.2016 um 14:43 schrieb Urs Liska:
>
> Am 13.11.2016 um 21:44 schrieb Thomas Morley:
>> 2016-11-13 15:45 GMT+01:00 Urs Liska :
>>> Hi all,
>>>
>>> I'm trying to build something like similar to an automated harmonic
>>> display on two staves, and it seems that
Tobian
On Mon, Nov 14, 2016 at 3:50 PM, Tobin Chodos [via Lilypond] <
ml-node+s1069038n196622...@n5.nabble.com> wrote:
> This one really is basic, but: a \tempo command in a large score will
> automatically register on each part, right? that is, if I insert the
> marking to change tempo in the
On Mon 14 Nov 2016 at 14:30:44 (+0100), Mojca Miklavec wrote:
> On 14 November 2016 at 13:31, Mojca Miklavec wrote:
> > Hi,
> >
> > While trying to add slightly more complex fingerings (button label +
> > finger number) on top of some scores, I'm facing a problem with ties
> > on the following
Hi all,
This one really is basic, but: a \tempo command in a large score will
automatically register on each part, right? that is, if I insert the
marking to change tempo in the flute part in bar 2, it will appear on every
other part...so where is it advisable to put it?
Thanks.
Tobin
> On 14 Nov 2016, at 22:34, Robert Schmaus wrote:
>
>> On 14 Nov 2016, at 21:22, Hans Åberg wrote:
>>
>>> On 14 Nov 2016, at 21:09, Robert Schmaus wrote:
>>>
>>> I've wondered why in the first instance, the tie is a down-tie,
> On 14 Nov 2016, at 22:27, Brian Barker wrote:
>
> At 21:09 14/11/2016 +0100, Robert Schmaus wrote:
>> something I just came across while pondering away: in the following snippet,
>> there are two ties across barlines.
>> [...]
>> I've wondered why in the first
> On 14 Nov 2016, at 21:22, Hans Åberg wrote:
>
>
>> On 14 Nov 2016, at 21:09, Robert Schmaus wrote:
>>
>> I've wondered why in the first instance, the tie is a down-tie, while in the
>> second it's an up-tie (see attached screenshot). Is there a
At 21:09 14/11/2016 +0100, Robert Schmaus wrote:
something I just came across while pondering away: in the following
snippet, there are two ties across barlines.
[...]
I've wondered why in the first instance, the tie is a down-tie,
while in the second it's an up-tie (see attached screenshot).
> On 14 Nov 2016, at 21:09, Robert Schmaus wrote:
>
> I've wondered why in the first instance, the tie is a down-tie, while in the
> second it's an up-tie (see attached screenshot). Is there a reason for this?
> Something like visual balance?
It is different in the
Dear Ponderers,
something I just came across while pondering away: in the following
snippet, there are two ties across barlines.
%
\version "2.19.35"
\score {
\relative c'' {
| a2 r8 a8 ( a ) b ~
| b2 r8 b8 ( a ) b ~
| b2 r2
}
}
Am 14.11.2016 um 09:52 schrieb Mojca Miklavec:
I'm using \markDefault from the following code for marking parts of music:
stdMarkFormat = {
\set Score.markFormatter = #format-mark-box-letters
}
markDefault = {
\stdMarkFormat
\mark \default
}
Why do you use these functions? A \set is
On 14.11.2016 01:01, Dominic wrote:
The \shape command, if I remember correctly, functions like a "\once
\override", so it needs to immediately precede the note to which the slur is
attached, thus:
/\stemUp r8
\shape #'((0 . 0)(0 . 0)(0 . 0)(0 . 0)) Slur
c( g' c e g /
For completeness’ sake:
Dear Robin,
On 14 November 2016 at 17:28, Robin Bannister wrote:
> Mojca Miklavec wrote:
>>
>> I eventually needed to run "locate rehearsal-mark-letter.ly" on my
>> computer and inspect the contents to arrive to the answer.
>
> I was referring to the regression tests at
>
Mojca Miklavec wrote:
I eventually needed to run "locate rehearsal-mark-letter.ly" on my
computer and inspect the contents to arrive to the answer.
I was referring to the regression tests at
http://lilypond.org/doc/v2.19/input/regression/collated-files.html
This links to all the test files
Dear Robin,
On 14 November 2016 at 15:58, Robin Bannister wrote:
> Mojca Miklavec wrote:
>>
>>
>> Is there a way to just set the counter without printing the mark
>> itself? (I would like to set the counter at the beginning of Coda and
>> then use \markDefault where appropriate just like
Mojca Miklavec wrote:
Is there a way to just set the counter without printing the mark
itself? (I would like to set the counter at the beginning of Coda and
then use \markDefault where appropriate just like everywhere else.)
Documentation points to
Am 14.11.2016 um 14:43 schrieb Urs Liska:
> The next step would be to have two notes connect their stems when *not*
> in different staves, e.g.
Never mind, I have found out how to generate my stuff as a chord.
Urs
___
lilypond-user mailing list
Hi David
I can only echo the good wishes and thanks that others have already
expressed. Lilypond is a great program - the more I use it the more I
can see the potential if I can ever get my head around the finer
points.
Meanwhile the list provides great support, and you have been a major
Dear Phil,
On 14 November 2016 at 14:34, Phil Holmes wrote:
> - Original Message - From: "Mojca Miklavec"
>>
>> While trying to add slightly more complex fingerings (button label +
>> finger number) on top of some scores, I'm facing a problem with ties
>> on the following structure:
>>
>>
Hi Gianmaria,
How about:
\score { { <>\p \frag <>\f \frag } \midi{}}
HTH,
Cheers,
Pierre
2016-11-14 14:55 GMT+01:00 Gianmaria Lari :
>
>
> On 14 November 2016 at 12:03, Bernhard Kleine
> wrote:
>
>> Am 14.11.2016 um 11:16 schrieb Gianmaria
On 14 November 2016 at 12:03, Bernhard Kleine
wrote:
> Am 14.11.2016 um 11:16 schrieb Gianmaria Lari:
>
> I have something like this:
>
> frag = { \repeat volta 2 {c'^\markup {p (2nd time: f)} d' e' f'}}
>
> \score {\frag \layout{}}
>
> \score {\unfoldRepeats \frag
Am 13.11.2016 um 21:44 schrieb Thomas Morley:
> 2016-11-13 15:45 GMT+01:00 Urs Liska :
>> Hi all,
>>
>> I'm trying to build something like similar to an automated harmonic
>> display on two staves, and it seems that alternative note head styles
>> break the cross staff
- Original Message -
From: "Mojca Miklavec"
To: "lilypond-user"
Sent: Monday, November 14, 2016 12:31 PM
Subject: Ties break the ability to add lyrics
Hi,
While trying to add slightly more complex fingerings (button label +
On 14 November 2016 at 13:31, Mojca Miklavec wrote:
> Hi,
>
> While trying to add slightly more complex fingerings (button label +
> finger number) on top of some scores, I'm facing a problem with ties
> on the following structure:
>
> << {f'2~} {s8 d'4.~} {s4 b4~} {s4. g8} >>
> 4. 8 |
I just
Hi,
While trying to add slightly more complex fingerings (button label +
finger number) on top of some scores, I'm facing a problem with ties
on the following structure:
<< {f'2~} {s8 d'4.~} {s4 b4~} {s4. g8} >>
4. 8 |
(This is some "simplification" that would look ugly if I would tie
five
Am 14.11.2016 um 11:16 schrieb Gianmaria Lari:
> I have something like this:
>
> frag = { \repeat volta 2 {c'^\markup {p (2nd time: f)} d' e' f'}}
>
> \score {\frag \layout{}}
>
> \score {\unfoldRepeats \frag \midi{}}
>
>
> As you can see I mentioned in the markup that the first time
Il giorno lun 14 nov 2016 alle 9:14, Andrew Bernard
ha scritto:
Hello Federico,
FWIW, this compiles cleanly on 2.19.50 under Linux Mint, using the
standard
distribution version. Not sure whether this fact is of any help.
I know that my minimal example compiles
I have something like this:
frag = { \repeat volta 2 {c'^\markup {p (2nd time: f)} d' e' f'}}
\score {\frag \layout{}}
\score {\unfoldRepeats \frag \midi{}}
As you can see I mentioned in the markup that the first time the score
should be played piano and the second forte. Is there any way to
Hi,
I'm using \markDefault from the following code for marking parts of music:
stdMarkFormat = {
\set Score.markFormatter = #format-mark-box-letters
}
markDefault = {
\stdMarkFormat
\mark \default
}
But if I follow:
http://flaminghakama.com/adding-a-coda
to make Coda a "score" on its
Hello Federico,
FWIW, this compiles cleanly on 2.19.50 under Linux Mint, using the standard
distribution version. Not sure whether this fact is of any help.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
35 matches
Mail list logo