Re: sesqui-flat spelling

[David Kastrup]

Edward Neeman  writes:

> Hello all,
>
> I've gotten quite used to the fact that "as" is A flat and "es" is E
> flat in Lilypond. Is there a reason why sesqui-flats need to be
> spelled aeseh and eeseh (instead of the abbreviated "aseh" or "eseh")?

I don't think so.  Note names in LilyPond, at least for half notes, are
made up as far as I remember.  For generation by computer, aes and ees
(and their derivatives) make some sense to support.  As the only option,
that seems a bit weird.

-- 
David Kastrup

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

Re: sesqui-flat spelling

[Caagr98]

You can add your own language which contains those two aliases:

#(define a (assoc-ref language-pitch-names 'nederlands))
#(set! a (acons 'aseh (ly:make-pitch -1 5 THREE-Q-FLAT) a))
#(set! a (acons 'eseh (ly:make-pitch -1 2 THREE-Q-FLAT) a))
#(set! language-pitch-names (acons 'nederlands2 a language-pitch-names))
#(note-names-language "nederlands2")

{a aeseh aseh e eeseh eseh}

On 11/22/17 04:37, Edward Neeman wrote:
> Hello all,
> 
> I've gotten quite used to the fact that "as" is A flat and "es" is E
> flat in Lilypond. Is there a reason why sesqui-flats need to be
> spelled aeseh and eeseh (instead of the abbreviated "aseh" or "eseh")?
> 
> This is not a huge issue, though it is annoying that Frescobaldi isn't
> aware that these abbreviations aren't accepted. So if I convert
> relative to absolute pitch in Frescobaldi, it changes my aeseh's to
> aseh's, and I need to search and replace to be able to compile again.
> 
> Thanks!
> Edward
> 
> --
> 
> Dr. Edward Neeman
> Adjunct Instructor, South Georgia State College
> Collaborative Pianist, Valdosta State University, Georgia
> Artist Faculty, ELMS Conservatory, Jakarta
> edward.nee...@gmail.com
> www.neemanpianoduo.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

Re: sesqui-flat spelling

[Simon Albrecht]

On 22.11.2017 04:37, Edward Neeman wrote:

This is not a huge issue, though it is annoying that Frescobaldi isn't
aware that these abbreviations aren't accepted. So if I convert
relative to absolute pitch in Frescobaldi, it changes my aeseh's to
aseh's, and I need to search and replace to be able to compile again.


That should be added to the Frescobaldi issue tracker.

Best, Simon

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

Re: Moving from lilypond 2.18 to 2.19

[Matt Wallis]

On 22/11/2017 16:33, David Kastrup wrote:

You know: the minimal example would have been

\midi { \time 4/4 }
Nice minimalism! And I thought I'd done well to reduce the original 200+ 
lines in 4 files down to 13 in 1!

and that would have saved adding a lot of other explanation:
... which shows my lack of understanding about what was the true nature 
of the problem...

The error is triggered by the use of \global in the midi block when
global contains "\time 4/4". Incidentally, if the midi block contains
a \key signature, but no \time, then it works fine in 2.19.80.

I can understand that \time is irrelevant to midi (as is \key?), but
I've used this lazily in the past because it works.

It is intended to work.  I am surprised that this has been overlooked
for so long.


I'd be interested to know if you think the correct fix is to restore
the original 2.18.2 behaviour, or to output an error message that
identifies the line that causes the problem.

I'm currently writing two fixes.  One makes a better warning, the other
does not trigger it.

Great. Thank you.

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

Frescobaldi Qt5

[Brett M. Gilio]

I know the Frescobaldi developers have been planning for a transition to
PyQt5/Qt5. I am quite versed with python and qt5, does anybody know how
far along they have gone in this?

-- 
Brett M. Gilio
B.S. Biological Sciences
B.M. Music Composition
http://www.brettgilio.com/

"Sometimes the obvious is the enemy of the true." 
- G. Stolzenberg


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

Re: sesqui-flat spelling

[David Kastrup]

Simon Albrecht  writes:

> On 22.11.2017 04:37, Edward Neeman wrote:
>> This is not a huge issue, though it is annoying that Frescobaldi isn't
>> aware that these abbreviations aren't accepted. So if I convert
>> relative to absolute pitch in Frescobaldi, it changes my aeseh's to
>> aseh's, and I need to search and replace to be able to compile again.
>
> That should be added to the Frescobaldi issue tracker.

Personally, I find it rather belongs to the LilyPond issue tracker in
the long run.

-- 
David Kastrup

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

Re: [OT] Linux Users

[Simon Albrecht]

On 20.11.2017 18:12, Hilary Snaden wrote:
If there are any "graphical tools" as good as LaTeX, I'll be 
interested to hear of them. 


Adobe InDesign is certainly in many ways a “better” tool than LaTeX, in 
some “just as good” (like with the line breaking algorithms that it 
learned from TeX), and in some “less useful”, I’d assume particularly 
due to its closed source nature and lack of plain text input format.


Best, Simon

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

Re: sesqui-flat spelling

[Edward Neeman]

That's an easy workaround! Thanks.

Best
Edward

--


Dr. Edward Neeman
Adjunct Instructor, South Georgia State College
Collaborative Pianist, Valdosta State University, Georgia
Artist Faculty, ELMS Conservatory, Jakarta
edward.nee...@gmail.com
www.neemanpianoduo.com



On Nov 22, 2017 5:04 AM, "Caagr98"  wrote:

You can add your own language which contains those two aliases:

#(define a (assoc-ref language-pitch-names 'nederlands))
#(set! a (acons 'aseh (ly:make-pitch -1 5 THREE-Q-FLAT) a))
#(set! a (acons 'eseh (ly:make-pitch -1 2 THREE-Q-FLAT) a))
#(set! language-pitch-names (acons 'nederlands2 a language-pitch-names))
#(note-names-language "nederlands2")

{a aeseh aseh e eeseh eseh}

On 11/22/17 04:37, Edward Neeman wrote:
> Hello all,
>
> I've gotten quite used to the fact that "as" is A flat and "es" is E
> flat in Lilypond. Is there a reason why sesqui-flats need to be
> spelled aeseh and eeseh (instead of the abbreviated "aseh" or "eseh")?
>
> This is not a huge issue, though it is annoying that Frescobaldi isn't
> aware that these abbreviations aren't accepted. So if I convert
> relative to absolute pitch in Frescobaldi, it changes my aeseh's to
> aseh's, and I need to search and replace to be able to compile again.
>
> Thanks!
> Edward
>
> --
>
> Dr. Edward Neeman
> Adjunct Instructor, South Georgia State College
> Collaborative Pianist, Valdosta State University, Georgia
> Artist Faculty, ELMS Conservatory, Jakarta
> edward.nee...@gmail.com
> www.neemanpianoduo.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: Moving from lilypond 2.18 to 2.19

[Matt Wallis]

On 17/11/2017 15:57, David Kastrup wrote:

Matt Wallis  writes:


On 17/11/2017 14:15, David Kastrup wrote:

There are no error messages referring to my own lilypond source files,
which makes me wonder what's going on here.

Your source is triggering an error in the library.  Have you called
convert-ly -ed on your source in order to upgrade its syntax?


I understand that the lilypond-devel package is not intended to be
stable, and so bugs may appear. Is that what's happening here? If not,
I'm happy to try to create a small example that exposes this error.

First try convert-ly.


When I tried lilypond 2.19 on a different score, I had the above
error, but also some relating to my own .ly files. I guess there are
changes that I need to make to my source (even though I have `\version
"2.18.2"` in the source). Is that right? Is there a guide to these
changes?



Many thanks David,

That looks like exactly what I need :-)

If it turns out that this does the trick, it would be interesting to see
just what construct triggered the problem in 2.19 and what convert-ly
changed.  Because I currently have no good guess at what might have
happened here.
I tried convert-ly. It changed nothing other than the version number, 
and unsurprisingly the error persisted.


So I made experimental changes to the source until I found the cause of 
the error.

Here is a small example:

   \include "english.ly"

   global = {
  \time 4/4
  \tempo 4 = 96
   }
   \score {
  \new Staff {
    \clef treble
    \global
    \relative c' { c1 }
  }
  \midi { \global }
   }

... that provokes this error in 2.19.80:

   GNU LilyPond 2.19.80
   Processing `PianoScore.ly'
   Parsing.../opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14:
   In procedure ly:add-context-mod in expression (ly:add-context-mod
   mods (list # #)):
   /opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
   type argument in position 1 (expecting Context_mod): #f

... but works fine in 2.18.2

The error is triggered by the use of \global in the midi block when 
global contains "\time 4/4". Incidentally, if the midi block contains a 
\key signature, but no \time, then it works fine in 2.19.80.


I can understand that \time is irrelevant to midi (as is \key?), but 
I've used this lazily in the past because it works.
I'd be interested to know if you think the correct fix is to restore the 
original 2.18.2 behaviour, or to output an error message that identifies 
the line that causes the problem.


Matt Wallis

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

Fwd: Custom woodwind-diagram

[Sven Axelsson]

On 21 November 2017 at 18:38, Mike Solomon  wrote:

> Hey there!
>
> I created the diagrams eons ago and I agree that the implementation is
> really difficult to understand. I'm sorry for that. Can you send me a photo
> of what you're trying to typeset? I'll see if I can help you out.
>

Thank you. What I need is really simple, basically the tin-whistle chart
with a thumb hole and an extra bottom hole, like this:


​
-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fwd: Custom woodwind-diagram

[Sven Axelsson]

On 21 November 2017 at 17:49, SoundsFromSound 
wrote:

> Sven Axelsson-3 wrote
> > Hello list.
> >
> > I would like to create fingering instructions for an eight hole wind
> > instrument.
> >
> > I have not really tried to do anything yet - the woodwind diagrams look
> > terribly complicated to customize. There was talk about including
> > fingering
> > for recorders on the list some time ago
> > --
> > Sven Axelsson
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> Hello Sven,
>
> Two things:
>
> First, as you mentioned, here is an older thread that has some good
> information about recorder fingerings...
> http://lilypond.1069038.n5.nabble.com/recorder-fingering-cha
> rt-td28375.html
>
> Second, what version of LilyPond are you using?
>
> Here is some documentation from 2.19 that also could help you, perhaps?
> http://lilypond.org/doc/v2.19/Documentation/snippets/winds#w
> inds-recorder-fingering-chart


Thank you. I could use fingering markup as described in the documentation,
but this is intended for absolute beginners, so "real" fingering charts are
probably better.

-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving from lilypond 2.18 to 2.19

[David Kastrup]

Matt Wallis  writes:

> So I made experimental changes to the source until I found the cause
> of the error.
> Here is a small example:
>
>\include "english.ly"
>
>global = {
>   \time 4/4
>   \tempo 4 = 96
>}
>\score {
>   \new Staff {
>     \clef treble
>     \global
>     \relative c' { c1 }
>   }
>   \midi { \global }
>}
>
> ... that provokes this error in 2.19.80:
>
>GNU LilyPond 2.19.80
>Processing `PianoScore.ly'
>Parsing.../opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14:
>In procedure ly:add-context-mod in expression (ly:add-context-mod
>mods (list # #)):
>/opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
>type argument in position 1 (expecting Context_mod): #f
>
> ... but works fine in 2.18.2
>
> The error is triggered by the use of \global in the midi block when
> global contains "\time 4/4". Incidentally, if the midi block contains
> a \key signature, but no \time, then it works fine in 2.19.80.
>
> I can understand that \time is irrelevant to midi (as is \key?), but
> I've used this lazily in the past because it works.

It isn't.  The time signature is actually part of Midi files (SMF).  I
am not sure whether it is also part of realtime Midi, but it might.

> I'd be interested to know if you think the correct fix is to restore
> the original 2.18.2 behaviour, or to output an error message that
> identifies the line that causes the problem.

This sounds like a bug to me, and I have to take a look at what might be
responsible here.

Huh.  The bug triggers in context-defs-from-music, but that is
pre-2.16.0 material entirely.

Hm, I think the representation of \time might have gotten changed.
Let's check.  There is

commit fb79cea8ec10ebc40b96a05bf7f643e47fd93ddd
Author: David Kastrup 
Date:   Sun Mar 15 12:15:18 2015 +0100

Issue 4324: Don't create Bottom to announce TimeSignatureEvent

As a fallout of issue 4138, << \time 3/4 \new Staff c2. >> created a
spurious Staff only containing a time signature.  This change avoids the
creation of a Bottom context just for accommodating \time.  As a result,

{ \tweak color #red \time 3/4 c2. }

will no longer show a change in color since no Staff context exists at
the time \time is executed and consequently the tweak does not apply
anywhere.  You have to use \time in existing Staff contexts to have
either \tweak and point have an effect (and get an error locator
when something with typesetting the signature goes wrong).  Outside of
such contexts, \time just changes properties of the Timing context.


which is just one of a whole series of \time-changing commits by various
authors after 2.18.

That's likely the first occurence of the problem, but likely
context-defs-from-music should be made safe against this usage.

-- 
David Kastrup

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

Re: Custom woodwind-diagram

[James.Correa]

Hi Sven
I did this to use as a template for notate some multiphonics in a piece for 
flute. I added one more hole to match your instrument. It is not a function 
yet, you have to write all each time you use it, but can be turned into one by 
someone with more skills.

%%
\version "2.19.80"

multiF =  \markup {
  \left-column {\draw-circle #0.5 #0.2 ##f}
  \left-column { \draw-circle #0.5 #0.2 ##f
\vspace #-0.5
\draw-circle #0.5 #0.2 ##t
\vspace #-0.5
\draw-circle #0.5 #0.2 ##t
\vspace #-0.5
\draw-line #' ( 1.3 . 0)
\vspace #-0.5
\draw-circle #0.5 #0.2 ##f
\vspace #-0.5
\draw-circle #0.5 #0.2 ##f
\vspace #-0.5
\draw-circle #0.5 #0.2 ##f
\vspace #-0.5
\draw-circle #0.5 #0.2 ##f}

}

{c'4 ^\multiFa}

%

I hope it will help you.
James

---
James Correa
Composer - guitarist - sound designer
http://www.jamescorrea.net
http://wp.ufpel.edu.br/labcomp/

>  Original Message 
> Subject: Custom woodwind-diagram
> Local Time: November 21, 2017 1:58 PM
> UTC Time: November 21, 2017 3:58 PM
> From: sven.axels...@gmail.com
> To: lilypond-user@gnu.org
>
> Hello list.
>
> I would like to create fingering instructions for an eight hole wind 
> instrument. The usual way to display these fingerings would be to have the 
> thumb hole at the top, slightly offset, and the other seven holes in the 
> center column of the diagram.
>
> I have not really tried to do anything yet - the woodwind diagrams look 
> terribly complicated to customize. There was talk about including fingering 
> for recorders on the list some time ago, did anything come out of this? If 
> so, I could probably start there.
>
> Thanks,
>
> --
> Sven Axelsson
> ++[>++>+++>++>++
>><-]>.+..>+.>+.<<-.>>+.>.<<.
> +++.>-.<<++.>>.<++.>>>++..>>.<.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi Qt5

[Urs Liska]

Hi Brett,


Am 23.11.2017 um 04:54 schrieb Brett M. Gilio:

I know the Frescobaldi developers have been planning for a transition to
PyQt5/Qt5. I am quite versed with python and qt5, does anybody know how
far along they have gone in this?



As can be seen from 
https://github.com/wbsoft/frescobaldi/blob/master/ChangeLog this 
transition has been completed some time ago. Frescobaldi 3 exclusively 
requires Python3 and PyQt5. There's a glitch on some (?) LInux 
distributions that tend not to properly recompile one custom library 
after any PyQt5 update but basically it works.


But you are more than welcome joining development with other topics.
Just one example: currently I'm reviewing the code produced by a student 
of the Google-Summer-of-Code project 
(https://github.com/wbsoft/frescobaldi/pull/974). The point we're 
currently at (and I've got a bit stuck) is adding/improving the 
integration of the functionality with QActions, i.e. a natively Qt 
related issue.
Apart from that you could find yourself some minor tasks from the issues 
or feature requests and start getting familiar with the code base. Of 
course you won't be on your own with this ...


Best
Urs

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

Re: Moving from lilypond 2.18 to 2.19

[David Kastrup]

David Kastrup  writes:

> Matt Wallis  writes:
>
>> Here is a small example:
>>
>>/opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
>>type argument in position 1 (expecting Context_mod): #f
>>
>> ... but works fine in 2.18.2
>
> You know: the minimal example would have been
>
> \midi { \time 4/4 }
>
> and that would have saved adding a lot of other explanation:


> I'm currently writing two fixes.  One makes a better warning, the other
> does not trigger it.

Tracker issue: 5241 (https://sourceforge.net/p/testlilyissues/issues/5241/)
Rietveld issue: 334140043 (https://codereview.appspot.com/334140043)
Issue description:
  Let \time announce itself at least in Score  Previously it just used
  whatever context had been active.  This leads to problems with \midi
  { \time 4/4 } for example.

Tracker issue: 5242 (https://sourceforge.net/p/testlilyissues/issues/5242/)
Rietveld issue: 338970043 (https://codereview.appspot.com/338970043)
Issue description:
  Make context-defs-from-music warn when missing context  Previously,
  this caused an error.


-- 
David Kastrup

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

Re: Moving from lilypond 2.18 to 2.19

[David Kastrup]

Matt Wallis  writes:

> Here is a small example:
>
>\include "english.ly"
>
>global = {
>   \time 4/4
>   \tempo 4 = 96
>}
>\score {
>   \new Staff {
>     \clef treble
>     \global
>     \relative c' { c1 }
>   }
>   \midi { \global }
>}
>
> ... that provokes this error in 2.19.80:
>In procedure ly:add-context-mod in expression (ly:add-context-mod
>mods (list # #)):
>/opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
>type argument in position 1 (expecting Context_mod): #f
>
> ... but works fine in 2.18.2

You know: the minimal example would have been

\midi { \time 4/4 }

and that would have saved adding a lot of other explanation:

> The error is triggered by the use of \global in the midi block when
> global contains "\time 4/4". Incidentally, if the midi block contains
> a \key signature, but no \time, then it works fine in 2.19.80.
>
> I can understand that \time is irrelevant to midi (as is \key?), but
> I've used this lazily in the past because it works.

It is intended to work.  I am surprised that this has been overlooked
for so long.

> I'd be interested to know if you think the correct fix is to restore
> the original 2.18.2 behaviour, or to output an error message that
> identifies the line that causes the problem.

I'm currently writing two fixes.  One makes a better warning, the other
does not trigger it.

-- 
David Kastrup

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

Re: Custom woodwind-diagram

[Sven Axelsson]

On 21 November 2017 at 18:38, Mike Solomon  wrote:

> Hey there!
>
> I created the diagrams eons ago and I agree that the implementation is
> really difficult to understand. I'm sorry for that. Can you send me a photo
> of what you're trying to typeset? I'll see if I can help you out.
>

 I just want to thank Mike Solomon for his hints off-list. I managed to get
something I'm happy with by adding my instrument directly to
display-woodwind-diagrams.scm. When putting the additions in its own file
however, I did not manage to resolve all dependencies. I would have thought
that I could just use what was already defined, but maybe the woodwind
diagram support functions are not exported for outside use. Anyways, this
is fine for now.

 [image: Inline images 1]

-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Custom woodwind-diagram

[Sven Axelsson]

On 22 November 2017 at 18:10, Carl Sorensen  wrote:

>
>
> From: Sven Axelsson 
> Date: Wednesday, November 22, 2017 at 9:59 AM
> To: Mike Solomon 
> Cc: 
> Subject: Re: Custom woodwind-diagram
>  I just want to thank Mike Solomon for his hints off-list. I managed to
> get something I'm happy with by adding my instrument directly to
> display-woodwind-diagrams.scm. When putting the additions in its own file
> however, I did not manage to resolve all dependencies. I would have thought
> that I could just use what was already defined, but maybe the woodwind
> diagram support functions are not exported for outside use. Anyways, this
> is fine for now.
>
>
>
> Can you submit your revised .scm file as a patch?
>

Sure!

The question is, though, as a patch for what instrument? I made this for
use in a Great Highland Bagpipe tutor that I'm currently working on, but it
is usable for any eight hole wind instrument so I named the instrument
"recorder", since that is a bit more common.

The patch also includes a change to `key-fill-translate` in
define-woodwind-diagrams.scm to fill with black even for half covered
holes. Personally, I don't think I have ever seen grey being used for that,
but I guess it really should be made into an user settable option.

-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.


add-recorder-to-woodwind.patch
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Custom woodwind-diagram

[Mike Solomon]

Bravo! Great work!Yeah, none of that stuff is imported. Easy to do so though. 
Don't hesitate to make a pull request with your new diagram!


Sent from my Samsung Galaxy smartphone.
 Original message From: Sven Axelsson  
Date: 11/22/17  6:59 PM  (GMT+02:00) To: Mike Solomon  
Cc: lilypond-user@gnu.org Subject: Re: Custom woodwind-diagram 
On 21 November 2017 at 18:38, Mike Solomon  wrote:
Hey there!
I created the diagrams eons ago and I agree that the implementation is really 
difficult to understand. I'm sorry for that. Can you send me a photo of what 
you're trying to typeset? I'll see if I can help you out.
 I just want to thank Mike Solomon for his hints off-list. I managed to get 
something I'm happy with by adding my instrument directly 
todisplay-woodwind-diagrams.scm. When putting the additions in its own file 
however, I did not manage to resolve all dependencies. I would have thought 
that I could just use what was already defined, but maybe the woodwind diagram 
support functions are not exported for outside use. Anyways, this is fine for 
now.
 
-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.

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

Re: Clarinet fingerings

[Knute Snortum]

You gave us all the version numbers... except for LilyPond!  I'm going to
assume 2.18.2.

Here is the way I got it to work.  Improvements, suggestions welcome:


\version "2.18.2"
\language "english"

#(print-keys-verbose 'clarinet (current-error-port))

\relative {
  \time 4/4
  \key f \major
  \textLengthOn

  f4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two three four five six))
 (lh . (thumb))
 (rh . (four)))
  }

  g4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two three four five six))
 (lh . (thumb))
 (rh . ()))
  }

  a4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two three four five))
 (lh . (thumb))
 (rh . ()))
  }

  bf4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two three four))
 (lh . (thumb))
 (rh . ()))
  }

  c4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two three))
 (lh . (thumb))
 (rh . ()))
  }

  d4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one two))
 (lh . (thumb))
 (rh . ()))
  }

  e4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one))
 (lh . (thumb))
 (rh . ()))
  }

  f4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . (one))
 (lh . ())
 (rh . ()))
  }
}



---
Knute Snortum
(via Gmail)

On Mon, Nov 20, 2017 at 8:10 PM, Paul Scott  wrote:

> A quick comment, not the answer to your question:
>
> You have given the correct fingering for Bb for the F major scale but you
> have called it b4 which would be a B natural quarter note.  In LilyPond,
> unlike Finale, the key signature does not affect the note.  You must
> say bes or its equivalent in whatever language file you include.
> For example Bb would be "bf" if you include "english.ly'
>
> Many of us have learned this hard way,
>
> Hope that helps,
>
> Paul
>
> On Mon, Nov 20, 2017 at 05:50:01PM -0700, Greg wrote:
> > I am new to Lilypond and am slowly trying to learn to use it. I have
> > rediscovered learning the clarinet and my teacher has asked me to start
> with
> > the G major and F major scales. I'm pretty much a novice with little
> > knowledge (thus far) of the deeper aspects and subtleties of musical
> > notation, but I'm working on it. I thought learning Lilypond would a)
> help
> > me create whatever scales I need - initially with the fingerings, to set
> me
> > on the right path and b) immerse me in the details, so I'd learn faster.
> I
> > have managed to construct what I think is the F major scale (see below)
> but
> > you'll also see that the clarinet fingerings are not showing up.  E is
> doing
> > something but its diagram is different for a reason I don't understand
> and
> > none of the other fingerings are showing on the vanilla clarinet key
> > diagrams? Can anyone pont to what's going on, please?
> >
> > Many thanks
> >
> > Greg
> >
> > (Frescobaldi: 2.19.0
> > Python: 3.4.6
> > python-ly: 0.9.4
> > Qt: 4.8.6
> > PyQt: 4.11.4
> > sip: 4.16.9
> > poppler: 0.43.0
> > python-poppler-qt: 0.24.0
> > OS: Linux-4.4.92-18.36-default-x86_64-with-SuSE-42.2-x86_64)
> >
> > My .ly code follows:
> > 
> >
> > \language "english"
> >
> > #(print-keys-verbose 'clarinet (current-error-port))
> >   \time 4/4
> >   \relative f {
> >   \key f \major
> >   \textLengthOn
> > f4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two three four five six))
> q>(lh . (thumb))
> >(rh . (four))
> >   }
> > g4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two three four five six))
> >(lh . (thumb)))
> >   }
> > a4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two three four five))
> >(lh . (thumb)))
> >   }
> > b4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two three four))
> >(lh . (thumb)))
> >   }
> > c4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two three))
> >(lh . (thumb)))
> >   }
> > d^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> > #'((cc . (one two))
> >(lh . (thumb)))
> >   }
> > e4^\markup
> >   \override #'(size . 0.5){
> >   \woodwind-diagram
> > #'clarinet
> >

Re: Custom woodwind-diagram

[Carl Sorensen]

On 22 November 2017 at 19:48, Sven Axelsson  wrote:
On 22 November 2017 at 18:10, Carl Sorensen  wrote:

Can you submit your revised .scm file as a patch?

Sure!

The patch also includes a change to `key-fill-translate` in 
define-woodwind-diagrams.scm to fill with black even for half covered holes. 
Personally, I don't think I have ever seen grey being used for that, but I 
guess it really should be made into an user settable option.

Having looked some more at the documentation and code, I now realise that the 
gray shading indicates various trills. There are many possibilities, but one to 
indicate just a partially covered hole displayed in black seems to be missing. 
I suggest allowing the notation e.g. "one1hF" to indicate a half covered filled 
hole. It is currently not valid. This would need a change to 
`make-symbol-alist` in define-woodwind-diagrams.scm. My Scheme-fu is currently 
not sufficient to make that change, but I suppose I could figure it out 
eventually.

Why not just use "one" to indicate a half-covered hole?  Since there is no 
graphical difference between a half-filled hole and a filled hole, it seems 
like there does not need to be a separate notation for the half-filled whole in 
the input.

If we had a real grob that was a woodwind diagram, we would have a 'details 
property for the grob with an element that would describe how to display a 
half-covered hole, and then one could set that property as one desired.  Maybe 
we should create a woodwind-diagram-details property for the TextScript grob 
that would capture the instrument and the display characteristics (i.e., what 
do we do with a half-covered hole).

But since it is all markups now, it seems that we just make the markup be what 
we want it to be.

Thanks,

Carl
 

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

Re: Custom woodwind-diagram

[Carl Sorensen]

From: Sven Axelsson 
Date: Wednesday, November 22, 2017 at 9:59 AM
To: Mike Solomon 
Cc: 
Subject: Re: Custom woodwind-diagram
 I just want to thank Mike Solomon for his hints off-list. I managed to get 
something I'm happy with by adding my instrument directly to
display-woodwind-diagrams.scm. When putting the additions in its own file 
however, I did not manage to resolve all dependencies. I would have thought 
that I could just use what was already defined, but maybe the woodwind diagram 
support functions are not exported for outside use. Anyways, this is fine for 
now.



Can you submit your revised .scm file as a patch?

Thanks,

Carl


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

Re: Custom woodwind-diagram

[Sven Axelsson]

On 22 November 2017 at 19:48, Sven Axelsson  wrote:

> On 22 November 2017 at 18:10, Carl Sorensen  wrote:
>
>>
>> Can you submit your revised .scm file as a patch?
>>
>
> Sure!
>
> The patch also includes a change to `key-fill-translate` in
> define-woodwind-diagrams.scm to fill with black even for half covered
> holes. Personally, I don't think I have ever seen grey being used for that,
> but I guess it really should be made into an user settable option.
>

Having looked some more at the documentation and code, I now realise that
the gray shading indicates various trills. There are many possibilities,
but one to indicate just a partially covered hole displayed in black seems
to be missing. I suggest allowing the notation e.g. "one1hF" to indicate a
half covered filled hole. It is currently not valid. This would need a
change to `make-symbol-alist` in define-woodwind-diagrams.scm. My Scheme-fu
is currently not sufficient to make that change, but I suppose I could
figure it out eventually.

-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re:Clarinet fingerings

[Flaming Hakama by Elaine]

> From: Knute Snortum 
> To: Paul Scott 
> Cc: Greg , lilypond-user@gnu.org
> Subject: Re: Clarinet fingerings
> You gave us all the version numbers... except for LilyPond!  I'm going to
> assume 2.18.2.
>
> Here is the way I got it to work.  Improvements, suggestions welcome:
>
> 
> \version "2.18.2"
> \language "english"
>
> #(print-keys-verbose 'clarinet (current-error-port))
>
> \relative {
>   \time 4/4
>   \key f \major
>   \textLengthOn
>
>   f4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two three four five six))
>  (lh . (thumb))
>  (rh . (four)))
>   }
>
>   g4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two three four five six))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   a4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two three four five))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   bf4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two three four))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   c4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two three))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   d4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one two))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   e4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one))
>  (lh . (thumb))
>  (rh . ()))
>   }
>
>   f4^\markup \override #'(size . 0.5) {
> \woodwind-diagram
>   #'clarinet
>   #'((cc . (one))
>  (lh . ())
>  (rh . ()))
>   }
> }
> 
>
>
> ---
> Knute Snortum
> (via Gmail)
>



FWIW, the fingering shown for the last note (written F) is incorrect.
It would produce a written F# on clarinet.

To get an F, you'd need the last one to be:

  f4^\markup \override #'(size . 0.5) {
\woodwind-diagram
  #'clarinet
  #'((cc . ())
 (lh . (thumb))
 (rh . ()))
  }



HTH,

David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Custom woodwind-diagram

[Sven Axelsson]

On 22 November 2017 at 21:59, Carl Sorensen  wrote:

>
> On 22 November 2017 at 19:48, Sven Axelsson 
> wrote:
>
> Having looked some more at the documentation and code, I now realise that
>> the gray shading indicates various trills. There are many possibilities,
>> but one to indicate just a partially covered hole displayed in black seems
>> to be missing. I suggest allowing the notation e.g. "one1hF" to indicate a
>> half covered filled hole. It is currently not valid. This would need a
>> change to `make-symbol-alist` in define-woodwind-diagrams.scm. My Scheme-fu
>> is currently not sufficient to make that change, but I suppose I could
>> figure it out eventually.
>
>
> Why not just use "one" to indicate a half-covered hole?  Since there is no
> graphical difference between a half-filled hole and a filled hole, it seems
> like there does not need to be a separate notation for the half-filled
> whole in the input.
>

Sure there is a difference, see
http://lilypond.org/doc/v2.19/Documentation/notation/woodwind-diagrams for "
one1qT3q" for instance. Using "one 1h" as of now, the hole is displayed
half covered gray. I'd like some way to display it half covered black
without breaking existing usage.

Maybe Mike Solomon could chime in as being the original author?


-- 
Sven Axelsson
++[>++>+++>++>++
><-]>.+..>+.>+.<<-.>>+.>.<<.
+++.>-.<<++.>>.<++.>>>++..>>.<.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Custom woodwind-diagram

[Carl Sorensen]

From: Sven Axelsson 
Date: Wednesday, November 22, 2017 at 2:33 PM
To: Carl Sorensen 
Cc: Mike Solomon , "lilypond-user@gnu.org" 

Subject: Re: Custom woodwind-diagram

On 22 November 2017 at 21:59, Carl Sorensen 
> wrote:

On 22 November 2017 at 19:48, Sven Axelsson 
> wrote:
Having looked some more at the documentation and code, I now realise that the 
gray shading indicates various trills. There are many possibilities, but one to 
indicate just a partially covered hole displayed in black seems to be missing. 
I suggest allowing the notation e.g. "one1hF" to indicate a half covered filled 
hole. It is currently not valid. This would need a change to 
`make-symbol-alist` in define-woodwind-diagrams.scm. My Scheme-fu is currently 
not sufficient to make that change, but I suppose I could figure it out 
eventually.

Why not just use "one" to indicate a half-covered hole?  Since there is no 
graphical difference between a half-filled hole and a filled hole, it seems 
like there does not need to be a separate notation for the half-filled whole in 
the input.

Sure there is a difference, see 
http://lilypond.org/doc/v2.19/Documentation/notation/woodwind-diagrams for 
"one1qT3q" for instance. Using "one 1h" as of now, the hole is displayed half 
covered gray. I'd like some way to display it half covered black without 
breaking existing usage.

Oh, I misunderstood what you wanted.  I thought you wanted to have a black 
filled hole, not a black half-filled hole.

One way to do this would be to develop a new notation, as you suggest.   I 
would suggest that a notation of one1hB would be better than one1hF, because 
both the default half-covered diagram and the new half-covered diagram are 
half-filled; the difference is the color.

Another way would be to have a property that defines the fill color.  The 
default value for the property would be gray, but it could be set to black.  Or 
potentially any other color that was wanted (say red, or green, or yellow).

Thanks,

Carl



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