Right. In the general case, you need to recurse through 'elements and
'element similar to the following:
(define-public (change-pitches music converter)
;; Recurse through music, applying converter to pitches.
;; The converter function must take a single pitch as its
;; argument and re
Thanks
(car ) was the trick I would have been looking for a long time to come up with
that one.
(car (...))- returns the first member of a list.
I'm assuming that if that member is a function it returns the functions result,
which is why we get the solution?
Scott
-Original Message-
Sorry, my previous answer was rubbish. The following runs without
error and prints the pitch object.
myN = #(define-music-function (parser location myx ) (ly:music?)
(display-scheme-music
(ly:music-property
(car (ly:music-property myx 'elements))
'pitch))
myx)
\my
Hi Scott,
I think the problem is that the music in your example doesn't have an
'elements property. You can eliminate the error by changing the third
line in your code to
#(display-scheme-music (ly:music-property $myx 'pitch))
but what gets displayed is an empty list '(). Probably not what you
Evening all.
I've been working on some scheme functions currently working on displaying
theactual scheme coding while referring primarily to 6.3.2 Music Properties
The following is working
___
myN = #(define-music-function (parser location my
2011/1/29 James Bailey :
> Were I singing this, I'd understand what it meant, but it seems an
> unnecessary complication. (...)
W dniu 29 stycznia 2011 22:18 użytkownik Michael Ellis
napisał:
> I agree with James. (...)
2011/1/29 Keith OHara :
> [Stone] merges note heads in vocal music (p. 300)
On 29 January 2011 23:23, Eric Dedieu wrote:
>
> Hi lilypond helpers,
>
> Here is a small program that does not compile:
>
> ---
> \version "2.12.3"
>
> %% the function that will fail
> tempoMarkEqual =
> #(define-music-function (parser location before after)
> (st
On 1/29/11 1:31 PM, "Michael Ellis" wrote:
> As long as I'm on my soapbox :-), it occurs to me that it would be a
> service to any student guitarist looking at that chart if the staff
> notation showed the actual voicing of the chords, perhaps in
> parentheses, alongside the root position close
Hi lilypond helpers,
Here is a small program that does not compile:
---
\version "2.12.3"
%% the function that will fail
tempoMarkEqual =
#(define-music-function (parser location before after)
(string? string?)
#{
\mark \markup \tiny { \note $before #1 = \no
On 1/29/11 12:02 PM, "bart deruyter" wrote:
> Hi all,
>
> I've noticed something strange in the predefined chord diagrams for guitar.
> While writing on my book for teaching guitar, I noticed the chord C#
> diminished is weird to say at the least. The fret diagram is very wrong I'm
> afraid
On 1/29/11 12:14 PM, "James Bailey" wrote:
>
>
> On Jan 29, 2011, at 7:10 PM, Carl Sorensen wrote:
>
>>
>>
>>
>> On 1/29/11 7:45 AM, "James Samir Ismail" wrote:
>>
The first thing to do is to run the specified command from a terminal
window:
lilypond -dshow-availab
I agree with James. As I think I've commented in another thread, I've
seen many rehearsals interrupted when singers needed to ask a question
because of confusing notation. Think of it this way: as a composer
you want to give the performers every possible chance to get it right
the first time so t
On Jan 29, 2011, at 1:02 PM, bart deruyter wrote:
> I've noticed something strange in the predefined chord diagrams for guitar.
> While writing on my book for teaching guitar, I noticed the chord C#
> diminished is weird to say at the least. The fret diagram is very wrong I'm
> afraid :
> http
On Jan 29, 2011, at 9:40 PM, Janek Warchoł wrote:
> W dniu 29 stycznia 2011 12:00:50 UTC+1 użytkownik James Bailey
> napisał:
>>
>> On Jan 29, 2011, at 11:25 AM, Janek Warchoł wrote:
>>
>>> 2011/1/29 James Bailey :
On Jan 29, 2011, at 12:17 AM, Janek Warchoł wrote:
> Hi,
>
Hello
-Original Message-
From: Michael Ellis
Date: Sat, 29 Jan 2011 15:44:09 -0500
To: Martin Chicoine
Cc: lilypond-user
Subject: Re: Problem with barcheck
>As Jay pointed out, \times 2/3 {d8 g a } will occupy the time of two
>eighth-notes, not three. Hence the barcheck fails because
Janek Warchoł gmail.com> writes:
> recently i was told that this notation
>
> { \mergeDifferentlyHeadedOn << b'2 \\ { b'8 a' g' f' } >> }
>
> is not allowed in vocal music (i.e., the noteheads shouldn't be
> merged). Is that true?
>
> By the way, if there is a notehead shared by two voices
As Jay pointed out, \times 2/3 {d8 g a } will occupy the time of two
eighth-notes, not three. Hence the barcheck fails because there is an
eighth-note's worth of time remaining in your first measure (and 2
1/8's missing in the second.)
Cheers,
Mike
On Sat, Jan 29, 2011 at 3:01 PM, Martin Chic
W dniu 29 stycznia 2011 12:00:50 UTC+1 użytkownik James Bailey
napisał:
>
> On Jan 29, 2011, at 11:25 AM, Janek Warchoł wrote:
>
>> 2011/1/29 James Bailey :
>>>
>>> On Jan 29, 2011, at 12:17 AM, Janek Warchoł wrote:
>>>
Hi,
recently i was told that this notation
{ \mergeD
As long as I'm on my soapbox :-), it occurs to me that it would be a
service to any student guitarist looking at that chart if the staff
notation showed the actual voicing of the chords, perhaps in
parentheses, alongside the root position close voicings, e.g
g, c e bes c' e'
for the C7 chord.
On Sat, Jan 29, 2011 at 1:01 PM, Martin Chicoine
wrote:
> The following example gives me barcheck errors. Could someone explain why?
>
> %%%
> \version "2.12.3"
>
> \header {
> title = ""
> }
>
> staffViolon = \new Staff {
> \time 6/8
> \set
The score is correct, the diagrams are wrong, of all diminished chords I
think. C diminished and D diminished are wrong too, the diagrams at least.
http://www.bartart3d.be/
2011/1/29 Michael Ellis
> On Sat, Jan 29, 2011 at 2:57 PM, David Kastrup wrote:
> >
> > Uh, why wouldn't it be in C# dim
The following example gives me barcheck errors. Could someone explain why?
%%%
\version "2.12.3"
\header {
title = ""
}
staffViolon = \new Staff {
\time 6/8
\set Staff.instrumentName = "Violon"
\set Staff.midiInstrument = "violin"
On Sat, Jan 29, 2011 at 2:57 PM, David Kastrup wrote:
>
> Uh, why wouldn't it be in C# diminuished? It's a minor third below C#,
> or three minor thirds above it.
>
>> Or am I so very mistaken?
>>
>> What should I do to fix this in my code?
>
> What's to fix?
Just looked at the doc. Bart's righ
What's to fix? the predefined fretdiagram of C#° shows a different chord,
namely C#dim7, according to Michael Ellis...
I need C#°, erroneous predefined chord diagrams need to be fixed of course.
http://www.bartart3d.be/
2011/1/29 David Kastrup
> bart deruyter writes:
>
> > Hi all,
> >
> >
bart deruyter writes:
> Hi all,
>
> I've noticed something strange in the predefined chord diagrams for
> guitar. While writing on my book for teaching guitar, I noticed the
> chord C# diminished is weird to say at the least. The fret diagram is
> very wrong I'm afraid :
> http://lilypond.org/do
Hi Bart,
Sounds like it's giving you a C#dim7, typically spelled C# E G A# .
Cheers,
Mike
On Sat, Jan 29, 2011 at 2:02 PM, bart deruyter wrote:
> Hi all,
>
> I've noticed something strange in the predefined chord diagrams for guitar.
> While writing on my book for teaching guitar, I noticed the
On Jan 29, 2011, at 7:10 PM, Carl Sorensen wrote:
>
>
>
> On 1/29/11 7:45 AM, "James Samir Ismail" wrote:
>
>>> The first thing to do is to run the specified command from a terminal
>>> window:
>>>
>>> lilypond -dshow-available-fonts x
>>>
>>> You said before that "it didn't work". We don
Hi all,
I've noticed something strange in the predefined chord diagrams for guitar.
While writing on my book for teaching guitar, I noticed the chord C#
diminished is weird to say at the least. The fret diagram is very wrong I'm
afraid :
http://lilypond.org/doc/v2.13/Documentation/notation/predefi
On 1/29/11 7:45 AM, "James Samir Ismail" wrote:
>> The first thing to do is to run the specified command from a terminal
>> window:
>>
>> lilypond -dshow-available-fonts x
>>
>> You said before that "it didn't work". We don't know what that means, so we
>> can't help you.
>
> This is what
>> I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I
>> see the same problem in both versions.
>
> The 2.14 release is coming soon (hopefully), and the current 2.13
> releases have beta status (more or less). Please use 2.13.47 and try
> again whether you still experience problems
>> Which version of LilyPond are you using? The 2.13 series has many,
>> many improvements in font/text handling that may not have been
>> backported to 2.12.
>
> I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I
> see the same problem in both versions.
The 2.14 release is comin
> Which version of LilyPond are you using? The 2.13 series has many,
> many improvements in font/text handling that may not have been
> backported to 2.12.
I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I see the same
problem in both versions.
-Samir
__
> The first thing to do is to run the specified command from a terminal
> window:
>
> lilypond -dshow-available-fonts x
>
> You said before that "it didn't work". We don't know what that means, so we
> can't help you.
This is what it means:
Zamzam:bin samir$ ./lilypond -dshow-available-fonts x
2011/1/29 James Bailey :
>
> On Jan 29, 2011, at 12:17 AM, Janek Warchoł wrote:
>
>> Hi,
>>
>> recently i was told that this notation
>>
>> { \mergeDifferentlyHeadedOn << b'2 \\ { b'8 a' g' f' } >> }
>>
>> is not allowed in vocal music (i.e., the noteheads shouldn't be
>> merged). Is that true?
>
34 matches
Mail list logo
