Re: manual Makam example

[BB]

I still think that the snippet ifrom the world music chapter is better 
than the one actually in the arabic chapter. I will recommend it in the 
bug-lilypond mailing list, if I find some time. Actually I am fighting 
with some problems.

I would post a better one, if I could get an example code! There is some 
inconsistency. If i use
\include arabic.ly
the arabic maqams are defined and will be found, but the english note 
names are not known.

\include "arabic.ly"

\relative do' {

\key re \bayati

%\set Staff.extraNatural = ##f

dod dob dosd \dwn dob dobsb dodsd do do

}

That is another important fact to say that given example in the arabic 
chapter is double-crap! This snippet indeed uses english note names not 
known with \arabic.ly!

As I prefer the english note names. If I use
\include maqam.ly
the maqams are undefined, but the english note names are known.

\include "makam.ly"

\relative c' {

\key d \bayati

c4 cc db fk

gbm4 gfc gfb efk

fk4 db cc c

}


If I try the definition of Bayati from arabic.ly, the resukt is vey 
strange, I do not understand why?

\include "makam.ly" \relative c' { \set Staff.keyAlterations = #`( (0 . 
,NATURAL) (1 . ,SEMI-FLAT) (2 . ,FLAT) (3 . ,NATURAL) (4 . ,NATURAL) (5 
. ,FLAT) (6 . ,FLAT) ) c4 cc db fk gbm4 gfc gfb efk fk4 db cc c }

I think that ha s to do with the missing key alteration order? May be an 
extension/redesign of maqam.ly is necessary? Help would be appreciated!

On 21.02.2016 13:27, Simon Albrecht wrote:
> On 21.02.2016 12:54, BB wrote:
> > At the end of subchapter "Arabic key signatures" in chapter "2.10.2 
> > Arabic music" on page
> > http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music
> > there is in subchapter "Selected Snippets" a snippet example. It is 
> > very peculiar that in this example is not even a single quarter tone. 
> > Peculiar and totally displaced and useless in this arabic notation 
> > section dealing with the special case of quarter tone notation! 
>
> You’re welcome to come up with a better example and post it on the 
> bug-lilypond mailing list, with a concise description what exactly it 
> is for and why it is better.
>
> Best, Simon