On 15 Sep 2012, at 23:55, eluze wrote:
>
> Damian leGassick wrote
>>
>> Hi all
>>
>> If I run this with no arguments (or have a tagline) everything's fine
>> if run the file with -dbackend=eps the bottom stem is clipped
>>
>> any clues?
>>
>>
>
> how do you open the eps file? I use IrfanVi
On Sat, Sep 15, 2012 at 07:26:55PM +0200, Knut Petersen wrote:
> Have a look at the attached source and the png, the problem is obvious.
> The first appearance dictates which of the two enharmonic equivalents is
> chosen for the ambitus.
Thanks for the report, Knut. You have encountered a known is
sorry, when I compiled I had inadvertently added a second score and then it
worked.
but this also is a clue: add a simple \markup " " at the end of your file
and then it should not cut off the beams.
I'll investigate later and send it to the bug list if needed!
Eluze
--
View this message in c
> but this also is a clue: add a simple \markup " " at the end of your
> file and then it should not cut off the beams.
>
> I'll investigate later and send it to the bug list if needed!
http://code.google.com/p/lilypond/issues/detail?id=720
It would be good if some images could be added for ref
On Sat, Sep 15, 2012 at 10:21 AM, Stefan Thomas
wrote:
> Dear Robert,
> thanks for Your proposals.
> I think a dotted quarter rest isn't a good solution.
> Musicians normally don't like them because they can easily be overlooked.
> And there is no keysignature, it's so called "atonal" music.
So,
On Wed, Sep 05, 2012 at 01:17:35AM -0700, eluze wrote:
>
> Frank Steinmetzger wrote
> >
> >
> > While the empty staves get removed as expected, using this feature breaks
> > the
> > merge-rests code -- I get two rests above each other.
> >
>
> for me it works - can you provide an example?
O
2012/9/16 Frank Steinmetzger :
> On Wed, Sep 05, 2012 at 01:17:35AM -0700, eluze wrote:
>>
>> Frank Steinmetzger wrote
>> >
>> >
>> > While the empty staves get removed as expected, using this feature breaks
>> > the
>> > merge-rests code -- I get two rests above each other.
>> >
>>
>> for me it wo
Thomas Morley writes:
>> \context {
>> \Staff
>> \override RestCollision #'positioning-done = #merge-rests-on-positioning
>> \override MultiMeasureRest #'Y-offset =
>> #merge-multi-measure-rests-on-Y-offset
>> }
>>
>> I simulated this in my attached example by having a \layout block at the
Hi list,
Is it possible to force an extra bar line in the form
\bar ":"
when inserted into a multi-stave score to only apply to one staff
instead of the default where the dots are added to all staves?
Many thanks,
Peter
--
//=
-> Peter O'Doherty
-> http://www.pe
On Sun, Sep 16, 2012 at 07:08:47PM +0200, David Kastrup wrote:
> […] Any changes made previously to \Staff after the definition of
> RemoveEmptyStaffContext will be gone. Broken by design, so it got
> deprecated. Perhaps we are not doing people a favor keeping it around.
Good to know, thank you
Werner LEMBERG wrote
>
>
> http://code.google.com/p/lilypond/issues/detail?id=720
>
I don't think it's the same bug
> It would be good if some images could be added for reference.
>
here they are:
http://lilypond.1069038.n5.nabble.com/file/n133040/png_snippet_with_changeStaff.ly
png_snippet
2012/9/16 Peter O'Doherty :
> Hi list,
>
> Is it possible to force an extra bar line in the form
>
> \bar ":"
>
> when inserted into a multi-stave score to only apply to one staff instead of
> the default where the dots are added to all staves?
>
> Many thanks,
> Peter
Hi Peter,
two possible meth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why does the attached file fail?
Simplified:
c c c c | c c c |: c | c c c c | 1. c c c :| 2. c c c c | c c c c ||
It seems to me, according to what (I recall that) I learned throughout
school, that this is correct; and when unfolded, all the bar lin
On Sun, Sep 16, 2012 at 8:01 PM, Christopher R. Maden wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Why does the attached file fail?
>
> Simplified:
>
> c c c c | c c c |: c | c c c c | 1. c c c :| 2. c c c c | c c c c ||
>
> It seems to me, according to what (I recall that) I learn
Christopher R. Maden maden.org> writes:
> It appears that the incomplete bar in the first alternative is
> carrying over into the second, which is nonsensical.
Yes. LilyPond counts beats straight through the repeats. Someday someone
will volunteer the effort to improve that.
Until then, you s
On Tue, Sep 11, 2012 at 10:12 AM, Janne Uusitalo
wrote:
> On Sat, Sep 8, 2012 at 1:03 AM, Thomas Morley
> wrote:
>
at the end of a line I'd change the order in which KeyCancellation and
KeySignature appears. This requires some new settings in KeySignature
>
> Thanks for this suggestion
>> http://code.google.com/p/lilypond/issues/detail?id=720
>>
> I don't think it's the same bug
Hmm. I see that the rendering of the documentation snippets has
changed fundamentally because the code has been changed, hiding the
deficiency. Compare this
http://lilypond.org/doc/v2.14/Documenta
17 matches
Mail list logo
