I'm trying to typeset a piece marked with 12/8 upper and 4/4 lower staves. By
default, Lilypond forces both staves to 4/4. I tried the code below, which
allowed independent staff timing, but the bars are now decoupled.
Any ideas on how to mod this to get bars on both staves synched up to same
Hi, Harm --
On Thu, Sep 15, 2011 at 6:18 PM, harm6 wrote:
>
> I tested your definitions with a longer example using StaffGroup and
> commented the not used parts with %{ ... %}. (see code below)
> The log states: ERROR: Wrong type (expecting pair): ()
>
> And now the strangest thing: If I uncomme
David Nalesnik-2 wrote:
>
>
>
> In the meantime, I've generalized the 'extra-offset approach so that you
> can
> center a grob of your choice between two others. of which centering
> between
> barlines is just one option. I've attached it in case it's useful to
> someone, or anyone has any fe
Michael Ellis writes:
> Did ly:parse-string-expression go away in 2.14.1? I get an undefined
> variable error if I try something like:
It became available later than that. Something like three weeks ago or
so.
--
David Kastrup
___
lilypond-user ma
On Thu, Sep 15, 2011 at 4:46 PM, David Kastrup wrote:
> Michael Ellis writes:
>
> > Thanks, David. I figured it must be a parsing issue so it's nice to
> > have it clarified by someone knowledgable. I like the
> > ly:parser-parse-string idea. Does that function return a music object
> > if t
On 15 Sep 2011, at 22:08, Patrick Schmidt wrote:
> in previews long instrument names seem to be indented automatically (see
> preview.png) whereas on the first full page of the same score they get lost
> in the left margin (see page1.png). Is there an option for the automatic
> calculation of t
Michael Ellis writes:
> Thanks, David. I figured it must be a parsing issue so it's nice to
> have it clarified by someone knowledgable. I like the
> ly:parser-parse-string idea. Does that function return a music object
> if the parsing is successful?
No. ly:parse-string-expression does, so
Hello,
On Thu, Sep 15, 2011 at 9:23 PM, Patrick Schmidt wrote:
>
> Am 15.09.2011 um 22:10 schrieb Reinhold Kainhofer:
...snip..
>>> whereas on the first full page of the same score they get
>>> lost in the left margin (see page1.png). Is there an option for the
>>> automatic calculation of the le
Am 15.09.2011 um 22:10 schrieb Reinhold Kainhofer:
> Am Thursday, 15. September 2011, 22:08:04 schrieb Patrick Schmidt:
>> in previews long instrument names seem to be indented automatically (see
>> preview.png)
>
> Actually, preview simply crops the image where the instrument name starts,
> wh
Am Thursday, 15. September 2011, 22:08:04 schrieb Patrick Schmidt:
> in previews long instrument names seem to be indented automatically (see
> preview.png)
Actually, preview simply crops the image where the instrument name starts,
which in this case is more to the left than the page start. So yo
On Thu, Sep 15, 2011 at 3:16 PM, David Kastrup wrote:
> Michael Ellis writes:
>
> > I've written some music functions I use frequently to operate on
> > lyrics. For example, there's one call "lacc" that allows me to
> > intermix lyrics and notation by accumulating the lyrics into a list I
> > c
Michael Ellis writes:
> I've written some music functions I use frequently to operate on
> lyrics. For example, there's one call "lacc" that allows me to
> intermix lyrics and notation by accumulating the lyrics into a list I
> can instantiate later in the \score block. Very nice and convenien
I have some further feedback to give you.
Indeed, there's no need to reconfigure, as you've said.
However, I notice this:
Each time I open a document with lilypond code in it which has previously
previewed well, I get the code in document font. There's nothing wrong with
the code, since it work
I've written some music functions I use frequently to operate on lyrics.
For example, there's one call "lacc" that allows me to intermix lyrics and
notation by accumulating the lyrics into a list I can instantiate later in
the \score block. Very nice and convenient, but the usage is a little
mes
On Mon, Sep 12, 2011 at 8:39 AM, Reinhold Kainhofer
wrote:
>
> Attached you can find the PDF version of this cheat sheet:
>
> http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf
>
> Thanks, Reinhold!
I, also, was unable to print the cheat sheet (Win XP) until I use
On 15 September 2011 13:37, -Eluze wrote:
>
> it's there - see subdividing beams
>
> \set subdivideBeams = ##t
> \set baseMoment = #(ly:make-moment 1 8)
> \set beatStructure = #'(2 2 2 2)
>
> should work for your example!
The result is not exactly the same.
With subdivideBeams you have only one b
Sven Axelsson-3 wrote:
>
> On 14 September 2011 23:49, Peekay Ex wrote:
>> Hello,
>>
>> On Wed, Sep 14, 2011 at 7:46 PM, Sven Axelsson
>> wrote:
>>> Hi list.
>>>
>>> This is probably in the manual,
>>
>> http://lilypond.org/doc/v2.14/Documentation/notation/beams#setting-automatic-beam-behavior
On 14 September 2011 23:49, Peekay Ex wrote:
> Hello,
>
> On Wed, Sep 14, 2011 at 7:46 PM, Sven Axelsson
> wrote:
>> Hi list.
>>
>> This is probably in the manual,
>
> http://lilypond.org/doc/v2.14/Documentation/notation/beams#setting-automatic-beam-behavior
Yes, thanks, I have looked at that p
18 matches
Mail list logo
