Dear Harm,
Am 15.01.2015 um 03:22 schrieb Thomas Morley:
arpeggioUp =
-\tweak #'stencil #ly:arpeggio::print
-\tweak #'X-extent #ly:arpeggio::width
-\tweak #'arpeggio-direction #UP
\arpeggio
I came back to this today and I like this simple approach most.
One more question: what are the
be converted to the
-\tweak syntax and I think that it would make them all a little easier to
use.
-Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/arpeggioArrowUp-tp170464p171231.html
Sent from the User mailing list archive at Nabble.com
Am 29.01.2015 um 18:08 schrieb tisimst:
Nice work, Harm!
+1
Anyone willing to help get this (and similar code for arpeggioDown) pushed
into property-init.ly? Shouldn't be too hard to get through and would be a
nice (i.e., more intuitive) syntax, especially for new users, IMHO.
+1
I also
once more a look at it and I'm not convinced that we
should change all the commands to tweak commands for some reasons:
%%%
1)
%%%
arpeggioArrowUp is currently defined as
arpeggioArrowUp = {
\revert Arpeggio.stencil
\revert Arpeggio.X-extent
\override Arpeggio.arpeggio-direction = #UP
Thank you Harm.
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
, I'd rather not have to use another function (\foo) to do this.
Otherwise, I don't think there's any benefit over what is currently required
with \arpeggioArrowUp. Can't it be put directly into a command that supports
the direction indicators? I can't seem to find in the documentation where
\arpeggio
}
I like this one.
Cheers,
Pierre
+1!
However, I'd rather not have to use another function (\foo) to do this.
Otherwise, I don't think there's any benefit over what is currently
required
with \arpeggioArrowUp. Can't it be put directly into a command that
supports
required
with \arpeggioArrowUp. Can't it be put directly into a command that supports
the direction indicators? I can't seem to find in the documentation where
the post-fix syntax is described.
-Abraham
The direction indicators _ and ^ are setting the 'direction, as their
name suggests
this.
Otherwise, I don't think there's any benefit over what is currently required
with \arpeggioArrowUp. Can't it be put directly into a command that supports
the direction indicators? I can't seem to find in the documentation where
the post-fix syntax is described.
-Abraham
The direction indicators
-processing
g b d g4\arpeggio
g b d g4^\arpeggio
g b d g4_\arpeggio
}
I like this one.
Cheers,
Pierre
+1!
However, I'd rather not have to use another function (\foo) to do this.
Otherwise, I don't think there's any benefit over what is currently
required with \arpeggioArrowUp. Can't
tisimst and Hwaen - Thanks for your replies. Like may things, the answer is
simple once it is pointed out to you.
Alistair
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/arpeggioArrowUp-tp170464p170478.html
Sent from the User mailing list archive at Nabble.com
Hi Abraham,
Am 14.01.2015 um 17:24 schrieb tisimst:
P.S. I'm with Alistair, though. Is there any reason \arpeggioArrow[Up/Down]
isn't designed to work by itself rather than requiring another explicit
\arpeggio?
I think, it is simply implemented in analogy to all the other Up/Down/Neutral
Can anyone tell me why \arpeggio works OK but \arpeggioArrowUp does not? When
I use it, no arpeggio line is displayed, not even one without an arrow.
Thanks
Alistair Millar
Edinburgh
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/arpeggioArrowUp-tp170464.html
Sent from
Hi Harm,
2015-01-15 3:22 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
foo =
#(define-music-function (parser location mus)(ly:music?)
(music-map
(lambda (m)
(if (music-is-of-type? m 'arpeggio-event)
(make-music
'ArpeggioEvent
'tweaks
\overrides persists!\
g b d g\arpeggio
\mark \arpeggioArrowUp clears overrides\
\arpeggioArrowUp
g b d g\arpeggio
g b d g\arpeggio
}
foo =
#(define-music-function (parser location mus)(ly:music?)
(music-map
(lambda (m)
(if (music-is-of-type? m 'arpeggio-event)
(make
- Original Message -
From: Alistair Millar alistair.mil...@blueyonder.co.uk
To: lilypond-user@gnu.org
Sent: Wednesday, January 14, 2015 3:40 PM
Subject: arpeggioArrowUp
Can anyone tell me why \arpeggio works OK but \arpeggioArrowUp does not?
When
I use it, no arpeggio line
I hope this is enough. Thanks
\version 2.18.2
\language english
\relative c'
{
\clef treble
\time 4/4
\key g \major
g b d g4\arpeggio
g b d g4\arpeggioArrowUp
\bar |.
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/arpeggioArrowUp-tp170464p170466
Alistair Millar wrote
I hope this is enough. Thanks
\version 2.18.2
\language english
\relative c'
{
\clef treble
\time 4/4
\key g \major
g b d g
4\arpeggio
g b d g
4\arpeggioArrowUp
\bar |.
}
Alistair,
It does work, just not in the way you (or I
Greetings Alistair,
The solution is actually quite simple. \arpeggioArrowUp is an override
setting of \arpeggio, so it must be entered before the chord you want
arpeggiated. Then, append \arpeggio to your chord, and all should be
fine. But remember then to revert to the arpeggio default
Hi!
\arpeggioArrowUp don't work in the polyphony!
\version 2.15.7
\paper { ragged-right = ##t }
\new Staff
\with
{
\consists Span_arpeggio_engraver
}
\relative c''
{
\set Staff.connectArpeggios = ##t
{\arpeggioArrowUp ces\arpeggio}
\\
{\arpeggioArrowUp es,\arpeggio
oiram73 wrote:
Hi!
\arpeggioArrowUp don't work in the polyphony!
\version 2.15.7
\paper { ragged-right = ##t }
\new Staff
\with
{
\consists Span_arpeggio_engraver
}
\relative c''
{
\set Staff.connectArpeggios = ##t
{\arpeggioArrowUp ces\arpeggio
Your code compiles fine, giving a nice output with 2.14.2 ! ???
Harm
You are sure? Your pdf output print the arrow?
In the mine no!
--
oiram/bin/selom
MkarlM-HomePage
___
lilypond-user mailing list
lilypond-user@gnu.org
On 19/08/11 01:57, Mario Moles wrote:
Your code compiles fine, giving a nice output with 2.14.2 ! ???
Harm
You are sure? Your pdf output print the arrow?
In the mine no!
No arrow on the arpeggio with 2.15.8 either, but you can use the following:
\version 2.15.7
\paper { ragged-right
Oohhh!
Yes! Yes! Yes!
Thank you!
No arrow on the arpeggio with 2.15.8 either, but you can use the following:
\version 2.15.7
\paper { ragged-right = ##t }
\new Staff
\with
{
\consists Span_arpeggio_engraver
}
\relative c''
{
\set Staff.connectArpeggios = ##t
\override
\set PianoStaff.connectArpeggios = ##f
Use these instead:
\connectArpeggiosOn
\connectArpeggiosOff
Also, don't use this type of thing anymore:
\override PianoStaff.Arpeggio #'arpeggio-direction = #UP
Use these commands in all situations (connected and unconnected):
\arpeggioArrowUp
--- On Mon, 8/3/09, Mark Polesky markpole...@yahoo.com wrote:
From: Mark Polesky markpole...@yahoo.com
Subject: Re: \arpeggioArrowUp across staves
To: Jonathan Wilkes jancs...@yahoo.com, Mats Bengtsson
mats.bengts...@ee.kth.se, lilypond-user lilypond-user@gnu.org
Date: Monday, August 3
Jonathan Wilkes wrote:
I guess I would have expected \arpeggioArrowUp to affect all the
following arpeggios, regardless of whether they are connected or not.
What do you think?
Ah, I put a context where I meant to put a parent. This is why
I need someone to test this stuff. You can fix
Mark Polesky wrote:
Yes, but this is tricky enough that I think something should be
added to the docs. Maybe when I have some time I can do that,
Why not add it to the LSR?
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
Mats Bengtsson wrote:
Yes, but this is tricky enough that I think something should be
added to the docs. Maybe when I have some time I can do that,
Why not add it to the LSR?
First I'd like to see what the general opinion is on this:
Why not add it to the LSR?
/Mats
I think a note about arrowed arpeggios that cross staves would be helpful
under the Arpeggios-Known issues and warnings subheading in NR 1.3.3.
There's such a note about cross-staff tremolos being tricky, which saved me
from trying a bunch of
Hi,
I've tried every combination of \arpeggioArrowUp, connectArpeggios, and/or
arpeggio-direction to get a squiggly arpeggio with an upward arrow that
spans both staves of a PianoStaff, but nothing seems to work.
Is it possible? I'm looking at the arpeggio examples in 1.3.3 as a guide
Oh, I'm using version 2.12.2 on winxp.
--- On Wed, 7/29/09, Jonathan Wilkes jancs...@yahoo.com wrote:
From: Jonathan Wilkes jancs...@yahoo.com
Subject: \arpeggioArrowUp across staves
To: lilypond-user@gnu.org
Date: Wednesday, July 29, 2009, 6:50 AM
Hi,
I've tried every combination
Jonathan Wilkes wrote:
I've tried every combination of \arpeggioArrowUp, connectArpeggios, and/or
arpeggio-direction to get a squiggly arpeggio with an upward arrow that
spans both staves of a PianoStaff, but nothing seems to work.
Is it possible? I'm looking at the arpeggio examples
Wow that was quick. Thanks!
-Jonathan
--- On Wed, 7/29/09, Mark Polesky markpole...@yahoo.com wrote:
From: Mark Polesky markpole...@yahoo.com
Subject: Re: \arpeggioArrowUp across staves
To: Jonathan Wilkes jancs...@yahoo.com, lilypond-user@gnu.org
Date: Wednesday, July 29, 2009, 7:01 AM
34 matches
Mail list logo
