On 14 January 2017 at 21:12, Trevor Daniels wrote:
>
> Thomas Morley wrote Friday, January 13, 2017 9:05 PM
>
>
> > 2017-01-13 17:05 GMT+01:00 Trevor Daniels :
> >>
> >> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
> >>
> >>
On 13 January 2017 at 01:20, Trevor Daniels wrote:
>
> Thomas Morley wrote Thursday, January 12, 2017 10:26 PM
>
>
> > 2017-01-12 21:13 GMT+01:00 Risto Vääräniemi :
> >
> >> The spacing between ChordNames and Staff seems a bit tight by default.
> I've
&g
2008/11/18 Neil Puttock <[EMAIL PROTECTED]>:
> It's fixed in git; I forgot to make sure that the volta bracket checks
> for the new barline strings when deciding to hide the right edge.
Nice! Thanks. I'll try it again when the next version is released.
>> That warning also occurs with the defaul
Hi Neil,
2008/9/4 Neil Puttock <[EMAIL PROTECTED]>:
> 2008/9/3 Risto Vääräniemi <[EMAIL PROTECTED]>:
>
>> Thanks Neil. They look very nice. Do they work with the volta brackets?
>
> Yes. You'd just have to override the default setting for
> doubleRepeatType t
2008/10/30 Trevor Daniels <[EMAIL PROTECTED]>:
> In my experience (vocal music), cresc and dim without a dashed
> line is used almost universally. Hairpins are used when an extent
> is being indicated.
I have the same impression (choir music).
> I vote for not adding the dashed line to these co
2008/10/8 Graham Percival <[EMAIL PROTECTED]>:
> http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Generating-LilyPond-files
Yes. Denemo is listed there but the link points to the old Sourceforge
page and not to denemo.org.
-Risto
___
Hi all,
2008/9/7 Neil Puttock <[EMAIL PROTECTED]>:
> Here's a patch which implements two double repeat signs as
> alternatives to the default type, together with a new context property
> `doubleRepeatType' which can be used to change the default for volte
> using \repeat volta.
Has anyone had a
2008/9/9 Neil Puttock:
> It works OK as long as there's a break (Mats fixed it in January).
>
> To ensure that the custom barline reverts back to a standard type if
> there's no break would require some kludgy work in
> repeat-acknowledge-engraver.cc I think.
Ah, I had misinterpreted Mats' messag
2008/9/4 Neil Puttock <[EMAIL PROTECTED]>:
> Yes. You'd just have to override the default setting for
> doubleRepeatType to use the new styles automatically.
Sorry to pester you again with this nice new feature...
Im' sure the automatic volta brackets will work fine. Have you also
tested it with
2008/9/3 Neil Puttock <[EMAIL PROTECTED]>:
> I've knocked up a patch which implements these styles, together with a
> context property `doubleRepeatType' for setting the default style
> using \repeat volta. At a line break, both styles will revert to ":|"
> (before) and "|:" (after).
>
> If the p
2008/6/11 Wilbert Berendsen :
> Hi, in scm/backend-library there is (line 114-115):
>
>(if (access? pdf-name W_OK)
>(delete-file pdf-name))
>
> Why is the PDF deleted (instead of just truncated on write)? It breaks the PDF
> watching feature of KDE, because KDE looses the watch on the f
On 30/05/2008, John Mandereau wrote:
> The volta text can already be a markup actually, but as this markup is
> the second element of a list, which is itself contained in the
> repeatCommands list, it's not obvious to set it. BTW I fixed the
> misleading description of repeatCommands in the Inter
2008/5/25 Graham Percival wrote:
> While you're at it, could you update any other properties?
> cd scm/
> grep ",string?" *
> shows a bunch of properties that shouldn't be touched (like filename),
> but a few that probably should be markup intead (like ottavation,
> soloText, and... hmm, I'm not
2008/5/20 Joe Neeman :
> On Mon, May 19, 2008 at 9:09 PM, Risto Vääräniemi wrote:
>> I tried to create the special case for 16th notes only. 8th notes and
>> notes from 32th forward (until 64th note) would use a common placement
>> rule. This is because the 16th note flags
2008/5/19 Risto Vääräniemi:
> 2008/5/17 Joe Neeman :
>
>> Sorry for the long delay. I certainly agree that the new behaviour looks
>> better. I'm a bit concerned, though, that you only use special cases for 8th
>> and 16th notes. Why not something like (< dir (+ 1
Dear Joe,
2008/5/17 Joe Neeman :
> Sorry for the long delay. I certainly agree that the new behaviour looks
> better. I'm a bit concerned, though, that you only use special cases for 8th
> and 16th notes. Why not something like (< dir (+ 1 (* 0.15 (- log 2?
Thanks for the tip. However, I tes
2008/5/8 Neil Puttock :
> Are you testing each variation in isolation, or generating several
> systems in one go?
I called LP separately for every attached image.
-Risto
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mail
Hi Greg,
2008/5/8 Greg Swinford:
> I'm not sure whether this bug has already been reported, but accidental
> suggestions don't seem to mix well with tied notes. The following example
> produces a lot of "warning: an outside-staff object should have a direction,
> defaulting to up" messages an
2008/4/25 Risto Vääräniemi :
> In current LP version the \note and \note-by-number put augmentation
> dots very close to the flags. Sometimes they even collide. On the
> other hand if the stem length is increased the dots are not moved any
> closer to the stem, i.e., under the
Dear All,
In current LP version the \note and \note-by-number put augmentation
dots very close to the flags. Sometimes they even collide. On the
other hand if the stem length is increased the dots are not moved any
closer to the stem, i.e., under the flags.
I made a small experiment with the dots
2008/4/24 Han-Wen Nienhuys :
> little shorter
>
> (cons (+ (car attach-off) (if (> dir 0) stem-thickness 0))
> .. )
Much more elegant, thanks. :-) However, in this case the (> dir 0)
should be reversed:
(cons (+ (car attach-off) (if (< dir 0) stem-thickness 0)) stemy)
I've included a pa
2008/4/23 Han-Wen Nienhuys :
> The reference point is the center of the stem, and the flag attaches
> to the right side of the stem.
2008/4/24 Han-Wen Nienhuys :
> If it is a rounding error, the difference should be 1 pixel at most;
> on a 600 dpi printer, that's practically invisible. There may
2008/4/23 Han-Wen Nienhuys :
> looks like a rounding error. Do you see the same if you use extreme
> magnification?
If I use \fontsize #5 and print it I can see the discontinuity in the
stem very clearly and even the gap between the stem and the flag. :-)
As I tried to say in the previous ema
Dear Han-Wen,
2008/4/23 Han-Wen Nienhuys :
> The reference point is the center of the stem, and the flag attaches
> to the right side of the stem.
Thanks for the info.
I think that would be the case if the flags would not have a piece of
a stem themselves. However, the flags (1/16 ->) have a
Hi Valentin,
2008/4/23 Valentin Villenave :
> Risto, I have applied you patch. I think it was OK, though I don't
> really understand why stem-thickness was divided by 2 in the first
> place.
>
> If anyone finds a good reason, please revert commit
> e646872695248ec7e8eaa9d513a5695d128f
Hi,
I now got the git up and running and made the suggested change to the
freshly retrieved file.
I tried to follow the instructions on the LP home page:
git commit -a
git-format-patch HEAD^
I hope I did it right. Could someone have a look at the patch and
possibly commit it to the git if it's O
Dear all,
I noticed that the flags in flagged notes created with \note command
(or \note-by-number) are not positioned properly. The flag grob is
attached to the right side of the stem and because the flags already
have a piece of stem attached the upper part of the stem is made
thicker (please, s
On 07/03/2008, Rune Zedeler wrote:
> That would be a tie/slur :-)
>
> The top edge of the slur is a bezier, the bottom is a bezier where the
> control
> points are just a bit different. Therefore "bezier-sandwich".
What about a thing called doubleSlurs that creates slurs on top of and
under a
On 27/02/2008, Risto Vääräniemi wrote:
> Sometimes the LP still seems a bit pessimistic about fitting the
> systems on a desired number of pages. Setting between-system-padding
> to zero and adjusting the between-system-space instead usually works.
Speak of the Devil... :-)
Today
Hi, Joe
On 25/02/2008, Joe Neeman wrote:
> Sorry, I missed this email. Is this still an issue? If so, could you
> send the example that fails in an email? I tried 2 examples given by
> Paul in this thread and they both took up 2 pages with latest git. But
> maybe I didn't find the right exampl
On 07/02/2008, Han-Wen Nienhuys wrote:
> 2008/2/7, Mats Bengtsson :
> > Keeping the description at a cookbook level, as you propose, is one
> > alternative.
Probably the worst one. :-) But a good conversation starter, I hope.
> > Another alternative is to describe more clearly what the different
Dear All,
In 2006 Eyolf made a extensive study about the combined effect of the
set-global-staff-size and the Pango font definitions in
make-pango-font-tree [1]. It seems that this manual section has not
been yet updated. I was struggling with the same thing yesterday and
because I've got no inter
On Jan 14, 2008 12:35 PM, Mats Bengtsson wrote:
> If you want to discuss issues with the latest development releases, I'd
> recommend to use the lilypond-devel mailing list. I have forwarded
> this email there.
OK. Thanks for the tip. I thought the lilypond-devel list was just for
the actual devel
33 matches
Mail list logo
