woops, I used % instead of ; in scheme
here the right code :)
Davide
\version "2.20.0"
#(define (split-music dir music ref)
(let ((es (ly:music-property music 'elements))
(e (ly:music-property music 'element))
(p (ly:music-property music 'pitch)))
(if (pair? es)
I did it!
the code works, but produces warnings.
Cheers
Davide
\version "2.20.0"
#(define (split-music dir music ref)
(let ((es (ly:music-property music 'elements))
(e (ly:music-property music 'element))
(p (ly:music-property music 'pitch)))
(if (pair? es)
(
Update:
\autoSplitChord \chordmode { c:/g}
doesn't work, but:
\chordmode { \autoSplitChord c:/g}
works.
So, if we can make \autoSplitChord accept sequences of music, that can
include chords or succession of chords, we'll have our goal.
Cheers
Davide
--
Questa e-mail è stata controllata
Hi Harm,
many thanks for testing.
thanks to you for the reply.
Below is an improved function which will simply returns the input, if
it's not an event-chord, avoiding the blank space.
\autoSplitChord << b \\ e' \\ g'' >> will stop working as well, all
notes are returned unchanged.
I see you'
Am Do., 7. Jan. 2021 um 13:08 Uhr schrieb Davide Bonetti
:
>
> Hi,
>
> Great work.
>
> I've done some testing and found some bugs. Below the code I've tested,
> attached the PDF with the result (on second page, first page are your
> examples).
>
> \autoSplitChord doesn't works with curly braces, i
Hi,
Great work.
I've done some testing and found some bugs. Below the code I've tested,
attached the PDF with the result (on second page, first page are your
examples).
\autoSplitChord doesn't works with curly braces, it returns blank output
(like a blank space in the score), so it's not po
Hi,
sometimes automatic cross-staff chords are requested here on the list.
After some thinking I come up with the code below.
Though, I suspect there are flaws in it, if used in real world codings.
I'd appreciate, if it would be tested in various situations.
Here the code:
\version &q
Thanks, Simon!
JM
> Le 7 avr. 2018 à 15:03, Simon Albrecht a écrit :
>
> On 07.04.2018 11:39, Jacques Menu Muzhic wrote:
>> When a hand doesn’t play, is it best for the keyboard player to read rests
>> or should skips be used instead?
>
> Definitely rests. Using skips is the convention if tha
On 07.04.2018 11:39, Jacques Menu Muzhic wrote:
When a hand doesn’t play, is it best for the keyboard player to read rests or
should skips be used instead?
Definitely rests. Using skips is the convention if that hand only
switched to the other staff.
There may be exceptions depending on cont
Hello Andrew,
When a hand doesn’t play, is it best for the keyboard player to read rests or
should skips be used instead?
JM
> Le 7 avr. 2018 à 11:11, Andrew Bernard a écrit :
>
> Hi JM,
>
> Speaking as a keyboard player myself, it's not just a matter of presenting
> the notes. Usually in c
Hello Rutger, Malte and Andrew,
I overlooked \crossStaff and didn’t get the Span_stem_engraver should be used,
sorry for that and for not removing the extraneous music in my last post.
Thanks for your help, and a nice day!
JM
> Le 7 avr. 2018 à 11:11, Andrew Bernard a écrit :
>
> Hi JM,
>
>
Hi JM,
Speaking as a keyboard player myself, it's not just a matter of presenting
the notes. Usually in contexts like this it can be an indication of which
hand takes what, with the upper staff being the RH and the lower the LH.
There's no hard and fast rule about that, (and some players don't eve
Am 07.04.2018 um 10:51 schrieb Menu Jacques:
I’m no pianist though: is this OK for a keyboard player, or is Finale’s
output: […] better, and if so, how can I obtain the cross-staves stems this way?
What is better depends on whether it should be played with one hand or
two. Please always give
\crossStaff { .. } for the
chords you want cross-staff? Be aware, you (probably) need to disable
auto-beaming and specify stem direction explicitly for those.
I applied these, the resulting .ly and .pdf are attached. It shows
cross-staff chords.
Rutger
On 04/07/2018 10:51 AM, Menu Jacques wrote
On 30 December 2010 22:30, Xavier Scheuer wrote:
>
> Hi!
>
> That's because you use a << { ... } \\ { ... } >> construct.
> Voices within that construct are different from voices outside this
> construct and then your \autoBeamOff does not apply to your "left UP"
> voice.
>
> 1. You could repl
have encountered a
> snag that does not seem to have an obvious solution. The problem is
> this. i am trying to make cross staff chords in a piano score.
> Following the example provided in the user manual works just fine
> until another voice in the bass is added at which point the re
problem is
this. i am trying to make cross staff chords in a piano score.
Following the example provided in the user manual works just fine
until another voice in the bass is added at which point the rendering
ignores the trickery used to make the chords appear to cross the
staff. So included is a
Hello, all!
Trevor offered
If any of the developers are looking for a sponsored project,
I would be happy to help sponsor this improvement
I second the offer -- especially if, as Trevor suggests, the fix handles
(1) non-grouped staves (e.g., not necessarily in a PianoStaff or
StaffGroup)
On 10/29/07, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote:
> Am Montag, 29. Oktober 2007 schrieb Trevor Bača:
> > Unfortunately, I know of no better way to create cross-staff chords
> > than the documentation you point to in the manual.
> >
> > I'm just fin
Am Montag, 29. Oktober 2007 schrieb Trevor Bača:
> Unfortunately, I know of no better way to create cross-staff chords
> than the documentation you point to in the manual.
>
> I'm just finishing a score with cross-staff chords, so I know what
> you're going through.
Y
On 10/27/07, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote:
> Hi,
> For the musicxml2ly application, I'm looking into how to convert cross-staff
> chords in PianoStaves (i.e. chords that have some notes in the upper and some
> in the lower staff). The documentation talk
Hi,
For the musicxml2ly application, I'm looking into how to convert cross-staff
chords in PianoStaves (i.e. chords that have some notes in the upper and some
in the lower staff). The documentation talks about these in
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Cross-staff-
ng stems and
> >a single beam.
>
> OK. This is a completely different feature than what Steve is looking
> for. It's also quite a bit easier, I suspect.
Yes, that does seem different. It's true that my interest in cross-staff
chords centers around their use in the context of
This is a completely different feature than what Steve is looking
> for. It's also quite a bit easier, I suspect.
Yes, that does seem different. It's true that my interest in cross-staff
chords centers around their use in the context of two adjacent staves
connected by a brace su
Trevor Bača wrote:
Yes, exactly. The notes can be separately articulated, with separate
accidentals and so on. What the notes share will be spanning stems and
a single beam.
OK. This is a completely different feature than what Steve is looking
for. It's also quite a bit easier, I suspect.
-
On 8/28/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Trevor Bača wrote:
> QUESTION: will the proposed cross-staff implementation path enable
> cross-staff stemming and beaming between *nonadjacent* staves (eg, 1st
> violins and basses, passing over the 2nd violins, violas and cellos)?
on 2nd
Trevor Bača wrote:
QUESTION: will the proposed cross-staff implementation path enable
cross-staff stemming and beaming between *nonadjacent* staves (eg, 1st
violins and basses, passing over the 2nd violins, violas and cellos)?
on 2nd thought, isn't this completely different from x-staff stemmin
Trevor Bača wrote:
> Well, if Steve or Vivian or Hans or somebody is willing to help out,
> then I'm willing to pitch in on the sponsoring too.
>
> I'm about to have cross-staff stuff all over some piano music and also
> between different *string* staves as well. So a question.
>
> QUESTION: will
On 8/23/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Trevor Bača wrote:
> On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> I once made an estimate for doing x-staff chords, for 400 EUR. I think
>> that would be the most difficult task. If the stems + noteheads work
>
Trevor Bača wrote:
On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hello,
I once made an estimate for doing x-staff chords, for 400 EUR. I think
that would be the most difficult task. If the stems + noteheads work
correctly, adding arpeggios and ties should be relatively easy.
For re
On Tue, Aug 22, 2006 at 10:29:49PM -0500, Trevor Bača wrote:
> On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >Hello,
> >I once made an estimate for doing x-staff chords, for 400 EUR. I think
> >that would be the most difficult task. If the stems + noteheads work
> >correctly, adding a
On 8/22/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hello,
I once made an estimate for doing x-staff chords, for 400 EUR. I think
that would be the most difficult task. If the stems + noteheads work
correctly, adding arpeggios and ties should be relatively easy.
For reference, I insert wh
e, hidden notes, etc.,
and in this case, the chord following the cross-staff grace-note
arpeggio was not itself a cross-staff chord. However, it would be great,
if it can be implemented, for the following to exist in LilyPond:
* chords that cross staves (perhaps like )
* cross-staff chords that can
I have in the past got Lilypond to do what you describe. The cross-staff chords are documented in the manual, although I agree the mechanism for achieving this is a bit clumsy (extending the stem from one of the chords.) I could imagine that to allow something like your example () could be a bit
dden notes, etc.,
and in this case, the chord following the cross-staff grace-note
arpeggio was not itself a cross-staff chord. However, it would be great,
if it can be implemented, for the following to exist in LilyPond:
* chords that cross staves (perhaps like )
* cross-staff chords that can be tie
35 matches
Mail list logo
