Re: Nashville notation as chord symbols

[Amelie Zapf]

Hello Stan, all,

I second the motion to introduce the (incredibly practical
key-independent) Nashville Number System to Lilypond.

> ♭7⁷ or 7♭⁷.

♭7⁷ is the "official" notation. Plus the NNS has a number of other
symbols for denoting breaks (long and short), anticipations, key and
meter changes, multiple chords per bar and the like.

Kind regards,

Amy

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

Re: a proper whiteout function

[Janek Warchoł]

Hi Paul,

thanks a lot for doing this!  The result is quite impressive, i didn't
expect this approach to produce so nice whiteouts :)
I have just a couple cosmetic suggestions:
- I think "offset" should be renamed to "padding".  Throughout LilyPond,
offsets are used to measure distances and position, while padding is used
for ensuring there's enough whitespace around an object.
- I think the default value for angle-increments should be 8, or at most
12.  Yes, with smaller value the whiteouts will be less regular, but this
will be visible only with very high magnification, while the improvement in
performance/pdf size may be noticeable.

best,
Janek


2015-05-19 20:41 GMT-07:00 Paul Morris :

> Hi Carl, Wilbert, David N, Kieren, Abraham,
>
> Thanks for all the feedback and suggestions.  I’m attaching a new revision.
>
> - Original spacing is maintained.  Thanks David and Carl for the tips on
> how to do this.
>
> - Optional parameters, with fallback defaults, for offset, color,
> angle-increments, radial-increments.  I went with Carl’s suggestions, but
> made them optional.  The stencil argument now comes first.
>
> - Prevents zero or negative angle- and radial- increments that would cause
> an infinite loop.
>
> - First pass at a doc string based on Carl’s descriptions.
>
>
> Let me know what you think and then I’ll go ahead and submit a patch for
> review.  BTW, what’s a good default for offset?
>
> Cheers,
> -Paul
>
>
> ___
> 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: a proper whiteout function

[Paul Morris]

Hi Carl, Wilbert, David N, Kieren, Abraham,

Thanks for all the feedback and suggestions.  I’m attaching a new revision.

- Original spacing is maintained.  Thanks David and Carl for the tips on how to 
do this.

- Optional parameters, with fallback defaults, for offset, color, 
angle-increments, radial-increments.  I went with Carl’s suggestions, but made 
them optional.  The stencil argument now comes first.

- Prevents zero or negative angle- and radial- increments that would cause an 
infinite loop.

- First pass at a doc string based on Carl’s descriptions.


Let me know what you think and then I’ll go ahead and submit a patch for 
review.  BTW, what’s a good default for offset?

Cheers,
-Paul



stencil-whiteout-outline2.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to add barre indications to automatic fret diagrams?

[Thomas Morley]

2015-05-19 21:59 GMT+02:00 pls :
>
> On 19.05.2015, at 21:47, Stephen MacNeil  wrote:
>
> you can check here see if that's what you want.
>
> http://lsr.di.unimi.it/LSR/Search?q=fret-diagram
>
>
> Thanks, but unfortunately these snippets are all about customizing
> predefined fret diagrams and not about adding barre indications to
> automatically generated fret diagrams.
>
> patrick
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

Hi Patrick,

maybe this will get you started:

\version "2.19.15"

\new FretBoards {

  \override FretBoard.before-line-breaking =
  #(lambda (grob)
 ;(display (ly:grob-property grob 'dot-placement-list))
 (ly:grob-set-property! grob 'dot-placement-list
(cons '(barre 6 1 1) (ly:grob-property grob 'dot-placement-list

  
}

HTH,
  Harm

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

Re: About pitch

[Reedmace Star]

* 2015-05-19 23:23 +0200:
> With the backquotes the display of the new language-pitch-names ends like
> this:
> (lak . #) (lakk . #) (sibb . #) (sib
> . #) (si . #) (sik . #) (sikk . # bisis >) (i unquote (ly:make-pitch 8 0 0)) (o unquote (ly:make-pitch 8 0
> 1
> you can see that lily does not apply the make-pitch to my new notes

Seems to work here:

---
$ LANG=C lilypond scheme-sandbox
GNU LilyPond 2.18.0
Processing
`/usr/local/lilypond/usr/share/lilypond/current/ly/scheme-sandbox.ly'
Parsing...
/usr/local/lilypond/usr/share/lilypond/current/ly/scheme-sandbox.ly:3:2:
error: GUILE signaled an error for the expression beginning here
#
 (load-user-init)
readline is not provided in this Guile installation

guile> (define fisarmonica
 `((i . ,(ly:make-pitch 8 0 DOUBLE-SHARP))
   (o . ,(ly:make-pitch 8 0 DOUBLE-FLAT
guile> fisarmonica
((i . #) (o . #))



Are you sure you replaced the apostrophe (') with a backquote (`)? Not
doing so gives me an expression that resembles yours.

HTH,
RS

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

Re: About pitch

[PharoahS]

With the backquotes the display of the new language-pitch-names ends like
this:
(lak . #) (lakk . #) (sibb . #) (sib
. #) (si . #) (sik . #) (sikk . #) (i unquote (ly:make-pitch 8 0 0)) (o unquote (ly:make-pitch 8 0
1
you can see that lily does not apply the make-pitch to my new notes



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/About-pitch-tp176774p176789.html
Sent from the User mailing list archive at Nabble.com.

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

Re: how to add barre indications to automatic fret diagrams?

[pls]

On 19.05.2015, at 21:47, Stephen MacNeil  wrote:

> you can check here see if that's what you want.
> 
> http://lsr.di.unimi.it/LSR/Search?q=fret-diagram

Thanks, but unfortunately these snippets are all about customizing predefined 
fret diagrams and not about adding barre indications to automatically generated 
fret diagrams.

patrick

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

Nashville notation as chord symbols

[Stan Mulder]

I would like to use Nashville Notation for chord symbols using Arabic
numbers instead of Roman numbers. Is there any way to do this?

So in the key of C:

C=1
D=2
E=3
F=4
G=5
A=6
B=7

So a blues progression might be:

1 4 5⁷

Instead of 
C F G⁷

So a B-flat7 chord in the key of C might be represented at either

♭7⁷ or 7♭⁷.

I think there is a great deal of value with what might be called "relative
notation" in this way. It is a hard system to learn, but once learned can
make key transpositions much easier.

For my projects I would like to write regular chord symbols, but above or
below those symbols I would have the Nashville number thing. 

After working with this system, I think all the fake books in the world
should be done this way.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: About pitch

[Reedmace Star]

* 2015-05-19 18:18 +0200:
> The aim would be to add  two notes to all the languages.
> I write
>  #(define fisarmonica
>   '(
> (i .  (ly:make-pitch 8 0 DOUBLE-SHARP))   ; input note, ie a closing
> note
> (o . (ly:make-pitch 8 0 DOUBLE-FLAT)); output note, ie a drawing
> note
>   ))
> 
> then
> #(define language-pitch-names
>(map
>  (lambda (x) (append (list (car x)) (append (cdr x)  fisarmonica)))
>  language-pitch-names)) 
> 
>  gives something ending by
> (si . #) (sik . #) (sikk . #) (i
> ly:make-pitch 8 0 DOUBLE-SHARP) (o ly:make-pitch 8 0 DOUBLE-FLAT)))
> so it does not work
> Have you an idea?

You need the backquoting mechanism described by Ralf Mattes.
ly:make-pitch is a *function* that needs to be evaluated to produce a
pitch object, but your whole definition of fisarmonica is quoted with ',
so this does not happen.

Change it to

  #(define fisarmonica
 `((i . ,(ly:make-pitch 8 0 DOUBLE-SHARP))
   (o . ,(ly:make-pitch 8 0 DOUBLE-FLAT

and it should work.


Best regards,
RS

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

how to add barre indications to automatic fret diagrams?

[pls]

Hi all,

LilyPond’s automatic fret diagrams really are a very helpful feature! More 
often than not it helps to not having to predefine and store a diagram in a 
lookup table.  But it has one little drawback: it doesn’t automatically include 
a barre indication when several strings are to be covered by one finger.  The 
default diagram actually looks a bit as if six fingers were needed to play this 
chord (see example).  

\version "2.19.15"
{
  \new FretBoards {

  }
}

I have had a look at the \override options of the FretBoard and many details 
are customizable but of course it’s not possible to override a barre indication 
that isn’t there.  Now, is there a known way to (manually) add barre 
indications to automatic fret diagrams or do I have to use predefined fret 
diagrams for barre chords in general?

tia
patrick



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

Re: About pitch

[PharoahS]

Thank you

The aim would be to add  two notes to all the languages.
I write
 #(define fisarmonica
  '(
(i .  (ly:make-pitch 8 0 DOUBLE-SHARP))   ; input note, ie a closing
note
(o . (ly:make-pitch 8 0 DOUBLE-FLAT)); output note, ie a drawing
note
  ))

then
#(define language-pitch-names
   (map
 (lambda (x) (append (list (car x)) (append (cdr x)  fisarmonica)))
 language-pitch-names)) 

 gives something ending by
(si . #) (sik . #) (sikk . #) (i
ly:make-pitch 8 0 DOUBLE-SHARP) (o ly:make-pitch 8 0 DOUBLE-FLAT)))
so it does not work
Have you an idea?




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/About-pitch-tp176774p176781.html
Sent from the User mailing list archive at Nabble.com.

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

Re: About pitch

[Richard Shann]

On Tue, 2015-05-19 at 15:15 +0200, Ralf Mattes wrote:
>  Am Dienstag, 19. Mai 2015 10:12 CEST, PharoahS  
> schrieb: 
>  
> > Hi all
> > 
> > When i write #(display language-pitch-names) i get someting beginning wuth:
> > ((nederlands (ceses . #) (ceh . #)
> > 
> > i see in 
> > http://denemo.org/~rshann/gub.bak/target/mingw/root/usr/share/lilypond/current/scm/define-note-names.scm
> > 
> >   
> > that it should begin with
> > (nederlands . (
> >(ceses . ,(ly:make-pitch -1 0 DOUBLE-FLAT))
> >(ceh . ,(ly:make-pitch -1 0 SEMI-FLAT))
> 
> This can't be true.
Well, besides quoting LilyPond source from a rather random place,
PharaohS failed to give the preceding context of the list which is in
the lilypond scm/define-note-names.scm as follows:

(define-public language-pitch-names
  `(

which has the backquote Ralf predicted.

>  You must be missing a backquote "`" somewhere since kommas "," 
> are only valid syntax within a "backquoted"  expression (schemers call that 
> quasi-quoted
> expression).
> 
> > Why is there such a difference? 
> 
> There is none, since the komma instructs the scheme reader to replace the 
> following
> expression with it's _value_ and the value of (ly:make-pitch ) will be a 
> lilypond pitch
> which _prints_ like #.
> 
> > and how can i display from lily the
> > denemo-like version?
> 
> You can't.  The scheme 'display' function does display pitches the way it 
> does since
> there is no print representation for pitches that can be read back by scheme.
> Anything starting with "#<" is consiered "unreadable" by scheme. This is why 
> denemo
> needs to substitute pitches with scheme code to generate them.

I don't think this has anything to do with Denemo - what is being quoted
is a bit of LilyPond source code which is in the GUB directory used to
build the Denemo+LilyPond package for windows. (And it is only there
because the build has been run on that GUB directory which resulted in
the LilyPond sources being downloaded... this build gub.bak is anyway
ancient, the LilyPond sources may have moved on).

Richard



> NB: I think there _should_ be a readable scheme representation for pitches 
>  but
> that's another thread ;-)
> 
>  HTH Ralf Mattes
> 
> > Thanks
> >  
> > 
> > 
> > 
> > --
> > View this message in context: 
> > http://lilypond.1069038.n5.nabble.com/About-pitch-tp176774.html
> > Sent from the User mailing list archive at Nabble.com.
> > 
> > ___
> > 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: About pitch

[Ralf Mattes]

 
Am Dienstag, 19. Mai 2015 10:12 CEST, PharoahS  
schrieb: 
 
> Hi all
> 
> When i write #(display language-pitch-names) i get someting beginning wuth:
> ((nederlands (ceses . #) (ceh . #)
> 
> i see in 
> http://denemo.org/~rshann/gub.bak/target/mingw/root/usr/share/lilypond/current/scm/define-note-names.scm
> 
>   
> that it should begin with
> (nederlands . (
>  (ceses . ,(ly:make-pitch -1 0 DOUBLE-FLAT))
>  (ceh . ,(ly:make-pitch -1 0 SEMI-FLAT))

This can't be true. You must be missing a backquote "`" somewhere since kommas 
"," 
are only valid syntax within a "backquoted"  expression (schemers call that 
quasi-quoted
expression).

> Why is there such a difference? 

There is none, since the komma instructs the scheme reader to replace the 
following
expression with it's _value_ and the value of (ly:make-pitch ) will be a 
lilypond pitch
which _prints_ like #.

> and how can i display from lily the
> denemo-like version?

You can't.  The scheme 'display' function does display pitches the way it does 
since
there is no print representation for pitches that can be read back by scheme.
Anything starting with "#<" is consiered "unreadable" by scheme. This is why 
denemo
needs to substitute pitches with scheme code to generate them.
NB: I think there _should_ be a readable scheme representation for pitches  
but
that's another thread ;-)

 HTH Ralf Mattes

> Thanks
>  
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/About-pitch-tp176774.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> 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

About pitch

[PharoahS]

Hi all

When i write #(display language-pitch-names) i get someting beginning wuth:
((nederlands (ceses . #) (ceh . #)

i see in 
http://denemo.org/~rshann/gub.bak/target/mingw/root/usr/share/lilypond/current/scm/define-note-names.scm

  
that it should begin with
(nederlands . (
   (ceses . ,(ly:make-pitch -1 0 DOUBLE-FLAT))
   (ceh . ,(ly:make-pitch -1 0 SEMI-FLAT))

Why is there such a difference? and how can i display from lily the
denemo-like version?
Thanks
 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/About-pitch-tp176774.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Ottava bracket offset

[Andrew Bernard]

Abraham,

Brilliant. Thank you.

It’s against all the engraving rules, but it’s exactly what I need.

Andrew

On 19 May 2015 at 16:29:54, tisimst (tisimst.lilyp...@gmail.com) wrote:

Not sure if this helps you, too, but it seems your example might could benefit 
from the following:

\override Staff.OttavaBracket.whiteout = ##t
\override Staff.OttavaBracket.layer = #10___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user