Am 24.01.2013 05:56, schrieb Marcos Press:
> Yes, because 1/3 is not the moment you want (I think).
> Try
> set tupletSpannerDuration = #(ly:make-moment 6 8)
>
>
> Actualy the moment I want would be the one that I can get with separated
> \times. Like:
>
> \times 6/4 { e16[ fis
Interesting!, a way for simplifying things!
But the confusion with tuplets, starts when I have to use then in
non-regular \time or non-regular tuplets like my example that its both
things at the same time.
In a \time 4/4 or 2/4 its easy to grasp the use of a standard \times 2/3
But in a \time 6/8
Hi Kieren,
> Yes, because 1/3 is not the moment you want (I think).
>
> Try
> set tupletSpannerDuration = #(ly:make-moment 6 8)
>
Actualy the moment I want would be the one that I can get with separated
\times. Like:
\times 6/4 { e16[ fis g gis] }
\times 6/4 { a16[ ais b b] }
But, wich wou
Sorry, I forgot that crucial step. You can name a context when you
create it:
\new StaffGroup = "violinII" \with { ... } { ... }
That's the value you can use for alignAboveContext and
alignBeforeContext. Thus:
\new Staff = "violinIdivisiB"
\with { alignAboveContext = "violinII" } { ... }
On Mon, Jan 21, 2013 at 03:49:20AM -0800, Eluze wrote:
> Frank Steinmetzger wrote
> > I attached a minimal example to clarify. Its repeat bars at marks A and B
> > are created by the music's repeat, the other two bars by the lyrics'
> > repeat.
>
> not sure to understand correctly why you want re
You can specify remove-first for an individual staff rather than the
entire score, either by putting \override VerticalAxisGroup.remove-first
= ##t inside the Staff's \with clause or by putting \override
Staff.VerticalAxisGroup.remove-first = ##t at the beginning of the music
for the staff.
>From
As for David's suggestion to set the context property remove-first to ##t:
Wouldn't that remove all empty staves from the first page, i.e., also the
empty staves of "regular" instrumental parts? What I want is to have the
"regular" parts on the first page, even if they are empty, and remove only
th
On Wed, Jan 23, 2013 at 9:42 AM, Phil Holmes wrote:
> These are called ossia staves. Please have a look in the documentation
for those and
> let us know if you need other help.
Thanks for the advice so far. I decided to look into the ossia staves,
which seemed to me to be similar to, but easier t
Hello,
2013/1/21 Julien Rioux
> Indeed, there is a bug here: the automatic line width detection fails
> because of the included file. This detection is done by copying the latex
> preamble to a temporary file in a temp dir, running latex on this file, and
> parsing some output about the line widt
In early versions of lilypond it was possible to create glissandi which
conected directly to the stem of the transparent headed note.
In 2.16 version, an annoying problem is: this space remains empty, as if
the note head was there. Does someone know how to do that? I tried to
specify negative valu
Alexandre writes:
> In early versions of lilypond it was possible to create glissandi
> which conected
> directly to the stem of the transparent headed note.
>
> In 2.16 version, an annoying problem is: this space remains empty, as if the
> note head was there. Does someone know how to do that? I
Am 23.01.2013 20:48, schrieb Alexandre:
> In early versions of lilypond it was possible to create glissandi which
> conected
> directly to the stem of the transparent headed note.
>
> In 2.16 version, an annoying problem is: this space remains empty, as if the
> note head was there. Does someone
In early versions of lilypond it was possible to create glissandi which
conected directly to the stem of the transparent headed note.
In 2.16 version, an annoying problem is: this space remains empty, as if
the note head was there. Does someone know how to do that? I tried to
specify negative valu
In early versions of lilypond it was possible to create glissandi which conected
directly to the stem of the transparent headed note.
In 2.16 version, an annoying problem is: this space remains empty, as if the
note head was there. Does someone know how to do that? I tried to specify
negative valu
> Date: Tue, 22 Jan 2013 23:03:58 +0100
> From: noeck.marb...@gmx.de
> To: lilypond-user@gnu.org
> Subject: Visual Index to Documentation
>
> Hi,
>
> since the beginning of the year, I have worked on an alternative access
> to the LilyPond documentation, which I call a visual index.
> It is int
Noeck writes:
> Am 23.01.2013 15:51, schrieb David Kastrup:
>> But with some luck, starting with
>> 2.17.11, things might become more "natural" for you after
>> http://code.google.com/p/lilypond/issues/detail?id=3095>.
>
> Am I right, that the fraction argument for \tuplet is inverse to the
> \
Am 23.01.2013 15:51, schrieb David Kastrup:
> But with some luck, starting with
> 2.17.11, things might become more "natural" for you after
> http://code.google.com/p/lilypond/issues/detail?id=3095>.
Am I right, that the fraction argument for \tuplet is inverse to the
\times argument? So, usual
Kieren MacMillan writes:
>> http://code.google.com/p/lilypond/issues/detail?id=3095>
>
> OOO… very nice!
Well, it is more or less one result from a heated discussion going
awfully bad eventually last fall. Minus shorthands \duplet (?),
\triplet, \quadruplet ... (that does not mean that they
> http://code.google.com/p/lilypond/issues/detail?id=3095>
OOO… very nice!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Marcos Press writes:
> Hi list!
> I always have some problems with the tuplets, but generaly I end up
> findig a solusion by my own. Today is not the day :)
Kieren already made your day. But with some luck, starting with
2.17.11, things might become more "natural" for you after
http://code.goog
p.s. That being said, in your example, there's no need to use \set
tupletSpannerDuration. That's only useful for multiple tuplets, e.g.:
\version "2.15.40"
\score {
\relative d'' {
\clef G
\time 6/8
\key a \major
a2.
\times 6/4 { e16[ fis g gis] a[ ais b b] }
\times 6/4 { e,16[ fis
Hi Marcos,
> Uncommenting the \set line produce extra spanner lines over the nexts bars.
> And adding again the tuplet, adds nested spanners over the nexts bars.
> I'm pretty sure the tuplet numbers are wrong and the SpannerDuration moments
> are wrong too :)
Yes, because 1/3 is not the moment
Hi David,
> I don't think it should be necessary to explain the idea of a minimal
> complete example to you.
My apologies — the minimal complete example included below triggers the
following error:
warning: cannot change `Staff' to `upper': not changing to same context
type: Staff
Thanks,
Hi list!
I always have some problems with the tuplets, but generaly I end up findig
a solusion by my own. Today is not the day :)
The problem is more with the spanner but I'm not sure the tuplet is
configured correcly.
Here, all seams ok.
Compile with no error and perfect graphic with one spanner
Am 23.01.2013 09:50, schrieb Werner LEMBERG:
>> Here it is:
>> http://joramberger.de/files/lilypond_visualindex.pdf
>
> This is an excellent idea and very well done! Hopefully, something
> like this can eventually be integrated into Lilypond.
That's why I asked about an html version.
> … Some
On Tue, Jan 22, 2013 at 6:45 PM, Peter Wannemacher sotw <
pe...@scriptureoftheweek.com> wrote:
> This is superb! Thank you very much.
>
>
>
> Peter Wannemacher
> ===
> From: Noeck
> Subject:Visual Index to Documentation
> Date: Tue, 22 Jan 2013 23:03:58
Shane Brandes writes:
> failed (0): gs: failed to fork (Cannot allocate memory) Did I break
> something or is it wanting a more robust machine? I was trying to run
> a file that runs to about a hundred pages using 2.17.9 over Ubuntu
> 12.10. Anyway that particular error does not seem obvious to m
Thomas writes:
> Hi,
> I'm typesetting an orchestral score and need to insert an "auxiliary"
> staff for some strings in some places. The situation is this: in
> general, the 2nd violins occupy only one staff, even if they play
> divisi; however, in one instance (a passage of a few bars) the part
Kieren MacMillan writes:
> I have defined several custom piano staff contexts (mostly to affect
> #'direction tweaks, but also for other things):
I don't think it should be necessary to explain the idea of a minimal
complete example to you.
--
David Kastrup
__
Hi Thomas,
Here's an example of what I would do. Changing the short instrument
names to reflect what instruments are in use at a certain moment
clutters the music a bit; perhaps a music function of some sort might be
appropriate there.
Mark Witmer
===File ~/source/in_development/lilypond-misc/e
Dear Eric,
I don't get what you're trying to do in your example. It looks like you're
trying to invoke the \rN outside of a markup context. It's best used in a
lyrics context or as markup attached to a note (there don't seem to be any
in your example).
And Roman numeral notation in LaTeX is eas
> These are called ossia staves. Please have a look in the
> documentation for those and let us know if you need other help.
Maybe adding an index entry `auxiliary staves'?
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lis
> since the beginning of the year, I have worked on an alternative
> access to the LilyPond documentation, which I call a visual index.
> It is intended especially for tweaking purposes, if a user wants to
> change a property of an object.
>
> Here it is:
> http://joramberger.de/files/lilypond_vi
These are called ossia staves. Please have a look in the documentation for
those and let us know if you need other help.
--
Phil Holmes
- Original Message -
From: Thomas
To: lilypond-user@gnu.org
Sent: Tuesday, January 22, 2013 3:13 PM
Subject: How to insert an "auxiliary"
34 matches
Mail list logo
