date:20131009

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Marc Hohl


Am 10.10.2013 01:56, schrieb Thomas Morley:

2013/10/9 Urs Liska :
[...]


One more thing which might be useful for the technical issues you are
talking about:
I started a snippet to switch program execution based on the used LilyPond
version
https://github.com/openlilylib/snippets/blob/master/specific-solutions/lilypond-version-switch.ly
Currently there is only one function 'lilypond-greater-than?' but I intend
to add equivalents to the other comparison operators. I think this approach
should allow you to make LilyJAZZ work with 2.16 and 2.17 at the same time?

HTH
Urs


Hi Urs,

your coding will not work.
Regard the results from:

2.12.3  -> 17
2.14.2  -> 18
2.16.2  -> 20
2.17.28 -> 47
seems to be ok,

though:

2.15.40 -> 57

You need to do a more detailed comparison.


Under the assumption that the last part of the version will never
exceed 99, why not go for

x.y.z -> (x*1000)+(y*100)+z

or, to be on the safe side for the next 300 years or so ;-)

x.y.z -> (x*10^6)+(y*10^3)+z

Just my 2ct

Marc


Cheers,
   Harm

___
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: Help ~ LilyPond Tablature

2013-10-09 Thread Marc Hohl


Am 09.10.2013 23:36, schrieb Pierre Perol-Schneider:

2013/10/9 Раул Апонт mailto:raulapo...@bk.ru>>

Hello.


Hi Раул


If you could send me an example, it would be great.


Here it is :

 [...]

stringTunings = #bass-tuning


stringTunings = #bass-five-string-tuning

if you have a bass with a low B string.

HTH,

Marc


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

Re: Automatic generation of scores skeletons

2013-10-09 Thread Johan Vromans

Jacques Menu  writes:

> After struggling with irregular bars, I've been working on a Python3 tool that
> transforms a spec such as:
> [...]
> into a ready-to-compile Lilypond source file.

Very interesting. It reminds me of something I considered a while ago:
a kind of meta-staff where the structure of the score is described
(time/tempo, repeats, special \bar's, and so on). These would then apply
to all the staffs automatically.

The rationale is that while a LilyPond score consists of horizontal
staffs, it is in fact structured vertically and sometimes it has
advantages to treat it as such. For example, using pseudo-LP:

  structure = {
  A1
  \repeat volta 2 {
 A2
  }
  \alternative{
 A21
 A22
  }
  A3
  \bar "||"
  A4
  \bar ":|"
  A5
  }
  A1 = { ... }
  B1 = { ... }
  C1 = { ... }
  ... and so on ...
  voiceA = { \A1 \A2 \A21 \A22 \A3 \A4 \A5 }
  voiceB = { \B1 \B2 \B21 \B22 \B3 \B4 \B5 }
  voiceC = { \C1 \C2 \C21 \C22 \C3 \C4 \C5 }

Much can be achieved with macro's, I know.

Can you give me a url for your tool?

Thanks,

-- Johan

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

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Martin Tarenskeen




On Thu, 10 Oct 2013, Martin Tarenskeen wrote:

Maybe it could even be possible to design a music font that improves the 
reading skills for people who have always had trouble to read music. 
Something comparable to that special text font that was designed for people 
with dyslexia: http://www.studiostudio.nl/en/information/


P.S. There is also OpenDyslexic, an open source version 
at http://opendyslexic.org/


--

PS

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

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Martin Tarenskeen




On Wed, 9 Oct 2013, Tim McNamara wrote:

Thanks for having a bash at that.  As a matter of taste, I think I 
prefer not having the font's sharps and flats used in the chord names 
because they look disproportionately large compared to the text, whereas 
the default accidentals look fine to my eyes.  Also, the lack of a lower 
case "m" in the font has confused my horn players so I use "-" instead 
of "m" in minor chords.



Hi,

I'm following this discussion from a distance. I am not a Jazz musician 
and have always wondered why Jazz musicians prefer computer-engraved sheet 
music that tries to look like it is hand written. My brother is a jazz 
composer/arranger who uses Finale and who always uses Finale's jazzfont 
for his compositions.


Is it just a tradition, and something jazz musicians feel familiar and 
comfortable with while writing and reading music? Or is a Jazzfont 
*really* easier to read on stage?


It would be interesting to do scientific research in what way a music font 
can influence the way we read music: reading speed, number of errors when 
sight-reading, things like that.


Maybe it could even be possible to design a music font that improves the 
reading skills for people who have always had trouble to read music. 
Something comparable to that special text font that was designed for 
people with dyslexia: http://www.studiostudio.nl/en/information/


I have heard this font really works for some people with dyslexia.

--

MT

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

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Tim McNamara

On Oct 9, 2013, at 6:40 PM, Thomas Morley  wrote:

> 2013/10/9 Jim Long :
>> On Wed, Oct 09, 2013 at 12:53:35AM +0200, Thomas Morley wrote:
>>> 2013/10/9 Jim Long :
>>> 
  \override ChordName #'font-name = #"lilyjazzchord"
>>> 
>>> Hi Jim,
>>> 
>>> never heard of "lilyjazzchord".
>>> Where to get?
>>> 
>>> Compiling your snippet returns LilyPond-default for the ChordNames.
>>> 
>>> Cheers,
>>>  Harm
>> 
>> It's available from the French-language page at:
>> 
>> https://sites.google.com/site/jpgzic/home/la-police
>> 
>> 
>> Jim
> 
> Hi,
> 
> this is another font and simply installing the font doesn't changes
> accidentals in chords with alterations.
> 
> So I made some effort and fully coded chords with Torstens font.
> -> ignatzek-jazz-chords.ily

Thanks for having a bash at that.  As a matter of taste, I think I prefer not 
having the font's sharps and flats used in the chord names because they look 
disproportionately large compared to the text, whereas the default accidentals 
look fine to my eyes.  Also, the lack of a lower case "m" in the font has 
confused my horn players so I use "-" instead of "m" in minor chords.

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

Re: New User Frescobaldi Setup for Mac

2013-10-09 Thread Paul Morris

Paul Morris wrote
> (Hmmm... this might be something to add to the guide.)

And done.  
-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/New-User-Frescobaldi-Setup-for-Mac-tp152054p152056.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: New User Frescobaldi Setup for Mac

2013-10-09 Thread Paul Morris

garrettm30 wrote
> After all of those instructions, I have successfully gotten Frescobaldi to
> launch, but it seems to have trouble pairing with LilyPond. When I go into
> the Preferences -> LilyPond Preferences, and set the "LilyPond version to
> use", I click add, point it to the LilyPond app, and then it says,
> "Running LilyPond, this can take some time..." Indeed it does: I can let
> it go for hours (I tried about three hours yesterday), and it will keep
> going forever. Now when the box with the above message first pops up,
> LilyPond itself launches. It's as though Frescobaldi can't hear back from
> LilyPond. Does that problem sound familiar to anyone?

Hi Garrett,
This is a familiar problem that tripped me up at first as well.  It's an
easy fix.  Instead of pointing it to the LilyPond app:
/Applications/LilyPond.app

You need to point it here:
/Applications/LilyPond.app/Contents/Resources/bin/lilypond

This is not intuitive, but should do the trick.  (Hmmm... this might be
something to add to the guide.)
-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/New-User-Frescobaldi-Setup-for-Mac-tp152054p152055.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

New User Frescobaldi Setup for Mac

2013-10-09 Thread Garrett McGilvray

I have tried thus far unsuccessfully to get Frescobaldi to work on my Mac, and 
I am wondering if any of you Mac Frescobaldi users could help me.

I have followed the instructions from this link:
https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide

After all of those instructions, I have successfully gotten Frescobaldi to 
launch, but it seems to have trouble pairing with LilyPond. When I go into the 
Preferences -> LilyPond Preferences, and set the "LilyPond version to use", I 
click add, point it to the LilyPond app, and then it says, "Running LilyPond, 
this can take some time..." Indeed it does: I can let it go for hours (I tried 
about three hours yesterday), and it will keep going forever. Now when the box 
with the above message first pops up, LilyPond itself launches. It's as though 
Frescobaldi can't hear back from LilyPond. Does that problem sound familiar to 
anyone?

I sure will appreciate your help.
-Garrett
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Thomas Morley

2013/10/9 Urs Liska :
[...]
>
> One more thing which might be useful for the technical issues you are
> talking about:
> I started a snippet to switch program execution based on the used LilyPond
> version
> https://github.com/openlilylib/snippets/blob/master/specific-solutions/lilypond-version-switch.ly
> Currently there is only one function 'lilypond-greater-than?' but I intend
> to add equivalents to the other comparison operators. I think this approach
> should allow you to make LilyJAZZ work with 2.16 and 2.17 at the same time?
>
> HTH
> Urs

Hi Urs,

your coding will not work.
Regard the results from:

2.12.3  -> 17
2.14.2  -> 18
2.16.2  -> 20
2.17.28 -> 47
seems to be ok,

though:

2.15.40 -> 57

You need to do a more detailed comparison.

Cheers,
  Harm

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

Re: Automatic generation of scores skeletons

2013-10-09 Thread Tim Reeves

Jacques,

This sounds like a great idea to me. I'm surprised no one else has 
commented.


Tim Reeves


> Message: 1
> Date: Wed, 9 Oct 2013 18:15:15 +0200
> From: Jacques Menu 
> To: "lilypond-user@gnu.org Users" 
> Cc: Jacques Menu 
> Subject: Automatic generation of scores skeletons
> Message-ID: 
> Content-Type: text/plain; charset="us-ascii"
> 
> Hello Folks,
> 
> After struggling with irregular bars, I've been working on a Python3
> tool that transforms a spec such as:
> 
> {
> "title" : "Thema allegro",
> "composer"  : "Ludwig van Beethoven (1808 -1854)",
> "tagline"   : "J. Menu - September 2013",
> "enteredby" : "Jacques Menu",
> 
> "instrumentName": "Bassoon",
> "clef"  : "bass",
> "key"   : "g \\major",
> "time"  : "2/4",
> 
> "initialUpBeat" : "8*1",
> 
> "firstBarNumber": 129,
> "lastBarNumber" : 150,
> 
> "finalBarPosition"  : "150:4/8",
> 
> "barNumbersAtBeginningOflines"  : [135, 142, 146],
> 
> "tempoMarks": { "129:1/8":"Thema allegro", "144:
> 1/8":"Coda"},
> 
> "repeats"   : [{"128:4/8-136:3/8", 1, []}, 
> {"136:4/8-144:3/8", 2, ["144:1/8-144:3/8", "144:1/8-144:4/8"]}],
> 
> "partName"  : "bassoonPart"
> 
> }
> 
> into a ready-to-compile Lilypond source file.
> 
> The latter contains either actual notes (all the same pitch) to 
> check the layout, or lines merely containing the "%nnn" comment at 
> the end, ready to be filled with the actual notes by whichever means.
> 
> The spec is in JSON format, which avoids writing a specific parser.
> 
> "136:4/8-144:3/8" denotes a range starting at the 4th eight in 
> measure 136 and ending at the 4rd eight in measure 144, inclusive.
> 
> There are still issues regarding the description of alternatives, as
> you can see.
> 
> barNumbersAtBeginningOflines can be used optionally to force line 
> breaks, to help check the score comparing it with the original.
> There's also the possibility to specify doubleBarsPositions.
> 
> The score described by the spec above is part of Beethoven's Trio X 
> WoO37 for flute, bassoon and piano:
> 
> 
> 
> The same skeleton could be used for the other instruments, of course.
> 
> Also, entering the spec data could be done in a GUI window as an 
extension.
> 
> Do you think there could be interest in such a tool for anyone else 
> than its author?
> 
> JM
> 
> --
> 
> Jacques Menu
> Ch. de la Pierre 12
> 1023 Crissier
> 
> mailto:jacques.m...@tvtmail.ch
>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help ~ LilyPond Tablature

2013-10-09 Thread and...@andis59.se

On 2013-10-09 22:19, Раул Апонт wrote:

Hello.

I need just a little help about a tablature. I know already how to get a
tablature with LilyPond, the situation I have now is about a Bass Guitar
tablature. I have tried to change the clef using the Bass clef, I still
get a six-string tablature, I just need to know HOW I GET the four and
five-string tablature because of the Bass Guitar range.
If you could send me an example, it would be great.

As usual it depends on your version of LilyPond.

Note to all! Always specify which version of LilyPond you are using!

When you use TabStaff it always default to Guitar. if you want something 
else you need to specify it.

Bass guitar (from the doc)

%% ---
\version "2.16"

<<
  \new Voice \with {
\override StringNumber #'stencil = ##f
  } {
\clef "bass_8"
\relative c, {
  c4 d e f
}
  }
  \new TabStaff \with {
stringTunings = #bass-tuning
  } {
\relative c, {
  c4 d e f
}
  }
>>
%% ---

%% ---
\version "2.17"

<<
  \new Voice \with {
\override StringNumber.stencil = ##f
  } {
\clef "bass_8"
\relative c, {
  c4 d e f
}
  }
  \new TabStaff \with {
stringTunings = #bass-tuning
  } {
\relative c, {
  c4 d e f
}
  }
>>
%% ---

Hope this helps!

// Anders
PS! The only difference I can see is the \overide StringNumber, which is 
different in 2.16 and 2.17. But since I don't know what it does I can't 
explain it... I leave this for the experts.

--
English isn't my first language.
So any error or strangeness is due to the translation.
Please correct my English so that I may become better.

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

Re: Help ~ LilyPond Tablature

2013-10-09 Thread Pierre Perol-Schneider

2013/10/9 Раул Апонт 

> Hello.
>

Hi Раул


>
> If you could send me an example, it would be great.
>
>
Here it is :

 \version "2.17.28"

global = {

\key c \major

\time 4/4

c c c c

}

music = \relative c, {

\global

}

\score {

\new TabStaff \with {

stringTunings = #bass-tuning

midiInstrument = "acoustic bass"

\consists "Instrument_name_engraver"

instrumentName = "Bass"

}

\music

\layout { }

\midi {

\context {

\Score

tempoWholesPerMinute = #(ly:make-moment 100 4)

}

}

}


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

Re: Help ~ LilyPond Tablature

2013-10-09 Thread Federico Bruni

There's an example in the documentation:
http://lilypond.org/doc/v2.16/Documentation/notation/common-notation-for-fretted-strings#custom-tablatures
Il 09/ott/2013 23:19 "Раул Апонт"  ha scritto:

> Hello.
>
> I need just a little help about a tablature. I know already how to get a
> tablature with LilyPond, the situation I have now is about a Bass Guitar
> tablature. I have tried to change the clef using the Bass clef, I still get
> a six-string tablature, I just need to know HOW I GET the four and
> five-string tablature because of the Bass Guitar range.
> If you could send me an example, it would be great.
>
> Thank you.
>
>
> --
> Раул Апонт
>
> ___
> 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: Help ~ LilyPond Tablature

2013-10-09 Thread Peter Crighton

Have a look at the Notation Reference:
http://lilypond.org/doc/v2.16/Documentation/notation/common-notation-for-fretted-strings.html#custom-tablatures
The tuning for a five-string bass is called #bass-five-string-tuning.


--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de


2013/10/9 Раул Апонт 

> Hello.
>
> I need just a little help about a tablature. I know already how to get a
> tablature with LilyPond, the situation I have now is about a Bass Guitar
> tablature. I have tried to change the clef using the Bass clef, I still get
> a six-string tablature, I just need to know HOW I GET the four and
> five-string tablature because of the Bass Guitar range.
> If you could send me an example, it would be great.
>
> Thank you.
>
>
> --
> Раул Апонт
>
> ___
> 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: Re:move notehead away

2013-10-09 Thread MING TSANG

Trevor,
Thank you very much. The "\once \override "  works.
I will read the "force-hshift" from learning doc.
Emanuel,
Ming. 



 From: Trevor Daniels 
To: MING TSANG ; lilypond-user@gnu.org; d...@gnu.org 
Sent: Wednesday, October 9, 2013 4:42:05 PM
Subject: Re: lilypond-user Digest, Vol 131, Issue 35
 


MING TSANG, you wrote Tuesday, October 08, 2013 6:02 PM


> I coded using \stemUP \stemDown as suggested. There seems no effect. 
> tenor and base note printed on top one another. For a normal score that 
> is what it should be. But since I use \ezNum, the number in the bass notehead 
> is seems over taken over the tenor note. It is ok. But when I code \ezNum for 
> tenor (no \ezNum on bass) the tenor note is over took by bass note. But on 
> my original .png (no \ezNum on tenor, \ezNum on bass) show tenor note over 
> took bass note, making hard to see the number.

The property you need to change is force-hshift.  This should go immediately
in front of the bass g4, like this:

        \once \override NoteColumn.force-hshift = #1.0 g4 |      %bar 05-06

You can read about force-hshift here:
http://lilypond.org/doc/v2.17/Documentation/learning/real-music-example
towards the end of that section.

HTH, Trevor___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Help ~ LilyPond Tablature

2013-10-09 Thread Раул Апонт

 Hello.

I need just a little help about a tablature. I know already how to get a 
tablature with LilyPond, the situation I have now is about a Bass Guitar 
tablature. I have tried to change the clef using the Bass clef, I still get a 
six-string tablature, I just need to know HOW I GET the four and five-string 
tablature because of the Bass Guitar range.
If you could send me an example, it would be great.

Thank you.


-- 
Раул Апонт___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond-user Digest, Vol 131, Issue 35

2013-10-09 Thread Trevor Daniels


MING TSANG, you wrote Tuesday, October 08, 2013 6:02 PM

> I coded using \stemUP \stemDown as suggested. There seems no effect. 
> tenor and base note printed on top one another. For a normal score that 
> is what it should be. But since I use \ezNum, the number in the bass notehead 
> is seems over taken over the tenor note. It is ok. But when I code \ezNum for 
> tenor (no \ezNum on bass) the tenor note is over took by bass note. But on 
> my original .png (no \ezNum on tenor, \ezNum on bass) show tenor note over 
> took bass note, making hard to see the number.

The property you need to change is force-hshift.  This should go immediately
in front of the bass g4, like this:

\once \override NoteColumn.force-hshift = #1.0 g4 |  %bar 05-06

You can read about force-hshift here:
http://lilypond.org/doc/v2.17/Documentation/learning/real-music-example
towards the end of that section.

HTH, Trevor

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

Re: Problem with LilyJAZZ.ily

2013-10-09 Thread David Kastrup

Urs Liska  writes:

> Am 09.10.2013 22:05, schrieb Curt:
>> Is it considered "bad behavior" to open up a github repository with
>> Thorsten's contribution, and then apply the patches to it, for that
>> to be considered the source of truth?
>>
> I don't think so.
>
> But is there an official statement about copyright and licensing when
> posting to lilypond-user?

LilyPond-user is an open mailing list, so there can not really be an
"official statement".  Like with other public utterances, one's
contributions are copyrighted.  If you want to be in the clear, you have
to ask people for their permission before putting contributions anywhere.

-- 
David Kastrup

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

Re: Problem with LilyJAZZ.ily

2013-10-09 Thread Urs Liska


Am 09.10.2013 22:05, schrieb Curt:

Is it considered "bad behavior" to open up a github repository with Thorsten's 
contribution, and then apply the patches to it, for that to be considered the source of 
truth?


I don't think so.

But is there an official statement about copyright and licensing when 
posting to lilypond-user?


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

Re: Move episema vertically

2013-10-09 Thread Ben Hillen

Hi David,

This works, thank you.

Greetz,

Ben



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Move-episema-vertically-tp151996p152038.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: Move episema vertically

2013-10-09 Thread David Nalesnik

Hi Ben,


On Wed, Oct 9, 2013 at 3:04 PM, Ben Hillen  wrote:

> Hi David,
>
> Thank you, your solution works fine, also in my installed version "2.16.2".
>
> Can you tell me how to code override of 'direction for getting Episema
> below
> the staff when the beam is down?
>
>  
>

Sure.  Like so:

\override Episema #'direction = #DOWN

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

Re: Problem with LilyJAZZ.ily

2013-10-09 Thread Curt

Is it considered "bad behavior" to open up a github repository with Thorsten's 
contribution, and then apply the patches to it, for that to be considered the 
source of truth?


On Oct 8, 2013, at 12:33 AM, Marc Hohl  wrote:

> Am 08.10.2013 06:23, schrieb Keith OHara:
>> Thomas Morley  gmail.com> writes:
>> 
>>> 2013/10/8 Steve Noland  thenolands.us>:
 Dear all,
 
 On a Mac, when trying to compile the jazz-test-3.ly file, I get the
 following error from Lilypond re: the LilyJAZZ.ily file:
>> 
>>> Try replacing #(define (jazz-keysig grob) ...) with Keith's suggestion:
>>> http://lilypond.1069038.n5.nabble.com/Pseudo-handwritten-font-tt142117.html#a147230
>>> 
>> 
>> Steve, could you put a link to that fix near wherever you found LilyJAZZ.ily 
>> ?
>> 
>> The history is, I extended the key-signature print function last August, for
>> development version 2.17.1 and eventually stable 2.18.  Meanwhile Thorsten 
>> was
>> probably working on LilyJAZZ, and had to depend on some undocumented 
>> internals
>> of the old key-signature print function.  In March he posted the version that
>> works with stable LilyPond 2.16.
>> 
>> Probably Thorsten, or any of us, will update his .ily file for version 2.18 
>> when
>> that comes out.
> 
> AFAIK Torsten has not answered any mail request since the beginning of
> August. I hope that this is does not imply any serious incidents ...
> 
> But some more or less "official", easy to be found location with the
> possibility to download (and update) code would be fine.
> 
> Would it be an option to include the file and the fonts similarly to the
> articulate script?
> 
> Marc
> 
> 
> ___
> 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: Move episema vertically

2013-10-09 Thread Ben Hillen

Hi David,

Thank you, your solution works fine, also in my installed version "2.16.2".

Can you tell me how to code override of 'direction for getting Episema below
the staff when the beam is down?

Greetz

Ben





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Move-episema-vertically-tp151996p152034.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: Colored note heads with black outline

2013-10-09 Thread Paul Morris

Pierre Perol-Schneider wrote
> Thanks Paul, your code is much better than the one I was going to put.
> Looks like a Christmas tree :)

Thanks Pierre, and thanks for figuring out how to do the note heads in the
first place!  That was a clever solution.  

I've made the changes you suggested, and made it so that it's possible to
assign different colors to sharp, flat, double-sharp, and double-flat
alterations, if you want.  It's more verbose this way, but also more
flexible.  See below...

-Paul


%

\version "2.17.28"

coloredNoteHeads =
#(lambda (grob)
   (let* ((fsz  (ly:grob-property grob 'font-size 0.0))
  (mult (magstep fsz))
  (stl '())
  (dur-log (ly:grob-property grob 'duration-log))
  (pch (ly:event-property (event-cause grob) 'pitch))
  (nnm (ly:pitch-notename pch))
  (alt (ly:pitch-alteration pch))
  (clr (case nnm
 ((0) (case alt
((-1) red) ;; Cbb
((-1/2) red) ;; Cb
((0) red) ;; C
((1/2) red) ;; C#
((1) red) ;; C##
(else black)))
 ((1) (case alt
((-1) green) ;; Dbb
((-1/2) green) ;; Db
((0) green) ;; D
((1/2) green) ;; D#
((1) green) ;; D##
(else black)))
 ((2) (case alt
((-1) blue) ;; Ebb
((-1/2) blue) ;; Eb
((0) blue) ;; E
((1/2) blue) ;; E#
((1) blue) ;; E##
(else black)))
 ((3) (case alt
((-1) red) ;; Fbb
((-1/2) red) ;; Fb
((0) red) ;; F
((1/2) red) ;; F#
((1) red) ;; F##
(else black)))
 ((4) (case alt
((-1) green) ;; Gbb
((-1/2) green) ;; Gb
((0) green) ;; G
((1/2) green) ;; G#
((1) green) ;; G##
(else black)))
 ((5) (case alt
((-1) blue) ;; Abb
((-1/2) blue) ;; Ab
((0) blue) ;; A
((1/2) blue) ;; A#
((1) blue) ;; A##
(else black)))
 ((6) (case alt
((-1) yellow) ;; Bbb
((-1/2) yellow) ;; Bb
((0) yellow) ;; B
((1/2) yellow) ;; B#
((1) yellow) ;; B##
(else black)))
 (else black

 ;; just for dev work
 ;; (display dur-log) (newline)
 ;; (display nnm) (newline)
 ;; (display alt) (newline)

 (set! stl
   (cond
;; quarter notes and smaller
((> dur-log 1)
 (grob-interpret-markup grob
   #{ \markup {
 \combine
 \musicglyph #"noteheads.s2"
 \translate-scaled #'(0.05 . 0)
 \scale #'(1.03 . 0.98)
 \rotate #'3
 \magnify # 0.9 \with-color #clr
 \musicglyph #"noteheads.s2"
   } #}
   ))
;; half notes
((= dur-log 1)
 (grob-interpret-markup grob
   #{ \markup {
 \combine
 \translate-scaled #'(0.11 . -0.01)
 \scale #'(1 . 0.82)
 \rotate #'7
 \magnify # 0.85
 \musicglyph #"noteheads.s1"
 \combine
 \musicglyph #"noteheads.s1"
 \translate-scaled #'(0.07 . 0)
 \scale #'(1.02 . 0.98)
 \rotate #'2
 \magnify # 0.9 \with-color #clr
 \musicglyph #"noteheads.s1"
   } #}
   ))
;; whole notes
((< dur-log 1)
 (grob-interpret-markup grob
   #{ \markup {
 \combine
 \translate-scaled #'(0.2 . 0)
 \magnify # 0.8
 \musicglyph #"noteheads.s0"
 \combine
 \musicglyph #"noteheads.s0"
 \translate-scaled #'(0.08 . 0)
 \scale #'(1.03 . 1)
 \magnify # 0.9 \with-color #clr
 \musicglyph #"noteheads.s0"
   } #}
   

 (set! (ly:grob-property grob 'stencil)
   (ly:stencil-scale stl mult mult


music =
\relative f' {
  c4 d e f g a b c d e f g a b c d
  c,,2 d e f g a b c d e f g a b c d
  c,,1 d e f g a b c d e f g a b

Re: Colored note heads with black outline

2013-10-09 Thread Paul Morris

SoundsFromSound wrote
> This is perfect Paul, it's exactly what I need for a project that just
> landed on my desk tonight! Man, you're a SCHEME machine! I'll get there
> someday...right? :)
> 
> Thank you so much for sharing that code with us!

Thanks Ben!  Glad you can use the code.  Sounds like it arrived just in
time!  I still feel like a novice next to some of the Schemers on this list,
but I've managed to learn my way around.  The initial learning curve can be
steep, but it's not so bad once you get the hang of it.

Cheers,
-Paul




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Colored-note-heads-with-black-outline-tp151821p152032.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: Lyric hyphens, preferred and otherwise

2013-10-09 Thread Joel C. Salomon

On Wed, Oct 9, 2013 at 2:53 PM, Kieren MacMillan
 wrote:
> You can force adjacent lyrics to be a minimum distance apart — that should do 
> it:

> \override LyricHyphen #'minimum-distance = #1

Thank you. Since I don't need that everywhere, I turned that idea into
the code below.

--Joel

\version "2.16.2"

realHyphen =
#(define-music-function
 (parser location text)
 (ly:music?)
   #{
 \override LyricHyphen #'minimum-distance = #1
 #text
 \revert LyricHyphen #'minimum-distance
   #})

\score {
  <<
\relative c'' { c4 c c c  }
\addlyrics {
  \realHyphen { two -- part }
  two -- part
}
  >>
}

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

Re: Catch direction operators

2013-10-09 Thread Paul Morris

David Kastrup wrote
> Might make more sense to add it to LilyPond's own snippet base, I guess.
> Obviously, we have no limitations how new any snippets may be there.

Sounds good.


David Kastrup wrote
> Well, I try keeping the global name space uncluttered, but if you see an
> actual potential for use outside of \colorizeDir, that's certainly a
> small price to pay.

That makes sense.  I can't think of any use for it outside of \colorizeDir,
so I've changed it back to its original form in that LSR snippet.

-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Catch-direction-operators-tp151552p152031.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: Lyric hyphens, preferred and otherwise

2013-10-09 Thread Kieren MacMillan

Hi Joel,

> It would be OK with me if this was displayed "two-part" or "two -
> part", but I want to avoid having this hyphen disappear: "twopart" is
> *not* good.

You can force adjacent lyrics to be a minimum distance apart — that should do 
it:

\version "2.16.2"

\layout {
  \context {
\Lyrics
\override LyricHyphen #'minimum-distance = #1
  }
}

\score {
 <<
   \relative c'' { c2 c }
   \addlyrics { two -- part }
  >>
}

Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Lyric hyphens, preferred and otherwise

2013-10-09 Thread Joel C. Salomon

Is there a way to indicate that a hyphen is desired here, or that it
is preferred that it be shrunk to nothing?  Consider this example:

\version "2.16.2"
\score {
  <<
\relative c'' { c2 c }
\addlyrics { two -- part }
  >>
}

It would be OK with me if this was displayed "two-part" or "two -
part", but I want to avoid having this hyphen disappear: "twopart" is
*not* good.

I've tried `\addlyrics { two-part _ }` and `\addlyrics { "two -" part
}`. They both sort-of work, but is there a more flexible solution?

--Joel

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

Re: Testers needed who use Frescobaldi from Git

2013-10-09 Thread Urs Liska

You don't need to be a Github user.
You simply can add my fork (g...@github.com:uliska/frescobaldi.git) as a remote 
to your frescobaldi git repo (git remote add). Then you can pull in any 
branches (use git remote show uliska to see which branches are there).

But that's not necessary anymore in this case since Wilbert already merged it 
into master.
So you can simlply pull in the latest master and try out the new Git menu :-)

Best
Urs

PS: Feedback is welcome nevertheless!



Francisco Vila  schrieb:
>2013/10/9 Urs Liska :
>> I'm working on adding some Git functionality for Frescobaldi.
>...
>> So anybody using Frescobaldi from its Git repository is kindly asked
>to test
>> this pull request
>> https://github.com/wbsoft/frescobaldi/pull/223
>> and report any issues or success, to me or the comments section on
>the pull
>> request.
>
>I run and install Frescobaldi from git, but I am not an user of
>github. How to test the pull request in a console?
>
>-- 
>Francisco Vila. Badajoz (Spain)
>www.paconet.org , www.csmbadajoz.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: Testers needed who use Frescobaldi from Git

2013-10-09 Thread Francisco Vila

2013/10/9 Urs Liska :
> I'm working on adding some Git functionality for Frescobaldi.
...
> So anybody using Frescobaldi from its Git repository is kindly asked to test
> this pull request
> https://github.com/wbsoft/frescobaldi/pull/223
> and report any issues or success, to me or the comments section on the pull
> request.

I run and install Frescobaldi from git, but I am not an user of
github. How to test the pull request in a console?

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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

Re: Page number changes & forcing headers to appear on second page

2013-10-09 Thread Eluze

EdBeesley wrote
> 
> Eluze: I copied and pasted your code into Lilypond but didn't get any
> copyright text on 2nd or 3rd pages...maybe this is a new thing with 2.17?
> (I'm still on 2.16)

correct - it works with 2.17.0 and newer!

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Page-number-changes-forcing-headers-to-appear-on-second-page-tp151916p152024.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

Testers needed who use Frescobaldi from Git

2013-10-09 Thread Urs Liska


Hi all,

I'm working on adding some Git functionality for Frescobaldi.
Initially this will control Frescobaldi's source repository itself (i.e. 
managing program versions), but the ultimate goal is to add 
functionality to manage LilyPond projects.


I've finished a first step, which doesn't provide very spectacular 
functionality but serves as a proof-of-concept.
Before proceeding I would like to have it tested by others in other 
contexts (OS, Git version, number of branches and remotes etc.) in order 
to catch any flaws as early as possible.


So anybody using Frescobaldi from its Git repository is kindly asked to 
test this pull request

https://github.com/wbsoft/frescobaldi/pull/223
and report any issues or success, to me or the comments section on the 
pull request.


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

Re: Colored note heads with black outline

2013-10-09 Thread Pierre Perol-Schneider

2013/10/9 Pierre Perol-Schneider 


> Well, your code makes me noticed that the layer change with the color...
> weird.
>
> Sorry for this ; it changes with pitches and stem direction. Not weird in
f
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Colored note heads with black outline

2013-10-09 Thread Pierre Perol-Schneider

2013/10/9 Paul Morris 

>
> Hi Onno,
> The code below should do what you want.  I combined Pierre's outlined note
> heads with some code I use to automatically override note head stencils
> based on their pitch.  It creates outlines around all note heads regardless
> of their color, and it requires LilyPond 2.17.
>
>
>
Thanks Paul, your code is much better than the one I was going to put.
Looks like a Christmas tree :)


>
> ((= dur-log 1)
>  (grob-interpret-markup grob
>#{ \markup {
>  \combine
>  \translate-scaled #'(0.11 . -0.01)
>  \scale #'(1 . 0.82)
>  \rotate #'7
>  \magnify # 0.85
>  \musicglyph #"noteheads.s1"
>  \combine
>  \musicglyph #"noteheads.s1"
>  \translate-scaled #'(0.07 . 0)
>  \scale #'(1.02 . 0.98)
>  \rotate #'2
>  \magnify # 0.9 \with-color #clr
>  \musicglyph #"noteheads.s1"
>} #} ))
>

Here, I'd like to change some settings in order to re-center the colored
notehead :


\combine

\musicglyph #"noteheads.s2"

\translate-scaled #'(0.05 . 0)

\scale #'(1.03 . 0.98)

\rotate #'3

\magnify # 0.9 \with-color #clr

\musicglyph #"noteheads.s2"


> \new Staff \with
> { \override NoteHead.before-line-breaking = \coloredNoteHeads }
> { \music }
>

Well, your code makes me noticed that the layer change with the color...
weird.
So better add it :

\new Staff \with {

\override NoteHead.layer = #2

\override NoteHead.before-line-breaking = \coloredNoteHeads }

{ \music }


Cheers,

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

Re: Problems with LilyJAZZ.ily

2013-10-09 Thread Urs Liska


Am 09.10.2013 01:07, schrieb Jim Long:

On Wed, Oct 09, 2013 at 12:53:35AM +0200, Thomas Morley wrote:

2013/10/9 Jim Long :


   \override ChordName #'font-name = #"lilyjazzchord"

Hi Jim,

never heard of "lilyjazzchord".
Where to get?

Compiling your snippet returns LilyPond-default for the ChordNames.

Cheers,
   Harm

It's available from the French-language page at:

https://sites.google.com/site/jpgzic/home/la-police


Jim


Hi all who are involved,

I followed this thread only loosely.
As long as we can't directly include LilyJAZZ into LilyPond I suggest 
making it available (and improvable) here:

https://github.com/openlilylib/snippets/tree/master/LilyJAZZ
I just created a folder where all related stuff can be placed.
So I would suggest that once you have sorted everything out someone adds 
the files there, maybe also writes an introduction in the README.md file 
(which will be automatically displayed when viewing the folder).


One more thing which might be useful for the technical issues you are 
talking about:
I started a snippet to switch program execution based on the used 
LilyPond version

https://github.com/openlilylib/snippets/blob/master/specific-solutions/lilypond-version-switch.ly
Currently there is only one function 'lilypond-greater-than?' but I 
intend to add equivalents to the other comparison operators. I think 
this approach should allow you to make LilyJAZZ work with 2.16 and 2.17 
at the same time?


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

Re: lilypond-user Digest, Vol 131, Issue 35

2013-10-09 Thread David Kastrup

Marc Hohl  writes:

> Am 08.10.2013 19:02, schrieb MING TSANG:
>> David,
>> I coded using \stemUP \stemDown as suggested. There seems no effect.
>
> I don't think that \stemUp/\stemDown was a suggestion but rather meant
> as a possible source for the errors.
>
> \new Staff <<
>   \clef "bass"
>   \new Voice = "Tenor" {  \stemUp \TimeKey \TenorMusic }
>   \new Voice = "Bass"  {  \stemDown\BassMusic  }
>>>
>
> Does the error still occur when you replace \stemUp/\stemDown by
> \voiceOne/\voiceTwo, as you did for Soprano and Alto?

I don't think this helps.  Identical unisono noteheads are merged.  It's
possible that pretending to be a different notehead style might help,
but I'm not sure LilyPond looks at that for the merging decision.

-- 
David Kastrup


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

Re: lilypond-user Digest, Vol 131, Issue 35

2013-10-09 Thread Marc Hohl


Am 08.10.2013 19:02, schrieb MING TSANG:

David,
I coded using \stemUP \stemDown as suggested. There seems no effect.


I don't think that \stemUp/\stemDown was a suggestion but rather meant
as a possible source for the errors.

\new Staff <<
  \clef "bass"
  \new Voice = "Tenor" {  \stemUp \TimeKey \TenorMusic }
  \new Voice = "Bass"  {  \stemDown\BassMusic  }
>>

Does the error still occur when you replace \stemUp/\stemDown by
\voiceOne/\voiceTwo, as you did for Soprano and Alto?

Marc


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

39 matches

Mail list logo