8 -1-3 ( 16 -2-4 -1-5 -2-4 -3-5 )
}
%%% END %%%
[image: Fingering-avoid-slur-ignore.png]
Trevor.
On Thu, May 9, 2024 at 10:25 AM Paul McKay wrote:
> Hi
> I want to show fingerings in front of slurs in a manner very like that
> demonstrated in the "Using the whiteout property&q
On Tue, Jul 30, 2024 at 5:57 AM David Kastrup wrote:
> Lukas-Fabian Moser writes:
>
> > You're using append! wrong.
> > So try
> >
> > (set! fl (append fl ...))
>
> (append! '() ...)
>
> cannot modify an empty list in-place because there is only one empty
> list in the whole system and it is an
Lukas-Fabian Moser writes:
> Hi Luca,
>
> without having tested your code: You're using append! wrong.
>
> From the Guile documentation: "append! is permitted, but not required, to
> modify the given lists to form its return."
> So the exclamation mark does not imply that your list gets modified
trying to understand a problem I'm seeing.
>
> I have this engraver that acknowledges stems and fingerings,
> this is meant to work with a before-line-breaking callback that
> repositions the fingerings.
> So I thought that I could just sit there, listen for the fingerings as
> t
Hi,
I'm trying to understand a problem I'm seeing.
I have this engraver that acknowledges stems and fingerings,
this is meant to work with a before-line-breaking callback that repositions
the fingerings.
So I thought that I could just sit there, listen for the fingerings as they
got
(display (assoc-get 'fingering (ly:grob-property stem
'details)))
(display "\n")))
(set! stem #f)
(set! fingering #f)
In the if scope right at the start of process-music, I'm trying to make a
list of all the fingerings seen for the cur
6/20/2024 5:00 PM, Fennel wrote:
>
> Hi all,
>
> Getting this behavior when trying to put fingerings in column format on
> chords:
>
> \version "2.24.3"
> \relative c'' {
> \set fingeringOrientations = #'(left)
>
> }
>
> I’d like
baseline-skip seems to do the job:
||
Found here: LilyPond snippets: Tweaks and overrides
<https://lilypond.org/doc/v2.23/Documentation/snippets/tweaks-and-overrides>
Regards,
Curt
On 6/20/2024 5:00 PM, Fennel wrote:
Hi all,
Getting this behavior when trying to put fingerings in
Hi all,
Getting this behavior when trying to put fingerings in column format on chords:
\version "2.24.3"
\relative c'' {
\set fingeringOrientations = #'(left)
}
I’d like the 1 to be much closer to the 2. Does anyone know the correct
property to adjust to make t
Hi Fennel,
This might be a little hacky, but…
%%% SNIPPET BEGINS
\version "2.24.3"
"fing13" =
\tweak X-offset #-1
\tweak Y-offset 0
\finger \markup \override #'(baseline-skip . 1.25) \column { "1" "3" }
\relative c'' {
<< { c4 d-2 } \\ a2-\"fing13" >>
}
%%% SNIPPET ENDS
You could ea
Hi
I want to show fingerings in front of slurs in a manner very like that
demonstrated in the "Using the whiteout property" snippet
This is what I've tried:
\version "2.24.0"
\language "english"
\relative {
\override Staff.Fingering.layer = 2
Yeah, I came across one of those bass clef, Bb transposed parts a couple of
months ago. Hit the whole trombone section for a six.
I've spent a lot of time delving though pre-Baroque manuscripts, both
handwritten and printed. One upside of this is a working familiarity with
all manner of clefs. Lil
On 31/10/2023 01:36, Adam M. Griggs wrote:
Your second recommendation is situational. I see you have a *.uk
email address. I'm familiar with the British brass band context. I get
it—almost everything is transposed for instruments pitched in Bb or Eb,
and in the entire ensemble, only bass trombo
Hi Wol,
Thank you for your feedback. You have a point in your first suggestion. My
pianist's visualisation of the pitch gamut overrode my trombone experience,
hence the grand staff. If I were to forego it in favour of a single staff,
I'd start with a tenor clef and switch to bass when appropriate.
On 29/08/2023 15:35, Adam M. Griggs wrote:
Here's a little self-help reference I made a little while back. Maybe it
will illustrate your point about different positions for different
octaves more clearly than words can.
Perhaps something in the tablature code can be adapted to this end.
Ouch
On Wed, Aug 30, 2023 at 2:45 AM samarutuk wrote:
> Hello Carl,
>
> Michael (Werner) may have just found a solution.
>
Yes, I really like Michael's solution. He found an existing context and
grob that he could tweak into a brass position indicator. I think that is
a very clever approach to gett
On 30/08/2023 09:17, samarutuk wrote:
Hi Michael,
thanks a lot, this looks very, very promising! I will fine tune it a bit
more and then send it back to this list. The great thing is that you can
also adapt it for other brass instruments e.g. tuba, French horn etc. I
think the Lilypond code f
our digits (see screenshot in attachment) and sometimes also
other characters or brackets for alternate fingerings/slide positions.
Kind regards
Andreas
You may not be aware of this, but LilyPond is developed and maintained
by volunteers.
If you wish to have fingering information for b
Sat, Aug 26, 2023 at 8:45 AM samarutuk wrote:
Hello,
I have been looking for a long time for a way to automatically
annotate slide positions or fingerings for brass instruments below
or above the notes. There have been one or two requests for this,
but never a complete so
or relative in Lilypond, you would always have to use the absolute
pitch (also for transposing instruments) as basis, so that the
assigned slide positions or fingerings are correct.
Yup. Just remember that defaults aren't always right ... 1+3 doesn't
always equal 4 ...
I was lookin
On Sat, Aug 26, 2023 at 8:45 AM samarutuk wrote:
> Hello,
>
> I have been looking for a long time for a way to automatically annotate
> slide positions or fingerings for brass instruments below or above the
> notes. There have been one or two requests for this, but never a comp
ys have to use the absolute pitch
(also for transposing instruments) as basis, so that the assigned slide
positions or fingerings are correct.
Yup. Just remember that defaults aren't always right ... 1+3 doesn't
always equal 4 ...
I was looking at doing something like this, but
so other
> characters or brackets for alternate fingerings/slide positions.
>
> Kind regards
> Andreas
>
You may not be aware of this, but LilyPond is developed and maintained by
volunteers.
If you wish to have fingering information for brass instruments
automatically calculated by
). So no matter if you notate notes absolute or relative in
> Lilypond, you would always have to use the absolute pitch (also for
> transposing instruments) as basis, so that the assigned slide positions or
> fingerings are correct.
> Here is my slightly modified code to better illustrate wh
samarutuk via LilyPond user discussion writes:
> Hi,
> I am not sure if I understand "iterated music" correctly? Is it about
> the internal order of processing to get to the PDF score?
"Iteration" is the main processing pass of music in musical time order.
There are several processing stages fo
ou notate notes absolute or
relative in Lilypond, you would always have to use the absolute pitch
(also for transposing instruments) as basis, so that the assigned slide
positions or fingerings are correct.
Here is my slightly modified code to better illustrate what I mean
regarding pitch and
Hi,
I'm not sure I understand your problem. If I infer your
goal from the ChatGPT output, you're trying to add a fingering
to each note based on its pitch. Is that right?
```
\version "2.24.2"
#(use-modules (srfi srfi-2))
autoFingerings =
#(define-music-function (spec music) (ly:music? ly:mus
Hello,
I have been looking for a long time for a way to automatically annotate
slide positions or fingerings for brass instruments below or above the
notes. There have been one or two requests for this, but never a
complete solution, at least the oracle of Google has not been able to
tell me
Hi Matthew,
How do I keep the new key signature from also appearing at the end of
the previous line?
Also, how can I write { 1 x 2 4 } in the fingering font, adding an "x"
between the notes to signify the extension between "1" and "2"?
One possibility would be
\version "2.24.0"
\relative
_
From: William Rehwinkel
Sent: Tuesday, December 20, 2022 7:28 PM
To: Matthew Pierce; lilypond-user@gnu.org
Subject: Re: extension fingerings, key sigs
Dear Matt,
This snippet should answer both of your questions, let me know if you have any
other questions about this.
Depending on exactl
Dear Matt,
This snippet should answer both of your questions, let me know if you
have any other questions about this.
Depending on exactly what you were intending to do, you may want to
consider putting each exercise in a separate score block, like shown in
the example. This avoids all pro
I am writing a scale page for my cello students. Since each line is a new
scale, each line has a new key signature.
Two basic questions:
How do I keep the new key signature from also appearing at the end of the
previous line?
Also, how can I write { 1 x 2 4 } in the fingering font, adding an "
Hello, I would like to indicate fingerings for a pitched trill, and also
be able to control where they appear. The
\set fingeringOrientations = #'(left) is ignored in the trill context, and
the fingering is ignored for the secondary note of the trill. Any ideas?
regards, Jim
\version &q
end for appending a small
amount of elements, just cons them together.
About collisions: To get proper support you’d need to go into the details of
the Beam position calculation and adapt it to incorporate fingerings. But if
you look at my solution you can see a way how we can only handle those
p
Hi Valentin,
thanks for the super prompt reply!
On Sun, Mar 6, 2022 at 5:34 PM Valentin Petzel wrote:
> So instead of doing the assoc-set! you might want to do something like
>
> (ly:grob-set-property! grob 'details `((beamed-lengths . ,stem-bmlgths)
> . ,detls))
>
For my edification, I'l
d of pushing the fingering
> >> > "down" (say we're doing \stemsUp) because the beams are too low,
> >> > to push the beams "up" to leave space for the fingering. And I played
> >>
> >> for a
> >>
> >> > second with
ple one-liner breadcrumbs such as "this section of
> the
> > docs" (which I tried to read without much success),
> > "grep and in the source", it's all in "scm/ > filenames>". Vague pointers like that are hopefully all I'll need.
> >
thout much success),
> "grep and in the source", it's all in "scm/ filenames>". Vague pointers like that are hopefully all I'll need.
>
> Many thanks,
> Luca
>
> On Mon, Feb 21, 2022 at 6:49 PM Luca Fascione wrote:
> > Yes exactly, because o
readability with the indication right at the head is
> enormous.
>
> L
>
> On Mon, 21 Feb 2022, 18:16 Valentin Petzel, wrote:
>
>> Sure. I suppose for a guitar person having stacked fingerings on top
>> would be
>> rather confusing, as there is no mono
Yes exactly, because of how our finger to note relation works, the
enhancement in readability with the indication right at the head is
enormous.
L
On Mon, 21 Feb 2022, 18:16 Valentin Petzel, wrote:
> Sure. I suppose for a guitar person having stacked fingerings on top would
> be
&g
Sure. I suppose for a guitar person having stacked fingerings on top would be
rather confusing, as there is no monotonic relating between finger and pitch.
As such I suppose guitar people would want to use fingerings with left or right
orientations in chords anyway.
Cheers,
Valentin
Am Montag
b 21, 2022 at 5:42 PM Valentin Petzel wrote:
> No, not nescessarily. If we want all Fingerings on top or below there is
> no real benefit of doing the chord thing. In fact doing that leads to the
> exact same issue of the fingering for d being next to the other ones.
>
> Cheers,
>
No, not nescessarily. If we want all Fingerings on top or below there is no
real benefit of doing the chord thing. In fact doing that leads to the exact
same issue of the fingering for d being next to the other ones.
Cheers,
Valentin
21.02.2022 12:38:40 Luca Fascione :
> But wouldn
this should go to
> -user
> > >
> > > or
> > >
> > > > > -devel.
> > > > >
> > > > > I'm looking for some guidance to set up fingering on classical
> guitar
> > > > > sheets.
> > > > >
>
to me even for proper chords the whole FingeringColumn idea
> > is also a weird concept: imagine you're in say C major, and you're laying
> > out fingering on the left of a chord like Fm : I'm very unclear
> > whether the most readable solution is to have the fingerings st
rd like Fm : I'm very unclear
> whether the most readable solution is to have the fingerings stacked one
> atop each other in a column (thereby more distant from f and c because of
> the intervening flat on the aes) or if instead the fingerings on f and c
> should be set tighter to the
ing some
> > > > trickery
> > > > involving one-note chords, purely to show a sample of what the result
> >
> > I'm
> >
> > > > after (and it's an approximation), vs what I get at the moment.
> > > >
> > > > Me
Hello Harm,
That is not exactly true. As I have done in my previous reply we can create an
engraver that acknowledges Fingerings and NoteHeads and store a reference to
the NoteHead grob in the Fingerings details property.
Cheers,
Valentin
Am Montag, 21. Februar 2022, 01:22:18 CET schrieb
7;re laying
out fingering on the left of a chord like Fm : I'm very unclear
whether the most readable solution is to have the fingerings stacked one
atop each other in a column (thereby more distant from f and c because of
the intervening flat on the aes) or if instead the fingerings on f and c
s
> after (and it's an approximation), vs what I get at the moment.
> > >
> > > Measures 1-5 in the source look like what I am intending to type, but
> it
> > > has a number of engraving defects I don't understand (you can see the
> > > beams
>
Am So., 20. Feb. 2022 um 22:41 Uhr schrieb Luca Fascione :
> a) I'm looking for a way to get the fingerings where I want them without
> using one-note-chord tricks
Well, for Fingerings not in chord, like b-1 or -2-1 X-parent
is NoteColumn _not_ NoteHead, Y-parent is VerticalAxisGrou
e chords, purely to show a sample of what the result I'm
> > after (and it's an approximation), vs what I get at the moment.
> >
> > Measures 1-5 in the source look like what I am intending to type, but it
> > has a number of engraving defects I don't understa
n deleting my source.
Going back to the example itself, there are two questions in flight here:
a) I'm looking for a way to get the fingerings where I want them without
using one-note-chord tricks
b) I'm also looking to position fingering a bit more finely than what the
second piece show
Le 20/02/2022 à 21:17, Luca Fascione a écrit :
So... would anybody be able to lend a hand here please?
Many thanks
Luca
It would be helpful if you provided smaller examples.
I'm not saying this as a reprimand, but as friendly
advice on how to get people to help you. Personally,
I had started
t; after (and it's an approximation), vs what I get at the moment.
>
> Measures 1-5 in the source look like what I am intending to type, but it
> has a number of engraving defects I don't understand (you can see the beams
> don't avoid the fingerings, nor they are located cor
Am Mi., 14. Apr. 2021 um 11:48 Uhr schrieb Thomas Morley
:
>
> Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra
> :
> >
> >
> > Le 13/04/2021 à 23:18, Thomas Morley a écrit :
> >
> > Hi,
> >
> > let's say I've a chord with F
Am Mi., 14. Apr. 2021 um 11:48 Uhr schrieb Thomas Morley
:
>
> Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra
> :
> >
> >
> > Le 13/04/2021 à 23:18, Thomas Morley a écrit :
> >
> > Hi,
> >
> > let's say I've a chord with F
>
> {
>\set fingeringOrientations = #'(left)
>\once \override Staff.FingeringColumn.positioning-done =
> #(lambda (grob)
> (let* ((fingering-array (ly:grob-object grob 'fingerings))
>(fingerings (ly:grob-array->list fingering-array)))
Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra :
>
>
> Le 13/04/2021 à 23:18, Thomas Morley a écrit :
>
> Hi,
>
> let's say I've a chord with Fingerings left.
> Now I want to tweak a certain Fingering a little bit up/down and left/right.
>
>
(let* ((fingering-array (ly:grob-object grob 'fingerings))
(fingerings (ly:grob-array->list fingering-array)))
(for-each
(lambda (fingering x y)
(ly:grob-translate-axis! fingering x X)
(ly:grob-translate-axis! fingering
ks work if there is only one fingering in the
> chord.
>
> \set fingeringOrientations = #'(left)
>
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer
>
Yeah, I noticed already. And it contradicts reasonable user-expectations.
Viewing it from inside LilyPond: the situati
On Wed, 14 Apr 2021 at 10:31, Jean Abou Samra wrote:
>
>
> Hi,
>
> Something very weird seems to be going
> on. Try:
Hello,
Speaking of weird, the tweaks work if there is only one fingering in the
chord.
\set fingeringOrientations = #'(left)
Cheers,
Xavier
--
Xavier Scheuer
Le 13/04/2021 à 23:18, Thomas Morley a écrit :
Hi,
let's say I've a chord with Fingerings left.
Now I want to tweak a certain Fingering a little bit up/down and left/right.
How to do so?
Here a minimal to play with:
{
\set fingeringOrientations = #'(left)
%% belo
Hi,
let's say I've a chord with Fingerings left.
Now I want to tweak a certain Fingering a little bit up/down and left/right.
How to do so?
Here a minimal to play with:
{
\set fingeringOrientations = #'(left)
%% below does not work
\once \override Fingering.Y-offs
Just a follow up to say that (almost) all my problems have been resolved by
moving from 32-bit Lilypond on Windows to 64-bit Lilypond on Linux. Many
thanks to all the kind folk who have helped me try to determine the
causes. Problems left are minor syntactical ones which I'll wrestle with
quiet
It's got even worse. Now I can barely do anything. This bar:
f,-1 f'-3 f, f' g,-2 f' |
now causes that error - also without the fingerings. I don't know what to
do.
On Sat, Sep 12, 2020 at 11:48 AM Alasdair McAndrew wrote:
> Thanks David.
>
> What a pain.
Tiny examples posted to the list would help.
You’ve only shared fragments, not tiny examples.
Carl
From: lilypond-user
on behalf of Alasdair McAndrew
Date: Friday, September 11, 2020 at 7:49 PM
To: lilypond-user Mailinglist
Subject: Re: Fingerings within voiced chord throw an error
Thanks David.
What a pain. I've tried a few other things: to formally instantiate new
voices with "voiceOne" and "voiceTwo", to include a "\relative" call - but
it makes no difference. Currently I seem to have run out of the ability in
this current score of changing the fingering styles when hav
You can follow the guidelines at
https://lilypond.org/tiny-examples.html#:~:text=A%20tiny%20example%20demonstrates%20that,to%20understand%20what%20is%20happening.
These guidelines seem to be less than helpful, but they actually reflect good
practice. Following these guidelines has helped me man
Send me the file and I will look at it. As mentioned, a picture is a
description but it's not code. Happy to help and check if we have
something to work with.
It would be helpful to know platform, and lilypond version.
I know in these sort of cases often MWE"s make it hard to duplicate the
is
On Fri 11 Sep 2020 at 23:46:03 (+1000), Alasdair McAndrew wrote:
> I have a chord of two notes. And I'd like to split it into two voices so
> that the top note's stem points up, and the bottom note's stem points down,
> and with a fingering, like this:
>
> <<{\set fingeringOrientations = #'(left)
I have a chord of two notes. And I'd like to split it into two voices so
that the top note's stem points up, and the bottom note's stem points down,
and with a fingering, like this:
<<{\set fingeringOrientations = #'(left) 4}\\{c,4}>>
However, in Frescobaldi this throws the error "return code -1
You're welcome Paul.
Cheers,
Pierre
PS. Be sure to respond to the list.
Le jeu. 2 juil. 2020 à 14:31, Paul McKay a écrit :
> Thanks for this Pierre. I can now do just what I'd hoped. I'm still
> struggling to write the appropriate markup function, but I'll keep going!
> Paul
>
> On Wed, 24 Jun 2
Hi Paul,
How about:
\version "2.20.0"
customFingering = {
\override Fingering.font-name = "Arial Black"
\override Fingering.font-size = #-1
\override Fingering.color = #(x11-color "DarkRed")
}
cust =
-\tweak font-name #"Arial Black"
-\tweak font-size #-2
-\tweak color #(x11-color "Da
Hi
I'd like to put a circle round occasional fingering marks. I have tried
*\circle*, but seem to have no control of the resulting thickness nor of
the font features. I can find no way to customize the fingering font within
the *\circle: *I always get some error message or other.
I tried \draw-cir
ers,
Harm
\version "2.19.82"
%%%
%%%
%%
%% GLISSANDI, DEFAULT AND BETWEEN FINGERINGS
%%
%%%
%%%
%% Thanks to David Nalesnik
%% See
%
> Hm. Can it be made breakable in a way that the glissando line appears on
> both ends?
Found it: \override Glissando.after-line-breaking = #'()
Hm. Can it be made breakable in a way that the glissando line appears on
both ends?
Joram
Wow. Thanks Harm! That makes sense and looks good.
I never thought of a glissando here. But it actually makes sense. Now I
wonder if a straight glissando line would even be more appropriate than
a slur … I would read it more easily.
Joram
Am Mo., 6. Apr. 2020 um 10:27 Uhr schrieb Noeck :
>
> Hi,
>
> can Lilypond draw ties between fingerings?
> I can fake it by using a slur and putting it above the fingering:
>
> \version "2.20.0"
> {
> % fake what I want
> \override Fingering.avo
Hi,
can Lilypond draw ties between fingerings?
I can fake it by using a slur and putting it above the fingering:
\version "2.20.0"
{
% fake what I want
\override Fingering.avoid-slur = #'inside
cis''-4( c''-4) r
% ties possible on one note
c'
Hi Urs (et al.),
> What is your stance on these peanut issues Kieren?
I’ve not previously encountered the idiom "peanut issues"… but if you mean
comparing the delay of a few minutes in a train ride within adjoining countries
in the EU zone versus my "25 consecutive hours of being awake because
new Voice.
> See below the fixed example.
>
> Best wishes.
> Davide
>
> \version "2.18.2"
>
> music-with-fingerings = {
> c'4-1 d'4-2
> a'4\finger \markup \tied-lyric #"4~3"
> c'4\finger "2 - 3"
> }
>
> \sc
Am 20. Januar 2020 21:30:19 MEZ schrieb David Kastrup :
>Thomas Morley writes:
>
>> Am Mo., 20. Jan. 2020 um 16:38 Uhr schrieb bkal...@gmail.com
>> :
>>>
>>> Is there a way to input fingerings separate from melody? I know I
>can tag my
>>
Thomas Morley writes:
> Am Mo., 20. Jan. 2020 um 16:38 Uhr schrieb bkal...@gmail.com
> :
>>
>> Is there a way to input fingerings separate from melody? I know I can tag my
>> fingerings and include or remove them using \keepWithTag and related markup,
>> but the
Am Mo., 20. Jan. 2020 um 16:38 Uhr schrieb bkal...@gmail.com
:
>
> Is there a way to input fingerings separate from melody? I know I can tag my
> fingerings and include or remove them using \keepWithTag and related markup,
> but the resulting code is very hard to read. I'd lo
Il giorno lun 20 gen 2020 alle ore 18:42 Jean-Julien Fleck
ha scritto:
> Won't it be colliding if you replace f' by a' ?
You are right: I forgot to explicitly initiate a new Voice.
See below the fixed example.
Best wishes.
Davide
\version "2.18.2"
music-with-finger
Le lun. 20 janv. 2020 à 17:20, Davide Liessi a
écrit :
> Il giorno lun 20 gen 2020 alle ore 16:38 bkal...@gmail.com
> ha scritto:
> > Is there a way to input fingerings separate from melody?
>
> You can attach fingerings to invisible rests and combine them with the
> mel
Il giorno lun 20 gen 2020 alle ore 16:38 bkal...@gmail.com
ha scritto:
> Is there a way to input fingerings separate from melody?
You can attach fingerings to invisible rests and combine them with the
melody using <<>>.
See the example below.
Best wishes.
Davide
\version "
Is there a way to input fingerings separate from melody? I know I can tag my
fingerings and include or remove them using \keepWithTag and related markup,
but the resulting code is very hard to read. I'd love to define them
separately, similarly to the way you can with lyrics or chords.
--
Perfect! Thank you, Harm. I appreciate it.
Emilio
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Am So., 9. Dez. 2018 um 17:18 Uhr schrieb Emilio Millan :
>
> I'm using fingerings for some above-the-staff harmonica notation. They are
> working well for this purpose but there is one bit of fine tuning I'd like
> to do if possible. In the example below, the fingerings are
I'm using fingerings for some above-the-staff harmonica notation. They are
working well for this purpose but there is one bit of fine tuning I'd like
to do if possible. In the example below, the fingerings are well-placed but
the "G4" and "A4" are a bit higher to appr
r my left-hand fretted-string
> fingerings ( i.e. c-3). It looks like a monospace font.
>
> I'm assuming that this is a systems font issue (Arch Linux). But I'm
> confused as to why all the other text shows up alright. I assume that
> lilypond uses the same font for all it's
Hello All,
I'm getting some really weird font for my left-hand fretted-string
fingerings ( i.e. c-3). It looks like a monospace font.
I'm assuming that this is a systems font issue (Arch Linux). But I'm
confused as to why all the other text shows up alright. I assume that
li
Maybe somebody is interested in the complete solution, TAB with right
hand fingering AND with capital letters (from Thomas Morley)?
\version "2.18.2"
#(define RH rightHandFinger)
\new TabStaff \relative c {
c-\RH #1 e-\RH #2 g-\RH #3 c-\RH #4
}
\layout {
\context {
\TabStaff
\ov
Thanks for help! Problem solved.
Regards
Am 28.01.2018 um 12:15 schrieb Pierre Perol-Schneider:
Hi Bernhard,
Try :
\version "2.18.2"
#(define RH rightHandFinger)
\new TabStaff \relative c {
c-\RH #1 e-\RH #2 g-\RH #3 c-\RH #4
}
\layout {
\context {
\TabStaff
\consists New_fing
Hi Bernhard,
Try :
\version "2.18.2"
#(define RH rightHandFinger)
\new TabStaff \relative c {
c-\RH #1 e-\RH #2 g-\RH #3 c-\RH #4
}
\layout {
\context {
\TabStaff
\consists New_fingering_engraver
strokeFingerOrientations = #'(down)
}
}
Cheers,
Pierre
2018-01-28 11:46 GMT+01
The left hand fingering is defined in the TAB, but how to get right a
hand fingering?
I tried this:
#(define RH rightHandFinger)
\new TabStaff \relative c {
\set strokeFingerOrientations = #'( down)
c-\RH #1 e-\RH #2 g-\RH #3 c-\RH #4
}
Compiles, but without fingering
Thanks for Help
PS:
> From: Knute Snortum
> To: Paul Scott
> Cc: Greg , lilypond-user@gnu.org
> Subject: Re: Clarinet fingerings
> You gave us all the version numbers... except for LilyPond! I'm going to
> assume 2.18.2.
>
> Here is the way I got it to work. Impr
1 - 100 of 311 matches
Mail list logo