headers
codesite-noreply | 1 Mar 2008 01:09
Picon
Favicon

Issue 583 in lilypond: Setting system-count disables stretching inside a system

Issue 583: Setting system-count disables stretching inside a system
http://code.google.com/p/lilypond/issues/detail?id=583

Comment #1 by joeneeman:
Duplicate of 325.

Issue attribute updates:
	Status: Duplicate

--

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Permalink | Reply | 1 comment |
headers
Rune Zedeler | 1 Mar 2008 01:41
Picon
Picon
Favicon

Re: System-stretch do not work with system-count

Rune Zedeler skrev:
> If system-count is set then system-stretching does not take place:

Sorry for - eh - triplicate report.

-Rune
Permalink | Reply | 0 comments |
headers
Joe Neeman | 1 Mar 2008 03:31
Picon

Re: page-count only works with an even number of pages

On Wed, 2008-02-27 at 20:43 +0100, Wilbert Berendsen wrote:
> Hi,
> 
> when I set \paper { page-count = 7 } (very current LilyPond) it 
> *says* 'Fitting music on 7 pages', but it actually *prints* 6 pages.
> Same with 5: it *says* 5, but prints 4.

I think this is fixed in git but it is hard to tell because you didn't
attach a complete example; please do so in the future (in the case of
page-breaking bugs, non-minimal examples are accepted because minimal
examples can be very hard to find).

Joe
Permalink | Reply | 3 comments |
headers
Joe Neeman | 1 Mar 2008 03:41
Picon

Re: Dynamics take up too much vertical space

On Fri, 2008-02-29 at 15:55 +0100, Rune Zedeler wrote:
> The outlines used to detect collisions are way too rough in the case of 
> dynamics.
> 
> \version "2.11.0"
> \layout { ragged-last = ##t }
> {
>    \dynamicUp
>    d''2  e''8 \< c'' c''4\!
>    d''2( e''8)\< c'' c''4\!
>    d''2( e''8)\> c'' c''4\!
>    d''2( e''8)\< c'' c''4\!\f
> }
> 
> In this example we notice the following.
> The first measure looks fine.
> In the second measure the cresc is for too high. The only difference to 
> first measure is the added slur, so it must be the slur, that pushes the 
> dynamic too high up.

Currently, all of the outside-staff placement is done using bounding
boxes. In this situation, I agree that the output is bad but the changes
needed to use more accurate outlines are probably too far-reaching to be
made so late in the 2.11 cycle. Anyway, I have added this as #584.

Joe
Permalink | Reply | 0 comments |
headers
codesite-noreply | 1 Mar 2008 03:41
Picon
Favicon

Issue 584 in lilypond: Outside-staff placement uses rough approximations

Issue 584: Outside-staff placement uses rough approximations
http://code.google.com/p/lilypond/issues/detail?id=584

New issue report by joeneeman:
%{
Reported by Rune:
The outlines used to detect collisions are way too rough in the case of
dynamics.
%}

\version "2.11.0"
\layout { ragged-last = ##t }
{
   \dynamicUp
   d''2  e''8 \< c'' c''4\!
   d''2( e''8)\< c'' c''4\!
   d''2( e''8)\< c'' c''4\!\f
}

%{
In this example we notice the following:
The first measure looks fine.

In the second measure the cresc is far too high.

In the third measure the cresc is even higher than the 2nd measure. The
forte sign pushes up the hairpin.
%}

Attachments:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Herrmann | 2 Mar 2008 02:25
Picon

Problems after installing

After installing the latest stable Lilypondversion I tried to follow the first
steps instructions and did not get a useful result

# -*-compilation-*-
»C:/Daten/test.ly.ly« wird verarbeitet
Analysieren...
Interpretation der Musik...[2]
Vorverarbeitung der grafischen Elemente...
Layout nach »C:Daten.ps« ausgeben...
Konvertierung nach »C:Daten.pdf«...
»gs -q   -dDEVICEWIDTHPOINTS#595.28 -dDEVICEHEIGHTPOINTS#841.89 
-dCompatibilityLevel#1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE#pdfwrite
-sOutputFile#"C:Daten.pdf" -c .setpdfwrite -f "C:Daten.ps"« gescheitert (1)
Fehler: gescheiterte Dateien: "C:\\Daten\\test.ly.ly"

only this. What did I do wrong?

Greetings Peter
Permalink | Reply | 1 comment |
headers
Mats Bengtsson | 2 Mar 2008 19:24
Picon
Picon
Favicon

Re: Problems after installing

It seems you didn't manage to convince your text editor
to use the correct file suffix, since your file is called test.ly.ly
instead of test.ly. If you used the LilyPad editor that's started
when you double-click on the LilyPond icon, my guess is that
you should not manually specify the file name with the suffix
.ly in the Save window since it's added automatically (most
programs would handle this correctly but the LilyPad editor
is, in contrast to Lilypond itself, a very ill-developed piece
of software). There are many better text editors available
with support for LilyPond, see
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Text-editor-support#Text-editor-support

   /Mats

Peter Herrmann wrote:

>After installing the latest stable Lilypondversion I tried to follow the first
>steps instructions and did not get a useful result
>
># -*-compilation-*-
>»C:/Daten/test.ly.ly« wird verarbeitet
>Analysieren...
>Interpretation der Musik...[2]
>Vorverarbeitung der grafischen Elemente...
>Layout nach »C:Daten.ps« ausgeben...
>Konvertierung nach »C:Daten.pdf«...
>»gs -q   -dDEVICEWIDTHPOINTS#595.28 -dDEVICEHEIGHTPOINTS#841.89 
>-dCompatibilityLevel#1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE#pdfwrite
>-sOutputFile#"C:Daten.pdf" -c .setpdfwrite -f "C:Daten.ps"« gescheitert (1)
>Fehler: gescheiterte Dateien: "C:\\Daten\\test.ly.ly"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valentin Villenave | 2 Mar 2008 21:29
Picon

Re: pas de son midi= no sound with kmid

[Redirecting to -user-fr]

Bonjour,

- tout d'abord, bienvenue sur cette liste de discussion qui est hélas
en anglais. Il existe cependant une liste spécialement consacrée aux
utilisateurs francophones de LilyPond : plus d'informations sur
http://lists.gnu.org/mailman/listinfo/lilypond-user-fr

- ensuite, il est impossible à quiconque sur cette liste de répondre
en disposant d'aussi peu d'informations. S'agit-il d'un fichier MIDI
produit par LilyPond ? Avez-vous fait le test avec d'autres fichiers ?
Votre fichier LilyPond était-il correctement formulé ?

- manifestement, il ne s'agit pas d'un problème lié à LilyPond (plus
probablement à KDE) ; en tout cas nous n'en avons pas rencontré de
cette nature à ce jour. Je vous conseillerais de faire quelques tests
avec différents fichiers MIDI, puis de contacter l'équipe de KDE si le
problème persiste.

Cordialement,
V. Villenave

2008/2/29, thimothe <arnauld.thimothe <at> free.fr>:
> Centos 5 kde 3.5...
>
>
>
>  _______________________________________________
>  bug-lilypond mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mats Bengtsson | 2 Mar 2008 23:23
Picon
Picon
Favicon

Bass figures collapsing

There's a regression bug in the handling of figured bass.
If you use extender lines and only one of two simultaneous
figures is extended, then the two figures are written on top
of each other. Example
\version "2.11.41"
\new FiguredBass \figuremode{
\set useBassFigureExtenders = ##t
<4 6> <4>
}

Another example is actually shown in the following snippet
copied directly from the manual,

<<
  \new Voice
  \figures {
    \set useBassFigureExtenders = ##t
    <6 4->4. <6 4->16. <6 4->32 <5>8. r16 <6>8 <6\! 5->
  }
  {
    \clef bass
    f16. g32 f16. g32 f16. g32 f16. g32 f8. es16 d8 es
  }
>>

where the final figure shows a similar collision.
Both these examples work well with version 2.10.

    /Mats
(Continue reading)

Permalink | Reply | 501 comments |
headers
codesite-noreply | 2 Mar 2008 23:47
Picon
Favicon

Issue 585 in lilypond: Regression: Bass figures collapsing

Issue 585: Regression: Bass figures collapsing
http://code.google.com/p/lilypond/issues/detail?id=585

New issue report by v.villenave:
% There's a regression bug in the handling of figured bass.

% If you use extender lines and only one of two simultaneous
% figures is extended, then the two figures are written on top
% of each other. Example
\version "2.11.41"
\new FiguredBass \figuremode{
\set useBassFigureExtenders = ##t
<4 6> <4>
}

% Another example is actually shown in the following snippet
% copied directly from the manual,

<<
 \new Voice
 \figures {
   \set useBassFigureExtenders = ##t
   <6 4->4. <6 4->16. <6 4->32 <5>8. r16 <6>8 <6\! 5->
 }
 {
   \clef bass
   f16. g32 f16. g32 f16. g32 f16. g32 f8. es16 d8 es
 }
>>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane