2008/12/9 Hans Aberg <[EMAIL PROTECTED]>:
> On 9 Dec 2008, at 13:26, Graham Breed wrote:
>
> I attach an example file.
I don't see any transpositions.
> I think it is the commented out part (long time ago), which for some reason
> only works with E24. Therefore, the keys must be written explicitl
2008/12/9 Hans Aberg <[EMAIL PROTECTED]>:
> On 9 Dec 2008, at 13:42, Graham Breed wrote:
>
> And key signatures make the notes sound different.
Yes, and it's a classic cause of errors in performance, despite the
key being reinforced by the music.
>>>
>>> If you don't know how
> > Since you put 'scheme' in single quotes, I suspect you don't know
> > about Scheme programming. Scheme is a Lisp-like programming
> > language.
>
> ()()((()))()()(((
>
> I hope not, that kinda stuff leaves me with a headache, thank the
> gods for programming editors with () bal
On Tue, Dec 9, 2008, "Carl D. Sorensen" <[EMAIL PROTECTED]> said:
> On 12/9/08 4:37 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> You're confusing users with developers. Code and data structures are
> developer-only items.
yes, but the data structures my code needs are tablature-oriented, not
st
> > Still a buglet: The stemwidth of the down arrow in the
> > `natural.arrowboth' glyph is too thick if compared to the other
> > arrowed natural signs. Everything else looks fine.
>
> Finally one with an instantaneous fix. :-) Indeed I used to check
> for up- XOR down-arrow before I added the a
On Sun, Dec 7, 2008 at 5:34 PM, Maximilian Albert
<[EMAIL PROTECTED]> wrote:
> Hi Neil,
>
> thanks a lot for your further very helpful ideas. Attached is a patch
> for a new approach which implements your suggestion to define a new
> property. It's called 'shifted-towards-stem and can take any real
On 12/9/08 6:12 PM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
>> On Wed, Dec 10, 2008 at 01:47:29AM +0100, Francisco Vila wrote:
>>> 2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
Sweet Mao no. That's horrible. We should *NOT* do this.
On Sun, Dec 7, 2008 at 8:29 PM, John Mandereau <[EMAIL PROTECTED]> wrote:
> Hello,
>
> With current Git master C++ flags are incorrect on my system:
>
> cp -p /home/lilydev/git/lily/master/config.hh out/config.hh
> rm -f ./out/all-font-metrics.dep;
> DEPENDENCIES_OUTPUT="./out/all-font-metrics.dep
2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> On Wed, Dec 10, 2008 at 01:47:29AM +0100, Francisco Vila wrote:
>> 2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
>> > Sweet Mao no. That's horrible. We should *NOT* do this.
>>
>> This hack would be advertised in a @c omment and not used anywher
On Wed, Dec 10, 2008 at 01:47:29AM +0100, Francisco Vila wrote:
> 2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> > Sweet Mao no. That's horrible. We should *NOT* do this.
>
> This hack would be advertised in a @c omment and not used anywhere
> else, only here.
In one (1) single example?
...
2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> On Tue, Dec 09, 2008 at 10:50:38PM +0100, Jean-Charles Malahieude wrote:
>> I've found an "intermediate" way, which consists in doubling the snippet:
>>
>> 1) it becomes an @example
>> 2) the @lilypond loses its verbatim option
>
> Sweet Mao no. Th
Le mardi 09 décembre 2008 à 16:38 -0800, Graham Percival a écrit :
> Sweet Mao no. That's horrible. We should *NOT* do this.
>
> Can't somebody hack the python translation stuff to avoid this?
Already sold, but not before next night :-P
John
___
l
On Tue, Dec 09, 2008 at 10:50:38PM +0100, Jean-Charles Malahieude wrote:
> I've found an "intermediate" way, which consists in doubling the snippet:
>
> 1) it becomes an @example
> 2) the @lilypond loses its verbatim option
Sweet Mao no. That's horrible. We should *NOT* do this.
Can't somebody
On 12/9/08 4:38 PM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/12/9 Jean-Charles Malahieude <[EMAIL PROTECTED]>:
>> Le 09.12.2008 21:55, Francisco Vila disait :
>>>
>>> 2008/12/9 Francisco Vila:
>
> Yes, let's use @c KEEP LY, a good solution.
I've done this adding a
On 12/9/08 4:37 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
>> But LilyPond already has an extensive code and data structures base. To use
>> data structures or code that are not compatible with the LilyPond paradigm
>> is not wise.
>
> What is wise is to bow to the users expectations,
Le mercredi 10 décembre 2008 à 00:38 +0100, Francisco Vila a écrit :
> That is easy, but I still don't understand why a KEEPt snippet suffers
> an undesired translation.
"KEEP LY" was initially designed to be recognized by snippet-update.py
and no other program, but it is quite easy to make lilypo
Le mardi 09 décembre 2008 à 22:50 +0100, Jean-Charles Malahieude a
écrit :
> Le 09.12.2008 21:55, Francisco Vila disait :
> > I am doing something badly, as the verbatim output insists on being
> > translated despite of the KEEP LY.
This was to be expected, as lilypond-book translates whatever var
2008/12/9 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> [...] I managed to find a workaround and hope that the attached
>> patches finally fix all the issues.
>
> Still a buglet: The stemwidth of the down arrow in the
> `natural.arrowboth' glyph is too thick if compared to the other
> arrowed natural si
2008/12/9 Jean-Charles Malahieude <[EMAIL PROTECTED]>:
> Le 09.12.2008 21:55, Francisco Vila disait :
>>
>> 2008/12/9 Francisco Vila:
Yes, let's use @c KEEP LY, a good solution.
>>>
>>> I've done this adding a comment:
>>>
>>>
>>> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commi
> But LilyPond already has an extensive code and data structures base. To use
> data structures or code that are not compatible with the LilyPond paradigm
> is not wise.
What is wise is to bow to the users expectations, not twist their mind.
User of tablature is thinking of where to put the fing
Le 09.12.2008 21:55, Francisco Vila disait :
2008/12/9 Francisco Vila:
Yes, let's use @c KEEP LY, a good solution.
I've done this adding a comment:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=6d7edb962644c9b657f88d8bfe5b480494996f94
I am doing something badly, as the ve
2008/12/9 Francisco Vila <[EMAIL PROTECTED]>:
>> Yes, let's use @c KEEP LY, a good solution.
>
> I've done this adding a comment:
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=6d7edb962644c9b657f88d8bfe5b480494996f94
I am doing something badly, as the verbatim output insist
2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> So, here's the patch:
> http://codereview.appspot.com/8686
>
> Any idea if this is the correct way to solve the problem that you have to
> enter non-standard key signatures in reverse order?
I'm not sure, but it seems to be a harmless change.
Hi everybody,
I've tweaked the examples for `Clef' in the Glossary, and they seem to
be the only examples which use [quote]. Shouldn't this apply to all
the snippets?
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gn
This following discussion comes from the -user list. Reinhold appears to
have identified a case where current LilyPond behavior doesn't match Read's
conventions.
This leads to two questions:
1) Should LilyPond be adjusted to match Read's conventions (Reinhold has
identified how it should be chan
Le 09.12.2008 13:05, Trevor Daniels disait :
Francisco Vila wrote Tuesday, December 09, 2008 10:08 AM
2008/12/8 Jean-Charles Malahieude:
I think a warning would be useful, even for the English users,
mentioning
that this use of the autochange command *needs* the staves to be
called "up"
a
> > I've just added ly:font-config-add-directory and
> > ly:font-config-add-font. Please test.
>
> Yeepee! I'm compiling right away.
Just a warning: I got crashes with fontconfig 2.4.1; if you experience
the same you should try version 2.6.0.
Werner
_
Le 09.12.2008 13:49, Francisco Vila disait :
2008/12/9 till Rettig:
Hi,
thanks for report, I didn't check on it. What if we use for this particular
case @c KEEP LY and put the
up and down there. So other instantiations with the same name get translated
correctly, where it doesn*t harm.
Yes,
2008/12/9 Werner LEMBERG <[EMAIL PROTECTED]>:
> I've just added ly:font-config-add-directory and
> ly:font-config-add-font. Please test.
Yeepee! I'm compiling right away.
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http:/
> > However, it shouldn't be to hard to add functions
> > `ly:font-config-register-directory' and
> > `ly:font-config-register-file' (using FcConfigAppFontAddFile) to
> > lilypond.
>
> That would be awesome; [...]
I've just added ly:font-config-add-directory and
ly:font-config-add-font. Please
2008/12/9 Francisco Vila <[EMAIL PROTECTED]>:
> 2008/12/9 till Rettig <[EMAIL PROTECTED]>:
>> Hi,
>>
>> thanks for report, I didn't check on it. What if we use for this particular
>> case @c KEEP LY and put the
>> up and down there. So other instantiations with the same name get translated
>> cor
On 9 Dec 2008, at 13:42, Graham Breed wrote:
And key signatures make the notes sound different.
Yes, and it's a classic cause of errors in performance, despite the
key being reinforced by the music.
If you don't know how to read them.
Even if you know how to read them you are likely to make
2008/12/9 till Rettig <[EMAIL PROTECTED]>:
> Hi,
>
> thanks for report, I didn't check on it. What if we use for this particular
> case @c KEEP LY and put the
> up and down there. So other instantiations with the same name get translated
> correctly, where it doesn*t harm.
Yes, let's use @c KEEP
2008/12/9 Hans Aberg <[EMAIL PROTECTED]>:
> On 9 Dec 2008, at 11:57, Graham Breed wrote:
>>>
>>> The format should be such that it can be sued by sound generating
>>> programs.
>>
>> Do you have a patch?
>
> Then I would not need to mention it here as an idea, would I.
Fine, you've mentioned it.
On 9 Dec 2008, at 13:26, Graham Breed wrote:
No, because Lilypond also preserves the number of scale steps. At
least, it should.
I attach what I wrote for E36. There seems to be two systems, but
they keep
the ratio M/m = 2.
Where are the transpositions?
I attach an example file.
I thi
Hi,
thanks for report, I didn't check on it. What if we use for this particular
case @c KEEP LY and put the
up and down there. So other instantiations with the same name get translated
correctly, where it doesn*t harm.
till
Original-Nachricht
Datum: Tue, 9 Dec 2008 11:08:05 +0
2008/12/9 Hans Aberg <[EMAIL PROTECTED]>:
> On 9 Dec 2008, at 05:00, Graham Breed wrote:
>> No, because Lilypond also preserves the number of scale steps. At
>> least, it should.
>
> I attach what I wrote for E36. There seems to be two systems, but they keep
> the ratio M/m = 2.
Where are the tr
On 9 Dec 2008, at 12:50, Graham Breed wrote:
How can it possibly do so? Tell me! C to Db is M. C to the diesis
above C# is M. How does abstract m and M distinguish M from M?
Sorry, that should be m and m. C-Db is m and C-C# plus a diesis is m.
So the goal is to distinguish m from m.
I
On 9 Dec 2008, at 11:57, Graham Breed wrote:
The format should be such that it can be sued by sound generating
programs.
Do you have a patch?
Then I would not need to mention it here as an idea, would I.
When a musician's reading the notation, they're not looking above or
before the key si
Francisco Vila wrote Tuesday, December 09, 2008 10:08 AM
2008/12/8 Jean-Charles Malahieude <[EMAIL PROTECTED]>:
I think a warning would be useful, even for the English users, mentioning
that this use of the autochange command *needs* the staves to be called
"up"
and "down".
I agree.
Ther
I wrote:
> How can it possibly do so? Tell me! C to Db is M. C to the diesis
> above C# is M. How does abstract m and M distinguish M from M?
Sorry, that should be m and m. C-Db is m and C-C# plus a diesis is m.
So the goal is to distinguish m from m.
Graha
2008/12/9 Hans Aberg <[EMAIL PROTECTED]>:
> On 9 Dec 2008, at 03:13, Graham Breed wrote:
>> Lilypond code is already semantic markup for music. Your intermediate
>> file would end up looking a lot like the original.
>
> If that would be the case, it would be not point, right?
Right.
> The forma
On 9 Dec 2008, at 03:13, Graham Breed wrote:
So it might be better to write an intermediate sound file with the
diatonic
structure. Then it can be used to return the output without
having to
recompile the typeset output.
What's an "intermediate sound file"?
The idea is, instead of writing
2008/12/8 Jean-Charles Malahieude <[EMAIL PROTECTED]>:
> I think a warning would be useful, even for the English users, mentioning
> that this use of the autochange command *needs* the staves to be called "up"
> and "down".
I agree.
> Therefore I also removed the relevant lines in the pot and po
On 9 Dec 2008, at 05:00, Graham Breed wrote:
To get it to sound right, you multiply by 6. If accidentals and
transpositions don't work you may need to define a different grid
from
them. The worst is that you need one init file to define the
notation
-- so that the accidentals are distinct
2008/12/9 Werner LEMBERG <[EMAIL PROTECTED]>:
>
> I've completed the removal of the tex and texstr backends. Please
> update the Spanish and French translations!
Done, thanks.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-de
I've completed the removal of the tex and texstr backends. Please
update the Spanish and French translations!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 9 Dec 2008, at 02:29, Graham Breed wrote:
Also, I made keyboard map, which I have used in Scala playing in
mainly
E31
for the last couple of months:
A# B# Cx Dx Ex
A B C# D# E# Fx Gx Ax Bx
Bb C D E F# G# A# B#
Cb Db Eb F G A B C'# D'#
Dbb Ebb
On 9 Dec 2008, at 06:09, Graham Breed wrote:
Are you on board with the regular mapping paradigm? I may as well
promote it while I'm here.
http://x31eq.com/paradigm.html
I looked a bit at it, the section "The Core Paradigm". The model I
indicated
also chooses some generators, but in additio
49 matches
Mail list logo
