Re: Special metronome marks

[Carsten Steger]

Xaiver, Graham,

On Tue, Apr 6, 2010 at 10:11 AM, Xavier Scheuer  wrote:
> On 5 April 2010 12:19, Graham Percival  wrote:
>> An example of this is in LSR.  Try searching for "jazz tempo" or
>> something ilke that.
>
> Rhythm marks / play style indication
> http://lsr.dsi.unimi.it/LSR/Item?id=204

thank you very much! This works like a charm.

This kind of notation is fairly common in drumming. Is there a chance
that the functions in http://lsr.dsi.unimi.it/LSR/Item?id=204 (or
something similar) could be made an official part of LilyPond?

Cheers, Carsten


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

Any way to use lilypond as a library? (embeded)

[Alejandro Piñeiro]

I would to ask if there are any way to use parts of lilypond as a library of a
different application (use lilypond embeded).

Right now I'm using Ubuntu, and there are only available lilypond, lilypond-data
or lilypond-doc packages. There isn't anything similar to lilypond-dev

As far as I see lilypond only includes executables.

Why I ask that?

I'm creating a little application and I would like to create simple midi files
on the fly, but I would like to avoid to enter in midi internals (avoid to waste
my time reinventing the wheel). And lilypond file format is really easy to use.

So my idea is:

 * My program creates a tune.
 * Create a string with the lilypond description.
 * Calls a function, and it creates a external midi file
 * My program uses the midi file.

Of course, other alternative could be:
 * My program creates a tune
 * Creates a external lilypond file
 * Calls lilypond to parse this string->creates midi file
 * Uses the file

But, I think that the second one is more slow.

Thanks for your attention.



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

Re: Any way to use lilypond as a library? (embeded)

[Graham Percival]

2010/4/7 Alejandro Piñeiro :
> I would to ask if there are any way to use parts of lilypond as a library of a
> different application (use lilypond embeded).

No.  Not the way you're imagining it, at least.

> Why I ask that?

Because nobody coded it.  Are _you_ volunteering to spend 50 hours
working on this?

> I'm creating a little application and I would like to create simple midi files
> on the fly, but I would like to avoid to enter in midi internals (avoid to 
> waste
> my time reinventing the wheel).

lilypond is completely impractical for this; you'll save much more
time by writing the midi files directly.  I'm sure there's some
libraries that help with this; there's certainly midi packages for
python, perl, and such scripting languages.

Cheers,
- Graham


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

Re: Any way to use lilypond as a library? (embeded)

[Boris Shingarov]

Hi Alejandro,
 
For what you are doing, you probably want to use libmidi; lilypond is
more like if your program created a tune and needed to render the score
on paper or on the screen.  If your program is in C  , you can use
libmidi directly.  If it is in another language, there are many
wrappers around libmidi available.
 
On Wed, 7 Apr 2010 11:32:42   (UTC), Alejandro Piñeiro  wrote:
I would to ask if there are any way to use parts of lilypond as a library of a
 > different application (use lilypond embeded).
 >
 > Right now I'm using Ubuntu, and there are only available lilypond,
lilypond-data
 > or lilypond-doc packages. There isn't anything similar to lilypond-dev
 >
 > As far as I see lilypond only includes executables.
 >
 > Why I ask that?
 >
 > I'm creating a little application and I would like to create simple
midi files
 > on the fly, but I would like to avoid to enter in midi internals
(avoid to waste
 > my time reinventing the wheel). And lilypond file format is really
easy to use.
 >
 > So my idea is:
 >
 >  * My program creates a tune.
 >  * Create a string with the lilypond description.
 >  * Calls a function, and it creates a external midi file
 >  * My program uses the midi file.
 >
 > Of course, other alternative could be:
 >  * My program creates a tune
 >  * Creates a external lilypond file
 >  * Calls lilypond to parse this string->creates midi file
 >  * Uses the file
 >
 > But, I think that the second one is more slow.
 >
 > Thanks for your attention.
 >
 >
 >
 > ___
 > lilypond-devel mailing list
 > lilypond-devel@gnu.org
 > http://lists.gnu.org/mailman/listinfo/lilypond-devel
 >
 >




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

Re: Any way to use lilypond as a library? (embeded)

[Bertalan Fodor (LilyPondTool)]

Why I ask that?

I'm creating a little application and I would like to create simple midi files
on the fly, but I would like to avoid to enter in midi internals (avoid to waste
my time reinventing the wheel). And lilypond file format is really easy to use.

So my idea is:

 * My program creates a tune.
 * Create a string with the lilypond description.
 * Calls a function, and it creates a external midi file
 * My program uses the midi file.

  

Check JFugue. That would be more appropriate for this purpose.

Bert



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

midstaff line = stem shortened?

[Kieren MacMillan]

Hello all,

I don't have Ross or any comparable book...

Could someone please confirm that the stem on a midstaff note (e.g., a d in the 
bass clef) is traditionally shortened?
I always thought shortening started with notes in the space above/below the 
midstaff line -- looking through several of my library scores confirms this 
intuition.

Lilypond currently shortens such stems, which looks odd to my eye.

Thanks,
Kieren.

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

Re: Any way to use lilypond as a library? (embeded)

[Florin Mihaila]

On Apr 7, 2010, at 7:50 AM, Graham Percival wrote:

> 2010/4/7 Alejandro Piñeiro :
>> I would to ask if there are any way to use parts of lilypond as a library of 
>> a
>> different application (use lilypond embeded).
> 
> No.  Not the way you're imagining it, at least.
> 
>> Why I ask that?
> 
> Because nobody coded it.  Are _you_ volunteering to spend 50 hours
> working on this?

It seems that you parsed his question is "Why, I ask?" when in fact it was 
probably meant as "Why do I ask that?" (he then goes on to explain why he 
asked.) Speakers of my native language, a relative of Portuguese and Spanish, 
tend to form English questions the same way.

--Florin

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

Dealing with character space issues in feta font

[Carl Sorensen]

The shape note community has asked for improvements in shape note heads,
because the current system creates "goofy" looking output.

See  for more
details.

In modifying the font, it now appears that there are at least three
different styles of shape note heads:

1) Sacred Harp style
2) Christian Harmony style
3) Southern Harmony style

In order to accommodate all of these styles, it made sense to me to add some
new glyphs to the file mf/feta-noteheads.mf

Unfortunately, when I added all the necessary glyphs, the upper index in
mf/feta11.log wrapped around to 4, so the font was broken.

Is there a convenient way to repackage the characters for the font?  I could
decrease the start number (which is currently at 32 in order to avoid the
control characters, IIUC). Should I do this, or is there some other way to
split the font, e.g. by moving one or more groups into a separate font?

Thanks,

Carl



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

Re: Fix #786. (issue885044)

[n . puttock]

On 2010/04/06 08:13:20, Trevor Daniels wrote:

Typo



http://codereview.appspot.com/885044/diff/1/2
File input/regression/display-lily-tests.ly (right):



http://codereview.appspot.com/885044/diff/1/2#newcode1
input/regression/display-lily-tests.ly:1: \version "2.13.8"
2.13.18


Done.

Thanks for checking, Trevor.

http://codereview.appspot.com/885044/show


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

Re: midstaff line = stem shortened?

[Carl Sorensen]

Sent again, with a smaller attachment 


On 4/7/10 8:06 AM, "Kieren MacMillan"  wrote:

> Hello all,
> 
> I don't have Ross or any comparable book...
> 
> Could someone please confirm that the stem on a midstaff note (e.g., a d in
> the bass clef) is traditionally shortened?
> I always thought shortening started with notes in the space above/below the
> midstaff line -- looking through several of my library scores confirms this
> intuition.
> 
> Lilypond currently shortens such stems, which looks odd to my eye.
> 

Read, p. 64: "Generally the stem length is one octave... This principle is
not literally observed when the end of the stem is extended avobe the secont
added space over the staff (for upward stems) or below the second added
space under the staff (for downwards stems)... Such stems are usually
somewhat shortened..."

The example in read does not show a note on the middle staff line; only
notes on the spaces above or below the middle staff line are shown.
However, in example 5-1 on page 64 (which talks about stem direction for
notes on the middle line, the stem is shortened).

Stone, p. 47: "Stems on single notes should be one octave long unless the
note is farther than one octave from the middle line of the staff, in which
case the stem is lengthened to reach the middle line."   This appears to
apply only to notes whose direction is chosen strictly by note location,
i.e. not for polyphonic situations.

Stone, p. 48: "Notes below the middle line of the staff are stemmed up;
notes above an on the middle line of the staff are stemmed down."

Stone, p. 48: "In double stemming, the stems are usually shortened by 1/2 to
1 space, i.e., from an octave to a seventh or sixth.. [Except for some
exceptions]"

Ross, p. 83: "The normal length of a stem is one octave (three and one-half
spaces)."

Ross, p. 86: Paraphrase:  Notes with stems up on the space above the middle
staff line and up have 2 and a half space long stems.  Notes on the second
staff line and below with stems down also have 2 1/2 space long stems.
Notes on the center staff line with stems up have 3 space stems.  Notes on
the space below the center line with stems down have 3 space stems.

My assessment after reading them all:

A stem going down on the midstaff note should be 3 1/2 spaces.  A stem going
up on the midstaff note should be 3 spaces.  (Although Read shows the stem
going down on the midstaff note as slightly less than 3 1/2 spaces).

HTH,

Carl



Read example.png
Description: Read example.png
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel