Hi Valentin,
repeats in NNS are specified with standard repeat signs, displayed
inline, and volta brackets above in case of an \alternative {{}{}}.
Repeats of 2nd order are displayed with segno and coda sign.
Short repeats can be achieved with percent style.
Cheers,
Amy
On 21.01.22 18:58, V
Hi Amelie,
@1: The mechanism is not hard coded but automatic. Thus we can get
arbitrarily small anticipations.
@2: This is a chase of a Chord Name exception (diminished as root° insteat of
root m b5), which are not yet properly supported here.
@3: This is a case of a triplet, which again I’ve
Hi Valentin, all,
this looks very good, but I have a few questions:
(1) I'm sure nobody will use chords anticipated by 1/32, 1/64, and 1/128
(bars 10, 12, 14). If they're just there for completeness's sake, that's
fine, but stuff like that just never happens.
(2) I don't know what the symbol 7-°
Hi Amelie,
See here the current status quo. Alignment is still not done, and 3,4 are
still missing.
Cheers,
Valentin
Am Dienstag, 18. Jänner 2022, 14:25:56 CET schrieb Amelie Protscher:
> Hi Valentin,
>
> I'm sorry. I thought it was a matter of course that time sig and key
> were specified in
Hello Valentin,
Thank you for your help with this, and for providing the example. I have
been able to use NNS to denote chord names as I need to. I agree that it
would be great to implement the full NNS notation as Amy described.
Thanks,
Samuel Gibson
On Fri, Jan 14, 2022 at 2:43 PM Valentin Pet
Hi Valentin,
Nashville Numbers came up repeatedly on this list in the last years. I'm
also a huge fan and would like to see them implemented.
Altered degrees are written b3 or #4 in the Nashville system. Chord
modifiers are as per normal. But there are also rhythmic markers that
should be include
Hello Sam,
(please keep lilypond-user in the address list)
The big problem here is the the chord naming function (which is responsible
for creating that chordname) does not expect the root name to depend on
context properties, so it does not pass the context as argument. This means we
cannot do
Hello Sam,
Sure, just use (number->string (1+ step)) to increment the number by 1.
Generally it is possible to do more, but you’d need to specify what is needed.
After all most of us probably have no real knowledge about the Nashville
System. For example this does not yet incorporate alteratio
Hello Sam,
What do want? ENTER chords in this system, or DISPLAY them in this system, or
both? I know nothing about this system, but you can specify what symbol gets
printed for chord roots like this
\version "2.22.1"
\chords {
\set chordRootNamer =
#(lambda (pitch lowercase?)
(let* (
Am Fr., 14. Jan. 2022 um 05:38 Uhr schrieb Tim's Bitstream
:
>
> There was a thread earlier this year on that very topic:
>
> https://mail.gnu.org/archive/html/lilypond-user/2021-06/msg00023.html
>
>
>
>
> On Jan 13, 2022, at 8:48 PM, Sam Gibson wrote:
>
>
> Good day.
>
> I wish to use the Nashv
There was a thread earlier this year on that very topic:
https://mail.gnu.org/archive/html/lilypond-user/2021-06/msg00023.html
> On Jan 13, 2022, at 8:48 PM, Sam Gibson wrote:
>
>
> Good day.
>
> I wish to use the Nashville Number System, using numbers in place of chord
> names, for a si
Good day.
I wish to use the Nashville Number System, using numbers in place of chord
names, for a simple lead sheet or chord chart. While it is possible to
simply enter and position chords using \lyricmode, I do not know of a way
to include the superscripts such as maj7 or sus4. Is there a way to
12 matches
Mail list logo
