Re: Alternative notation for guitar 7th chords

2013-12-22 Thread Alex Loomis 
I'm not sure what it does, like I said I just upgraded it to be compatible
with 2.17.95. Given your error I assume you're using 2.16.x, before a
certain change in syntax became usable, so changing it to

\override ChordName #'extra-spacing-width = #'(-1.25 . 1.25)

should work. If it displays well with it commented out though I don't see
any reason to leave it in.


On Sun, Dec 22, 2013 at 9:48 AM, Marten Visser  wrote:

> Marten Visser  planet.nl> writes:
>
> Follow-up:
> if I leave out
>
> \override ChordName.extra-spacing-width = #'(-1.25 . 1.25)
>
> it works, and indeed the seventh is displayed the way I'd like.
>
> What is the \override good for? From the name I gather it adds some extra
> spacing somewhere, but where is it intended to go?
>
> Thanks,
> Marten
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Alternative notation for guitar 7th chords

2013-12-22 Thread Marten Visser 
Marten Visser  planet.nl> writes:

Follow-up:
if I leave out

\override ChordName.extra-spacing-width = #'(-1.25 . 1.25)

it works, and indeed the seventh is displayed the way I'd like.

What is the \override good for? From the name I gather it adds some extra 
spacing somewhere, but where is it intended to go?

Thanks,
Marten


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Alternative notation for guitar 7th chords

2013-12-22 Thread Marten Visser 
Alex Loomis  gmail.com> writes:

> 
> 
> Here is the file. Convert-ly upgraded the syntax but something happened 
in an internal fine that made a large part of it that changed the way 
accidentals look not work, so I commented that part out. I'm not familiar 
with pop notation, so if there's anything that needs to change let me know.
> 
> 
> On Sun, Dec 22, 2013 at 12:03 AM, Alex Loomis  
gmail.com> wrote:
> I didn't see it in the LSR and the version of pop-chord.ly I found was 
written for 2.11.52, so it might not work perfectly. Give me a moment and 
I'll attach one that works with 2.17.95
> 
> 
> 
> On Sat, Dec 21, 2013 at 10:06 PM, Tim McNamara  
bitstream.net> wrote:The easiest thing is using the pop-chords.ly 
alternatives to the default chordname style, using \include.  I think it is 
available in the snippet repository.  Or you can write your own chordname 
exceptions, the procedure for which should be in the Notation reference.
> 
> > On Dec 21, 2013, at 8:46 PM, Marten Visser  planet.nl> 
wrote:
> >
> > Hi Lilyponders,
> >
> > Typesetting my masterpiece is drawing to completion, and one fine point 
of
> > typesetting remains.
> >
> > \chordmode { c1:7 } typesets the 7 as a superscript. I'd like to know 
how
> > the 7 can be typeset on the baseline, like the m of a minor chord. I
> > couldn't find any tweak that does that for me.
> >
> > Regards,
> > Marten
> >
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user  gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> ___
> lilypond-user mailing listlilypond-user  
gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Attachment (pop-chords.ly): text/x-lilypond, 4888 bytes
> 
> ___
> lilypond-user mailing list
> lilypond-user  gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 


Hi Alex,

Thanks for the reply. I tested it, but there is an error still. Maybe you 
can help, as I know too little about how Lilypond has been set up 
internally?

test file:


\version "2.16.2"

\include "pop-chords.ly"

myMusic = {
  f1 g1
}

myChords = {
\chordmode{ f1:m }
\chordmode{ g1:7 }
}

\score {
<<
\new ChordNames { \myChords }
\new Staff {
\key c \minor
\new Voice {\relative c' \myMusic }
}
>>
}

--

The error I recieve:

D:/Marten/Muziek/Bladmuziek/Lilypond/Flaws and bugs/pop-chords.ly:191:23: 
error: syntax error, unexpected '.', expecting SCM_FUNCTION or 
SCM_IDENTIFIER or SCM_TOKEN
\override ChordName
   .extra-spacing-width = #'(-1.25 . 1.25)
D:/Marten/Muziek/Bladmuziek/Lilypond/Flaws and bugs/pop-chords.ly:193:0: 
error: syntax error, unexpected '}'

}



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Alternative notation for guitar 7th chords

2013-12-21 Thread Alex Loomis 
Here is the file. Convert-ly upgraded the syntax but something happened in
an internal fine that made a large part of it that changed the way
accidentals look not work, so I commented that part out. I'm not familiar
with pop notation, so if there's anything that needs to change let me know.


On Sun, Dec 22, 2013 at 12:03 AM, Alex Loomis wrote:

> I didn't see it in the LSR and the version of pop-chord.ly I found was
> written for 2.11.52, so it might not work perfectly. Give me a moment and
> I'll attach one that works with 2.17.95
>
>
> On Sat, Dec 21, 2013 at 10:06 PM, Tim McNamara wrote:
>
>> The easiest thing is using the pop-chords.ly alternatives to the default
>> chordname style, using \include.  I think it is available in the snippet
>> repository.  Or you can write your own chordname exceptions, the procedure
>> for which should be in the Notation reference.
>>
>>
>>
>> > On Dec 21, 2013, at 8:46 PM, Marten Visser  wrote:
>> >
>> > Hi Lilyponders,
>> >
>> > Typesetting my masterpiece is drawing to completion, and one fine point
>> of
>> > typesetting remains.
>> >
>> > \chordmode { c1:7 } typesets the 7 as a superscript. I'd like to know
>> how
>> > the 7 can be typeset on the baseline, like the m of a minor chord. I
>> > couldn't find any tweak that does that for me.
>> >
>> > Regards,
>> > Marten
>> >
>> >
>> >
>> >
>> > ___
>> > lilypond-user mailing list
>> > lilypond-user@gnu.org
>> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>
% Pop chords as used in English/American popular music
% by James L. Hammons

% Written against \version "2.17.29"

chordFlat = \markup { \hspace #0.2 \tiny \raise #1.0 \flat }

chordSharp = \markup { \hspace #0.1 \teeny \raise #1.0 \sharp }

popChordsMusic =
{
% Triads

-\markup { "5" }
-\markup { "2" }
%   -\markup { "sus2" }

-\markup { "sus" }
%   -\markup { "sus4" }
%   -\markup { \small \raise #1.0 "o" }
-\markup { \raise #0.8 "o" }

%   -\markup { "dim" }
%   -\markup { "aug" } 
% or +

% Sixths

-\markup { "6" }

-\markup { "m6" }

% Sevenths (including altered)

-\markup { "7" }
-\markup { "m7" }
-\markup { "maj7" }

-\markup { "7sus4" }
-\markup { "7sus2" }
-\markup { "7" \chordFlat "5" }
-\markup { "7" \chordSharp "5" }

%   -\markup { "aug7" }
% or +7
-\markup { "m(maj7)" }
%   -\markup { \small \raise #1.0 { "o" } "7" }

-\markup { \raise #0.8 { "o" } "7" }
%   -\markup { "dim7" }
  

% -\markup { \small \raise #1.0 { $(ly:wide- char->utf-8 #x00f8) } "7" } % -\markup { \raise #0.8 { $(ly:wide-char- >utf-8 #x00f8) } "7" }

-\markup { "m7" \chordFlat "5" }
-\markup { "maj7" \chordFlat "5" }
-\markup { "maj7" \chordSharp "5" }


% Ninths (including altered--incomplete)

-\markup { "9" }
-\markup { "m9" }
-\markup { "maj9" }

-\markup { "add9" }
-\markup { "6/9" }
-\markup { "m6/9" }
-\markup { "m(maj9)" }

-\markup { "7" \chordFlat "9" }
-\markup { "7" \chordSharp "9" }
%dim7add9, dim7b9, dim7#9, 9#5, 9b5, maj9#5, maj9b5, 9sus4, 9sus2


% Elevenths (incomplete)

-\markup { "11" }
-\markup { "m11" }
-\markup { "maj11" }

-\markup { "add11" }
-\markup { "m add11" }
-\markup { "m7add11" }

% Thirteenths (incomplete)


-\markup { "13" }
-\markup { "m13" }
-\markup { "maj13" }
-\markup { "add13" }


% Misc add chords

-\markup { "7" \chordFlat "9" \chordFlat "13" }
-\markup { "7" \chordSharp "5" \chordFlat "9" }

-\markup { "maj9" \chordSharp "11" }
-\markup { "9" \chordSharp "11" }
}

% Add to existing exceptions

popChordsAdd = #(append
 (sequential-music-to-chord-exceptions popChordsMusic #t)
 ignatzekExceptions)

% Bah, can't we set this globally? YES! See below...
% \set chordNameExceptions = #popChords


% Bah, this doesn't work either...
% #(set chordNameExceptions popChords)


% Let's try fixing the accidentals with some Scheme...
%It breaks the file, let's not.

%{
#(define (chord-name->pop-markup pitch)

  (let* ((alt (ly:pitch-alteration pitch)))


  (make-line-markup
(list
  

(make-simple-markup (vector-ref #("C" "D" "E" "F" "G" "A" "B") (ly:pitch-notename pitch)))

  ;; If it's natural, do nothing

  (if (= alt 0)

(make-line-markup (list empty-markup))

(if (= alt FLAT)

  ;; Otherwise, handle adding the flat symbol


  (make-line-markup

Re: Alternative notation for guitar 7th chords

2013-12-21 Thread Alex Loomis 
I didn't see it in the LSR and the version of pop-chord.ly I found was
written for 2.11.52, so it might not work perfectly. Give me a moment and
I'll attach one that works with 2.17.95


On Sat, Dec 21, 2013 at 10:06 PM, Tim McNamara  wrote:

> The easiest thing is using the pop-chords.ly alternatives to the default
> chordname style, using \include.  I think it is available in the snippet
> repository.  Or you can write your own chordname exceptions, the procedure
> for which should be in the Notation reference.
>
>
>
> > On Dec 21, 2013, at 8:46 PM, Marten Visser  wrote:
> >
> > Hi Lilyponders,
> >
> > Typesetting my masterpiece is drawing to completion, and one fine point
> of
> > typesetting remains.
> >
> > \chordmode { c1:7 } typesets the 7 as a superscript. I'd like to know how
> > the 7 can be typeset on the baseline, like the m of a minor chord. I
> > couldn't find any tweak that does that for me.
> >
> > Regards,
> > Marten
> >
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Alternative notation for guitar 7th chords

2013-12-21 Thread Tim McNamara 
The easiest thing is using the pop-chords.ly alternatives to the default 
chordname style, using \include.  I think it is available in the snippet 
repository.  Or you can write your own chordname exceptions, the procedure for 
which should be in the Notation reference.



> On Dec 21, 2013, at 8:46 PM, Marten Visser  wrote:
> 
> Hi Lilyponders,
> 
> Typesetting my masterpiece is drawing to completion, and one fine point of 
> typesetting remains.
> 
> \chordmode { c1:7 } typesets the 7 as a superscript. I'd like to know how 
> the 7 can be typeset on the baseline, like the m of a minor chord. I 
> couldn't find any tweak that does that for me.
> 
> Regards,
> Marten
> 
> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Alternative notation for guitar 7th chords

2013-12-21 Thread Marten Visser 
Hi Lilyponders,

Typesetting my masterpiece is drawing to completion, and one fine point of 
typesetting remains.

\chordmode { c1:7 } typesets the 7 as a superscript. I'd like to know how 
the 7 can be typeset on the baseline, like the m of a minor chord. I 
couldn't find any tweak that does that for me.

Regards,
Marten




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user