Hi Kieren,
now I had a look into the autotranspose code. The problem is the order
of context properties set in the Staff. If you change the transposed
code to:
\new Staff \with \autoTranspose << \global \flutepart >>
It should get the key-signatures right. Though this is only a hint where
t
Hi again,
it needs some more thinking, how key signatures can be treated right for
this case. It is all about the timing - if you set the
instrumentTransposition with the editionEngraver, the properties are set
early and the keys look fine here.
I am going to add key-sigs to the EE, so that th
Am 14.03.2017 um 13:11 schrieb Urs Liska:
> From
> https://github.com/openlilylib/openlilylib/blob/master/notation-snippets/shaping-bezier-curves/shape-tie-column/definition.ily
> I got this:
> (let ((ties (ly:grob-array->list (ly:grob-object grob 'ties
> but in that case "grob" is a TieColu
Hi David (Nalesnik),
Am 14.03.2017 um 16:12 schrieb David Nalesnik:
> On Tue, Mar 14, 2017 at 9:46 AM, Urs Liska wrote:
>>
>> Am 14.03.2017 um 13:37 schrieb David Kastrup:
>>
>> (let ((ties (ly:grob-array->list (ly:grob-object grob 'ties
>>
>> but in that case "grob" is a TieColumn, and I d
On 15 March 2017 at 05:48, Robert Schmaus wrote:
> Just a thought - you apply the SpacingSpanner modifications to context
> \Score ... did you already try to apply those to context \ChordNames
> instead? That *does* change something, but I'm not sure if it is what you
> want ...
>
> Cool analysis,
Am 15.03.2017 um 01:11 schrieb Adam Spiers:
It would be very instructive to produce a clear visualisation of the
harmonic variations he uses in each chorus, so I have dropped the
notes of the solo from the .ly file, leaving only the chords, rendered
in landscape, with all the choruses vertically
On 15 March 2017 at 12:28, Simon Albrecht wrote:
> Am 15.03.2017 um 01:11 schrieb Adam Spiers:
>> It would be very instructive to produce a clear visualisation of the
>> harmonic variations he uses in each chorus, so I have dropped the
>> notes of the solo from the .ly file, leaving only the chord
Am 15/03/2017 um 14:54 schrieb Adam Spiers:
On 15 March 2017 at 13:45, Robert Schmaus wrote:
Hi Adam,
you're right ... I might have changed something else. Anyway, applying the
overrides to the Score seems to be the correct way.
I tried your file. Maybe you'll have to insert more line break
Hi Adam,
Adam Spiers-5 wrote
> On 15 March 2017 at 12:28, Simon Albrecht <
> simon.albrecht@
> > wrote:
>> why not put all the music expressions in one score in
>> parallel?
> But please could you give an example of how to do that, bearing in mind
> that
> there are no notes or staves, only ch
On 15 March 2017 at 14:35, Klaus Blum wrote:
> Adam Spiers-5 wrote
>> On 15 March 2017 at 12:28, Simon Albrecht wrote:
>>> why not put all the music expressions in one score in
>>> parallel?
>> But please could you give an example of how to do that, bearing in mind that
>> there are no notes or s
Dear All,
I noticed some weird behaviour with stem directions after compiling
(both on Linux and Windows).
Consider these two lines of code from a score:
\version 2.18.2
% bar 30
\relative bes'' << {bes4 c d} \\ {\relative bes'' {bes32 f d bes}
\change Staff = "lower" {f,, d bes f} \change S
On 15 March 2017 at 14:33, Robert Schmaus wrote:
> Am 15/03/2017 um 14:54 schrieb Adam Spiers:
>> On 15 March 2017 at 13:45, Robert Schmaus wrote:
>>> How about this:
>>>
>>> \context {
>>> \Score
>>> proportionalNotationDuration = #(ly:make-moment 1/10)
>>> \override SpacingSpanner.uniform
On Wed 15 Mar 2017 at 16:07:31 (+), Adam Spiers wrote:
> On 15 March 2017 at 14:33, Robert Schmaus wrote:
> > Am 15/03/2017 um 14:54 schrieb Adam Spiers:
> >> On 15 March 2017 at 13:45, Robert Schmaus wrote:
> >>> How about this:
> >>>
> >>> \context {
> >>> \Score
> >>> proportionalNotat
- Original Message -
From: "Gerard"
To:
Sent: Wednesday, March 15, 2017 4:07 PM
Subject: Unexpected stem behaviour
Dear All,
I noticed some weird behaviour with stem directions after compiling (both
on Linux and Windows).
Consider these two lines of code from a score:
\version 2.1
Am 15.03.2017 um 17:07 schrieb Gerard:
\version 2.18.2
% bar 30
\relative bes'' << {bes4 c d} \\ {\relative bes'' {bes32 f d bes}
\change Staff = "lower" {f,, d bes f} \change Staff = "upper" {c'''
bes f c} \change Staff = "lower" {bes f c bes} \change Staff = "upper"
{d'' bes f d} \change S
Hello!
My question concerns MIDI output. I wonder if there is way in Lilypond to
give every note a velocity value. I don't mean using dynamic markings, just
want to enhance the MIDI output by for example giving every note in a chord
a random velocity value. I know that Lilypond is primarily used
Hi Adam,
I have tried lots of solutions for this. I am thinking this cannot be
satisfactorily done in lilypond at this time. The attached solution
works up to a point, but the chord names clash. Using really large
paper - which I also tried - to gain space such as architectural A0
does not seem pr
On Thu 16 Mar 2017 at 12:40:28 (+1100), Andrew Bernard wrote:
> Hi Adam,
>
> I have tried lots of solutions for this. I am thinking this cannot be
> satisfactorily done in lilypond at this time. The attached solution
> works up to a point, but the chord names clash. Using really large
> paper - wh
I’m working on a project that involves one full size staff and several smaller
staves providing cues for other instruments. I’m using \magnifyStaff to
accomplish this, but it seems to be adjusting the horizontal spacing in ways
that I’m not liking. My hope is to have the spacing largely determ
19 matches
Mail list logo
