problem with \autochange and \ottava

[Gilberto Agostinho]

Hello LilyPonders,

I am having trouble dealing with ottava changes while using autochange. Have
a look on the code below:

\score {
  <<
\new Staff = up {
  c' d' c' \change Staff = "down" b
  \change Staff = "up" \ottava#1  \ottava#0 c' b a
}
\new Staff = down {
  \clef bass 
  s1 s1
}
  >>
}

\score {
  \new PianoStaff \autochange {
 c'4 d' c' b \ottava#1  \ottava#0 c' b a
  }
}

Which produces this:
 

The top system is manually written, while the second uses autochange. I can
see what's happening is that autochange is waiting for the next note higher
than c to change staffs, and thus any command before this note (including
ottavation) will be written before it (that is, still in the bottom staff).
Is there any way of dealing with this situation or do I need to manually
deal with it?

Thanks a lot,
Gilberto





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/problem-with-autochange-and-ottava-tp168278.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: Accidental Notes in different colour

[Paul Morris]

Jay Vara wrote
> Is there a similar way to get at the accidental grob from the NoteNames? I
> tried a similar method by overriding the NoteNames.stencil and giving the
> NoteName a colour there. When I do an (accidental (ly:grob-object grob
> 'accidental-grob)), it always comes up with null. Also, I have several key
> signature changes in my music and I realised that by the time Lilypond
> gets to printing the NoteNames, it seems to have lost knowledge of the key
> signatures and only remembers the very last one. 

This will be harder to do... There are no accidental grobs attached to note
names grobs, so that approach won't work. 

My next thought is to make a custom engraver, add it to the note names
context, and use it to set the color of accidental note names.  But it seems
that the note names context does not have a key signature property, like a
staff context does. (With a custom note head engraver you can access the key
signature property in the staff context, and use that to identify accidental
notes, but that won't work with note heads context.)  

So I'm not sure how to achieve this...  I'll let you know if I think of
anything.

-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Accidental-Notes-in-different-colour-tp168088p168276.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: Place objects by hand

[Noeck]

>> However, how can I control the Y position? Y-offset does not work:

> I don't think you need to do anything.  As soon as the dynamics context has
> more content it should all appear centralised again.

That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).

Joram

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

Re: Place objects by hand

[Trevor Daniels]

Noeck wrote Saturday, November 01, 2014 11:49 PM

> However, how can I control the Y position? Y-offset does not work:
> 
> Warning: the property 'Y-offset of # cannot be offset

I don't think you need to do anything.  As soon as the dynamics context has
more content it should all appear centralised again.

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

Re: Place objects by hand

[David Nalesnik]

Hi Joram,

On Sat, Nov 1, 2014 at 6:48 PM, Joram Berger  wrote:

> > Yay!  This is an example where \offset is useful!  Try this:
> > \once \offset X-offset -3 DynamicText
>
> Hi Trevor,
>
> thanks, that's cool!
> However, how can I control the Y position? Y-offset does not work:
>
> Warning: the property 'Y-offset of # cannot be offset
>

Try:

 {
  \offset padding 2 DynamicLineSpanner
  c\f
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Place objects by hand

[Noeck]

> Yay!  This is an example where \offset is useful!  Try this:
> \once \offset X-offset -3 DynamicText 

Hi Trevor,

thanks, that's cool!
However, how can I control the Y position? Y-offset does not work:

Warning: the property 'Y-offset of # cannot be offset


Joram




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

Re: Place objects by hand

[Joram Berger]

> Yay!  This is an example where \offset is useful!  Try this:
> \once \offset X-offset -3 DynamicText 

Hi Trevor,

thanks, that's cool!
However, how can I control the Y position? Y-offset does not work:

Warning: the property 'Y-offset of # cannot be offset


Joram




signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dots far from beam

[Trevor Daniels]

Noeck wrote Saturday, November 01, 2014 11:11 PM

> why are the dots on the first two notes so far away from the beam?
> 
> \version "2.18.2"
> 
> \relative c {
>  \clef bass \voiceOne
>  16-.[ q-.] -.[ q-.]
> }

It's due to quantising the Y-position to avoid leger lines (even though
they are not visible.
 
> How can I put them closer to the beam like at the last two notes?
> Anything else than extra-offset?
>  \once \override Script.extra-offset = #'(0 . -0.8)
> 
> Is this a bug?

It would be an enhancement not to quantise the position outside the
visible leger lines.

One solutions is to move the beams down slightly, and the dots then
drop down.  Another use for \offset!  I've been searching for good
examples!  Like this:

\version "2.18.2"

\relative c {
  \clef bass \voiceOne
  \once \offset positions -0.2 Beam
  16-.[ q-.] -.[ q-.]
}

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

Re: Place objects by hand

[Trevor Daniels]

Noeck wrote Saturday, November 01, 2014 10:59 PM

> I would like to move some objects by hand. This minimal example shows
> the beginning of a piano staff.
> 
> \version "2.18.2"
> 
> \new PianoStaff <<
>  \new Staff { g-_ }
>  \new Dynamics {
>%\override DynamicText.extra-offset = #'(-4 . 0)
>s\f
>  }
>  \new Staff { \clef bass g'-_ }
>>>
> 
> The forte symbol is in between the two notes and prevents the staffs to
> get closer together. extra-offset does not help as it comes too late.
> How can I place the DynamicText such that the staffs can come closer
> together?

Yay!  This is an example where \offset is useful!  Try this:

\version "2.18.2"

\new PianoStaff <<
  \new Staff { g-_ }
  \new Dynamics {
%\override DynamicText.extra-offset = #'(-4 . 0)
\once \offset X-offset -3 DynamicText 
s\f
  }
  \new Staff { \clef bass g'-_ }
>>

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

Re: Happy 18th birthday, LilyPond

[Kieren MacMillan]

> Could we say that LilyPond has entered Adulthood now?

Depends on the jurisdiction, I suppose…

Cheers,
Kieren.
___

Kieren MacMillan, composer
www:  
email:  i...@kierenmacmillan.info


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

Dots far from beam

[Noeck]

Hi,

why are the dots on the first two notes so far away from the beam?

\version "2.18.2"

\relative c {
  \clef bass \voiceOne
  16-.[ q-.] -.[ q-.]
}

How can I put them closer to the beam like at the last two notes?
Anything else than extra-offset?
  \once \override Script.extra-offset = #'(0 . -0.8)

Is this a bug?

Thanks for any help!

Joram

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

Place objects by hand

[Noeck]

Hi,

I would like to move some objects by hand. This minimal example shows
the beginning of a piano staff.

\version "2.18.2"

\new PianoStaff <<
  \new Staff { g-_ }
  \new Dynamics {
%\override DynamicText.extra-offset = #'(-4 . 0)
s\f
  }
  \new Staff { \clef bass g'-_ }
>>

The forte symbol is in between the two notes and prevents the staffs to
get closer together. extra-offset does not help as it comes too late.
How can I place the DynamicText such that the staffs can come closer
together?

Joram

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

Re: Happy 18th birthday, LilyPond

[Martin Tarenskeen]

On Sat, 1 Nov 2014, Pierre Perol-Schneider wrote:


 Happy brithday ! :)

 2014-11-01 12:07 GMT+01:00 David Kastrup :
  
   Well, one gets the idea: this looks more like
   conception/pregnancy than
   the actual birth of LilyPond.  So maybe the Oct 1996 date is
   indeed the
   point to celebrate.



Could we say that LilyPond has entered Adulthood now?

--

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

Re: Where to Download the New Music Fonts?

[Hans Aberg]

On 29 Jul 2014, at 21:16, Graham Breed  wrote:
> 
> On 29/07/14 15:18, Hans Aberg wrote:
> 
>> Graham Breed wrote a file for equal temperaments for an earlier version of 
>> LilyPond, which I was able to tweak for the latest version (discussed on the 
>> devel list). When using the currently available microtonal symbols, then 
>> also key signatures seemed to work fine - a problem in the past.
> 
> The latest code is here: https://bitbucket.org/x31eq/microlily
> 
> I thought it was up to date.  I can take patches if it isn't.
> 
>> So it seems that all one has to do in order to get decent microtonality into 
>> LilyPond is to include this version of Graham’s file in the distribution and 
>> add microtonal symbols so that they can be called like the ones currently 
>> available.
> 
> Sagittal works for accidentals as a text font.  It should work for key 
> signatures as well, but I don't test that.  I didn't use a music font because 
> it was too much trouble to create a music font with Sagittal. Also, it's 
> possible to use strings for chained accidentals with a text font.  This would 
> be important for Extended Helmholtz if anybody wired it up.

I found that LilyPond 2.19.15 already is capable of this, using the SMuFL 
standard [1], and the font Bravura [2], plus the OpenLily code [3]. 
Specifically, I use your file regular.ly to make one E53 (53-ET), then I tweak 
the file definitions.ily, by adding the SMuFL accidental names (those with 
singe and double up and down arrows, in multiples of 6/53) to the definition of 
the variable smufl-alteration-glyph-name-alist. Microtonal key signatures seem 
to work.

The file example.ly also compiled. So it seems to be good to have this stuff 
integrated into the LilyPond distribution.

1. http://www.smufl.org
2. http://www.smufl.org/fonts/
3. 
https://github.com/openlilylib/openlilylib/tree/master/custom-music-fonts/smufl



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

Re: Unicode Font Issues

[Werner LEMBERG]

> If it works on Linux, I may have a way to get Linux on the windows
> PC using Virtual Box. On the other hand I am using version 2.18.2 -
> perhaps I should try 2.19.5 first.

I fear that 2.19.5 will fail on Windows as 2.18.2 does.


Werner

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

Re: Accidental Notes in different colour

[Jay Vara]

Paul,

Is there a similar way to get at the accidental grob from the NoteNames? I
tried a similar method by overriding the NoteNames.stencil and giving the
NoteName a colour there. When I do an (accidental (ly:grob-object grob
'accidental-grob)), it always comes up with null. Also, I have several key
signature changes in my music and I realised that by the time Lilypond gets
to printing the NoteNames, it seems to have lost knowledge of the key
signatures and only remembers the very last one. 

Jay




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Accidental-Notes-in-different-colour-tp168088p168244.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: Unicode Font Issues

[Jay Vara]

If it works on Linux, I may have a way to get Linux on the windows PC using
Virtual Box. On the other hand I am using version 2.18.2 - perhaps I should
try 2.19.5 first.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Unicode-Font-Issues-tp168122p168243.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: Development and Stable version on Mac

[Davide Liessi]

2014-10-31 21:43 GMT+01:00 Br. Samuel Springuel :
> 1) Download the binary for the latest development release
> 2) Unpack the tarball
> 3) Rename the application file to "LilyPond-dev"
> 4) Copy into Applications

This is what I usually do.
Indeed at the moment I have about a dozen of different versions of
LilyPond.app that I renamed as "LilyPond X.Y.Z.app" (all of them are
registered in Frescobaldi).

If I remember correctly, this was somehow problematic with 2.12.X
and/or 2.13.X, but I think that renaming LilyPond.app version >=
2.14.0 is perfectly OK.

Best wishes.
Davide

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

Re: Happy 18th birthday, LilyPond

[Pierre Perol-Schneider]

Hi Han-Wen

2014-11-01 21:05 GMT+01:00 Han-Wen Nienhuys :

> The 0.0.0 release happened in the first half of October 1996. I can't
> remember the exact date, but it was a weekday and I celebrated by
> having a beer with my dorm-mates.
>


So maybe you remember which day : 12th & 13th was resp. a Saturday and a
Sunday?...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Happy 18th birthday, LilyPond

[Han-Wen Nienhuys]

The 0.0.0 release happened in the first half of October 1996. I can't
remember the exact date, but it was a weekday and I celebrated by
having a beer with my dorm-mates.



On Sat, Nov 1, 2014 at 6:11 AM, Francisco Vila  wrote:
> Sorry for the cross-posting. Just a short note to say LIlyPond is 18
> since october if our git history is true.
>
> Congrats to all for using/developing/maintaining/enjoying this great
> piece of software.
> --
> Francisco Vila. Badajoz (Spain)
> www.paconet.org , www.csmbadajoz.com
>
> ___
> lilypond-devel mailing list
> lilypond-de...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel



-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

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

Re: Development and Stable version on Mac

[Daniel Berjón Díez]

> Am 31.10.2014 20:19, schrieb Br. Samuel Springuel:
>>
>> What's the simplest way to get both the development and stable version of
>> lilypond running on a Mac from a user perspective?  I already have the
>> stable version installed from the downloadable binaries and don't want to
>> mess with this but also want to test some changes that have taken place in
>> the development version to see if they solve some issues I've been having
>> (some chatter on the list makes me think they might). I'm not planning on
>> contributing modifications to the source as I'm too busy with other
>> projects.

I'd say the easiest way to do this is using homebrew (brew.sh). You
can install both regular and devel branches of lilypond ("brew install
lilypond" or "brew install --devel lilypond"), each in its own
directory. Then, you can either use them in its own directory or use
"brew switch lilypond " to create the correct symlinks
automatically. I don't use the devel branch, so I cannot tell you if
whether it's broken or not, but it's so easy it's worth a try. ;)

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

Re: Beaming until barline

[Gilberto Agostinho]

David Nalesnik-2 wrote
> By the way, part of this can be made a little prettier:

Thanks David, I also appreciate slim and pretty codes :)

Take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Beaming-until-barline-tp167937p168235.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: Fortran library for generating LilyPond code

[Gilberto Agostinho]

Hi Urs,

Thanks for your reply, I really appreciate it. 


Urs Liska wrote
> It's perfectly reasonable to go that route. There are contexts where it 
> may be preferable to have everything encapsulated in a LilyPond/Scheme 
> "application" while in others it is better to have generated .ly files 
> as a *persistent* intermediate state.

Indeed, when you want to create a persistent state that can be tweaked, this
approach of mine is quite handy. But also I find it much easier to deal with
compositional aspects in a separate code than my final scores.

In case you or anyway is interested, here are some samples of my own work
generated using this Fortran library (and as I mentioned before, there was
absolutely no tweaking or corrections after the program created the final
.ly file).

http://s7.postimg.org/s83fd887f/Palimpsest_for_chamber_orchestra.png
http://s28.postimg.org/4gcfx408d/Tete_a_tete_for_two_marimbas.png
http://s17.postimg.org/ijhpf8zwv/On_the_Origin_of_Pitches_for_solo_vibraphone.png
http://s21.postimg.org/fkcgbwvif/Composition_for_Nine_Sounds_for_solo_percussion.png
http://s30.postimg.org/5kzu3xz5t/Three_for_flute_alto_flute_and_clarinet.png


Urs Liska wrote
> So it's of course a good addition to have a library for an additional 
> language available.

I have been promising myself to properly learn Python and to convert this
library, but I just can't find the time. If this ever happen, then I'll also
upload a Python version of this library, which would be much more useful to
other users (I am one of the last three people in this world who can still
speak Fortran ;) )


Urs Liska wrote
> Ehm, I'm sorry and embarrassed that we still have your post dangling 
> somewhere. Maybe this "publication" is an appropriate opportunity to 
> pick that up ...

No worries about it, Urs. I guess that if would still be interested in
something similar to that post, probably the best would be to rewrite the
whole thing. I think I could do much better today :)

Thanks again for the encouraging words, and take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fortran-library-for-generating-LilyPond-code-tp168112p168234.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: Unicode Font Issues

[Jean-Luc Chevillard]

My failure with the Tamil script was also on Windows.

It is obviously time for me to switch to Linux :-)

-- Jean-Luc Chevillard (Paris)


"https://univ-paris-diderot.academia.edu/JeanLucChevillard";

"https://plus.google.com/u/0/113653379205101980081/posts/p/pub";

"https://twitter.com/JLC1956";


On 01/11/2014 18:50, Werner LEMBERG wrote:

I tried to use unicode fonts for the lyrics. While the fonts show
perfectly well in the input file, the output is not correct. Is
there a workaround?

If the bottom one is correct then it is rendering correctly on
Ubuntu 14.04, lilypond 2.19.3.

... This means we are again bitten by the ligature bug on Windows...


 Werner

___
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: Unicode Font Issues

[Werner LEMBERG]

>> I tried to use unicode fonts for the lyrics. While the fonts show
>> perfectly well in the input file, the output is not correct. Is
>> there a workaround?
> 
> If the bottom one is correct then it is rendering correctly on
> Ubuntu 14.04, lilypond 2.19.3.

... This means we are again bitten by the ligature bug on Windows...


Werner

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

Re: Happy 18th birthday, LilyPond

[Francisco Vila]

2014-11-01 11:43 GMT+01:00 David Kastrup :
> So it's more like 19 since July for (work on?) version 1.0.1 though our
> git history seems rather messed up.  Just out of interest: where did you
> get that 18-year number?

You guessed it: I used the most naïve method possible. I moved the
scroll bar in gitk (without --all) at the bottom and there it was:

commit 4f4ad24a3bfeb77cfd0ecca104319607bfd28a63
Author: Han-Wen Nienhuys 
Date:   Wed Oct 9 14:04:46 1996 +0100

Initial.

-- 
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: Unicode Font Issues

[Bric]

On 10/31/2014 07:29 AM, Jay Vara wrote:
I tried to use unicode fonts for the lyrics. While the fonts show 
perfectly well in the input file, the output is not correct. Is there 
a workaround?


%%
\version "2.18.2"

 \score {

   \new Staff \relative c' {

  <<

  {c2 d4e f2 g a b c}

   \new Lyrics \lyricmode { ಸಾ ರಿ ಗಾ ಮಾ ಪಾ ದಾ ನೀ ಸಾ }

  >>

   }

}

%%%


Here is what it prints and also what it should print.


Inline image 1





If the bottom one is correct then it is rendering correctly on Ubuntu 
14.04, lilypond 2.19.3.

see attached jpeg.



___
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: Happy 18th birthday, LilyPond

[Pierre Perol-Schneider]

Happy brithday ! :)

2014-11-01 12:07 GMT+01:00 David Kastrup :


> Well, one gets the idea: this looks more like conception/pregnancy than
> the actual birth of LilyPond.  So maybe the Oct 1996 date is indeed the
> point to celebrate.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Development and Stable version on Mac

[Urs Liska]

I assume that this works the same (or at least reasonably similar) on 
Linux and Mac:


- install one version (as you have) on the user level (i.e. not as root)
- *move* the whole installation directory from ~/lilypond to somewhere 
else, e.g. ~/lilyponds/2.18.2 (the last part is an arbitrary name, but I 
think the version number is a good idea).

[arbitrary step to check:
- create a symlink from ~/lilypond to the new location
]
-install the second version in the user's home directory (the first 
version has been moved out of the way)
- move the new installation directoryy from ~/lilypond to e.g. 
~/lilyponds/2.19.16


Now you can set a symlink to point from ~/lilypond to either of the 
directories where you moved the install dirs to. This way you can easily 
switch between the two versions.


Instead of juggling wiht the symlink you could also create two wrapper 
scripts that simply call the right executable.


I don't know if that works out exactly the same on Mac, but I think the 
general idea should work.


If you are using Frescobaldi, you can simply register an arbitrary 
number of LilyPond versions in the Preferences, though.


HTH
Urs

Am 31.10.2014 20:19, schrieb Br. Samuel Springuel:
What's the simplest way to get both the development and stable version 
of lilypond running on a Mac from a user perspective?  I already have 
the stable version installed from the downloadable binaries and don't 
want to mess with this but also want to test some changes that have 
taken place in the development version to see if they solve some 
issues I've been having (some chatter on the list makes me think they 
might). I'm not planning on contributing modifications to the source 
as I'm too busy with other projects.



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

Re: Fortran library for generating LilyPond code

[Urs Liska]

Am 31.10.2014 03:47, schrieb Gilberto Agostinho:

Hello LilyPonders,

I am really not sure this will be of any use for anyone else besides myself,
but here we go: today I finally finished cleaning the code of my Fortran
library that I use to generate LilyPond code algorithmically, and I uploaded
it to gitHub together with some few examples. I plan to add some more
complex examples and some clear instructions as soon as I have some free
time. Below is the link to the repository:

https://github.com/gilbertohasnofb/lilypondLibrary


This is a good thing to have done, thank you.



What this library does: basically you can write a code in Fortran and it
outputs a perfectly looking .ly file. So let's say you want to create a
staff with a middle C note, you could simply use:

[...]
call STAFF()
call NOTE(60,"4")
call END_STAFF()
[...]

My personal use of this library is to produce algorithmic music. I have been
using these types of techniques for the past year, including an orchestral
work completely generated by the computer (i.e., absolutely NO changes or
corrections or any input from me). I am pretty certain that all this could
be achieved by programming a whole piece using Scheme inside a .LY file, but
that is really beyond me, so I took an alternative route: /if the mountain
won't come to Fortran, then Fortran must go to the mountain/.


It's perfectly reasonable to go that route. There are contexts where it 
may be preferable to have everything encapsulated in a LilyPond/Scheme 
"application" while in others it is better to have generated .ly files 
as a *persistent* intermediate state. For example if there was the 
chance you might want to be able to post-process the composition. Or if 
you want to have a score that you can fine-tune for better output.


So it's of course a good addition to have a library for an additional 
language available.



If anyone is interested in the subject, feel free to contact me both here in
our forum or by mail.


Ehm, I'm sorry and embarrassed that we still have your post dangling 
somewhere. Maybe this "publication" is an appropriate opportunity to 
pick that up ...


Best
Urs



Take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fortran-library-for-generating-LilyPond-code-tp168112.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

Re: Beaming until barline

[David Nalesnik]

On Fri, Oct 31, 2014 at 6:32 PM, Gilberto Agostinho <
gilbertohasn...@gmail.com> wrote:

> David Nalesnik-2 wrote
> > The attached file is what I come up with.
>
> Absolutely fantastic, David! Thanks really a lot, this function is
> looking really great!
>

Glad I can help!

By the way, part of this can be made a little prettier:


#(define (calc-beam-right segments)
   (fold
(lambda (elem prev)
  (if (> (cddr (cadr elem)) prev)
  (cddr (cadr elem))
  prev))
0
segments))

could be:

#(define (calc-beam-right segments)
   (fold
(lambda (elem prev)
  (max (cddr (cadr elem)) prev))
0
segments))

%%

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

Re: A pause in 3/4 measure

[Thomas Morley]

2014-11-01 5:21 GMT+01:00 Dr. Bernhard Kleine :
> Yes it does. I prefer the d1*3/4\rest since it is the least letters to write. 
> I may substitute it in the final version.

Using d1*3/4\rest has a draw-back:
The rest will change it's position, if \transpose is used.

-Harm

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

Re: Happy 18th birthday, LilyPond

[David Kastrup]

Federico Bruni  writes:

> Il giorno sab 1 nov 2014 alle 11:43, David Kastrup  ha
> scritto:
>> So it's more like 19 since July for (work on?) version 1.0.1 though
>> our
>> git history seems rather messed up.  Just out of interest: where did
>> you
>> get that 18-year number?
>
> probably he didn't use the --all
>
> $ git log --date-order --reverse
> commit 4f4ad24a3bfeb77cfd0ecca104319607bfd28a63
> Author: Han-Wen Nienhuys 
> Date: Wed Oct 9 14:04:46 1996 +0100
>
>Initial.
>
> commit 675bd3e6ea001c3af033b51a6e2eeab6a5809e86
> Author: Han-Wen Nienhuys 
> Date: Wed Oct 9 14:04:47 1996 +0200
>
>release: 0.0.1
>
> commit 727cdcbadf23c1986b0aed547aa645c9813f351b
> Author: Han-Wen Nienhuys 
> Date: Tue Oct 22 22:09:43 1996 +0200
>
>release: 0.0.2

So according to our Git history, lilypond-1.0.1 is on record more than a
year before 0.0.1.

That's – interesting.

More interesting is to add --source.  That would indicate that the early
commits are reachable through refs/tags/release/1.7.25:

commit c4823afaaa48ef634ed9a2f6ce0441c1c0f894d2
Merge: af31352 4b2ad63
Author: janneke 
Date:   Fri Jul 18 00:04:55 2003 +

This commit was manufactured by cvs2svn to create tag 'lilypond_1_7_25'.

Now why is that commit/branch not in our normal history?

What _is_ this history?

git log --stat --all --date-order --reverse --source |head -400 >/tmp/hist

commit 0ff96d5d41379dbb968507fd848642da518dc50b refs/tags/release/1.7.25
Author: fred 
Date:   Tue Jul 18 00:23:16 1995 +

lilypond-1.0.1

 intl/gettext.h | 105 +
 1 file changed, 105 insertions(+)

commit 93d1d90d4645fc0f64ae310e0df224f00228ee78 refs/tags/release/1.7.25
Author: fred 
Date:   Thu Sep 21 11:20:44 1995 +

lilypond-1.0.1

 intl/intl-compat.c | 76 ++
 1 file changed, 76 insertions(+)

commit c369b62fc955f44df7464709d9b8ccd6eaf5b112 refs/tags/release/1.7.25
Author: fred 
Date:   Wed Sep 27 00:42:09 1995 +

lilypond-1.0.1

 intl/dgettext.c | 59 +
 1 file changed, 59 insertions(+)

commit f3e3a164f40ca6f48261a23c7d4f8036ba9c8e79 refs/tags/release/1.7.25
Author: fred 
Date:   Wed Sep 27 00:55:11 1995 +

lilypond-1.0.1

 intl/textdomain.c | 97 +++
 1 file changed, 97 insertions(+)

commit 269f694c15d9d7eee4d6a9cb74ad3b46a29a0555 refs/tags/release/1.7.25
Author: fred 
Date:   Wed Sep 27 20:14:38 1995 +

lilypond-1.0.1

 intl/bindtextdom.c | 172 +
 1 file changed, 172 insertions(+)

commit b1a9a734bf98c6dd15f84d7ec9541c71bd92a34c refs/tags/release/1.7.25
Author: fred 
Date:   Thu Nov 2 17:40:31 1995 +

lilypond-1.0.1

 intl/gettext.c | 70 ++
 1 file changed, 70 insertions(+)

commit 3934c1ff38595198aa8f6dea24b5794e035e5fa5 refs/tags/release/1.7.25
Author: fred 
Date:   Sun Nov 5 12:24:30 1995 +

lilypond-1.0.1

 intl/loadmsgcat.c | 191 ++
 1 file changed, 191 insertions(+)

commit 11d3a2fd4403b3f6b9c927df4ff75c69d2b49d6c refs/tags/release/1.7.25
Author: fred 
Date:   Tue Nov 7 14:21:04 1995 +

lilypond-1.0.1

 intl/finddomain.c | 503 ++
 1 file changed, 503 insertions(+)

commit c41f9e6a811fcaf2a0a27d41146b72f42e536738 refs/tags/release/1.7.25
Author: fred 
Date:   Sun Nov 12 12:41:39 1995 +

lilypond-1.0.1

 intl/gettextP.h | 79 +
 1 file changed, 79 insertions(+)

commit 6307b0b9806d4acabb4def1090d02c1fa118b143 refs/tags/release/1.7.25
Author: fred 
Date:   Mon Nov 20 16:20:57 1995 +

lilypond-1.0.1

 intl/localealias.c | 317 +
 1 file changed, 317 insertions(+)

commit dcaf504442744419880660b2a1102bdcd9d63fb4 refs/tags/release/1.7.25
Author: fred 
Date:   Thu Nov 23 01:45:24 1995 +

lilypond-1.0.1

 intl/linux-msg.sed | 100 +++
 intl/po2tbl.sed.in | 102 
 intl/xopen-msg.sed | 104 +
 3 files changed, 306 insertions(+)

commit 56d2b082a3ff1d62bd6d339c2f4a57a7489cf4ea refs/tags/release/1.7.25
Author: fred 
Date:   Sat Nov 25 02:34:41 1995 +

lilypond-1.0.1

 intl/libgettext.h | 177 ++
 1 file changed, 177 insertions(+)

commit e0e03f14a6182005211c27c977c0fd33cb6c30be refs/tags/release/1.7.25
Author: fred 
Date:   Sat Nov 25 11:30:40 1995 +

lilypond-1.0.1

 intl/dcgettext.c | 522 +++
 1 file changed, 522 insertions(+)

commit ee940257d9d4adc36868ba83243ab20f91e84b34 refs/

Re: Happy 18th birthday, LilyPond

[Federico Bruni]

Il giorno sab 1 nov 2014 alle 11:43, David Kastrup  ha 
scritto:
So it's more like 19 since July for (work on?) version 1.0.1 though 
our
git history seems rather messed up.  Just out of interest: where did 
you

get that 18-year number?


probably he didn't use the --all

$ git log --date-order --reverse
commit 4f4ad24a3bfeb77cfd0ecca104319607bfd28a63
Author: Han-Wen Nienhuys 
Date: Wed Oct 9 14:04:46 1996 +0100

   Initial.

commit 675bd3e6ea001c3af033b51a6e2eeab6a5809e86
Author: Han-Wen Nienhuys 
Date: Wed Oct 9 14:04:47 1996 +0200

   release: 0.0.1

commit 727cdcbadf23c1986b0aed547aa645c9813f351b
Author: Han-Wen Nienhuys 
Date: Tue Oct 22 22:09:43 1996 +0200

   release: 0.0.2


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

Re: Happy 18th birthday, LilyPond

[David Kastrup]

Francisco Vila  writes:

> Sorry for the cross-posting. Just a short note to say LIlyPond is 18
> since october if our git history is true.
>
> Congrats to all for using/developing/maintaining/enjoying this great
> piece of software.

git log --all --date-order --reverse

starts with the following here:

commit 0ff96d5d41379dbb968507fd848642da518dc50b
Author: fred 
Date:   Tue Jul 18 00:23:16 1995 +

lilypond-1.0.1

commit 93d1d90d4645fc0f64ae310e0df224f00228ee78
Author: fred 
Date:   Thu Sep 21 11:20:44 1995 +

lilypond-1.0.1

commit c369b62fc955f44df7464709d9b8ccd6eaf5b112
Author: fred 
Date:   Wed Sep 27 00:42:09 1995 +

lilypond-1.0.1

commit f3e3a164f40ca6f48261a23c7d4f8036ba9c8e79
Author: fred 
Date:   Wed Sep 27 00:55:11 1995 +

lilypond-1.0.1

commit 269f694c15d9d7eee4d6a9cb74ad3b46a29a0555
Author: fred 
Date:   Wed Sep 27 20:14:38 1995 +

lilypond-1.0.1


So it's more like 19 since July for (work on?) version 1.0.1 though our
git history seems rather messed up.  Just out of interest: where did you
get that 18-year number?

-- 
David Kastrup

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

Happy 18th birthday, LilyPond

[Francisco Vila]

Sorry for the cross-posting. Just a short note to say LIlyPond is 18
since october if our git history is true.

Congrats to all for using/developing/maintaining/enjoying this great
piece of software.
-- 
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: Beaming until barline

[Pierre Perol-Schneider]

Hi David,

2014-10-31 20:39 GMT+01:00 David Nalesnik :


> You could scale the stencil.  That way you wouldn't need to reconstruct
> the beam from what you find in 'beaming.
>

But of course!  Thanks much David!
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Multiple score scenario

[Philippe Massart]

Hello,

For me, it *is* the most logical way (I sometime use it in a single piece, when 
transposition leads to overcomplicated tonality).

But you could try to play with tags; I don't use them, but I think it's a 
solution to call only a portion of a variable.

http://lilypond.org/doc/v2.18/Documentation/notation/different-editions-from-one-source#using-tags

Philippe

> Le 1 nov. 2014 à 04:16, Jon Arnold  a écrit :
> 
> Hi -
> 
> I think I have a unique scenario and am trying to figure out the best way 
> to move forward.
> 
> I am working on an edition of Bach's Jesu Meine Freude, and will be doing 
> at least three different editions:
> 
> 1) choral scores of individual mvts
> 2) book of choral scores
> 3) book of string parts which double voices (soprano=vln, tenor=vla, etc.)
> 
> I have each movement in a file (jesu1.ly, jesu2.ly) and have the staff 
> layout stored in a variable so that I can call it on the individual 
> movement and the book without getting voice variables confused between 
> movements.
> 
> So, my book file looks like this: 
> 
> \include "jesu1.ly"
> \include "jesu2.ly"
> 
> \book {
>  \score {
>\jesuOneScore
>\header { piece = "Mvt. I" }
>\layout { }
>  }
>  %etc. etc.
> 
> The problem is the instrumental parts. How can I call one voice from one 
> particular file? I tried putting the \include command in each bookpart, but 
> that tries to pull the whole score for some reason.
> 
> The only solution that I can think of is to name each voice and lyric 
> variable with a movement (sopranoNotesOne, sopranoLyricsOne), but I'm 
> hoping there is a more logical solution.
> 
> Thanks so much for any help!
> 
> Jon
> 
> 
> ___
> 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