Joram,
I stumbled upon a solution to this! It turns out that the second parameter
to extra-offset is vertical spacing, so for odd staff lines you can draw
the rest at the even line below it, and then bump it up by 0.5 with
extra-offset to get the desired effect.
This is what I came up with:
longb
Hi! I'm full of questions today :D
In these case, I have three times the same last ligature and when I repeat
it a fourth time, it doesn't print the same before like you can see at the
attached file.
Why?
\version "2.17.28"
one = \relative c''{e8-. g( e) c( b[) d( b) a8*1/2]( s8*1/2)}
two = \re
The question was not over convert-ly. I'm sory if it sounds like that. It
was not the intention.
Actualy I first try by re-tipeing under 2.17 and when that didn't work I
went back to the original file and convert it.
I don't think it has nothing to do with convert-ly and absolutly don't
think conv
Federico Bruni writes:
> 2013/10/20 Marcos Press
>
>> The result I need is the one that said correct.
>> I don't know whay, in 2.16 the
>>
>> \override Stem.transparent = ##t
>>
>> It just turn transparent the steams, without toching the Beams.
>> But now 2.17 It turn transparent the beams too.
Graet!
Thanks!
2013/10/20 Federico Bruni
> 2013/10/20 Marcos Press
>
>> The result I need is the one that said correct.
>> I don't know whay, in 2.16 the
>>
>> \override Stem.transparent = ##t
>>
>> It just turn transparent the steams, without toching the Beams.
>> But now 2.17 It turn transpa
Hi Pierre,
2013/10/16 Janek Warchoł :
>
> 2013/10/16 Pierre Perol-Schneider :
>> There is something I found disturbing for years : I think \super and \sub
>> are not properly settled. []
>
> Here's a patch that fixes it:
> http://code.google.com/p/lilypond/issues/detail?id=3619
> http://codere
2013/10/20 Marcos Press
> The result I need is the one that said correct.
> I don't know whay, in 2.16 the
>
> \override Stem.transparent = ##t
>
> It just turn transparent the steams, without toching the Beams.
> But now 2.17 It turn transparent the beams too.
seen recently on this list :-)
ht
Hello,
I have a fresh install of Lilypond 2.17.28 in my home directory (under
~/local/opt/lilypond-2.17.28) on CentOS release 6.4. I do not have sudo
powers. When I try to compile this file, named test.ly:
\version "2.17.28"
{
c' e' g' e'
}
using lilypond test.ly, I get:
warning: `(gs -q -dSA
(I bought a copy of the fon a while ago, and yes, some glyphs are
verbatim copies of the LilyPond ones)
On Sun, Oct 20, 2013 at 12:00 PM, Han-Wen Nienhuys wrote:
> I've heard of these guys before, but we never got round to initiating
> any sort of legal action. From what I remember, it looked lik
I've heard of these guys before, but we never got round to initiating
any sort of legal action. From what I remember, it looked like a
one-man company somewhere in Switzerland.
On Sat, Oct 19, 2013 at 10:52 PM, SoundsFromSound
wrote:
> Hello,
>
> I stumbled upon this website recently and just not
Hi Peter,
All three print fine here (2.17).
Maybe try this with 2.16 (which I don't have):
\version "2.16.2"
\language "english"
sopranoVoice = \relative c'' {
\key c \major
\numericTimeSignature
\time 3/2
{ \[ d2 ef \] \[ f | g \] \[ f1*15/16 s16 \]}
}
\score {
\new Staff { \sopranoVoice }
}
H
Kieren,
I was in the process of preparing one!
\version "2.16.2"
\language "english"
sopranoVoice = \relative c'' {
\key c \major
\numericTimeSignature
\time 3/2
{ \[ d2 ef \] \[ f | g \] \[ f1 \]}
}
\score {
\new Staff { \sopranoVoice }
}
The last ligature isn't printed.
Best regards,
Peter
m
Hi Peter,
> It doesn't work too well (as the 2.16 doc says), and there's definitely a
> problem where there's a 4-beat note (tied over the 3-beat bar) in the
> relevant voice. Can't work out how to do that one.
Might I suggest including a minimal snippet to the list, so we can see the
exact pr
Thanks both. I'd not thought of it as "ancient" notation - its only Purcell!
And I use it for Handel as well. "Early", maybe.
It doesn't work too well (as the 2.16 doc says), and there's definitely a
problem where there's a 4-beat note (tied over the 3-beat bar) in the relevant
voice. Can't wor
I'm using the same as Mark but with back slash.
c \[ a b e d \]
It's actually a ligature in the docs.
http://www.lilypond.org/doc/v2.17/Documentation/notation/ancient-notation_002d_002dcommon-features#ligatures
also take a look at
http://www.lilypond.org/doc/v2.17/Documentation/8e/lily-9b273927.
Peter,
Does this help?
\version "2.16.2"
global = {
\key c \major
\numericTimeSignature
\time 6/8
}
violin = \relative c'' {
\global
c8 [ c c ] c [ c c ] |
c [ c ] c [ c ] c [ c ] |
}
\score {
\new Staff \violin
\layout { }
}
Mark
I want to indicate a hemiola - the best method seems to be horizontal brackets
indicating each double-length beat.
I can't find anything in the documentation or snippets telling how to do it.
What am I missing please?
Regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
Works now :) Thank you. Is there any way to have these numbers displayed in log file on Windows?
Dnia 20-10-2013 o godz. 18:06 Phil Holmes napisał(a):
Try running lilypond simply from the command line, with no options to create the logfile (i.e. no redirection, no -dgui).
--Phil Holmes
-
Try running lilypond simply from the command line, with no options to create
the logfile (i.e. no redirection, no -dgui).
--
Phil Holmes
- Original Message -
From: Karol Majewski
To: David Nalesnik
Cc: Thomas Morley ; lilypond-user
Sent: Sunday, October 20, 2013 3:58 PM
No numbers in log file.
After generating PDF from this code:
==
\version "2.17.28"{ \override Tie.after-line-breaking = #(lambda (grob) (display (ly:grob-property grob 'control-points)) (newline)) c'1~ c'1}
==
I get the following log:
==
# -*-compilation-*-
Thomas Morley-2 wrote
> Why not simply:
>
> \markup \stencil
>#(make-connected-path-stencil
> '((0 2) (2 2))
> 0.1
> 1
> 1
> #f ;; <-- error if set to #t
> #t)
>
> Maybe including the error-log
Sounds good, and good call on using \markup.
-Paul
--
View this messag
2013/10/20 Paul Morris :
> David Kastrup wrote
>> Paul Morris <
>
>> paul@
>
>> > writes:
>>
>>> 2. Setting connect to #t gives this GUILE error (this seems like a bug):
>>> Wrong type argument in position 1 (expecting empty list): closepath
>>
>> Try making a report (including example) focusing ju
Paul Morris writes:
> David Kastrup wrote
>> Paul Morris <
>
>> paul@
>
>> > writes:
>>
>>> 2. Setting connect to #t gives this GUILE error (this seems like a bug):
>>> Wrong type argument in position 1 (expecting empty list): closepath
>>
>> Try making a report (including example) focusing jus
2013/10/20 Paul Morris :
[...]
>
> I see there's no snippet about using make-connected-path-stencil in the LSR.
> I'll put it on my list to add one when I get a chance.
[...]
There are some snippets using 'path'
http://lsr.dsi.unimi.it/LSR/Search?q=path
Would be nice to have one with 'make-connect
David Kastrup wrote
> Paul Morris <
> paul@
> > writes:
>
>> 2. Setting connect to #t gives this GUILE error (this seems like a bug):
>> Wrong type argument in position 1 (expecting empty list): closepath
>
> Try making a report (including example) focusing just on that problem.
> Our bug squad
David Kastrup wrote
> Thomas Morley <
> thomasmorley65@
> > writes:
>
>> Hi Paul,
>>
>> 2013/10/20 Paul Morris <
> paul@
> >:
>>> Hi all, I'm trying to use make-connected-path-stencil, but it's not
>>> working as expected, in two ways. Here's a tiny example:
>>>
>>>
>>>
>>> \ver
Am 19.10.2013 05:45, schrieb Joshua Nichols:
I'd like to tie the common notes below:
{
<<{a1~}\\{f4 e}>>
a1
}
But I'm not sure I'm doing it correctly.
Thoughts?
OK, the remainder of this thread obviously went into a different direction.
Apart from the documentation (which is authoritative
And David, I am so sorry to bother you so much with this subject, but you
didn't mention if there is any hope for a possible exhumation of the Issue
1333.
Thanks and take care,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Grace-notes-yet-again-tp152618p15267
Hi all,
Here are two possible little bugs (of type ugly) that do not look well IMO.
If you give me green light, I would happily add them to our Issue Tracker
myself.
1) Some ugly positioning when using \pitchedTrill:
\version "2.17.28"
\markup {Everything is fine here}
{
\pitchedTrill d'8.\st
On Sun, Oct 20, 2013 at 6:20 AM, Karol Majewski wrote:
> I must be doing something wrong. Where are the numbers? In PDF? In
> separate file?
>
> I use version 2.17.28 on Windows 7. Perhaps it is Windows issue?
>
>
The numbers are in the log.
___
lilypon
I must be doing something wrong. Where are the numbers? In PDF? In separate
file?
I use version 2.17.28 on Windows 7. Perhaps it is Windows issue?
Dnia 20-10-2013 o godz. 12:45 Thomas Morley napisał(a):
> 2013/10/20 Karol Majewski :
> > Hmm... the code:
> >
> >
> >
> > {
> >
> > \override Tie.a
2013/10/20 Karol Majewski :
> Hmm... the code:
>
>
>
> {
>
> \override Tie.after-line-breaking =
>
> #(lambda (grob)
>
> (display (ly:grob-property grob 'control-points))
>
> (newline))
>
> c'1~ c'1
>
> }
>
>
>
> doesn't work for me. I see no control points (nor the numbers).
Well, it works for me
Paul Morris writes:
> 2. Setting connect to #t gives this GUILE error (this seems like a bug):
> Wrong type argument in position 1 (expecting empty list): closepath
Try making a report (including example) focusing just on that problem.
Our bug squad is not a team of programmers that can secondgu
Thomas Morley writes:
> Hi Paul,
>
> 2013/10/20 Paul Morris :
>> Hi all, I'm trying to use make-connected-path-stencil, but it's not working
>> as expected, in two ways. Here's a tiny example:
>>
>>
>>
>> \version "2.17.28"
>>
>> myStencil =
>> #(let* ((A 0) (B 1))
>>(make-con
Hi Paul,
2013/10/20 Paul Morris :
> Hi all, I'm trying to use make-connected-path-stencil, but it's not working
> as expected, in two ways. Here's a tiny example:
>
>
>
> \version "2.17.28"
>
> myStencil =
> #(let* ((A 0) (B 1))
>(make-connected-path-stencil
> '((A B) (B B)
Am 20.10.2013 11:00, schrieb David Kastrup:
But SIL wouldn't allow to sell them as a standalone project either,
isn't it?
No idea, I'm just familiar with the GPL. At any rate, they say
"Lilypond look is here", but that does not in itself imply that they
copied or converted the font programs.
Hmm... the code:
{
\override Tie.after-line-breaking =
#(lambda (grob)
(display (ly:grob-property grob 'control-points))
(newline))
c'1~ c'1
}
doesn't work for me. I see no control points (nor the numbers).
Meanwhile, I've found this:
===
#(define (make-cross-stencil coords) (ly:
Urs Liska writes:
> Am 20.10.2013 10:14, schrieb David Kastrup:
>> Janek Warchoł writes:
>>
>>> 2013/10/20 SoundsFromSound :
Hello,
I stumbled upon this website recently and just noticed they have this font
offered for sale, dubbed "Lilypond look is here!"
Do any of
Am 20.10.2013 10:14, schrieb David Kastrup:
Janek Warchoł writes:
2013/10/20 SoundsFromSound :
Hello,
I stumbled upon this website recently and just noticed they have this font
offered for sale, dubbed "Lilypond look is here!"
Do any of you know anything about this vendor and/or fonts? I'm
Janek Warchoł writes:
> 2013/10/20 SoundsFromSound :
>> Hello,
>>
>> I stumbled upon this website recently and just noticed they have this font
>> offered for sale, dubbed "Lilypond look is here!"
>>
>> Do any of you know anything about this vendor and/or fonts? I'm
>> curious...anyone try these
Hi,
2013/10/20 SoundsFromSound :
> Hello,
>
> I stumbled upon this website recently and just noticed they have this font
> offered for sale, dubbed "Lilypond look is here!"
>
> Do any of you know anything about this vendor and/or fonts? I'm
> curious...anyone try these fonts before?
>
> Paris...
41 matches
Mail list logo
