2013/11/30 Joseph Rushton Wakeling :
> On 30/11/13 12:30, Janek Warchoł wrote:
>>
>> We'll see how to split the amount between sponsors when i'm finished -
>> i originally intended to do just flat, natural and sharp, so doing all
>> microtonal accidentals may take me extra time.
>
>
> Why don't we
On 30/11/13 12:30, Janek Warchoł wrote:
We'll see how to split the amount between sponsors when i'm finished -
i originally intended to do just flat, natural and sharp, so doing all
microtonal accidentals may take me extra time.
Why don't we split the task? Regular accidentals first as a proof
Hi,
2013/11/30 Josiah Boothby :
> To clarify:
>
>> >> > Would you like to sponsor this? For $20 i could add special
>> >> > accidentals to LilyPond font and adjust \flat, \sharp and
>> >> > \natural commands to use them (and maybe others like \semiflat,
>> >> > if i'll have time).
>> >>
>> >> Why
On 30/11/13 21:38, Joseph Rushton Wakeling wrote:
On 30/11/13 00:03, Janek Warchoł wrote:
2013/11/29 David Kastrup :
Why not use the Unicode charpoints, like B♭, F♯ and so on? They are
_supposed_ to go well with the text font and kern properly.
because *we* have the most beautiful musical fo
2013/11/30 Joseph Rushton Wakeling :
> On 30/11/13 00:03, Janek Warchoł wrote:
>>
>> 2013/11/29 David Kastrup :
>>
>>> Why not use the Unicode charpoints, like B♭, F♯ and so on? They are
>>> _supposed_ to go well with the text font and kern properly.
>>
>> because *we* have the most beautiful musi
On 30/11/13 00:03, Janek Warchoł wrote:
2013/11/29 David Kastrup :
Why not use the Unicode charpoints, like B♭, F♯ and so on? They are
_supposed_ to go well with the text font and kern properly.
because *we* have the most beautiful musical font in the world? ;-)
I've looked at the output of
\
> I've looked at the output of
> \markup { B♭ F♯ }
> and it is *hideous* (see attached). Totally unusable.
Wow, could you please implement these as the default accidentals into
feta font?
Just kidding.
___
lilypond-user mailing list
lilypond-user@gnu
Am 30.11.2013 00:37, schrieb Urs Liska:
It should be very easy to write commands that combine note names in
the default text font with accidentals from LilyPond while having
complete control about scaling and placement is provided.
For example, a quick shot
\documentclass{article}
\usepackage
Am 30.11.2013 00:09, schrieb Janek Warchoł:
I would also sponsor a solution for using this text accidental in
> lilypond-book.
I totally recommend using LilyGlyphs! Their added advantage is that
they are already implemented - you can send money to Urs right away,
he deserves it!:-)
Maybe I d
To clarify:
> >> > Would you like to sponsor this? For $20 i could add special
> >> > accidentals to LilyPond font and adjust \flat, \sharp and
> >> > \natural commands to use them (and maybe others like \semiflat,
> >> > if i'll have time).
> >>
> >> Why not use the Unicode charpoints, like B♭,
Hi,
2013/11/29 Josiah Boothby :
> On Fri, 29 Nov 2013 15:45:33 +0100
> David Kastrup wrote:
>
>> Janek Warchoł writes:
>>
>> > Would you like to sponsor this? For $20 i could add special
>> > accidentals to LilyPond font and adjust \flat, \sharp and \natural
>> > commands to use them (and maybe
2013/11/29 David Kastrup :
> Janek Warchoł writes:
>> What do you think about \at function that David wrote?
>> (see snippet here
>> https://github.com/openlilylib/snippets/tree/master/input-shorthands/articulations-not-aligned-with-notes)
>> The syntax is a bit awkward, but this function already
Am 29.11.2013 21:19, schrieb Josiah Boothby:
I would also sponsor a solution for using this text accidental in
lilypond-book.
If you're after using notation elements in LaTeX (Lua- or Xe- only) you
may also have a look at http://www.ctan.org/pkg/lilyglyphs
Urs
On Fri, 29 Nov 2013 15:45:33 +0100
David Kastrup wrote:
> Janek Warchoł writes:
>
> > Would you like to sponsor this? For $20 i could add special
> > accidentals to LilyPond font and adjust \flat, \sharp and \natural
> > commands to use them (and maybe others like \semiflat, if i'll have
> > t
On 29/11/13 15:45, David Kastrup wrote:
Why not use the Unicode charpoints, like B♭, F♯ and so on? They are
_supposed_ to go well with the text font and kern properly.
Should fit nicely with the idea of a \textPitch function I floated in the other
email. Are there any international-note-name
On 29/11/13 15:34, Janek Warchoł wrote:
What do you think about \at function that David wrote?
(see snippet here
https://github.com/openlilylib/snippets/tree/master/input-shorthands/articulations-not-aligned-with-notes)
The syntax is a bit awkward, but this function already does exactly
what we w
Janek Warchoł writes:
> Hi,
>
> 2013/11/29 Joseph Rushton Wakeling :
>> Hairpins that don't begin or end with a notehead or rest are such a typical
>> musical notation, so easy to do by hand or with a WYSIWYG score editor, and
>> really annoying and finnicky to do with Lilypond.
>
> What do you t
Hi,
2013/11/29 Joseph Rushton Wakeling :
> Hairpins that don't begin or end with a notehead or rest are such a typical
> musical notation, so easy to do by hand or with a WYSIWYG score editor, and
> really annoying and finnicky to do with Lilypond.
What do you think about \at function that David
On 13/09/13 05:54, Curt wrote:
- Hairpins are surprisingly difficult. Most instruments do not have a natural
decay, so hairpins don't necessarily start or end right at the note
boundaries. It's necessary to use "fake voices" in these cases. Even
with this, it didn't sup
2013/9/15 Janek Warchoł :
> 2013/9/14 Jim Long :
>> On Sat, Sep 14, 2013 at 12:14:55PM +0200, Janek Warcho?? wrote:
>>>
>>> I think that we should add to LilyPond a simple, user-friendly
>>> interface that would allow choosing the "density" of music, so that
>>> one could write
>>> \layout { \horiz
PMA wrote:
David Kastrup wrote:
PMA writes:
David Kastrup wrote:
PMA writes:
Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a fact
2013/9/15 David Kastrup :
> Janek Warchoł writes:
>> As far as i see, implementing this with some reasonable and
>> user-friendly syntax would require a substantial discussion. We tried
>> to discuss these "GLISS" things last September, but the outcome was
>> somewhat discouraging...
>
> The "dis
Janek Warchoł writes:
> Hi,
>
> 2013/9/14 Kieren MacMillan :
>>> Please take a look at this snippet:
>>> http://github.com/openlilylib/snippets/blob/master/input-shorthands/articulations-not-aligned-with-notes.ly
>>> It has some issues, but you'll get an idea immediately after compiling
>>> it.
Hi,
2013/9/14 Kieren MacMillan :
>> Please take a look at this snippet:
>> http://github.com/openlilylib/snippets/blob/master/input-shorthands/articulations-not-aligned-with-notes.ly
>> It has some issues, but you'll get an idea immediately after compiling
>> it. I think it's clever and could pro
2013/9/14 Jim Long :
> On Sat, Sep 14, 2013 at 12:14:55PM +0200, Janek Warcho?? wrote:
>>
>> I think that we should add to LilyPond a simple, user-friendly
>> interface that would allow choosing the "density" of music, so that
>> one could write
>> \layout { \horizontalSpacingLoose }
>> and it woul
David Kastrup wrote:
PMA writes:
David Kastrup wrote:
PMA writes:
Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a factor of #-1
PMA writes:
> David Kastrup wrote:
>> PMA writes:
>>
>>> Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a factor of
Am 14.09.2013 20:54, schrieb David Kastrup:
PMA writes:
Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a factor of #-1.0 would mean t
David Kastrup wrote:
PMA writes:
Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a factor of #-1.0 would mean that the glyphs are engr
PMA writes:
> Jim Long wrote:
>> I suppose that, by extension, this means that a factor of #0.0
>> means the layout would have no spacing at all, and all glyphs
>> would be engraved over the top of each other in one big blob, and
>> a factor of #-1.0 would mean that the glyphs are engraved
>> nor
Jim Long wrote:
I suppose that, by extension, this means that a factor of #0.0
means the layout would have no spacing at all, and all glyphs
would be engraved over the top of each other in one big blob, and
a factor of #-1.0 would mean that the glyphs are engraved
normally, but spaced right-to-le
On Sat, Sep 14, 2013 at 12:14:55PM +0200, Janek Warcho?? wrote:
>
> I think that we should add to LilyPond a simple, user-friendly
> interface that would allow choosing the "density" of music, so that
> one could write
> \layout { \horizontalSpacingLoose }
> and it would result in common-shortest-
Hi Janek (et al.),
> I think that we should add to LilyPond a simple, user-friendly
> interface that would allow choosing the "density" of music, so that
> one could write
> \layout { \horizontalSpacingLoose }
> and it would result in common-shortest-duration being increased by
> some factor.
+1
Hi,
2013/9/13 Curt :
> Hi all -
>
> About a year ago, several of you answered questions of mine about notating a
> film score. I reached a stopping point with the first cue and learned a bit
> more about git, so I have the first film cue from the score up on github now:
>
> https://github.com/t
David Kastrup wrote Friday, September 13, 2013 3:03 PM
> Sometimes the effort is better spent simplifying the underlying concepts
> and documenting the results. One hits diminuishing returns pretty fast
> when trying to simplify the explanation of complex matters.
>
> I think when I tried start
Urs Liska writes:
>> Unexpectedly hard parts of creating this score (all specific to v2.16):
>>
>> - General spacing and staff sizes. I believe Lilypond by default
>> puts everything
>> too close together for music that is read by instrumentalists,
>> particularly
>> sight-readers. Th
Hi Curt,
this seems very nice work. If you feel like sharing one or the other
experience as a blog post or pdf tutorial on lilypondblog.org don't
hesitate contacting me privately.
As I'm working in quite different fields I don't have to say much to
many of your perceptions. Just a few commen
Hi Curt,
Thank you so much for doing this!
As someone who dabbled in film scoring pre-Lilypond (and, in fact, before
Sibelius was on anything but RISC OS), and wants to get back into it in
Lilypond, this is all very interesting information.
> The score was originally prepared (in Sibelius) a fe
Hi all -
About a year ago, several of you answered questions of mine about notating a
film score. I reached a stopping point with the first cue and learned a bit
more about git, so I have the first film cue from the score up on github now:
https://github.com/tunesmith/TheForgivingSea
(pdf of
39 matches
Mail list logo
