Re: The LilyPond Report: a new weekly opinion column about Lily's world

[Frédéric Moinard]

Valentin Villenave a écrit :

Hi everybody,


(...)


Its sole purpose is to be pleasant to read, entertaining -- and to
make LilyPond look sexy. It's primarily intended for newbies,


and it works !! ;)

--
Regards,

  Frédéric Moinard

--
ps: and nice, just after reading gmane.comp.web.spip.user/dev/zone !



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

Re: minimumVerticalExtent & minimum-Y-extent

[Mats Bengtsson]

Frédéric Moinard wrote:

Hi,

I'm beginning with 2.10: 3 voices + verses, and I'd like to keep the 
default distance between music and verse 1 but a shorter vertical 
spacing between the next lines of lyrics.


I found that
\layout  {
  \context {
\Lyrics
minimumVerticalExtent = #'(0 . 0)
  }
}

didn't do anything... but that
That's correct. This syntax was removed in version 2.7.14. If you have 
it an old .ly file,
and update it using convert-ly, then you should automatically get the 
new relevant syntax

(which you use below).


\layout  {
  \context {
\Lyrics
  \override VerticalAxisGroup #'minimum-Y-extent = #'(0 . 0)

  }
}

was 'working'.

Yes, but as you have seen, it redefines all Lyric contexts in the score.


Now, how do I keep the 'above default spacing' for the first verse?
To do settings for only one specific instantiation of a context, use the 
\with construct:
\new Lyrics \with {\override VerticalAxisGroup #'minimum-Y-extent = #'(0 
. 0) }

 { Here comes the ly -- rics }

   /Mats


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

Re: \parenthesize ??

[Mats Bengtsson]

Waiting for 2.11.44, you can still use \parenthesize the same way as in 
earlier versions,

namely for notes within a chord:

 c2 <\parenthesize d>
 c2 <\parenthesize c \parenthesize e \parenthesize g>

  /Mats

Graham Percival wrote:

It only works on 2.11.44 and higher (not released).  You got caught in a
very rare moment.

Cheers,
- Graham


On Tue, 8 Apr 2008 00:28:36 -0300
luis jure <[EMAIL PROTECTED]> wrote:

  

in the manual i find: "Objects may be parenthesized by prefixing
\parenthesize to the music event."  but when i compile the example in
the manual i get no parenthesis. the following code gives the output
attached:

\version "2.11.43"

\layout {
ragged-right = ##t
}
	\relative c'' { 
		c2 \parenthesize d

c2 \parenthesize 
}


i tried with both 2.11.42 and 2.11.43. is \parenthesize not working,
or am i missing something?

best,

lj




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


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



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

Re: The LilyPond Report: a new weekly opinion column about Lily's world

[Valentin Villenave]

2008/4/7 Karl Hammar <[EMAIL PROTECTED]>:

>  Hmm, I don't see them as unusual, I see it more like that I bend
>  lilypond-book to the way I am used to when developing program and using
>  latex.

Yes, I meant "unusual to me" :)

I should have said "ambitious" rather than "unusual". If I understand
correctly, you prefer to modify existing tools instead of just adding
extra macros, layers, supersets etc (such as what Reinhold did with
OrchestralLily). That's an approach I found interesting, and I wanted
to emphasize this difference.

Anyway, I added a link to your explanations as a footnote in the article.
http://valentin.villenave.info/spip.php?article62#nb3

PostScript Blue Book: thanks. I added your link in the article.

About production vs unstability: thanks a lot for these explanations.
I will quote you (if you don't mind) on next week's issue, as a
follow-up to this week's article.


Frédéric: thanks :-) You may know what the spip CMS means to us French
Free people...

Cheers,
Valentin


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

Re: lilypond-book not honoring --psfonts?

[Karl Hammar]

Han-Wen:
> The recommended way to do the fonts is to have them included in
> separate .eps files.  If file size is a concern, you can use
> -dgs-load-fonts. The result will be that you have to go through a PS
> -> PDF step before sending to the printer, though.

I have forgot the exact problems, but I have had som issues sending pdf 
to the printer.

> (I can recommend pdflatex anyway; the results are usually more predictable.)

What issues have you seen?

Regards,
/karl




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

Re: The LilyPond Report: a new weekly opinion column about Lily's world

[Karl Hammar]

Villenave:
> About production vs unstability: thanks a lot for these explanations.
> I will quote you (if you don't mind) on next week's issue, as a
> follow-up to this week's article.
...

I don't mind.

Regards,
/Karl




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

Re: GDP: Reorganisation of NR 2 - Final call for comments

[Trevor Daniels]

Karl Hammar wrote:


Trevor:
Would "Ancient and modern from one source" cover it.  I can't think of 
anything shorter.


Anyone else any better suggestions?


Why not "Best practices" or the like.


I was trying to capture the essence of the subject matter, which
is printing both ancient and modern music within a single .ly file
using just one set of music notation.  The problem with short 
general headings, attractive as they are, is ensuring uniqueness

throughout the manual :(   Thanks anyway.


/Karl

Trevor D


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

Re: \parenthesize ??

[luis jure]

El Tue, 08 Apr 2008 10:13:50 +0200
Mats Bengtsson <[EMAIL PROTECTED]> escribió:

> Waiting for 2.11.44, you can still use \parenthesize the same way as
> in earlier versions, namely for notes within a chord:

yes, this works! 

thank you, and waiting for 2.11.44...


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

Re: GDP: Reorganisation of NR 2 - Final call for comments

[Trevor Daniels]

Karl Hammar wrote

Till:

8.5 Transcription of ancient music


Why not call it "Editing" or "Making an edition", but transcription is 
also fine.


I think we'll stick with "Transcription" - it seems closer to the action
being performed by those working with ancient music, who usually
want to preserve the original as faithfully as possible, rather than
editing it.


5.2 Incipits and Mensurstriche-layout


Theese are different beasts, should they not be in seperate sections.


I'm out of my depth here.  Anyone else have an opinion?
I'm quite happy to make this into two sections if there is
something different to write about each of them.


5.4 Musica ficta
5.4.1 Suggested accidentals (new) (2.8.4) 


This has already been changed to just

5.4 Musica ficta accidentals
 (containing just the current text from 2.8.4)

Instead of Musica ficta, which are notes not in the regular hexachords, 
I suggests a section for editorial markings. Which includes suggested 
accidentals, slurs, different rhythmic (like french barock) 
interpretation. 


Happy to add Editorial markings for ancient music as an additional
section, incorporating 5.4, if someone volunteers to send me suitable 
text for it, but I can't write this stuff myself :(  


Regards,
/Karl

Trevor D



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

Re: GDP: Reorganisation of NR 2 - Final call for comments

[Karl Hammar]

> Karl Hammar wrote
> > Till:
> >> 8.5 Transcription of ancient music
> > 
> > Why not call it "Editing" or "Making an edition", but transcription is 
> > also fine.
> 
> I think we'll stick with "Transcription" - it seems closer to the action
> being performed by those working with ancient music, who usually
> want to preserve the original as faithfully as possible, rather than
> editing it.

Ohh, I might have misunderstood the word (transcription) but I thought 
it ment converting to modern notation. Also a "critical edition" is to 
preserve the original (or rather the manuscripts, the sources, the
original meaning the thing in the composers head) as faithfully as
possible with comments about dubious places, differences between manuscripts,
etc (but usually still in modern notation) and transcription is not 
that strict.

So, there is two differnt things here,

1, notation imitating historic sources visually in some way
   (which also apply to the barock to the romantic period, e.g. the 
   1900th cent. 4th rest)
2, making it in modern notation

In both cases you could want to add some notes or explanations, this 
note should be a fis even if it isn't in the source, ... -- editorial 
markings.

But ok, lets stick with transcription.

> >> 5.2 Incipits and Mensurstriche-layout
> > 
> > Theese are different beasts, should they not be in seperate sections.
> 
> I'm out of my depth here.  Anyone else have an opinion?
> I'm quite happy to make this into two sections if there is
> something different to write about each of them.

The incipit is an pre part showing the clefs, mensuration signs, the 
first few notes etc. so we can get a fealing of the transcriptions
source, but still read on in modern notation.

Mensurstriche is a way to include (or a substitute for) "bar lines"
for sources that didn't contain them, but without splitting the notes
and/or rests that are "syncopated" over the bar lines the editor wants.

> >> 5.4 Musica ficta
> >> 5.4.1 Suggested accidentals (new) (2.8.4) 
> 
> This has already been changed to just
> 
> 5.4 Musica ficta accidentals
>   (containing just the current text from 2.8.4)
> 
> > Instead of Musica ficta, which are notes not in the regular hexachords, 
> > I suggests a section for editorial markings. Which includes suggested 
> > accidentals, slurs, different rhythmic (like french barock) 
> > interpretation. 
> 
> Happy to add Editorial markings for ancient music as an additional
> section, incorporating 5.4, if someone volunteers to send me suitable 
> text for it, but I can't write this stuff myself :(  

I would be happy to help, but I'm kind of busy. Please hand me 
something to work on in that case.

Regards,
/Karl




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

Re: GDP: Reorganisation of NR 2 - Final call for comments

[Trevor Daniels]

Karl Hammar wrote

Trevor Daniels wrote

Karl Hammar wrote
> Till:
>> 8.5 Transcription of ancient music
>
> Why not call it "Editing" or "Making an edition", but transcription is
> also fine.

I think we'll stick with "Transcription" - it seems closer to the action
being performed by those working with ancient music, who usually
want to preserve the original as faithfully as possible, rather than
editing it.


Ohh, I might have misunderstood the word (transcription) but I thought
it ment converting to modern notation.


Maybe "transliteration"  is closer to what I meant, although "transcription"
means changing the medium while preserving the content.  It was "editing"
I didn't like - which implies a change to the original content, rather than
its representation.


Also a "critical edition" is to
preserve the original (or rather the manuscripts, the sources, the
original meaning the thing in the composers head) as faithfully as
possible with comments about dubious places, differences between 
manuscripts,

etc (but usually still in modern notation) and transcription is not
that strict.

So, there is two differnt things here,

1, notation imitating historic sources visually in some way
  (which also apply to the barock to the romantic period, e.g. the
  1900th cent. 4th rest)
2, making it in modern notation

In both cases you could want to add some notes or explanations, this
note should be a fis even if it isn't in the source, ... -- editorial
markings.


Ahh - right! - that's what you mean by editing.  (When I "edited" the
proceedings of a conference it consisted mainly of deleting half the
contents of the submitted papers to meet the strict length guidelines :)


But ok, lets stick with transcription.


It's probably as good as anything.


>> 5.2 Incipits and Mensurstriche-layout
>
> Theese are different beasts, should they not be in seperate sections.


The incipit is an pre part showing the clefs, mensuration signs, the
first few notes etc. so we can get a fealing of the transcriptions
source, but still read on in modern notation.

Mensurstriche is a way to include (or a substitute for) "bar lines"
for sources that didn't contain them, but without splitting the notes
and/or rests that are "syncopated" over the bar lines the editor wants.


OK, thanks. I'll split that section into two


>> 5.4 Musica ficta
>> 5.4.1 Suggested accidentals (new) (2.8.4)

This has already been changed to just

5.4 Musica ficta accidentals
  (containing just the current text from 2.8.4)

> Instead of Musica ficta, which are notes not in the regular hexachords,
> I suggests a section for editorial markings. Which includes suggested
> accidentals, slurs, different rhythmic (like french barock)
> interpretation.

Happy to add Editorial markings for ancient music as an additional
section, incorporating 5.4, if someone volunteers to send me suitable
text for it, but I can't write this stuff myself :(


I would be happy to help, but I'm kind of busy. Please hand me
something to work on in that case.


Thanks.  Might not be for a week or two, as all NR 2 will have to
be re-arranged first.

So in Draft 8 of NR 2 headings let's change to

  .5 Transcribing ancient music (new)
.1 Ancient and modern from one source
   [Here among others the snippets about reducing note length]
.2 Incipits (new)
   (clefs, mensuration signs etc from lsr and -user)
.3 Mensurstriche-layout (new)
   (lsr and -user)
.4 Transcribing Gregorian chant (new)
   (extract from 1.6.1.1)
  .6 Editorial markings
.1 Suggested accidentals
   (2.8.4)
.2 Suggested slurs (new)
   (new - KH?)
.3 Suggested rhythmic interpretation (new)
   (new - KH)

How does this look?


/Karl
Trevor D 




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

vertical text

[luis jure]

hello list, i'd like to add vertical text after the final bar line,
like in the image attached. i guess i can do that using postscript
code, but i'd like to know if there is a property in LP to control
that. i haven't been able to find one in the manual so far.

best,

lj<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Fonts in LilyPond document

[Bernard Meylan]

Hi,

I search to change the fonts (amost all... =-O  : measure numbers, 
lyrics, titles) in my .ly documents. What is the most simple maneer to do?


Bernard


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

Old LilyPond versions

[Laura Conrad]

In The LilyPond Report #4, Valentin Villenave writes:

   So, what can make you use an old LilyPond version? Is LilyPond
   "moving too fast", as suggested on the Download page? (Honestly,
   I've always seen that as a purely rhetorical question.)
   Is it because of your Linux distribution? Is it a matter of taste?

In my case, it's usually because convert-ly isn't converting something
important.  I was on 2.0.6 until the current version was 2.8, because
there was no way to automatically convert lyrics between 2.0 and 2.4.
(I may have the exact numbers wrong.)  Yes, the manual change was
pretty easy, but I have hundreds of pieces, each of which has a dozen
or so lilypond files, so doing a manual conversion is not trivial.
Even if you manage to script it on the piece level, it still is a
major time investment to run the script and look at the output.

So the "moving too fast" question is not at all rhetorical.  If you're
trying to put together a book, and you have to convert the earlier
pieces several times before you finish transcribing the later pieces,
some people consider that "moving too fast".  Or the developers might
consider that the transcribers are "moving too slow".   

I consider it unfortunate that lily development seems to live on the
bleeding edge of so many programs.  So I currently have a pretty major
project that I can't recompile because I'd have to hand-convert all
the lyrics to run the current version, and I can no longer run the
older version on my relatively current Ubuntu linux system.

The reason I'm currently using 2.10 instead of 2.11, which would
enable me to make more of a contribution to testing current
development, is that I've never managed to convince the developers
that there should be a feature freeze some weeks or months before a
stable release.  I got burned badly having to convert lilypond files
from an odd-numbered version before I could use them on a stable
version once, so now all my production work (which is most of my work)
is on stable versions.

I've once thought I didn't like the look of the newer version as well
as the older version, but once I got used to it, I decided I was
wrong.  (It was when the lyrics font changed sometime before 2.8.)

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139


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

cannot find lilypond icon on my desktop after installation (window xp)

[ming tsang]

I download and installed lilypond_3.10.33-1.mingw.exe

I did not see lilypond icon.   

I tried to execute c:\Program Files\LilyPond\usr\bin\lilypond-windows.exe, but
no lilypond screen displayed.  Is this the right program to execute?



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

Re: braces in the lyrics

[Tim Litwiller]

sorry for replying to myself - I don't see that the frist attempt 
reached the list.


Timothy C Litwiller wrote:
A friend of mine composed a song and we have some similar layouts in 
our Church songbooks

look like this attached braces.jpg

You sing to the start of the chorus on the first line of the first 
verse the return to the second line of the the first verse and
after you get to the choruse the second time then you sing the chorus 
before the second verse starts


He says he could have made it a six verse song as that was how the 
inspiration came, but it gets too long singing the chorus after every 
verse so he combined the verses. He would like a brace after the 
stanza number combining the two lines that make up each verse.

I have this code
leftbrace = \markup { \override #'(font-encoding . fetaBraces) \lookup 
#"brace70" }

rightbrace = \markup { \rotate #180 \leftbrace }

and the LSR has an example of using it - but only to end several 
verses and go to the chorus - not 3 stacked with 2 lyrics lines after 
them.



How would I go about laying this out. I have the notes and a lyrics 
line defined for each line of lyrics liuke they are six verses  but 
every other line doesn't have a set stanza with a number in it.


and second question how do I make the midi it creates play the verse 
twice and then the chorus when it is laid out this way.






First try didn't go thru - I suspect the jpg image blocked it
anyways this is a representation of what i want 
1. | first   -   line of first  verse |

   | second  line of first  verse |

2. | first  -   line of second verse |
   | second line of second verse |

3. | first  -   line of third verse |
   | second line of third verse |

   words of chorus words of chorus



where the 2 | in front of the words of the verse are a { that reaches 
across both lines and at the end of the verse a similar } that lets the 
singer know that they need to return to the second line of the verse 
before going on to the chorus.


I'll try to get the .jpg with the


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

Re: Old LilyPond versions

[Mats Bengtsson]

This is certainly a very important issue. However, for the changes 
between 2.10 and 2.11
(and the coming 2.12), very few affect the actual syntax and convert-ly 
should handle
them very well. Compared to some earlier version upgrades, you should 
expect a very
smooth procedure. The main exception is if you previously have done lots 
of manual adjustments
to handle the vertical positioning of things like bar numbers, 
articulations and text scripts.
Since these now are handled much better by default, the old fixes will 
probably make the

result worse if they remain in a 2.11 score.

I think this points very clearly to the main problem here. Nobody can 
argue that it's a
bad thing that LilyPond 2.11 produces a much nicer result by default. 
Still, this is a
non-compatible change that can cause quite some manual extra work for 
each user
who wants to update all his/her old files. Also, we don't have the 
programming resources

available to maintain a number of backwards compatibility features.

  /Mats

Laura Conrad wrote:

In The LilyPond Report #4, Valentin Villenave writes:

   So, what can make you use an old LilyPond version? Is LilyPond
   "moving too fast", as suggested on the Download page? (Honestly,
   I've always seen that as a purely rhetorical question.)
   Is it because of your Linux distribution? Is it a matter of taste?

In my case, it's usually because convert-ly isn't converting something
important.  I was on 2.0.6 until the current version was 2.8, because
there was no way to automatically convert lyrics between 2.0 and 2.4.
(I may have the exact numbers wrong.)  Yes, the manual change was
pretty easy, but I have hundreds of pieces, each of which has a dozen
or so lilypond files, so doing a manual conversion is not trivial.
Even if you manage to script it on the piece level, it still is a
major time investment to run the script and look at the output.

So the "moving too fast" question is not at all rhetorical.  If you're
trying to put together a book, and you have to convert the earlier
pieces several times before you finish transcribing the later pieces,
some people consider that "moving too fast".  Or the developers might
consider that the transcribers are "moving too slow".   


I consider it unfortunate that lily development seems to live on the
bleeding edge of so many programs.  So I currently have a pretty major
project that I can't recompile because I'd have to hand-convert all
the lyrics to run the current version, and I can no longer run the
older version on my relatively current Ubuntu linux system.

The reason I'm currently using 2.10 instead of 2.11, which would
enable me to make more of a contribution to testing current
development, is that I've never managed to convince the developers
that there should be a feature freeze some weeks or months before a
stable release.  I got burned badly having to convert lilypond files
from an odd-numbered version before I could use them on a stable
version once, so now all my production work (which is most of my work)
is on stable versions.

I've once thought I didn't like the look of the newer version as well
as the older version, but once I got used to it, I decided I was
wrong.  (It was when the lyrics font changed sometime before 2.8.)

  


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



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

Re: vertical text

[Kieren MacMillan]

Hi Luis,


hello list, i'd like to add vertical text after the final bar line,
like in the image attached. i guess i can do that using postscript
code, but i'd like to know if there is a property in LP to control
that. i haven't been able to find one in the manual so far.


The attached snippet works -- there's probably a slightly simpler way  
(by using the #'rotation numbers properly), but I don't know it.


HTH!
Kieren.

%%
\version "2.11.42"
\paper { ragged-right = ##t }

theMark =
{
\once \override Score.RehearsalMark #'rotation = #'(90 0 0)
\once \override Score.RehearsalMark #'extra-offset = #'(11 . -18.5)
	\once \override Score.RehearsalMark #'break-visibility = #begin-of- 
line-invisible

\once \override Score.RehearsalMark #'font-size = #1
\once \override Score.RehearsalMark #'font-shape = #'italic
\mark "Budapest, 1928, VII.-IX."
}

\score
{
\new GrandStaff
<<
\new Staff { c'' r r2 }
\new Staff { c''4 r r2 }
\new Staff { c''4 r r2 }
\new Staff { c''4 \theMark r r2 \bar "|." }
>>
}
%%%


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

Re: Fonts in LilyPond document

[Kieren MacMillan]

Hi Bernard,

to change the fonts (amost all... =-O  : measure numbers, lyrics,  
titles)

in my .ly documents. What is the most simple maneer to do?


See the bottom of the page



HTH!
Kieren.


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

Re: cannot find lilypond icon on my desktop after installation (window xp)

[Tim Litwiller]

Are you thinking that lilypond is a program you open and interactively 
work with?


If that is what you want you will want to download from here.
http://valentin.villenave.info/spip.php?article44
It will give you an editor with an output viewer and a music player 
linked to lilypond  that all work together on windows very well.


Lilypond by it's self is a command line program that processes an input 
file and outputs a "engraving". With lilypondtool that is a pdf, other 
options let it also output midi files and image files.





ming tsang wrote:

I download and installed lilypond_3.10.33-1.mingw.exe

I did not see lilypond icon.   


I tried to execute c:\Program Files\LilyPond\usr\bin\lilypond-windows.exe, but
no lilypond screen displayed.  Is this the right program to execute?



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

  




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

Re: cannot find lilypond icon on my desktop after installation (window xp)

[Mats Bengtsson]

Tim Litwiller wrote:


Lilypond by it's self is a command line program that processes an 
input file and outputs a "engraving". With lilypondtool that is a pdf, 
other options let it also output midi files and image files.


Still, a normal installation on Windows leaves an icon on the desktop. 
Also, if you

open a command prompt and run the command
lilypond-windows -dgui
then you should see the same thing as normally happens when you 
double-click on the
LilyPond icon, namely that the very primitive text editor "LilyPad" is 
opened with a

simple test example file.

No matter if you follow Tim's advice or use your existing solution, 
don't expect to be able
to do anything useful with the program until you have read the Tutorial 
(i actually recommend
you to click on the Documentation link for version 2.11 even if you have 
installed version 2.10
and click on the "Learning Manual" there, since it's been more or less 
completely rewritten and

improved compared to the documentation for version 2.10).

   /Mats




ming tsang wrote:

I download and installed lilypond_3.10.33-1.mingw.exe

I did not see lilypond icon.  
I tried to execute c:\Program 
Files\LilyPond\usr\bin\lilypond-windows.exe, but

no lilypond screen displayed.  Is this the right program to execute?



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

  




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


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



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

Re: Old LilyPond versions

[Valentin Villenave]

2008/4/8 Laura Conrad <[EMAIL PROTECTED]>:

>  In my case, it's usually because convert-ly isn't converting something
>  important.

Thank you very much for these comments. I do think we need to talk
more about this issue.

In my case, I've been working for almost three years on a same
project, always using the latest development version (as I mentioned,
I'm a pure geek). I remember quite well the discussion Nicolas and you
had some time ago:

http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00595.html

I have to say that by using following his advices, I've never
encountered any problem. All my overrides are basically gathered in
one or two files, and I only needed to update these files (I got
trapped when, for instance, 'breaking-symbol was turned into
'breaking-symbols, but since I always keep track of the changelog I
quickly found out what was wrong).

In other words, either you keep using a stable version, either you
keep up, month after month, with all the changes. The latter means a
huge amount of work but it's really exciting :-)

Cheers,
Valentin


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

Re: GDP: Reorganisation of NR 2 - Final call for comments

[Mats Bengtsson]

Mensurstriche is a way to include (or a substitute for) "bar lines"
for sources that didn't contain them, but without splitting the notes
and/or rests that are "syncopated" over the bar lines the editor wants.
  
By the way, is "mensurstriche" the established English term? I have no 
idea, but it might be

an idea to check if this German term also is the best one in English.

  /Mats


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

Re: lilypond-user Digest, Vol 65, Issue 34

[Till Rettig]

Hi

Karl Hammar wrote
  

Trevor Daniels wrote


Karl Hammar wrote
  

Till:


8.5 Transcription of ancient music
  

Why not call it "Editing" or "Making an edition", but transcription is
also fine.


I think we'll stick with "Transcription" - it seems closer to the action
being performed by those working with ancient music, who usually
want to preserve the original as faithfully as possible, rather than
editing it.
  

Ohh, I might have misunderstood the word (transcription) but I thought
it ment converting to modern notation.



Maybe "transliteration"  is closer to what I meant, although "transcription"
means changing the medium while preserving the content.  It was "editing"
I didn't like - which implies a change to the original content, rather than
its representation.
  
I still like transcription, that's what I call an edition with modern 
notes. Well, I agree, its edition and transcription, but still. Or then, 
Transcribing, as it is now.
  

5.2 Incipits and Mensurstriche-layout
  

Theese are different beasts, should they not be in seperate sections.


The incipit is an pre part showing the clefs, mensuration signs, the
first few notes etc. so we can get a fealing of the transcriptions
source, but still read on in modern notation.

Mensurstriche is a way to include (or a substitute for) "bar lines"
for sources that didn't contain them, but without splitting the notes
and/or rests that are "syncopated" over the bar lines the editor wants.



OK, thanks. I'll split that section into two
  
Yes, I also go for that, now, even though I am afraid the mensurstriche 
section will be really short.
  

Instead of Musica ficta, which are notes not in the regular hexachords,
I suggests a section for editorial markings. Which includes suggested
accidentals, slurs, different rhythmic (like french barock)
interpretation.


Happy to add Editorial markings for ancient music as an additional
section, incorporating 5.4, if someone volunteers to send me suitable
text for it, but I can't write this stuff myself :(
  

I would be happy to help, but I'm kind of busy. Please hand me
something to work on in that case.



Thanks.  Might not be for a week or two, as all NR 2 will have to
be re-arranged first.

So in Draft 8 of NR 2 headings let's change to

   .5 Transcribing ancient music (new)
 .1 Ancient and modern from one source
[Here among others the snippets about reducing note length]
 .2 Incipits (new)
(clefs, mensuration signs etc from lsr and -user)
 .3 Mensurstriche-layout (new)
(lsr and -user)
 .4 Transcribing Gregorian chant (new)
(extract from 1.6.1.1)
   .6 Editorial markings
 .1 Suggested accidentals
(2.8.4)
 .2 Suggested slurs (new)
(new - KH?)
 .3 Suggested rhythmic interpretation (new)
(new - KH)

How does this look?
  
I don't know, what these slurs mean, I came up with the following 
editiorial items:


1. annotational accidentals
2. ligature brackets  [I think they should be here, and not together 
with the ligatures]

3. Barock rhythm indication

1 is the same as 6.1, maybe 2 is the same as 6.2 (?), and by the topic 3 
is the same as 6.3 .


Suggested accidentals sounds good, but the others I wouldn't call 
"suggested", since they are about how to interpret the notes, not an 
addition/suggestion by the editor as the accidentals are. So I would go for:


6.2 Brackets indicating ligatures" or "Ligature brackets"
6.3 Rhythmic Barock notation -- or something the like.

Hopefully this doesn't get now too complicated - I guess issues will 
clear up when we are actualy working on that section.


Greetings
Till

  

/Karl

Trevor D 






--

Message: 4
Date: Tue, 8 Apr 2008 10:55:08 -0300
From: luis jure <[EMAIL PROTECTED]>
Subject: vertical text
To: lilypond-user 
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"


hello list, i'd like to add vertical text after the final bar line,
like in the image attached. i guess i can do that using postscript
code, but i'd like to know if there is a property in LP to control
that. i haven't been able to find one in the manual so far.

best,

lj
-- next part --
A non-text attachment was scrubbed...
Name: bartok.png
Type: image/png
Size: 15125 bytes
Desc: not available
Url : 
http://lists.gnu.org/pipermail/lilypond-user/attachments/20080408/fdf05186/bartok.png

--

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


End of lilypond-user Digest, Vol 65, Issue 34
*

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

Fw: GDP: Reorganisation of NR 2 - Final call for comments

[Trevor Daniels]

Kurt

What's your view on this?

Trevor
- Original Message - 
From: "Mats Bengtsson" <[EMAIL PROTECTED]>

To: 
Sent: Tuesday, April 08, 2008 4:48 PM
Subject: Re: GDP: Reorganisation of NR 2 - Final call for comments








Mensurstriche is a way to include (or a substitute for) "bar lines"
for sources that didn't contain them, but without splitting the notes
and/or rests that are "syncopated" over the bar lines the editor wants.
  
By the way, is "mensurstriche" the established English term? I have no 
idea, but it might be

an idea to check if this German term also is the best one in English.

  /Mats


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




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

Re: minimumVerticalExtent & minimum-Y-extent

[Frédéric Moinard]

Hi,

Mats Bengtsson a écrit :



Frédéric Moinard wrote:

Hi,

I'm beginning with 2.10: 3 voices + verses, and I'd like to keep the 
default distance between music and verse 1 but a shorter vertical 
spacing between the next lines of lyrics.

(...)

That's correct. This syntax was removed in version 2.7.14. If you have 
it an old .ly file,


That's right...


and update it using convert-ly,  then you should automatically get the
new relevant syntax
(which you use below).

(...))

To do settings for only one specific instantiation of a context, use the 
\with construct:
\new Lyrics \with {\override VerticalAxisGroup #'minimum-Y-extent = #'(0 
. 0) }

 { Here comes the ly -- rics }


Many thanks... I have to do some more rtfm :)

--
Regards,

   FM



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

Metronome marks

[Matthias Loitsch]

Hi!

I'm new to this list, and quite new to lilypond too.

I'm trying to change the tempo in a song, and I can't find how to do so...

What I want to do, is not a normal metronome tempo change, but I want a 
triplet to become a quarter note.

I found how to set the tempo with a metronome marking (\tempo 4=120), and I 
found the syntax to display an eigth note becoming a quarter note:
\markup {
   (
   \smaller \general-align #Y #DOWN \note #"8" #1
   =
   \smaller \general-align #Y #DOWN \note #"4" #1
   ) }


But how can I use this with a triplet? I tried \note #"12" and \note #"4/3" 
but they both don't work...

Is there a way to get a triplet with \note ? Or do I need a completely 
different approach?



Thank you in advance,
Matthias



-- 
Matthias Loitsch

http://www.youtube.com/watch?v=yAUYaweNQME


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

Re: Old LilyPond versions

[Laura Conrad]

> "Graham" == Graham Percival <[EMAIL PROTECTED]> writes:

Graham> On Tue, 8 Apr 2008 17:37:16 +0200
Graham> "Valentin Villenave" <[EMAIL PROTECTED]> wrote:

>> Thank you very much for these comments. I do think we need to talk
>> more about this issue.

Graham> Oh, has it been six months already?  ... yeah, I guess it has.

Graham> No, we most certainly do *not* need to bloody talk about this
Graham> issue.  We "talk" about it approximately twice a year. 

I am aware that all the issues I raised in my email are things I've
said before.  I said them again because Valentin asked.  He's an
important and involved member of the lilypond community, and if he
isn't aware of the problems, many other readers of the list probably
aren't either.

All mailing lists have recurring topics -- the membership changes, and
the focus of individual members changes, and sometimes there are new
perspectives on the old topics.  If you don't like reading the old
arguments, you have a delete button.

Graham> - a certain grumpy doc writer points out that if you read the
Graham>   instructions in
Graham>   LM 5.1 Suggestions for writing LilyPond files
Graham>   then you can avoid almost all these problems.

The grumpy doc writer has said many times that he knows nothing about
vocal music.  None of the suggestions in 5.1 is going to change the
fact that manual conversion is necessary for all vocal music
transcribed before 2.4.

And in any case, drawing the attention of new members of the list who
are struggling to convert old projects to LM5.1 is one of the benefits
of rehashing the old topic.

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139


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

Re: Old LilyPond versions

[Graham Percival]

On Tue, 8 Apr 2008 17:37:16 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:

> Thank you very much for these comments. I do think we need to talk
> more about this issue.

Oh, has it been six months already?  ... yeah, I guess it has.

No, we most certainly do *not* need to bloody talk about this
issue.  We "talk" about it approximately twice a year.  We,
collectively, spend about 20 hours "talking" (reading/writing
emails on the subject).  And at the end of all that "talk",
absolutely nothing changes.

Here's what will happen (or has already happened):
- some people complain about a lot of old projects that convert-ly
  doesn't handle.
- other people point at a famous work created with lilypond
  1.something, which has only required X minutes of manual
  tweaking to make it run on modern lilypond.
- a certain grumpy doc writer points out that if you read the
  instructions in
  LM 5.1 Suggestions for writing LilyPond files
  then you can avoid almost all these problems.
- a certain grumpy organizer points out that nobody has
  volunteered to work on convert-ly or its docs.
- some people complain that they "don't have the time" to do this
  themselves, but it's still "very important".
- I call BS; if something is "very important" to you, you can find
  an hour a week to work on it.  Unless you're a world-famous
  brain surgeon or something like that, you can find an hour a
  week.  And if you're really *so* busy that you can't afford that
  much time, then you're not reading this email list anyway.

To elaborate the final point: of course we all judge how to spend
our time.  Some commitments are more important than others -- if I
had a girlfriend, I'd spend way less time on lilypond.  If I had a
baby or young child, I'd probably stop contributing entirely.

I'm not criticizing anybody who decides that helping improve
convert-ly isn't important.  I mean, *I* certainly don't think
it's worth *my* time to work on it!  However, be honest.  If it's
not important enough for *you* to work on, then don't expect it to
be important enough for "somebody else" to work on.  This is a
volunteer project.  All the reasons that you have for not working
on convert-ly can apply equally well to the rest of us.


...
That said, if anybody *does* want to help out, either with
convert-ly itself, its documentation (ie listing problems which
require manual attention)... or really, anything else... then I'd
be happy to hear from you!

Unless you're Valentin.  He's doing too many things as it is, and needs
to do those things better, not add more tasks.

Cheers,
- Graham


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

Colored hairpins?

[Tim Reeves]

Actually I need colored dynamics, including hairpins, but I thought 
"colored hairpins" sounds like something you find at a beauty salon and 
not in software!

I was trying to find in the user manual (NR) a color property for dynamics 
(\f, \cr, \cresc, etc.) but there doesn't seem to be any. I can color 
noteheads, stems, bar lines, staff lines, and text. Is that everything?
I want to make some dynamics a different color to indicate that they are 
not in the original part. Did I miss something, or is there a way to do it 
with Scheme? I would settle for doing it with a text spanner as well, but 
I can't see that there's a color property for those either.

Tim Reeves___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Old LilyPond versions

[Nicolas Sceaux]

Le 8 avr. 08 à 19:01, Graham Percival a écrit :


Some commitments are more important than others -- if I
had a girlfriend, I'd spend way less time on lilypond.  If I had a
baby or young child, I'd probably stop contributing entirely.


ouch, that hurts.
Note to myself: spend more time with my wife and son.

nicolas



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

Re: Old LilyPond versions

[Graham Percival]

On Tue, 8 Apr 2008 20:15:50 +0200
Nicolas Sceaux <[EMAIL PROTECTED]> wrote:

> Le 8 avr. 08 __ 19:01, Graham Percival a __crit :
> >
> > Some commitments are more important than others -- if I
> > had a girlfriend, I'd spend way less time on lilypond.  If I had a
> > baby or young child, I'd probably stop contributing entirely.
> 
> ouch, that hurts.
> Note to myself: spend more time with my wife and son.

Oops.  :)

In an attempt to remedy this counterproductive-ness, I'll remind
everybody that I don't do any composition or transcriptions these
days.  If I were still composing, I wouldn't be reducing my
lilypond contributions at all -- I think it's important to keep an
active role in the tool(s) that you use most often.  (that's why
I'm focusing on documentation for other projects now; I use them
far more than lilypond)

Cheers,
- Graham


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

Re: Colored hairpins?

[Kieren MacMillan]

Hi Tim,


Actually I need colored dynamics, including hairpins, but I thought
"colored hairpins" sounds like something you find at a beauty salon
and not in software!  I was trying to find in the user manual (NR)
a color property for dynamics (\f, \cr, \cresc, etc.) but there  
doesn't seem to be any.


Dynamics are DynamicText graphical objects (grobs); if you look at  
the bottom of the corresponding page





you'll see that one of the interfaces DynamicText supports is the  
grob-interface; on *that* page (which is conveniently linked),





you'll find the property to set. To save you the trouble (this  
time ;) I've included it here, as a variable:


redDyn = \once \override DynamicText #'color = #red

I can color noteheads, stems, bar lines, staff lines, and text. Is  
that everything?


Anything that inherits the grob-interface *should* be color-able...  
and that's just about everything in the 'Pond.  =)


HTH,
Kieren.


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

Re: Old LilyPond versions

[Graham Percival]

On Tue, 08 Apr 2008 13:14:42 -0400
Laura Conrad <[EMAIL PROTECTED]> wrote:

> The grumpy doc writer has said many times that he knows nothing about
> vocal music.  None of the suggestions in 5.1 is going to change the
> fact that manual conversion is necessary for all vocal music
> transcribed before 2.4.

You're talking about the old LaTeX accents -> utf-8 ?

Manual conversion is necessary with current convert-ly.  I can
think of three ways to automate it.  They're all kind-of hackish,
but they'd work in theory.  It just needs somebody to translate
that theory into practice.

> And in any case, drawing the attention of new members of the list who
> are struggling to convert old projects to LM5.1 is one of the benefits
> of rehashing the old topic.

That's true.

Cheers,
- Graham


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

Re: Old LilyPond versions

[Mats Bengtsson]

Quoting Graham Percival <[EMAIL PROTECTED]>:


On Tue, 08 Apr 2008 13:14:42 -0400
Laura Conrad <[EMAIL PROTECTED]> wrote:


The grumpy doc writer has said many times that he knows nothing about
vocal music.  None of the suggestions in 5.1 is going to change the
fact that manual conversion is necessary for all vocal music
transcribed before 2.4.


You're talking about the old LaTeX accents -> utf-8 ?


No, probably rather about \lyricsto and \addlyrics.

  /Mats



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

Re: Metronome marks

[Trevor Daniels]

Hi Mattias

It's possible (most things are in LilyPond) but it's not easy (at least I 
don't know an easy way).  Essentially you have to create a tiny score 
without a staff, etc.  Have a look at

http://lsr.dsi.unimi.it/LSR/Item?id=204
This should give you some clues, or maybe easier, you can simply copy out 
the functions and use them.


Trevor D

- Original Message - 
From: "Matthias Loitsch" <[EMAIL PROTECTED]>

To: 
Sent: Tuesday, April 08, 2008 6:09 PM
Subject: Metronome marks



Hi!

I'm new to this list, and quite new to lilypond too.

I'm trying to change the tempo in a song, and I can't find how to do so...

What I want to do, is not a normal metronome tempo change, but I want a
triplet to become a quarter note.

I found how to set the tempo with a metronome marking (\tempo 4=120), and 
I

found the syntax to display an eigth note becoming a quarter note:
\markup {
  (
  \smaller \general-align #Y #DOWN \note #"8" #1
  =
  \smaller \general-align #Y #DOWN \note #"4" #1
  ) }


But how can I use this with a triplet? I tried \note #"12" and \note 
#"4/3"

but they both don't work...

Is there a way to get a triplet with \note ? Or do I need a completely
different approach?



Thank you in advance,
Matthias



--
Matthias Loitsch

http://www.youtube.com/watch?v=yAUYaweNQME


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





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

Fwd: convert text encodings (was: Old LilyPond versions)

[fiëé visuëlle]

Am 2008-04-08 um 20:28 schrieb Graham Percival:

You're talking about the old LaTeX accents -> utf-8 ?

Manual conversion is necessary with current convert-ly.  I can
think of three ways to automate it.  They're all kind-of hackish,
but they'd work in theory.  It just needs somebody to translate
that theory into practice.


Conversion of "LaTeX encoding" to any other encoding, esp. UTF-8 is  
easy.
I've a little script ready for such - but it converts whole files, I  
don't know if it will affect LilyPond commands.


Here:
http://www.fiee.net/texnique/?menu=0-2-2&lang=en
you can download the "mab2bib" archive, it includes "utf2latex.py".

Just rename that to "latex2utf.py" (or any other encodings, like  
"latin12utf" or "macroman2utf", it analyzes its filename when called).


It should work with all encodings that Python knows of. Normally  
LaTeX is not one of them, so the also included "latex.py" must reside  
in the same directory.


Have fun!


Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)

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

Re: Fwd: convert text encodings (was: Old LilyPond versions)

[Mats Bengtsson]

Please note that convert-ly automatically will convert
latin1 to UTF-8 if the input file is older than version 2.5.13.
It will not handle any embedded TeX commands, but my guess is that in
many of the cases, the embedded TeX commands will have
to be replaced by some appropriate \markup command or other
construct in LilyPond, not by a single UTF-8 encoded character
string.

  /Mats

Quoting fiëé visuëlle <[EMAIL PROTECTED]>:


Am 2008-04-08 um 20:28 schrieb Graham Percival:

You're talking about the old LaTeX accents -> utf-8 ?

Manual conversion is necessary with current convert-ly.  I can
think of three ways to automate it.  They're all kind-of hackish,
but they'd work in theory.  It just needs somebody to translate
that theory into practice.


Conversion of "LaTeX encoding" to any other encoding, esp. UTF-8 is  easy.
I've a little script ready for such - but it converts whole files, I
don't know if it will affect LilyPond commands.

Here:
http://www.fiee.net/texnique/?menu=0-2-2&lang=en
you can download the "mab2bib" archive, it includes "utf2latex.py".

Just rename that to "latex2utf.py" (or any other encodings, like
"latin12utf" or "macroman2utf", it analyzes its filename when called).

It should work with all encodings that Python knows of. Normally
LaTeX is not one of them, so the also included "latex.py" must reside
 in the same directory.

Have fun!


Greetlings from Lake Constance
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)

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







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

Re: Fwd: convert text encodings (was: Old LilyPond versions)

[Graham Percival]

On Tue, 8 Apr 2008 22:14:41 +0200
fi visu__lle <[EMAIL PROTECTED]> wrote:

> Am 2008-04-08 um 20:28 schrieb Graham Percival:
> > You're talking about the old LaTeX accents -> utf-8 ?
> >
> > Manual conversion is necessary with current convert-ly.  I can
> > think of three ways to automate it.  They're all kind-of hackish,
> > but they'd work in theory.  It just needs somebody to translate
> > that theory into practice.
> 
> Conversion of "LaTeX encoding" to any other encoding, esp. UTF-8 is  
> easy.
> I've a little script ready for such - but it converts whole files, I  
> don't know if it will affect LilyPond commands.
>
> Here:
> http://www.fiee.net/texnique/?menu=0-2-2&lang=en
> you can download the "mab2bib" archive, it includes "utf2latex.py".

This was option #3.  :)

Just this script can save some time.  Ideally, somebody would spend two
hours modifying this script so that it only looks inside \markup or
\lyrics or something like that.  Then perhaps another two hours to
integrate it with convert-ly -- or, if that's not possible/ideal, dump
it somewhere on the web and get our convert-ly docs to point to it as a
"helper script" for a particularly difficult transistion.

I'm not offering to do any of this, but if somebody else is interested,
I'm quite willing to mentor them and help them through these steps.

Cheers,
- Graham


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

Re: Old LilyPond versions

[Graham Percival]

On Tue, 08 Apr 2008 20:42:15 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:

> Quoting Graham Percival <[EMAIL PROTECTED]>:
> 
> > On Tue, 08 Apr 2008 13:14:42 -0400
> > Laura Conrad <[EMAIL PROTECTED]> wrote:
> >
> >> The grumpy doc writer has said many times that he knows nothing
> >> about vocal music.  None of the suggestions in 5.1 is going to
> >> change the fact that manual conversion is necessary for all vocal
> >> music transcribed before 2.4.
> >
> > You're talking about the old LaTeX accents -> utf-8 ?
> 
> No, probably rather about \lyricsto and \addlyrics.

Hmm.  According to our docs, that was 2.0->2.2... and I can't see
what the problem was.

1)  it might be nice to give some more info about this, so that
people *can* make these updates manually.

2)  it would of course be nice to automate this.  At the moment, I
can't see why this would take more than five hours.  Maybe 15
hours if the person had never touched python before.


As before, I'm not offering to do anything myself, but I'll
happily mentor anybody who's interested.

I'm very serious about this -- one of my "day jobs" is being a TA
in computer science, and so far I've always been teaching
first-year non-CS students how to use excel, access, and a tiny
bit of java programming.  They hate the programming because it has
no relevance to them, and I can't honestly disagree... especially
when their assignments are silly things like "write a program that
calculates the interest compounded daily, monthly, and yearly" --
that calls for a spreadsheet, not compiled language!

By my rough calculations, teaching a complete programming novice
how to solve a problem they're *interested* in solving would be
10 times easier and approximately 15 billion times more fun than
being a TA.

In addition, this is a relatively easy problem to tackle for
novices.  Python + text file processing is a very nice
combination.


Of course, it all depends on volunteers, and that depends on how
much work it would be to translate everything by hand.  If it
would take 15 hours of learning programming to save 50 hours of
manual lilypond updating, it's obviously a good choice.  If it
would take 20 hours of programming to save 2 hours of manual
lilypond updating, it's probably not a good choice... although the
finished program could still be useful for other people, so it
might still be worth it.

Cheers,
- Graham


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

Re: Old LilyPond versions

[Mats Bengtsson]

Quoting Graham Percival <[EMAIL PROTECTED]>:


On Tue, 08 Apr 2008 20:42:15 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:


Quoting Graham Percival <[EMAIL PROTECTED]>:

> On Tue, 08 Apr 2008 13:14:42 -0400
> Laura Conrad <[EMAIL PROTECTED]> wrote:
>
>> The grumpy doc writer has said many times that he knows nothing
>> about vocal music.  None of the suggestions in 5.1 is going to
>> change the fact that manual conversion is necessary for all vocal
>> music transcribed before 2.4.
>
> You're talking about the old LaTeX accents -> utf-8 ?

No, probably rather about \lyricsto and \addlyrics.


Hmm.  According to our docs, that was 2.0->2.2... and I can't see
what the problem was.

Actually, the old \addlyrics syntax was supported to keep backward
compatibility for quite a long time (convert-ly converted the construct 
to \oldaddlyrics).




1)  it might be nice to give some more info about this, so that
people *can* make these updates manually.

2)  it would of course be nice to automate this.  At the moment, I
can't see why this would take more than five hours.  Maybe 15
hours if the person had never touched python before.


See http://lists.gnu.org/archive/html/bug-lilypond/2007-12/msg00156.html
I don't think the problem is that easy, especially since the music 
expression may in the general case contain an arbitrarily deep nesting

of {} and <<>>, which means that you cannot use regular expressions.

  /Mats



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

Re: Old LilyPond versions

[Graham Percival]

On Wed, 09 Apr 2008 00:21:36 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:

> Quoting Graham Percival <[EMAIL PROTECTED]>:
> > 2)  it would of course be nice to automate this.  At the moment, I
> > can't see why this would take more than five hours.  Maybe 15
> > hours if the person had never touched python before.
> 
> See
> http://lists.gnu.org/archive/html/bug-lilypond/2007-12/msg00156.html
> I don't think the problem is that easy, especially since the music
> expression may in the general case contain an arbitrarily deep
> nesting of {} and <<>>, which means that you cannot use regular
> expressions.

I'm not really comfortable with regular expressions, so I wasn't
going to suggest this anyway.  :)   As for nesting, we could
simply count the number of { } and << >> to figure out when the
expression is over.

My solutions often end up quite hack-ish, but they work.  As long
as a human can explain to me what they want done, I can get the
result... or in this case, I can teach somebody how to do it
themselves.

The first step would be simply to get a working program that does
this, with no attempt being made to integrate it with convert-ly.
Once we had working code, we'd investigate merging it or simply
leaving it as a standalone tool for that particular conversion.

Besides, these's nothing wrong -- and quite a few things right --
about inexperienced programmers rewriting code.  :)

Cheers,
- Graham


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

Re: Colored hairpins?

[Tim Reeves]

Well, it helps some, but why do I get an error when I try the same thing 
with hairpins?

error: syntax error, unexpected EVENT_IDENTIFIER

r4 d4 \p d d | \repeat "unfold" 4 {d1~} | d1 \once 
\override Hairpin #'color = #blue   \cr | d1 | d1 \f

(using 2.11.43 on Windows XP)

and where can I put the variable redDyn in my .ly file? Everywhere I try 
seems to give me errors, which is why I just put the \override right in 
with the music.

Finally, when does one have to include the context, like \once \override 
Voice.DynamicText #'color = #blue?

Thanks for your help.

Tim Reeves





Kieren MacMillan <[EMAIL PROTECTED]> 
04/08/2008 11:28 AM

To
Tim Reeves <[EMAIL PROTECTED]>
cc
lilypond-user@gnu.org
Subject
Re: Colored hairpins?






Hi Tim,

> Actually I need colored dynamics, including hairpins, but I thought
> "colored hairpins" sounds like something you find at a beauty salon
> and not in software!  I was trying to find in the user manual (NR)
> a color property for dynamics (\f, \cr, \cresc, etc.) but there 
> doesn't seem to be any.

Dynamics are DynamicText graphical objects (grobs); if you look at 
the bottom of the corresponding page

 

you'll see that one of the interfaces DynamicText supports is the 
grob-interface; on *that* page (which is conveniently linked),

 

you'll find the property to set. To save you the trouble (this 
time ;) I've included it here, as a variable:

 redDyn = \once \override DynamicText #'color = #red

> I can color noteheads, stems, bar lines, staff lines, and text. Is 
> that everything?

Anything that inherits the grob-interface *should* be color-able... 
and that's just about everything in the 'Pond.  =)

HTH,
Kieren.

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

OOoLilypond instilation problems and coding help

[Levi Hendricks]

I am  running windows XP (with sp2) and open office v 2.0.2 . I followed the 
instructions on using lilypad with open office. I have downloaded (and written 
in) the lilypond script as well as the open office macro, i installed the macro 
as said in the instructions, but when i press alt m an error orccurs. The 
message is this: "BASIC syntax error. Dimension specifications do not match." 
it highlights a portion of the code:"SortStringArray(sTemplate" approximately 
4/5ths the way down the page. I cant get the macro to work, can anyone help me?

On another note, I am reading the tutorial and manuals for lilypond, but am 
having trouble assimilating all the information. I have done some html and java 
programing so im no stranger to computer code, but the "voices" concept is 
giving me trouble. I am using this program to write percussion music for 
lessons that I am giving, and if someone could help me disect some code this 
would be great: 
 \new DrumStaff <<
   \new DrumVoice = "1" { s1 *2 }
   \new DrumVoice = "2" { s1 *2 }
   \drummode {
 bd4 sn4 bd4 sn4
 <<
   { \repeat unfold 16 hh16 }
   \\
   { bd4 sn4 bd4 sn4 }
 >>
   }
 >>

here is what I understand: DrumStaff creates a staff, thats simple. drummode 
initiates the acceptance of sn bd hh etc. as valid input. I also understand 
that there is a measure of alternating bd/sn hits for 4 beats before the 
'polyphonic' measures. I understand that the polyphonic measure uses two 
'voices, one that is just the hh and one that is the bd and sn. 

Here is what I don't understand: the creation of  \new DrumVoice = "1" { s1 *2 
}. Why do i need to create new drum voices. And if im not referencing them 
later, how does the code know which one is which. Are "1" and "2" simply names, 
or do they have do do with stem directions, or what? and what in heck does {s1 
*2} mean?

Thank you for your help. I am new at using lilypad, i stumble across it and 
don't know anyone else who can help me. This is the first time I've used this 
mailing list so even if you cant help me, letting me know that I've succeeded 
in asking for help would be nice. thanks.





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

Re: vertical text

[Michael Watts]

Cool!  I'll be using that.


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

Re: OOoLilypond instilation problems and coding help

[Michael Watts]

Hi Levi,

The example drum notation you give shows how to use the short form of 
polyphonic notation when entering percussion, with the DrumVoices 
"instantiated by hand first".


You might find verbose polyphonic notation easier to use; both forms are 
given here:

http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Percussion-staves#Percussion-staves

The {s1 *2 } means simply a semibreve ('whole note') skip, multiplied by 
two.



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