Hello Jan! I'm just testing out EE and I've come across the need to adress a
noteHead tweak in a note inside a chord. Looking for a solution, I came to
this post. Is this implemented?
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Thank you Thomas, that's very helpful!
2018-02-03 12:10 GMT-03:00 Thomas Morley :
> 2018-02-03 15:44 GMT+01:00 Stefano Troncaro :
> > Hi Thomas, thank you for your corrections!
> >
> > If I may ask, where are functions like event-chord-pitches
2018-02-03 15:44 GMT+01:00 Stefano Troncaro :
> Hi Thomas, thank you for your corrections!
>
> If I may ask, where are functions like event-chord-pitches documented?
A lot of definitions in .scm-files are not documented.
You may try the code attached to
Hi Thomas, thank you for your corrections!
If I may ask, where are functions like event-chord-pitches documented? I
have only found a list of functions with their name starting with "ly:". I
assumed those were named that way to differentiate Lilypond exclusive
functions from Scheme's own, but it
2018-02-03 3:52 GMT+01:00 Stefano Troncaro :
> After a lot of stumbling around I finally managed to expand Jan-Peters'
> function so that it can modify more than one note in a given chord. I
> attached it so its available for anyone interested in using it.
Hi Stefano,
Thank you for your help everyone!
After a lot of stumbling around I finally managed to expand Jan-Peters'
function so that it can modify more than one note in a given chord. I
attached it so its available for anyone interested in using it.
On the other hand, I too think that the real solution
Hi David (et al.),
> I think it would make a whole lot more sense to teach the Edition
> Engraver how to mark/identify and tweak single items.
+1
At the risk of opening a serious can-o'-worms… I would love for you (David K.)
— who has the best Lilypond-fundamentals programming mind I know — to
Jan-Peter Voigt writes:
> Hello Harm, Stéfano,
>
> I always underestimate the usability of before/after-line-breaking ...
> Based on Harms code I scratched a music-function to conditionally omit
> the accidental. This one can be used with the EE.
> It smells a bit hacky, but it
Am 02.02.2018 um 17:55 schrieb David Kastrup:
Jan-Peter Voigt writes:
Hello Harm, Stéfano,
I always underestimate the usability of before/after-line-breaking ...
Based on Harms code I scratched a music-function to conditionally omit
the accidental. This one can be used with
Hello Harm, Stéfano,
I always underestimate the usability of before/after-line-breaking ...
Based on Harms code I scratched a music-function to conditionally omit
the accidental. This one can be used with the EE.
It smells a bit hacky, but it seems to work and is extendable for other
use
Hello Harm, Stéfano,
I always underestimate the usability of before/after-line-breaking ...
Based on Harms code I scratched a music-function to conditionally omit
the accidental. This one can be used with the EE.
It smells a bit hacky, but it seems to work and is extendable for other
use
Hello Harm, Stéfano,
I always underestimate the usability of before/after-line-breaking ...
Based on Harms code I scratched a music-function to conditionally omit
the accidental. This one can be used with the EE.
It smells a bit hacky, but it seems to work and is extendable for other
use
I'm not sure if EE supports ApplyOutputEvents, but you could try something like
this:
⋘
\applyOutput Voice.Accidental
#(let ((n 1))
(lambda (grob ctx1 ctx2)
(if (= n 0)
(ly:grob-set-property! grob 'stencil #f))
(set! n (1- n
% Will omit the N-th
2018-02-02 3:55 GMT+01:00 Stefano Troncaro :
> @Thomas
> I was not aware that it was possible to write a function inside of a
> parameter of a grob, and that before-line-breaking and after-line-breaking
> served this purpose. The documentation describes them as booleans
@Jan-Peter
>
> *this is a feature I long to implement for quite some time. This means it
> is not possible with the EE right now. The following ideas came up to
> provide a solution: 1. add IDs to certain elements and allow addressing
> elements b ID. 2. Add tweaks with a predicate, e.g. at
2018-02-01 16:59 GMT+01:00 Stefano Troncaro :
> Ideally, I wanted a function
> that I could use with the edition-engraver to tweak target elements inside
> chords. I framed the question around accidentals in the post above, but
> ultimately I hoped to be able to use the
Stefano Troncaro writes:
>> *But you also can use stuff like \once \accidentalStyle forget I think to
>> similar effect.*
>>
>
> Thank you for the suggestion. Unfortunately, if you read my reply to
> Caarg98 you'll notice that I'm looking for something more flexible.
Hello Stéfano,
this is a feature I long to implement for quite some time. This means it
is not possible with the EE right now.
The following ideas came up to provide a solution: 1. add IDs to certain
elements and allow addressing elements b ID. 2. Add tweaks with a
predicate, e.g. at moment
@Caagr98
>
>
> *If you could be a bit more specific about your goal (hiding all sharps?
> Hiding accidentals on even-indexed notes? Hiding accidentals specifically
> on cis?), that would make it possible to make a more specific function for
> your goals. (Note that this function can only be used
Stefano Troncaro writes:
> Hello again everyone!
>
> Suppose I have the following example:
>
> \version "2.19.80"\language "english"
> command = {
> %What should go here to omit the sharp while keeping the natural?}
> \score {
> \new Staff {
> \new Voice
In that case, you could use something like this:
⋘
\version "2.19.80"
nth =
#(define-music-function
(n tweak mus) (integer? ly:music? ly:music?)
(single tweak (list-ref (ly:music-property mus 'elements) n))
mus)
{
\nth 1 \omit Accidental % Remember, zero-indexed
}
⋙
If you could be
I just tried it, but unfortunately it appears to only work when used inside
the chord, and I need to find a way to do it from outside.
2018-01-31 17:39 GMT-03:00 Caagr98 :
> You could try \single instead of \once, as in cs,>.
>
> On 01/31/18 21:27, Stefano Troncaro wrote:
> >
You could try \single instead of \once, as in .
On 01/31/18 21:27, Stefano Troncaro wrote:
> Hello again everyone!
>
> Suppose I have the following example:
>
> \version "2.19.80" \language "english" command = { %What should go here to
> omit the sharp while keeping the natural? } \score {
Hello again everyone!
Suppose I have the following example:
\version "2.19.80"\language "english"
command = {
%What should go here to omit the sharp while keeping the natural?}
\score {
\new Staff {
\new Voice \relative c'' {
\key b \minor \accidentalStyle modern
\partial 4
Urs Liska u...@openlilylib.org writes:
Christ van Willegen cvwille...@gmail.com schrieb:
[Amadeus]
And if you'd life to get an F-natural in the key of D major, how would
you write that?
I'll look that up, I have got the manual.
My guess would be something like fn or its equivalent according
Urs Liska u...@openlilylib.org writes:
I find that very annoying, but he insists that it is in no way
ambiguous (because you always _see_ the score fragment you're working
on and the editor also always shows you the effective key). And he
insists that it is much more efficient simply because
On Fri, Apr 18, 2014 at 3:48 PM, Urs Liska u...@openlilylib.org wrote:
Actually I'm currently in a discussion with a (highly) professional engraver
using Amadeus (a Unix/Linux program that has been out of development for 15
years now but is still used by a number of professionals). Amadeus is a
I'll look that up, I have got the manual.
Christ van Willegen cvwille...@gmail.com schrieb am 19.04.2014:
On Fri, Apr 18, 2014 at 3:48 PM, Urs Liska u...@openlilylib.org wrote:
Actually I'm currently in a discussion with a (highly) professional
engraver
using Amadeus (a Unix/Linux program that
At 15:41 19/04/2014 +0200, Christ van Willegen wrote:
And if you'd life to get an F-natural in the key of D major, how
would you write that?
Clearly, following normal musical notation, you'd annotate the F in
some way as being not the expected F in D major (F#) - using
something such as fn.
Hi Brian,
Since you are [ostensibly] sitting on the fence… ;)
This is my “+1” for the cut-and-pastability (and, by extension,
variable-referencibility, etc.) of Lily-code as noted by David K.
Having engraved hundreds of Lilypond scores in the past 11 years — many with
dozens of movements, 50+
At 23:09 17/04/2014 -0300, Alfredo Noname wrote:
I sometimes have to write many accidentals in a bar and was
wondering if there was a way I could write the music in C major and
then transpose only the notes I need to be sharpened or flattened.
I'm not sure exactly what you mean here.
a.l.f.r.e.d.o lompo_la...@yahoo.se writes:
Hi, everybody.
I sometimes have to write many accidentals in a bar and was wondering
if there was a way I could write the music in C major and then
transpose only the notes I need to be sharpened or flattened.
Sure. You just need to mark the
Hi Brian,
2014-04-18 8:26 GMT+02:00 Brian Barker b.m.bar...@btinternet.com:
But perhaps you are referring to the method of textual input in Lilypond,
where notes that are named sharp or flat need to be qualified as such,
notwithstanding what the \key indication would appear already to imply.
Hi,
On Fri, Apr 18, 2014 at 7:41 AM, Thomas Morley thomasmorle...@gmail.comwrote:
Hi Brian,
2014-04-18 8:26 GMT+02:00 Brian Barker b.m.bar...@btinternet.com:
But perhaps you are referring to the method of textual input in Lilypond,
where notes that are named sharp or flat need to be
At 14:41 18/04/2014 +0200, Thomas Morley wrote:
2014-04-18 8:26 GMT+02:00 Brian Barker:
But perhaps you are referring to the method of textual input in
Lilypond, where notes that are named sharp or flat need to be
qualified as such, notwithstanding what the \key indication would
appear
At 07:57 18/04/2014 -0500, David Nalesnik wrote:
In my experience, speaking that sort of thing--calling F-sharp F ...
Sorry, but who made that suggestion, please? This was about
notation, not description!
On Fri, Apr 18, 2014 at 7:41 AM, Thomas Morley wrote:
... I don't want it
Am 18.04.2014 15:38, schrieb Brian Barker:
At 14:41 18/04/2014 +0200, Thomas Morley wrote:
2014-04-18 8:26 GMT+02:00 Brian Barker:
But perhaps you are referring to the method of textual input in
Lilypond, where notes that are named sharp or flat need to be
qualified as such, notwithstanding
Hi Brian,
On Fri, Apr 18, 2014 at 8:43 AM, Brian Barker b.m.bar...@btinternet.comwrote:
At 07:57 18/04/2014 -0500, David Nalesnik wrote:
In my experience, speaking that sort of thing--calling F-sharp F ...
Sorry, but who made that suggestion, please? This was about notation, not
At 08:58 18/04/2014 -0500, David Nalesnik wrote:
On Fri, Apr 18, 2014 at 8:43 AM, Brian Barker wrote:
By the way, if you get to have a thousand times as many votes as I
do, I'll make a note not to bother competing with you in any future
dispute. ;^)
Not sure how to take that, but I certainly
At 15:48 18/04/2014 +0200, Urs Liska wrote:
Am 18.04.2014 15:38, schrieb Brian Barker:
No - certainly not (though I know people who do!). You are quite
right not to believe I could be that foolish. But there is still a
difference in the representations: in musical notation, a note on
the F
in context:
http://lilypond.1069038.n5.nabble.com/Certain-accidentals-tp161597p161633.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
in context:
http://lilypond.1069038.n5.nabble.com/Certain-accidentals-tp161597p161637.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi, everybody.
I sometimes have to write many accidentals in a bar and was wondering if there
was a way I could write the music in C major and then transpose only the notes
I need to be sharpened or flattened. ___
lilypond-user mailing list
I think, if you don't specify a key at all, the music will always be in C (no
accidentals at the staff's beginning). Of course the notes have all necessary
accidentals.
Best, Robert
On 18 Apr 2014, at 04:09, a.l.f.r.e.d.o lompo_la...@yahoo.se wrote:
Hi, everybody.
I sometimes have to
44 matches
Mail list logo