Hi David,
> The engraver would convert into something akin to c c' d' f'
> bf' (somewhat opaque example since the first is the root pitch and the
> others are the relation to the root note, expressed as intervals from
> c'). There would be one or several markups for interpreting the c' d'
> f'
Sorry for misunderstanding/misinterpretation.
In lilypond I write bes for bflat, In text writing I use bB.
On 18.01.2016 15:23, Kieren MacMillan wrote:
Hi,
Bb/C is built of C Bb D F
…which is what I wrote: “bf” is Bb using english note names.
May be you did a typing error
No.
You
Hi Robert,
> It is possible though that all tools for doing that are already present in
> LilyJazz ... I simply don't remember now.
Sorry, I wasn’t clear: the accidentals in your chord names aren’t using the
LilyJazz font, as far as I can tell, whereas the rest of the glyphs (e.g.,
letters,
Kieren MacMillan writes:
> Hi David,
>
>> The engraver would convert into something akin to c c' d' f'
>> bf' (somewhat opaque example since the first is the root pitch and the
>> others are the relation to the root note, expressed as intervals from
>> c'). There
On 18.01.2016 14:33, BB wrote:
On 18.01.2016 13:29, Kieren MacMillan wrote:
might be named
Dm9no5/C,
Cno5add2add4,
Fmaj7add6no3/C
depending on the context. Names are interpretations of the notes and
always depend on the context. Your chords in the posting
be labelled as Bb/C or
Hi,
> Bb/C is built of C Bb D F
…which is what I wrote: “bf” is Bb using english note names.
> May be you did a typing error
No.
> You never get correct chord names without knowing the context
That’s exactly my point.
Regards,
Kieren.
Kieren MacMillan,
Kieren MacMillan writes:
> Hi David,
>
>> Here's my take on how to do this more transparently: first have an
>> engraver that does the basic chord analysis and writes one or several
>> properties with the basic analysis results (like fundamental pitch and
>> scale
On 18.01.2016 13:29, Kieren MacMillan wrote:
might be named
Dm9no5/C,
Cno5add2add4,
Fmaj7add6no3/C
depending on the context. Names are interpretations of the notes and
always depend on the context. Your chords in the posting
be labelled as Bb/C or C7(sus2,sus4)
Bb/C is built of C Bb D F
Yes, that's true - I guess that never bothered me ... until now, that is, now
that you mention it, thank you very much.
Quite possibly that is easy to fix though - I'll look into that asap.
Maybe I should add that, while I like producing aesthetically pleasing lead
sheets, my first priority
Hi Robert,
> I guess that never bothered me ... until now, that is, now that you mention
> it, thank you very much.
You’re welcome!
I’m very detail-oriented, so things that others might consider “little” often
drive me quite crazy. =)
> Quite possibly that is easy to fix though
Should be.
Am 18.01.2016 08:44, schrieb Carl-Henrik Buschmann:
18. jan. 2016 kl. 02.40 skrev tim...@bitstream.net:
On Jan 17, 2016, at 4:16 PM, Carl-Henrik Buschmann
wrote:
I'm not talking about code, i'm talking about style. And by the looks of
it Sibelius at least have by and
On Mon, 18 Jan 2016 09:12:42 +0100
Blöchl Bernhard wrote:
> Do you really believe that Sibelius was inspired by R?
Not sure if troll
> Johan Julius Christian („Jean“) Sibelius * 8. Dezember 1865 in
> Hämeenlinna; † 20. September 1957 in Järvenpää near
Am 18.01.2016 um 09:12 schrieb Blöchl Bernhard:
[...]
Do you really believe that Sibelius was inspired by R?
The first edition of
Standardized chord symbol notation : (a uniform system for the music
profession)
von Carl Brandt; Clinton Roemer Englisch
was published 1976 by Sherman Oaks, Calif.
Kieren MacMillan writes:
> Hi Simon,
>
>> Note the effect of sensible code formatting – it can’t be emphasised
> often enough…
>
> I actually had it that way in my example, but decided to put it on one
> line to save vertical space in the post.
Well, that's
Carl-Henrik Buschmann writes:
> Kieren is thankfully working on this and i hope the brains that code
> for lilypond can bash heads together and at least give us a *working*
> solution and stop bickering over personal preferences that only hinder
> the development.
I think
Kieren MacMillan writes:
> Hello all,
>
> If I’ve want to explicitly enter a chord in a chordmode block, e.g.,
>
> \chordmode {
> c1
> d1:m6
>
> }
>
> what’s the incantation?
That already works as of version 2.19.13,
commit
Thomas Morley writes:
> 2016-01-17 22:28 GMT+01:00 Carl-Henrik Buschmann :
>
> Thanks for code and links!
>
>> A properly formatet complex chord stacks alterations in parenthesis.
>
> Well, I disagre - at least as a general verdict.
>
>> Lilyponds
--
Note beforehand: I'm sending this from a phone, and I can't control if the
attached picture is sent inline or not - hope you can see it, otherwise I'll
have to resend it later today.
--
Hi Carl-Henrik,
Fwiw, I write jazz sheets all the time, and I've trimmed Lilypond to produce
stuff
Chill pills for everybody! Smile :-)
> 18. jan. 2016 kl. 09.39 skrev David Kastrup :
>
> There is no "brains that code" who have to placate "us" by "at least
> giving us a *working* solution".
I see how that might have been misunderstood, but please belive it was with the
best
ehm, attachment?
Am 18.01.2016 um 18:20 schrieb Urs Liska:
> One more from this round of review ...
>
> I had changed the subdivision behaviour (which is already in 2.19.35)
> for shortened beams.
>
> c32 [ c c c c c c] r
>
> (i.e. a beam shortened by 1/32) subdivided by 1/8 currently has *two*
>
Am 18.01.2016 um 18:24 schrieb Kieren MacMillan:
> Hi Urs,
>
>> c)
>> Take a) as the default and provide a context property
> This.
>
> Thanks,
> Kieren.
>
Any suggestions for a better name than
\set subdividedBeamCountAddForShortenedBeam = ##t
?
Am 18.01.2016 um 18:28 schrieb Kieren MacMillan:
> Hi Urs,
>
>> deep in my heart I also feel we shouldn't support incorrect notation
> Well, okay, then… Let's eliminate the ability to move NoteHead to the wrong
> side of Stem, block \rotate from affecting e.g., Rest, etc. etc. ;)
>
> Just a
Hi all,
> the options seem to be complex enough to be better stored in an alist.
Agreed!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user
On 18.01.2016 18:27, Urs Liska wrote:
Am 18.01.2016 um 18:24 schrieb Kieren MacMillan:
Hi Urs,
c)
Take a) as the default and provide a context property
This.
Thanks,
Kieren.
Any suggestions for a better name than
\set subdividedBeamCountAddForShortenedBeam = ##t
It would almost
Thanks for the feedback.
off-list I got one strong opinion against providing the #'one option
because it's incorrect.
I know it's incorrect, and that's why I had asked for an improvement
around a year ago.
However, it's the way everybody is used to, and that's why some might
still *want* to
One more from this round of review ...
I had changed the subdivision behaviour (which is already in 2.19.35)
for shortened beams.
c32 [ c c c c c c] r
(i.e. a beam shortened by 1/32) subdivided by 1/8 currently has *two*
beams at the subdivision - to indicate that the remaining group is
shorter
On 18.01.2016 18:12, Urs Liska wrote:
Thanks for the feedback.
off-list I got one strong opinion against providing the #'one option
because it's incorrect.
‘Because it’s incorrect’ being one of the weaker arguments. Actually it
impedes legibility, so…
I know it's incorrect, and that's
Hi Urs,
> c)
> Take a) as the default and provide a context property
This.
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing
Hi Urs,
> deep in my heart I also feel we shouldn't support incorrect notation
Well, okay, then… Let's eliminate the ability to move NoteHead to the wrong
side of Stem, block \rotate from affecting e.g., Rest, etc. etc. ;)
Just a Devil’s Advocate-y way of saying: I completely agree that
Hi David,
> Here's my take on how to do this more transparently: first have an
> engraver that does the basic chord analysis and writes one or several
> properties with the basic analysis results (like fundamental pitch and
> scale offsets). Those properties are made part of text-interface.
>
>
,
>
>> it involves the (fantastic) LilyJazz package which was created by Thorsten
>> Hämmerle some time ago.
>
> Why are the alterations in the chord names not LilyJazz?
Well, now that you mention it, they might well be. It's been quite some time
since I worked on that. What I *am* sure of is
Hi Simon,
> In case you should need that for which you initially asked :-) – there’s
> \notemode {}. Normally implicit, it can be used in special situations such as
> this.
That’s what I was looking for! Thanks.
I think I will need this for tagged non-chord material (e.g., split Voice
Hi David,
>\chordmode { \clef bass c/e c/e }
>or other ways of explicitly spelling out some not-really chord material.
On a related note, I discovered yesterday — quite by accident — the output of
\chordmode { c1:1 }
Cheers,
Kieren.
Kieren
On 13/01/16 16:53, Luca Danieli wrote:
I tried to find information on how to do it on internet, but I am unable to
find anything.
I am sorry to continuously asking, but can you give me any hint on how to do it?
I think this is what you want:
arrowGlyphs = #`(
(,DOUBLE-SHARP .
This is smashing! Great job.
The alignment of the chords, is it possible to push above the staff like
traditional chords? The 8, is it part of a multi rest?
> 18. jan. 2016 kl. 11.40 skrev Robert Schmaus :
>
>
> --
> Note beforehand: I'm sending this from a phone,
On Mon, 18 Jan 2016 11:40:47 +0100
Robert Schmaus wrote:
> Fwiw, I write jazz sheets all the time, and I've trimmed Lilypond to
> produce stuff like this:
Nice, very nice!
It's a shame the "8" won't match...
I've tried to obtain something like this some years ago, but
Thanks!
I can post the code for that if you're interested, I just can't promise I'll be
able to do that tonight. And it involves the (fantastic) LilyJazz package which
was created by Thorsten Hämmerle some time ago.
If can get a hold of that, and put it together with Kieren's suggestions,
Hi Robert,
> it involves the (fantastic) LilyJazz package which was created by Thorsten
> Hämmerle some time ago.
Why are the alterations in the chord names not LilyJazz?
> If can get a hold of that, and put it together with Kieren's suggestions,
> that's basically it - the rest is routine
On 18.01.2016 17:32, Urs Liska wrote:
This gives arguably the best option as default and still gives
Sibelius-converts the chance to redo their familiar shortcomings ;-)
Opinions?
LGTM :-)
Best, Simon
___
lilypond-user mailing list
Hi again,
some aspects of the discussion about beaming made me realize again that
we shouldn't always/only look for "the" solution but rather provide the
choices and set a sensible default. And this is probably true also for
the beam count at subdivisions.
Earlier (up to ca. 2.19.20) LilyPond
Hi Urs,
> This gives arguably the best option as default and still gives
> Sibelius-converts the chance to redo their familiar shortcomings ;-)
>
> Opinions?
LGreatTM!
Thanks for doing this.
Kieren.
Kieren MacMillan, composer
‣ website:
Am 18.01.2016 um 18:37 schrieb Simon Albrecht:
> On 18.01.2016 18:27, Urs Liska wrote:
>> Am 18.01.2016 um 18:24 schrieb Kieren MacMillan:
>>> Hi Urs,
>>>
c)
Take a) as the default and provide a context property
>>> This.
>>>
>>> Thanks,
>>> Kieren.
>>>
>> Any suggestions for a better
Hi!
I have just recently discovered the world of Lilypond and was really
pleased as long as I wrote the lyrics in English. When switching to Swedish
I ran into trouble. There are three specific characters in Swedish and only
onle of them is available in the Lilypond "list of special
Karin:
> I have just recently discovered the world of Lilypond and was really
> pleased as long as I wrote the lyrics in English. When switching to Swedish
> I ran into trouble. There are three specific characters in Swedish and only
> onle of them is available in the Lilypond "list of special
Hi David,
2016-01-18 22:56 GMT+01:00 David Sumbler :
> After spending some hours trying to get to the bottom of this problem,
[...]
Well, I spend some hours creating the function(s) ;)
> I narrowed it down to 3 different elements in my files
[...]
> I feel
> that ideally an
On 1/18/16 10:28 AM, "Kieren MacMillan"
wrote:
>Hi Urs,
>
>> deep in my heart I also feel we shouldn't support incorrect notation
>
>Well, okay, thenŠ Let's eliminate the ability to move NoteHead to the
>wrong side of Stem, block \rotate from affecting e.g.,
> On Jan 18, 2016, at 5:07 PM, Malte Meyn wrote:
>
>
>
>> Am 18.01.2016 um 23:52 schrieb Mark Stephen Mrotek:
>> In 2.18,
>>
>> Tuplet - no number\override TupletNumber #'stencil = ##f
>
> Setting the stencil to ##f is exactly what \omit does ;) (\omit already
>
> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote:
>
> I was wondering if it would be possible to develop a variant of "all on
> one line", namely "all on one page", where the page height would be
> automatically adjusted to fit the music, leaving the width as set.
I’m
2016-01-19 1:04 GMT+01:00 Thomas Morley :
> Hi David,
>
> 2016-01-18 22:56 GMT+01:00 David Sumbler :
>
>> After spending some hours trying to get to the bottom of this problem,
> [...]
>
> Well, I spend some hours creating the function(s) ;)
>
>> I
On 1/18/16 3:30 PM, "Sharon Rosner" wrote:
>In many cases this would not be such a problem, as the highest object on
>the
>top staff would be the bar number. But in cases where there are high notes
>on ledger lines, or other objects high above the top staff, this would
>lead
Hi Karin,
Lilypond is Unicode aware. HTML escape codes have no relevance to lilypond. Any
editor that supports Unicode will allow you to type Swedish, and there is no
need for ‘special characters’.
Frescobaldi is highly recommneded as a lilypond programming environment.
Andrew
> On Jan 18, 2016, at 1:44 AM, Carl-Henrik Buschmann
> wrote:
>
>
>> 18. jan. 2016 kl. 02.40 skrev tim...@bitstream.net:
>>
>>>
>>> On Jan 17, 2016, at 4:16 PM, Carl-Henrik Buschmann
>>> wrote:
>>>
>>> While i might agree with you to some extent
Greetings All,
I am generating parts from an orchestral score and am wondering if
there is any way of handling percent repeats in the same manner as
\compressFullBarRests does for multimeasure rests? That is, a number
would be placed above, say, an isolated repeat informing the player
how many
>> b) Always do the second version (i.e. shorten to indicate the
>>shortened length of the beam)
I prefer this, and it seems to me that this would be a good default.
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote:
>
> I was wondering if it would be possible to develop a variant of "all on
> one line", namely "all on one page", where the page height would be
> automatically adjusted to fit the music, leaving the width as set.
I’m
On 19.01.2016 01:52, Andrew Bernard wrote:
Hi Karin,
Lilypond is Unicode aware. HTML escape codes have no relevance to
lilypond.
There are the text replacements, see NR A.13 (2.19.35).
Best, Simon
___
lilypond-user mailing list
Simon Albrecht:
> On 18.01.2016 22:18, k...@aspodata.se wrote:
> > Simon Albrecht:
> >> On 18.01.2016 22:03, Karin Glasmästar wrote:
> >>> Now I found the way to what Karl wrote: I am using the built-in
> >>> crude editor of Lilypond itself - doesn't that editor support UTF-8?
> >> I don’t know,
Am 18.01.2016 um 23:46 schrieb Stanton Sanderson:
> How does one revert \omit TupletNumber to allow the number to appear for a
> specific tuplet?
There are two options:
1. If you want to omit only one TupletNumber you can use \once:
… \once \omit TupletNumber \tuplet …
2. Revert the
Am 18.01.2016 um 23:52 schrieb Mark Stephen Mrotek:
> In 2.18,
>
> Tuplet - no number\override TupletNumber #'stencil = ##f
Setting the stencil to ##f is exactly what \omit does ;) (\omit already
exists in 2.18)
___
lilypond-user mailing list
On 18.01.2016 22:03, Karin Glasmästar wrote:
Now I found the way to what Karl wrote: I am using the built-in crude editor of
Lilypond itself - doesn't that editor support UTF-8?
I don’t know, I’m not even sure if there is a Linux version of it. Anybody?
Best, Simon
BR,
Karin
Hi Karin,
first: we use to keep all the discussions on-list. Thus others may step
in (e.g. if I cannot help with the editor you are using – which is
likely…) or retrieve the information from the list archives.
On 18.01.2016 21:58, Karin Glasmästar wrote:
Hi!
Thanks for fast answer. It's
Simon Albrecht:
> On 18.01.2016 22:03, Karin Glasmästar wrote:
> > Now I found the way to what Karl wrote: I am using the built-in
> > crude editor of Lilypond itself - doesn't that editor support UTF-8?
> I don’t know, I’m not even sure if there is a Linux version of it. Anybody?
As far as I
Hello
I'm currently exploring layout in lilypond and have come across a problem
which I haven't noticed before and it's kind of a show stopper for me. In
Elaine Gould's excellent "Behind bars" she states:
"Match the levels of top and bottom staves across facing pages, regardless
of whether the
How does one revert \omit TupletNumber to allow the number to appear for a
specific tuplet? In the following example, I would like to show the tupet
number in the second measure. Thanks in advance.
Stan
\version "2.19.35"
\relative c'' {
c \omit TupletNumber \tuplet 3/2 {c4 b8}
On Sun, 2016-01-17 at 20:15 +0100, Thomas Morley wrote:
> 2016-01-17 19:21 GMT+01:00 David Sumbler :
>
> >
> > The only trouble is, I am getting a lot of compiler errors and warnings.
> > For each of the relevant layout blocks, I get:
> >
> > programming error: infinite rod
>
Mark
Thanks for the very complete answer. Malte’s method ( \undo \omit TupletNumber
) is almost too obvious! Both work exactly aa hoped.
Stan
> On Jan 18, 2016, at 4:52 PM, Mark Stephen Mrotek wrote:
>
> Stan,
>
> In 2.18,
>
> Tuplet - no bracket \override
Stan,
In 2.18,
Tuplet - no bracket \override TupletBracket #'bracket-visibility = ##f
Tuplet - no number \override TupletNumber #'stencil = ##f
Tuplet - number \revert TupletNumber #'stencil
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
On 18.01.2016 20:33, Karin wrote:
Hi!
I have just recently discovered the world of Lilypond and was really
pleased as long as I wrote the lyrics in English. When switching to Swedish
I ran into trouble. There are three specific characters in Swedish and only
onle of them is available in the
On 18.01.2016 22:18, k...@aspodata.se wrote:
Simon Albrecht:
On 18.01.2016 22:03, Karin Glasmästar wrote:
Now I found the way to what Karl wrote: I am using the built-in
crude editor of Lilypond itself - doesn't that editor support UTF-8?
I don’t know, I’m not even sure if there is a Linux
Martin Tarenskeen:
> On Mon, 18 Jan 2016, k...@aspodata.se wrote:
> > Example:
> > http://turkos.aspodata.se/git/musik/songs/pilgrimssaang_1200.ly
> Unfortunately not a fully working example, because of the two \include
> statements at the beginning of the file:
>
> \include
70 matches
Mail list logo