Re: packed-spacing setting produce bad layout with long text
On Sun, Jul 20, 2014 at 9:42 AM, Colin Campbell wrote:
>
> It works for me when I move the \override into a \layout block:
[hidden snippet...]
With your snippet, it acts as if the packed-spacing setting is
useless. Removing the whole \context block produces same layout.
And with one slight change the problem surfaces again:
%=
\score {
\relative c' {
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
}
\layout {
\context {
\Score
\override SpacingSpanner #'packed-spacing = ##t % <--- no Score prefix
}
}
}
%=
Abel
>
>
> Cheers,
> Colin
>
>
> --
> Excellent day for putting Slinkies on an escalator.
> - Dan Galvin, TFTD List 20070228
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: packed-spacing setting produce bad layout with long text
On 14-07-19 07:11 PM, Abel Cheung wrote:
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
\repeat unfold 16 {c}
}
It works for me when I move the \override into a \layout block:
\version "2.19.11"
\score {
\relative c' {
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
}
\layout {
\context {
\Score
\override Score.SpacingSpanner #'packed-spacing = ##t
}
}
}
Cheers,
Colin
--
Excellent day for putting Slinkies on an escalator.
- Dan Galvin, TFTD List 20070228
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
packed-spacing setting produce bad layout with long text
It is illustrated with this fragment:
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
\repeat unfold 16 {c}
}
The packed-spacing setting acts as if \textLengthOn is in effect, producing
unsightly layout between 3rd and 4th note.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
binding-offset bug
Hi,
it seems that binding-offset size scales accordingly to global-staff-size,
which of course is a bug:
%%%
\version "2.19.10"
#(set-global-staff-size 20)
\paper {
top-markup-spacing = #'((basic-distance . 0) (minimum-distance . 0) (padding
. 0) (stretchability . 0))
two-sided = ##t
binding-offset = 2\cm
}
\bookpart {
\header {
poet = \markup { \abs-fontsize #13 "left" }
composer = \markup { \abs-fontsize #13 "right" }
}
\score {
\new Staff { d'4 }
}
}
%%%
Now, change global-staff-size to smaller and you'll notice that inner-margin
becomes smaller too! However, when binding-offset is disabled, changing
global-staff-size does not affect inner-margin size.
Best
--Karol
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
On 19/07/14 15:18, David Kastrup wrote: > Jan Nieuwenhuizen writes: > >> James writes: >> >>> Does it also matter that the clef is different when you run it back >>> through midi2ly (at least it was for me running 2.19.8) >> Yes, for 2.16.2 also. >> >>> I assume so in which case that is a second bug report right? >> If so, indeed a second report. For this one, the qualification >> of bug is even more disputable. If MIDI has a way to encode >> clef information, then it's a bug. > I don't think Midi can encode clefs. > http://code.google.com/p/lilypond/issues/detail?id=4018 James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Martin Tarenskeen writes: > As far as I know there is not a commonly accepted MIDI file event for > Clefs, like there is for Time Signature (FF 58 04) and Key Signature > (FF 59 02). But I guess it is possible for a Sequencer like Rosegarden > to put a special message in a "Sequencer Specific Meta-Event" (FF > 7F). Or in a text event (FF 01) which, according to the Standard > MIDI-File Format Spec 1.1 that I'm looking into now, can contain "Any > type of text containing anything". Yes, that's an interesting perspective. Why not talk to the Rosegarder guys and gals? Greetings, Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
On Sat, 19 Jul 2014, Francisco Vila wrote: Sure? I know there is a message for encoding the key signature, but the clef? Yesterday I was messing with a MIDI imported in Rosegarden and edited a bass segment with the event editor, and one of the first events was a clef event. Let me look at it again tonight. Maybe the clef event was generated by Rosegarden on import? As far as I know there is not a commonly accepted MIDI file event for Clefs, like there is for Time Signature (FF 58 04) and Key Signature (FF 59 02). But I guess it is possible for a Sequencer like Rosegarden to put a special message in a "Sequencer Specific Meta-Event" (FF 7F). Or in a text event (FF 01) which, according to the Standard MIDI-File Format Spec 1.1 that I'm looking into now, can contain "Any type of text containing anything". Personally I would not choose to let Lilypond/midi2ly be able to export or import such a non-standard Clef event. -- MT ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila writes: > Maybe the clef event was generated by Rosegarden on import? That would not surprise me. There is a lot of smart heuristics you can think of to amend midi2ly. Greetings, Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
2014-07-19 16:19 GMT+02:00 David Kastrup : > Francisco Vila writes: > >> El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió: >>> >>> If MIDI has a way to encode >>> clef information, then it's a bug. >>> >> >> Yes it has. > > Sure? I know there is a message for encoding the key signature, but the clef? Yesterday I was messing with a MIDI imported in Rosegarden and edited a bass segment with the event editor, and one of the first events was a clef event. Let me look at it again tonight. Maybe the clef event was generated by Rosegarden on import? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila writes: >> If MIDI has a way to encode >> clef information, then it's a bug. >> > > Yes it has. That's nice. If you have documentation you can point at, that would help. Greetings, Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Francisco Vila writes: > El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió: >> >> If MIDI has a way to encode >> clef information, then it's a bug. >> > > Yes it has. Sure? I know there is a message for encoding the key signature, but the clef? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
Jan Nieuwenhuizen writes: > James writes: > >> Does it also matter that the clef is different when you run it back >> through midi2ly (at least it was for me running 2.19.8) > > Yes, for 2.16.2 also. > >> I assume so in which case that is a second bug report right? > > If so, indeed a second report. For this one, the qualification > of bug is even more disputable. If MIDI has a way to encode > clef information, then it's a bug. I don't think Midi can encode clefs. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
El 19/07/2014 15:58, "Jan Nieuwenhuizen" escribió: > > If MIDI has a way to encode > clef information, then it's a bug. > Yes it has. > Greetings, > Jan > > -- > Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org > Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
James writes: > Does it also matter that the clef is different when you run it back > through midi2ly (at least it was for me running 2.19.8) Yes, for 2.16.2 also. > I assume so in which case that is a second bug report right? If so, indeed a second report. For this one, the qualification of bug is even more disputable. If MIDI has a way to encode clef information, then it's a bug. Greetings, Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly produces 8*5, can we do better?
On 17/07/14 22:08, 'Jan Nieuwenhuizen wrote: > Hi, > > Running > > lilypond bug.ly > midi2ly bug.midi > grep fis bug-midi.ly > > produces > > fis1 > fis'4. d8*5 > > While technically correct, duration-wise, in printed output it > will look as if the d2 has been omitted. In other words > > fis'4. d8 ~ d2 > > looks so much nicer! Tested with 2.16.2 and 2.19.11. > > Greetings, Jan > > > Does it also matter that the clef is different when you run it back through midi2ly (at least it was for me running 2.19.8) I assume so in which case that is a second bug report right? James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
