Jim Long writes:
> On Fri, Jan 18, 2013 at 11:19:33AM +0100, David Kastrup wrote:
>>
>> I was just pointing out that LilyPond's default is not all-lunatic.
>
> I'd like to eat some crow, as it seems I'm the lunatic in this
> thread for which I must apologize.
I was not stating that LilyPond's d
On 19/01/13 18:04, Mark Stephen Mrotek wrote:
Hello:
From the manual:
\relative c' {
\time 2/4
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\times 2/3 { c8 c c c c c }
}
I understand everything except how the "1" and "4" relate to the notation.
Have a look at the section of
Hello:
>From the manual:
\relative c' {
\time 2/4
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\times 2/3 { c8 c c c c c }
}
I understand everything except how the "1" and "4" relate to the notation.
Would someone explain?
Thank you.
Mark
<>__
On 18/01/2013 4:56 PM, Stefan Thomas wrote:
Dear community,
when I compile the following file with latex and lilypondbook, it looks
quite strange.
There's is a break after every bar of the lilypond example.
I think it has to do with the input-command.
Here is the code of the latex-file:
\docume
On Fri, Jan 18, 2013 at 11:19:33AM +0100, David Kastrup wrote:
>
> I was just pointing out that LilyPond's default is not all-lunatic.
I'd like to eat some crow, as it seems I'm the lunatic in this
thread for which I must apologize. :( I mis-characterized this
issue based on a mis-recollection o
Am 2013-01-18 um 15:14 schrieb Urs Liska:
> Am 18.01.2013 14:29, schrieb Henning Hraban Ramm:
>>> But do I see correctly that I can't compile my original file with latex
>>> anymore (because of the undefined environment/command)?
>>> I find this inacceptable, because I want to be able to compile
Dear community,
when I compile the following file with latex and lilypondbook, it looks
quite strange.
There's is a break after every bar of the lilypond example.
I think it has to do with the input-command.
Here is the code of the latex-file:
> \documentclass[a4paper,12pt]{article}
> \usepackage[
2013/1/18 Shane Brandes :
> That once useful function no longer works properly or as most people might
> anticipate, after 2.12 or thereabouts. Something about multiple headers
> causes Lilypond to crap out. From what i understand a header is a top level
> widget and there can be only one unless yo
Shane:
Thank you for your response and information. At least I know that some
"fudging" is needed. I shall work with the "\global" and scope out the
threads.
Mark
From: Shane Brandes [mailto:sh...@grayskies.net]
Sent: Friday, January 18, 2013 10:15 AM
To: Mark Stephen Mrotek
Cc: lilypo
That once useful function no longer works properly or as most people might
anticipate, after 2.12 or thereabouts. Something about multiple headers
causes Lilypond to crap out. From what i understand a header is a top level
widget and there can be only one unless you declare some odd ball
incantatio
Hello:
The attached file is for a Prelude and Fugue. The header for the Prelude
does not appear and is replaced by the header for the Fugue. I have compared
mine to the examples in the manual and cannot find my error.
Would someone please point it out to me?
Thank you for your kind atte
Can anybody help me?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/The-alignment-of-staves-systems-tp139536p139739.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.o
On 01/18/2013 03:06 PM, Yannick CHARLES wrote:
Regarding the typesetting, the quarter tone is written on the score, but not the
glissando. Is there a way to make it visible ?
Perhaps by tweaking minimum-length settings for the glissando? Most likely
(from my experience) it "appears" but is ju
Hello to everybody !
I tried to typeset a clarinet glissando (more like a kind of "bend" in
fact), with an amplitude of a quarter tone, in the following way:
es,4(\glissando eeh\glissando |
es8) r r4 |
Regarding the typesetting, the quarter tone is written on the score, but
not the glissando. Is
Kieren MacMillan writes:
> Hi all,
>
>> Here is my solution.
>
> In general, I prefer to avoid using a markup, and override the stencil of the
> grob instead, i.e.,
>
> prallSharp = {
> \once \override Script #'stencil = #ly:text-interface::print
> \once \override Script #'text = \markup {
>
Hi Jay,
This doesn't Do The Right Thing™ when the key signatures are abstracted, e.g.,
\version "2.17.10"
#(define (adjust-note mus key currkey)
(cond ((or
(eq? (ly:music-property mus 'name) 'NoteEvent)
(eq? (ly:music-property mus 'name) 'KeyChangeEvent))
(ly:music-tran
Hi all,
> Here is my solution.
In general, I prefer to avoid using a markup, and override the stencil of the
grob instead, i.e.,
prallSharp = {
\once \override Script #'stencil = #ly:text-interface::print
\once \override Script #'text = \markup {
\override #'(baseline-skip . 1.2) \cente
>>> The naïve approach
>>>
>>> prallSharp = -\tweak Script.script-priority #-100
>>>^\prall
>>>-\tweak X-offset #0.4
>>>^\markup { \fontsize #-5 \sharp }
>>>
>>> doesn't work, and I wonder whether there exists a solution without
Am 18.01.2013 14:29, schrieb Henning Hraban Ramm:
Am 2013-01-16 um 11:20 schrieb Urs Liska:
Hi list,
I'm just starting my first try with lilypond-book.
I see that I have to enter the code in my latex document, process this document
with lilypond-book and then compile the resulting file to get
David Kastrup writes:
> I was just pointing out that LilyPond's default is not all-lunatic.
My apologies if I accidentally said something that suggested that.
-- Johan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman
Am 2013-01-16 um 11:20 schrieb Urs Liska:
> Hi list,
>
> I'm just starting my first try with lilypond-book.
> I see that I have to enter the code in my latex document, process this
> document with lilypond-book and then compile the resulting file to get my
> final pdf document.
>
> But do I se
>> The naïve approach
>>
>> prallSharp = -\tweak Script.script-priority #-100
>>^\prall
>>-\tweak X-offset #0.4
>>^\markup { \fontsize #-5 \sharp }
>>
>> doesn't work, and I wonder whether there exists a solution without
>> a lo
Werner LEMBERG writes:
> Folks,
>
>
> I want this
>
> c4-\tweak Script.script-priority #-100
> ^\prall
> -\tweak X-offset #0.4
> ^\markup { \fontsize #-5 \sharp }
>
> converted to a macro so that I can say
>
> c4\prallSharp
>
> (actually, I think that this com
Folks,
I want this
c4-\tweak Script.script-priority #-100
^\prall
-\tweak X-offset #0.4
^\markup { \fontsize #-5 \sharp }
converted to a macro so that I can say
c4\prallSharp
(actually, I think that this command and its siblings \prallFlat,
\pralldownSha
>>Am 16.01.2013 08:51, schrieb Maarten de Keijzer:
>>
>> Hi,
>>
>> Is it possible to create some general setup for the total number of
>> bars within the score, including time changes?
>>
>> In the example I have a score with two voices on the right (piano)
>> staff with 6/8 and 3/8 bars.
>>
>>
Werner LEMBERG writes:
>> Enclose a passage that is to be played more than once. If there is
>> no left repeat sign, the right repeat sign sends the performer back
>> to the start of the piece or the nearest double bar.
>
> Interesting. This is the first time ever that I've heard about this
> r
> Enclose a passage that is to be played more than once. If there is
> no left repeat sign, the right repeat sign sends the performer back
> to the start of the piece or the nearest double bar.
Interesting. This is the first time ever that I've heard about this
rule w.r.t. the double bar. Actu
Johan Vromans writes:
> According to the common interpretation of the :| symbol, repetition is
> to start at a |: and if there's none, the music must be repeated from the
> beginning -- clearly not what is intended.
http://en.wikipedia.org/wiki/List_of_musical_symbols>
Music-repeat.pngR
Jim Long writes:
> I just wanted to increment the tally on Johan's feature request.
I'm utterly surprised by all these reactions... Mostly because noone
seems to agree with me that, in the case of
... \bar "||" \break \repeat ...
not having a "||" at the end of the line and a "|:" at the sta
Am 18.01.2013 09:39, schrieb Johan Vromans:
Marc Hohl writes:
Except that it does not work with \repeat, AFAIK.
Yes, it does.
c1 \bar "||:" \break
\repeat volta 2 { d2 d }
Sorry if I was unclear -- what I meant to say is that IMHO LilyPond
should be able to handle this correctly:
c1 \bar
Marc Hohl writes:
>> Except that it does not work with \repeat, AFAIK.
> Yes, it does.
>
> c1 \bar "||:" \break
> \repeat volta 2 { d2 d }
Sorry if I was unclear -- what I meant to say is that IMHO LilyPond
should be able to handle this correctly:
c1 \bar "||" \break
\repeat volta 2 { d2 d }
Am 18.01.2013 06:03, schrieb Jim Long:
[...]
There is no confusion at all. The source file tells Lilypond
exactly where the double bars should be. Lilypond knows that at
several places, the source code says:
\bar "||" \break
As I understood Johan's suggestion, Lilypond should interpret
that t
32 matches
Mail list logo
