Originally posted to user list by mistake, sorry for doublepost to anyone
who follows both.
If any of the interfaces for MultiMeasureRests (e.g. rest-interface,
spanner-interface, multi-measure-rest-interface) are included in
keepAliveInterfaces (useful if you want to condense some systems in a
sc
2018-08-31 16:14 GMT+02:00 Peter Toye :
> In a dynamic staff there aren't engraved notes to attach the text to. My
> issue (which I wasn't 100% clear about) is that dynamics and text are treated
> differently - dynamics ( s2\p ) appear to be centred on the staff (at least,
> they're half-way bet
Hi Malte,
Thanks very much for this.I'd not read your comment - I've not had a Lilypond
Digest yet today so didn't know you'd commented.
Your answer below is far fuller. My comments are inserted into it.
Sorry for my ignorance - I don't use LP much and this is the first time I've
had to tweak
Hi Peter,
have you read my latest answer on the user list?
(https://lists.gnu.org/archive/html/lilypond-user/2018-08/msg00412.html)
Am 31.08.18 um 13:36 schrieb Peter Toye:
1. Just inserting the text by attaching it to a silent note using "^" or "_" works
as expected. See examples 1 & 2
I
Please ignore previous mail - forgot to add the scores!
I'm trying to align dynamics with markup text in a Dynamics staff and have
found several issues:
1. Just inserting the text by attaching it to a silent note using "^" or "_"
works as expected. See examples 1 & 2
2. Trying "-" is the same
I'm trying to align dynamics with markup text in a Dynamics staff and have
found several issues:
1. Just inserting the text by attaching it to a silent note using "^" or "_"
works as expected. See examples 1 & 2
2. Trying "-" is the same as "_". This isn't documented, and probably shouldn't
be
Hello,
On Sat, 21 Apr 2018 06:26:50 -0700, Knute Snortum wrote:
> In this example...
>
> %%% Start
> \version "2.19.81"
> \language "english"
>
> {
> \override TrillSpanner.avoid-slur = #'inside
> \override TrillSpanner.outside-staff-priority = ##f
> c''1( | c''2. \startTrillSpan c''4 \
On Sat, Apr 21, 2018 at 10:54 AM, James Lowe wrote:
> Knute
>
> On Sat, 21 Apr 2018 06:26:50 -0700, Knute Snortum
> wrote:
>
> > In this example...
> >
> > %%% Start
> > \version "2.19.81"
> > \language "english"
> >
> > {
> > \override TrillSpanner.avoid-slur = #'inside
> > \override Trill
Knute
On Sat, 21 Apr 2018 06:26:50 -0700, Knute Snortum wrote:
> In this example...
>
> %%% Start
> \version "2.19.81"
> \language "english"
>
> {
> \override TrillSpanner.avoid-slur = #'inside
> \override TrillSpanner.outside-staff-priority = ##f
> c''1( | c''2. \startTrillSpan c''4 \s
In this example...
%%% Start
\version "2.19.81"
\language "english"
{
\override TrillSpanner.avoid-slur = #'inside
\override TrillSpanner.outside-staff-priority = ##f
c''1( | c''2. \startTrillSpan c''4 \stopTrillSpan | c''1) |
}
%%% End
...the slur doesn't avoid the trill spanner.
---
K
Simon Albrecht writes:
> Hello Mats,
>
> IIUC \partial serves to insert an additional amount of time,
Nope.
> however in this example we actually need to skip a beat – thus call
> \partial with a negative duration, which is impossible :-) So you need
> to insert \set Timing.measureLength = #(ly
Mats,
Here's a workaround, although I bet you already have one:
\relative c'{
\time 2/4
\partial 4
c4 |
d8 e f g |
f4*2
\bar "||"
\time 3/4
R2.*3 |
f4 ( a f ) |
f2.
}
Trevor
>
> My apologies for spamming the mailing list. After some more trials, I
> realize that the problem remains even if
Mats Bengtsson, you wrote Sunday, August 16, 2015 9:55 PM
Subject: Re: Possible bug with new \partial
> My apologies for spamming the mailing list. After some more trials, I
> realize that the problem remains even if I write \partial after \time.
> Still, the problem only app
Am 16.08.2015 um 22:32 schrieb Mats Bengtsson:
On 08/16/2015 10:05 PM, Simon Albrecht wrote:
Hello Mats,
IIUC \partial serves to insert an additional amount of time, however
in this example we actually need to skip a beat – thus call \partial
with a negative duration, which is impossible :-
My apologies for spamming the mailing list. After some more trials, I
realize that the problem remains even if I write \partial after \time.
Still, the problem only appears with multimeasure rests, as the two
following examples illustrate:
\version "2.19.25"
% Working example
\relative c'{
\
I just realized that if i swap \partial and \time, it works as expected,
at least if I explicitly specify the bar line:
\version "2.19.25"
\relative c'{
\time 4/4
\partial 4
c |
d e f g |
f2.
\bar "||" %Removing this line still gives ugly collisions!
\time 3/4
\partial 4*3
R2.*3 |
f4 ( a f ) |
f
On 08/16/2015 10:05 PM, Simon Albrecht wrote:
Hello Mats,
IIUC \partial serves to insert an additional amount of time, however
in this example we actually need to skip a beat – thus call \partial
with a negative duration, which is impossible :-)
So you need to insert \set Timing.measureLengt
Hello Mats,
IIUC \partial serves to insert an additional amount of time, however in
this example we actually need to skip a beat – thus call \partial with a
negative duration, which is impossible :-)
So you need to insert \set Timing.measureLength = #(ly:make-moment 3/4)
before the second bar
Hi,
I tried version 2.19.25 to typeset a piece that changes from 4/4 with an
upbeat to 3/4 without an upbeat, in the middle of the piece. The new
\partial handling worked for all parts, except a part that started with
a multimeasure rest. Here's a small example illustrating the problem.
Uncom
On 06/05/15 18:54, Knute Snortum wrote:
> I have a possible bug here. This may be another "Yeah, we know there are
> problems with acciaccatura."
>
> When using articulate.ly and \barNumberCheck, you can get into a pickle
> where the bar check never reports correctl
I have a possible bug here. This may be another "Yeah, we know there are
problems with acciaccatura."
When using articulate.ly and \barNumberCheck, you can get into a pickle
where the bar check never reports correctly. In my sample, the bar number
should be bar 3, but you get a warn
At 00:03 on 25 Mar 2015, Thomas Morley wrote:
>I disagree.
>\set Score.skipBars = ##t _is_ intended to affect notes _and_ useful!
>Don't limit your thoughts to modern music.
>
>Below I retyped (quick'n dirty) the last bar from Missa Papae
>Marcelli, Sanctus by Palestrina taken from an edition which
2015-03-24 17:06 GMT+01:00 Mark Knoop :
> At 15:43 on 24 Mar 2015, Kevin Barry wrote:
>>On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
>>
>>> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>>>
>>> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>>>
>>
>>At best I would
At 12:31 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 9:01 AM, Mark Knoop wrote:
At 18:16 on 23 Mar 2015, Mark Knoop wrote:
>>>Barlines disappear when skipBars is true and a note duration
>>>continues over the bar. I don't think this should happen.
>>>
>>>\version "2.18.2"
>>>
>
At 15:43 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
>
>> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>>
>> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>>
>
>At best I would consider these to be non-standard notation. At wo
On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>
> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>
At best I would consider these to be non-standard notation. At worst I'd
say it's incorrect. It's possible to write a
James writes:
> On 02/06/14 17:38, David Kastrup wrote:
>> Yes, that's plausible, but your above reasoning about << >> remains
>> incorrect.
>>
>> Things are more readable if you revert to << >> only when you indeed
>> want parallel voices rather than just multiple notes in a chord. But
>> they
On 02/06/14 17:38, David Kastrup wrote:
> Urs Liska writes:
>
>> Am 02.06.2014 09:51, schrieb Brian Eve:
>>> \version "2.18.2-1"
>>>
>>> {
>>> \clef bass
>>> \compressFullBarRests
>>> \override Rest #'staff-position = #0
>>>R1*6
>>> << g4. e >> << f d >> <>
>>>a1
>>>R1*6
>>> << b8 e8
Urs Liska writes:
> Am 02.06.2014 09:51, schrieb Brian Eve:
>> \version "2.18.2-1"
>>
>> {
>> \clef bass
>> \compressFullBarRests
>> \override Rest #'staff-position = #0
>>R1*6
>> << g4. e >> << f d >> <>
>>a1
>>R1*6
>> << b8 e8 >>
>>r8 r4 r2
>>R1*6
>>R1
>>r
>>
Am 02.06.2014 09:51, schrieb Brian Eve:
\version "2.18.2-1"
{
\clef bass
\compressFullBarRests
\override Rest #'staff-position = #0
R1*6
<> << f d >> <>
a1
R1*6
<>
r8 r4 r2
R1*6
R1
r
R
}
No, that's very wrong code.
With these << >> you a
Urs Liska googlemail.com> writes:
>
> Am 02.06.2014 09:33, schrieb Brian Eve:
> > {
> > \clef bass
> > \compressFullBarRests
> > \override Rest #'staff-position = #0
> >R1*6
> > <<
> > {
> >\voiceOneg4. f e4 }
> >\new Voice {
> >\voiceTwo e4. d d4 }
> >>> >>
> > \oneVoice
"Urs Liska" wrote in message
news:538c29c2.9050...@googlemail.com...
Am 02.06.2014 09:33, schrieb Brian Eve:
{
\clef bass
\compressFullBarRests
\override Rest #'staff-position = #0
R1*6
<<
{
\voiceOne g4. f e4 }
\new Voice {
\voiceTwo e4. d d4 }
>>
\oneVoice a1
R1*6
<<
{
\v
Am 02.06.2014 09:33, schrieb Brian Eve:
{
\clef bass
\compressFullBarRests
\override Rest #'staff-position = #0
R1*6
<<
{
\voiceOneg4. f e4 }
\new Voice {
\voiceTwo e4. d d4 }
>>
\oneVoice a1
R1*6
<<
{
\voiceOneb8 }
\new Voice {
\voiceTwo e8 }
>>
r8 r4 r2
Brian Eve gmail.com> writes:
>
> I am trying to write a single trombone part in which there are a few bars of
> divisi every once in a while in the part. The problem I am having is with
> the position of whole rests and shorter multi-measure rests being placed on
> the staff too high once divis
I am trying to write a single trombone part in which there are a few bars of
divisi every once in a while in the part. The problem I am having is with
the position of whole rests and shorter multi-measure rests being placed on
the staff too high once divisi ends.
Notice the r1's are not affected,
2014-03-15 11:12 GMT+01:00 Pierre Perol-Schneider
:
> I'm not top posting.
>
> Hi Frogs,
>
> In the following code :
>
>
> \version "2.18.0"
>
> myMusic = {
> R1
> \repeat volta 2 {
> \repeat unfold 2 R1
> }
> s8
> }
>
> \new StaffGroup <<
> \set
I'm not top posting.
Hi Frogs,
In the following code :
\version "2.18.0"
myMusic = {
R1
\repeat volta 2 {
\repeat unfold 2 R1
}
s8
}
\new StaffGroup <<
\set Score.startRepeatType = #"[|:"
\set Score.endRepeatType = #":|]"
\new Staff {
On 13-09-19 12:23 PM, Phil Holmes wrote:
- Original Message - From: "Mark Knoop"
To:
Sent: Thursday, September 19, 2013 4:51 PM
Subject: bendAfter affected by bar numbers - possible bug?
In the following example the bends are compressed to avoid the bar
numbers. This wou
- Original Message -
From: "Mark Knoop"
To:
Sent: Thursday, September 19, 2013 4:51 PM
Subject: bendAfter affected by bar numbers - possible bug?
In the following example the bends are compressed to avoid the bar
numbers. This would seem to be unnecessary. Possible bu
Sorry for delay; it's here:
http://code.google.com/p/lilypond/issues/detail?id=3418
2013/6/20 Janek Warchoł :
> i'll report it.
>
> 2013/6/20 Karol Majewski :
>> Hi,
>>
>> It seems to me that the strange spacing behavior, which I described here:
>>
>> http://lilypond.1069038.n5.nabble.com/strange-
i'll report it.
2013/6/20 Karol Majewski :
> Hi,
>
> It seems to me that the strange spacing behavior, which I described here:
>
> http://lilypond.1069038.n5.nabble.com/strange-spacing-behavior-is-it-expected-td147132.html
>
> is not expected and therefore should be reported as a bug. Probably the
Hi,
It seems to me that the strange spacing behavior, which I described here:
http://lilypond.1069038.n5.nabble.com/strange-spacing-behavior-is-it-expected-td147132.html
is not expected and therefore should be reported as a bug. Probably there
is something wrong with so called "double backslash
Colin Hall writes:
> pls writes:
>> Am 07.02.2013 um 10:46 schrieb Richard Lanyon :
>>
>>> The last note in the file "02a-Rests-Durations.xml" is a dotted 128th note,
>>> but
>>> the file is set up with 32 divisions per quarter notes, which means that a
>>> dotted 128th note is not representable
Many thanks for confirming this - I realise it's only a small thing, but I
just wanted to make sure I understood the intent of the test.
Cheers,
Richard
From: pls
To: Richard Lanyon ,
Cc: bug-lilypond@gnu.org
Date: 08/02/2013 11:22
Subject: Re: possible bug in Mus
pls writes:
> Am 07.02.2013 um 10:46 schrieb Richard Lanyon :
>
>> The last note in the file "02a-Rests-Durations.xml" is a dotted 128th note,
>> but
>> the file is set up with 32 divisions per quarter notes, which means that a
>> dotted 128th note is not representable (it would be 1.5 divisions
Richard,
you are right it should be 64 divisions but for some reason the result is
correct. So it's not the worst musicxml2ly bug!
Cheers
patrick
Am 07.02.2013 um 10:46 schrieb Richard Lanyon :
> The last note in the file "02a-Rests-Durations.xml" is a dotted 128th note,
> but
> the file is se
The last note in the file "02a-Rests-Durations.xml" is a dotted 128th note, but
the file is set up with 32 divisions per quarter notes, which means that a
dotted 128th note is not representable (it would be 1.5 divisions long). Is this
intentional? I understand that the notated duration does not ne
Il 04/01/2013 15:10, Colin Hall ha scritto:
Please correct me if I am wrong, but as far as I can see there is no
actual bug here.
If you would like to start a discussion about a design change then I
think either lilypond-user or lilypond-dev are the correct place to do
that.
Once you have a con
Il 04/01/2013 15:26, David Kastrup ha scritto:
Federico Bruni writes:
2013/1/4 Eluze
Yevgeny Lezhnin wrote
When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
all notes, that can be on 0 fret.
see the NR:
http://www.lilypond.org/doc/v2.17/Documentation/notation/common-n
Federico Bruni writes:
> 2013/1/4 Eluze
>
>> Yevgeny Lezhnin wrote
>> > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
>> > all notes, that can be on 0 fret.
>>
>> see the NR:
>>
>> http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-string
On Fri, Jan 04, 2013 at 12:34:08PM +0100, Federico Bruni wrote:
> 2013/1/4 Eluze
>
> > Yevgeny Lezhnin wrote
> > > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
> > > all notes, that can be on 0 fret.
> >
> > see the NR:
> >
> > http://www.lilypond.org/doc/v2.17/Documentat
2013/1/4 Eluze
> Yevgeny Lezhnin wrote
> > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
> > all notes, that can be on 0 fret.
>
> see the NR:
>
> http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-strings
>
> Even when minimumFret is set,
enever possible. This
behaviour can be changed by setting restrainOpenStrings to #t
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Fwd-Possible-bug-with-minimumFret-tp138764p138780.html
Sent from the Bugs mailing list archive at Nabb
When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
all notes, that can be on 0 fret.
\version "2.17.9"
\language "deutsch"
musicForBass = \relative c {
\tempo 4 = 90
\set TabStaff.minimumFret = #3
g4 f e d c h a g
}
bassStaff =
\new Staff {
\set Staff.instrument
Fine by me. Great snippets btw!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Sun, Jun 10, 2012 at 07:26:52AM +, Sami Amiris wrote:
> Mark Mathias gmail.com> writes:
>
> >
> > Colin,
> > I just read through this, and I think it is over my head as far as creating
> > issues as suggested by David. I'll pass on this one hoping someone more
> > competent untangles the
Thank you!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi Sami, Mark,
On Sun, Jun 10, 2012 at 07:26:52AM +, Sami Amiris wrote:
> Mark Mathias gmail.com> writes:
>
> >
> > Colin,
> > I just read through this, and I think it is over my head as far as creating
> > issues as suggested by David. I'll pass on this one hoping someone more
> > compete
Mark Mathias gmail.com> writes:
>
> Colin,
> I just read through this, and I think it is over my head as far as creating
> issues as suggested by David. I'll pass on this one hoping someone more
> competent untangles the threads to create issues as needed.
> Mark
Normally I would just shut my m
Colin,
I just read through this, and I think it is over my head as far as creating
issues as suggested by David. I'll pass on this one hoping someone more
competent untangles the threads to create issues as needed.
Mark
On Fri, Jun 8, 2012 at 1:06 PM, Sami Amiris wrote:
>
> > If you have found s
> If you have found something interesting perhaps it is worthy of
> becoming a Lilypond Snippet?
This is not really for me to say. If you think that it is worthy of being a
snippet, by all means take it!
Thank you for everything.
___
bug-lilypond
On Fri, Jun 08, 2012 at 04:02:55PM +, Sami Amiris wrote:
> I think I solved the problem. I sent a message to the other list.
> Should I copy it here too?
Glad to hear you have fixed it!
If you have found something interesting perhaps it is worthy of
becoming a Lilypond Snippet?
There's no
I think I solved the problem. I sent a message to the other list.
Should I copy it here too?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thanks! I will try this with 7/8 that the book examples use...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
s on the version (I'm using 2.15.40) - please consult the
manuals : there's also a link there to the file in LilyPond where these
settings are defined for all timings.
hth
Eluze
--
View this message in context:
http://old.nabble.com/Possible-bug%2C-or-I-am-doing-something-wrong--tp3396
Would you be kind enough to share the code?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e (maybe open a new post and wait for a few hours…)
Eluze
--
View this message in context:
http://old.nabble.com/Possible-bug%2C-or-I-am-doing-something-wrong--tp33965119p33977658.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
_
-Eluze gmail.com> writes:
> that's all I tried to solve…
and you did, and thank you! Once I saw that, I tried all sorts of combinations
to
circumvent the autochange problem that followed by a "hat trick"
sort of workaround, but always hit a brick wall due to the
autochange going haywire...
even though I am a
> registered
> user. Still pending...
>
altogether, did you think of switching staves manually? you'd be faster than
waiting for a new release with this/these bug/bugs fixed (they are not even
in the issue tracker yet!)
Eluze
it's here now
--
View this me
> does it help if you put
>
> \autochange \new Voice { … }
>
>
> Eluze
Thank you. It opens up a new can of worms. The stem up - down work fine now,
but
the autochange is reversed! Running this will show what I mean:
\version "2.14.2"
\score
{
\new PianoStaff
<<
Sami wrote:
>
>
> Thank you. Just sent it.
>
does it help if you put
\autochange \new Voice { … }
?
Eluze
--
View this message in context:
http://old.nabble.com/Possible-bug%2C-or-I-am-doing-something-wrong--tp33965119p33976023.html
Sent from the Gnu - Lilypond - Bugs
Colin Hall gmail.com> writes:
> The best place for "what is going on here" type questions is the
> lilypond-user mailing list. You could try sending your last to
> bug-lilypond there and see if anyone steps up to help.
Thank you. Just sent it.
___
On Wed, Jun 06, 2012 at 03:36:47PM +0300, Sami - Vasileios Amiris wrote:
> Thank you very much. I sent a message to the group. If it is not good
> enough, just tell me what to do and I will gladly do it. Thank you once
> again!
Thank you, Sami, you have made it very clear. It is definitely good
en
Thank you very much. I sent a message to the group. If it is not good
enough, just tell me what to do and I will gladly do it. Thank you once
again!
2012/6/6 Colin Hall
>
> Hi Sami,
>
> On Wed, Jun 06, 2012 at 07:41:13AM +, Sami Amiris wrote:
> > David Kastrup gnu.org> writes:
> >
> >
> > >
> Thanks for the bug report you sent in.
>
> You are new to lilypond so it is hard for you to separate the bugs
> from everything else in your example.
You can say that again! Reducing the initial example to the reduced example
took
10 years out of my life. Growing pains, I know...
> If one
Hi Sami,
On Wed, Jun 06, 2012 at 07:41:13AM +, Sami Amiris wrote:
> David Kastrup gnu.org> writes:
>
>
> > It means that if there is supposed to be a right way, it is too hard to
> > discover. You triggered a number of bugs and/or design deficiencies.
> > Enough of them actually to make f
David Kastrup gnu.org> writes:
> It means that if there is supposed to be a right way, it is too hard to
> discover. You triggered a number of bugs and/or design deficiencies.
> Enough of them actually to make for several independent bug reports. I
> think that your main issue would likely sho
Sami Amiris writes:
> David Kastrup gnu.org> writes:
>
>>
>> There are so many things going wrong here that it is not actually easy
>> to start. This is still not a minimal example, and in fact it would
>> warrant several minimal examples.
>
> As I said, I am a newbie. I stretched my abilities
David Kastrup gnu.org> writes:
>
> There are so many things going wrong here that it is not actually easy
> to start. This is still not a minimal example, and in fact it would
> warrant several minimal examples.
As I said, I am a newbie. I stretched my abilities to shrink it this far.
> One t
Sami Amiris writes:
> David Kastrup gnu.org> writes:
>
>>
>> Sami Amiris gmail.com> writes:
>>
>> > Please run this, it is self-explanatory. It is an issue with
>> > autochange and
>> > beaming. Is it me, or a bug?
>>
>> You are doing something wrong. You don't start a voice before writing
by the way, it works fine of the only thing I change is the
"\relative c''" of the "up" staff, to
"\relative c'" or lower.
The whole thing crumbles only when the
"\relative"
of the upper hand goes from c'' and up.
Otherwise, it works as intended. Even without entering voices.
__
Janek Warchoł gmail.com> writes:
>
> also, please send smaller examples. See
> http://www.lilypond.org/tiny-examples.html
I apologise. New and clumsy...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-
David Kastrup gnu.org> writes:
>
> Sami Amiris gmail.com> writes:
>
> > Please run this, it is self-explanatory. It is an issue with autochange and
> > beaming. Is it me, or a bug?
>
> You are doing something wrong. You don't start a voice before writing
> \autochange, and so \autochange _f
On Tue, Jun 5, 2012 at 6:39 PM, David Kastrup wrote:
> Sami Amiris writes:
>
>> Please run this, it is self-explanatory. It is an issue with autochange and
>> beaming. Is it me, or a bug?
>
> [...]
also, please send smaller examples. See
http://www.lilypond.org/tiny-examples.html
cheers,
Janek
Sami Amiris writes:
> Please run this, it is self-explanatory. It is an issue with autochange and
> beaming. Is it me, or a bug?
You are doing something wrong. You don't start a voice before writing
\autochange, and so \autochange _first_ changes the Staff, and then
there is no longer a need t
Please run this, it is self-explanatory. It is an issue with autochange and
beaming. Is it me, or a bug?
\version "2.14.2"
\score
{
\new PianoStaff
<<
\new Staff = "up
"Phil Holmes" writes:
> OK. It's not a bug in the build system - the directory exists. If
> you do use -o ./out-www/ (with the trailing slash) it makes no
> difference - it still produces files names out-www.pdf, etc.
It might be a nice featurelet if with this spelling the directory was
create
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Bugs"
Sent: Sunday, February 12, 2012 12:44 PM
Subject: Re: Possible bug
On Sun, Feb 12, 2012 at 12:35:28PM -, Phil Holmes wrote:
[path]lilypond -H texidoc -H options -o ./out-www
"Phil Holmes" writes:
> Again, this is one I'm not sure is a bug or not - I can't find it in
> the bug list.
>
> make runs lilypond with a number of command lines like the one below:
>
> [path]lilypond -H texidoc -H options -o ./out-www
> /home/phil/lilypond-git/input/regression/midi/key-option-a
On Sun, Feb 12, 2012 at 12:35:28PM -, Phil Holmes wrote:
> [path]lilypond -H texidoc -H options -o ./out-www
> /home/phil/lilypond-git/input/regression/midi/key-option-all-staves.ly
>
> This is supposed to create the files key-option-all-staves.texidoc
> key-option-all-staves.options key-opti
Again, this is one I'm not sure is a bug or not - I can't find it in the bug
list.
make runs lilypond with a number of command lines like the one below:
[path]lilypond -H texidoc -H options -o ./out-www
/home/phil/lilypond-git/input/regression/midi/key-option-all-staves.ly
This is supposed t
>>>> investigated, though.
>>>>
>>> it obviously does:
>>>
>>> { \accidentalStyle "modern-voice-cautionary" ces1 c }
>>> { #(set-accidental-style 'modern-voice-cautionary) ces1 c }
>>
>> Sigh. I'll investigate
David Kastrup writes:
> -Eluze writes:
>
>> David Kastrup wrote:
>>>
>>> -Eluze writes:
>>>
Phil Holmes wrote:
>
> With this input:
>
> {
> #(set-accidental-style 'modern-voice-cautionary)
> \clef bass
> ces4 ces ces ces |
> c4 c c c |
> }
>>
-Eluze writes:
> David Kastrup wrote:
>>
>> -Eluze writes:
>>
>>> Phil Holmes wrote:
With this input:
{
#(set-accidental-style 'modern-voice-cautionary)
\clef bass
ces4 ces ces ces |
c4 c c c |
}
I get a cautionary in the second
nce. It is a nicer
> interface, but the results should be the same I think. I have not
> investigated, though.
>
it obviously does:
{ \accidentalStyle "modern-voice-cautionary" ces1 c }
{ #(set-accidental-style 'modern-voice-cautionary) ces1 c }
http://old.nabble.com/fil
-Eluze writes:
> Phil Holmes wrote:
>>
>> With this input:
>>
>> {
>> #(set-accidental-style 'modern-voice-cautionary)
>> \clef bass
>> ces4 ces ces ces |
>> c4 c c c |
>> }
>>
>> I get a cautionary in the second bar up until 2.15.16 (which I believe I
>> would expect) but none in 2.1
ut none in 2.15.18.I reckon this is a bug, but would
> like
> someone who does this stuff to confirm that it's not a deliberate change
> (for some reason).
>
>
use \accidentalStyle "modern-voice-cautionary" instead - couldn't find this
in Changes either!
With this input:
{
#(set-accidental-style 'modern-voice-cautionary)
\clef bass
ces4 ces ces ces |
c4 c c c |
}
I get a cautionary in the second bar up until 2.15.16 (which I believe I
would expect) but none in 2.15.18.I reckon this is a bug, but would like
someone who does this stuff t
2011/3/20 Carl Sorensen :
>
>
>
> On 3/19/11 4:18 PM, "Wim van Dommelen" wrote:
>
>>> I'm not top posting.
>>
>> I found some weird behaviour in music disappearing when adding a lyric.
>>
>> This is the smallest I could get the problem reduced to:
>>
>> \version "2.13.54"
>>
>> \score {
>>
On 3/19/11 4:18 PM, "Wim van Dommelen" wrote:
>> I'm not top posting.
>
> I found some weird behaviour in music disappearing when adding a lyric.
>
> This is the smallest I could get the problem reduced to:
>
> \version "2.13.54"
>
> \score {
> \new Staff {
> \relat
1 - 100 of 134 matches
Mail list logo
