Hi Bart,
> - c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just
> tested it)
Oh ... I think there have been some changes from the previous stable
version (2.14) then. I had the problem that I could *not* produce 11 or
9 chords - I always got the "add9" or "add11" version, unt
On 07/02/13 12:39, Michael Winter wrote:
This does not work when there are groups of notes beamed together that
are either all in the upper staff or in the lower staff. I assume it
would only work if you could guarantee that all notes grouped under a
beam have notes in both the upper and lower
On Sat, Jan 26, 2013 at 10:04 PM, Adam Spiers
wrote:
> On Tue, Jan 15, 2013 at 3:05 PM, Adam Spiers
> wrote:
>> On Tue, Jan 15, 2013 at 9:41 AM, David Kastrup wrote:
>>> You could use an engraver in ChordNames for wiping out the (event) cause
>>> of the last involved grob. Then the point-and-cl
2013/2/7 Martin Bergande :
> is there a standard solution to improve the following snippet from
> the docs?
Please try to be a little more specific!
What isn't sufficient?
What should be improved?
-Harm
___
lilypond-user mailing list
lilypond-user@gnu
This does not work when there are groups of notes beamed together that are
either all in the upper staff or in the lower staff. I assume it would only
work if you could guarantee that all notes grouped under a beam have notes in
both the upper and lower staves.
thanks,
Mike
On Feb 6, 2013, at
Hallo,
is there a standard solution to improve the following snippet from
the docs?
% cut & pasted from LilyPond — Notation Reference for version 2.14.2
#(define mydrums '((hiwoodblock default #t 3)
(lowoodblock default #t -2)))
woodstaff = {
% This defines a staff with on
2013/2/6 bart deruyter :
> It's sad thought that 'add' is not accepted by \storepredifineddiagram in a
> chord name.
How about:
\version "2.16.1"
% \version "2.17.10"
chExceptionMusic = {
1-\markup { \super "add9" }
}
chExceptions = #(append
(sequential-music-to-chord-exceptions chExceptio
Am 06.02.2013 22:47, schrieb Nick Payne:
> \new PianoStaff {
> \autochange {
> \relative c'' {
> \override Beam #'positions = #'(4.5 . 4.5)
> b16 b b,, b
> }
> }
> }
Do you mean, #'(-4.5 . -4.5) ?
___
lilypond-user mailing list
On 07/02/13 07:57, Michael Winter wrote:
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I
@Noeck: thanks for the help, was just working on that solution. Indeed,
that seems to be the way to go.
It's sad thought that 'add' is not accepted by \storepredifineddiagram in a
chord name.
It would have made things quite a bit easier for a chord that is, in my
opinion, used quite often.
I'll put
Hi,
Am Mittwoch, 6. Februar 2013, 22:24:32 schrieb bart deruyter:
> lol, indeed, 2.17.6... so the search continues...
OK, might be a change in the development version…
> I was hoping to get it by trying out c:2 for diagram, and splitting
> chordnames and and chord diagrams, and using " \set ad
Am 06.02.2013 22:24, schrieb bart deruyter:
> lol, indeed, 2.17.6... so the search continues...
>
> I was hoping to get it by trying out c:2 for diagram, and splitting
> chordnames and and chord diagrams, and using " \set
> additionalPitchPrefix = #"add"",
> but c:2 renders a Csus2 diagram.. b
On 07/02/13 07:57, Michael Winter wrote:
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I
lol, indeed, 2.17.6... so the search continues...
I was hoping to get it by trying out c:2 for diagram, and splitting
chordnames and and chord diagrams, and using " \set additionalPitchPrefix
= #"add"",
but c:2 renders a Csus2 diagram.. bummer getting quite completely stuck
here...
http://w
Hi there,
Am Mittwoch, 6. Februar 2013, 21:54:57 schrieb bart deruyter:
> - c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just
> tested it)
yes, thats perfectly correct, since 9 means 7th and 9th. :)
> - c:7.9 renders a C9, including seventh too
this is the same command as
Dear All,
It seems that with proportional notation even strict spanning does not allow
collisions of notehead and accidentals. Is it possible to allow any collision
such that the resolution and accuracy are exact no matter what? Or maybe I am
missing something
Many thanks in advance,
Mike
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I really want to do is force the beam to be f
hm, thanks for all the tips, but:
- c:9 produces a C9, including the seventh, (sorry Robert Schmaus, I just
tested it)
- c:7.9 renders a C9, including seventh too
- C:9^7 produces a C7 chord (just tried it Robert Kohnert).
- Using: \set additionalPitchPrefix = #"add" only changes the chord name,
Helge Kruse writes:
> 2013/2/4 David Kastrup
>
> I have created
> http://code.google.com/p/lilypond/issues/detail?id=3153>
> which will
> let all the music created within #{ ... #} point to \tr. That's
> pretty
> much the best you can hope to do with reasonable effort.
>
2013/2/4 David Kastrup
> I have created
> http://code.google.com/p/lilypond/issues/detail?id=3153> which will
> let all the music created within #{ ... #} point to \tr. That's pretty
> much the best you can hope to do with reasonable effort.
Ah that's great I will try this, when a Lilypond vers
2013/2/6 Stefan Thomas :
> Sorry, I can't find the mistake!
> Here's my code:
>
> \version "2.16.2"
> TheScore = #(define-scheme-function (parser location x y) (ly:music?
> ly:music?)
> #{
> \score {
> \new StaffGroup
> <<
> \new Staff \with { instrumentName = "first" } $x
> \new Staff \with { inst
Hi List,
is there some way to put bar lines, or more specifically repeat signs,
inside a text markup? Other than recreating them with the help of
\draw-line and \draw-circle?
--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de
___
Stefan Thomas writes:
> Dear David,
> I also use version 2.16.2
> But Your example doesn't work for me.
> I get the error message
> partiturtest.ly:17:34: Fehler: syntax error, unexpected '} \score {
> \TheScore \first \second}
>
Looks more like a copy&paste error than anything else. Non-br
Dear David,
I also use version 2.16.2
But Your example doesn't work for me.
I get the error message
partiturtest.ly:17:34: Fehler: syntax error, unexpected '} \score {
\TheScore \first \second}
> I don't have 2.16 installed, but with current versions
> \version "2.16.2"
> TheScore = #(define
\set additionalPitchPrefix = #"add"
within \chordmode renders the chord name with add9 instead of 9 only.
Example:
\version "2.16.0"
cd = \chordmode {
\set additionalPitchPrefix = #"add"
c1:9 c:9^7 c:5.9
}
<<
\new ChordNames \cd
\new FretBoards \cd
\new Staff \cd
>>
Am 06.02.2013 13:40, sc
Did you try c:5.9?
On Wed, Feb 6, 2013 at 1:40 PM, bart deruyter wrote:
> Hi all,
>
> I've searching for a way to add 'add9' chords to my own version of
> predefined fretboards, but whatever I do, it does not accept it and doesn't
> render it. I think the system doesn't allow 'add9' as chordname,
Hi,
Am 2013-02-06 13:40, schrieb bart deruyter:
I've searching for a way to add 'add9' chords to my own version of
predefined fretboards, but whatever I do, it does not accept it and
doesn't render it. I think the system doesn't allow 'add9' as
chordname, because when I change it to '9', like 'c
> Hi Bart,
>
> Lily's behaviour is quite correct. c:9 will produce a c major triad plus the
> ninth, ie ... that's an add9 chord. A proper ninth chord is bf d'>, ie a stack of thirds. Thus, you'll need c:7.9 for a 9 chord. You can
> check it out if you put your chords in an ordinary Staff to s
Hi all,
I've searching for a way to add 'add9' chords to my own version of
predefined fretboards, but whatever I do, it does not accept it and doesn't
render it. I think the system doesn't allow 'add9' as chordname, because
when I change it to '9', like 'c:9' it does render.
How can I solve this?
On 6 févr. 2013, at 09:31, Keith OHara wrote:
> Thomas Morley googlemail.com> writes:
>
>>
>> in some situations I used to override the Y-extent of the Clef.
>>
>> With 2.17.10 it doesn't work any more.
>>
>
> I noticed this, too, and found the change that caused it.
>
> https://lists.gnu
Dear LilyPond users,
I frequently have to layer many horizontal brackets over a small number of
notes (motivic analysis), and to do this I use extra voices with hidden
notes. Mostly this works fine, but sometimes the hidden notes cause some
odd behaviour with stem lengths in the main part. I've
On Feb 6, 2013 4:46 PM, "Wim van Dommelen" wrote:
>
> Hi James,
>
> Note that the Lilypond diagrams are different, not such "squarisch", see
the notation reference manual for details.
The notation reference is the first place I went. Those details were
helpful to get me started, but didn't answer
Stefan Thomas writes:
> Dear community,
> is it possible to have the score command in a music function?
A music function returns music. Use a scheme function to return
arbitrary Scheme.
> I need it for a piece with different movements.
> I've tried it with the following code which doesn't work
Dear community,
is it possible to have the score command in a music function?
I need it for a piece with different movements.
I've tried it with the following code which doesn't work:
\version "2.16.2"
TheScore = #(define-music-function (parser location x y) (ly:music?
ly:music?)
#{
\score {
Thomas Morley googlemail.com> writes:
>
> in some situations I used to override the Y-extent of the Clef.
>
> With 2.17.10 it doesn't work any more.
>
I noticed this, too, and found the change that caused it.
https://lists.gnu.org/archive/html/lilypond-user/2013-01/msg00559.html
Now that I
35 matches
Mail list logo
