David Kastrup,
Thank you for your kind attention to my request.
I shall attempt both of your procedures.
Mark
-Original Message-
From: David Kastrup [mailto:d...@gnu.org]
Sent: Friday, November 01, 2019 4:33 PM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re: Notation in
"Mark Stephen Mrotek" writes:
> Hello all,
>
>
>
> A C.P.E. Bach Piano sonata has the upper staff written with the soprano
> clef.
>
> My skill at reading music in soprano clef is minimal. So I am attempting a
> translation to treble clef.
>
> Does Lilypond have means to assist in this task?
"Mark Stephen Mrotek" writes:
> Hello all,
>
>
>
> A C.P.E. Bach Piano sonata has the upper staff written with the soprano
> clef.
>
> My skill at reading music in soprano clef is minimal. So I am attempting a
> translation to treble clef.
>
> Does Lilypond have means to assist in this task?
Hello all,
A C.P.E. Bach Piano sonata has the upper staff written with the soprano
clef.
My skill at reading music in soprano clef is minimal. So I am attempting a
translation to treble clef.
Does Lilypond have means to assist in this task?
Thank you,
Mark
soprano.pdf
Description:
On 01.11.19 22:33, Solomon Foster wrote:
Any hints how to do this? I've got to say, at this point I feel like
not really understanding markup / markuplist is my major obstacle to
getting things done. I can't even tell in this is a simple problem
I'm asking or a subtle and difficult one.
Hi all,
Thanks so much for the earlier help on things I needed to get a tune book
up and running. At this point I'm successfully generating a fully
functional 122 page tune book, and I'm just looking for ways to improve the
appearance of things a tad.
Perhaps the biggest one (and one that will,
Am 1. November 2019 18:57:37 MEZ schrieb Peter Toye :
>I'm trying to find out exactly what grobs are produced as one point ins
>a score, so tried engraving with layout control and "display grob
>names" ticked on the layout control.
For the record: this refers to the Frescobaldi functionality
I'm trying to find out exactly what grobs are produced as one point ins a
score, so tried engraving with layout control and "display grob names" ticked
on the layout control. And got this on the log:
warning: no such internal option: debug-grob-names
Processing
On Fri 01 Nov 2019 at 13:51:49 (+0100), Simon Albrecht wrote:
> On 01.11.19 00:10, David Olson wrote:
> > This is for sight-singing fun; I'll hand out a song sheet, we'll
> > spend 2 or 3 minutes on this, once through, then sing something
> > else.
> >
> > So, for the basses who take the profound
> Also, doing everything to accommodate
> inexperienced sight-readers can often lead to bad conclusions.
Well, experienced sight-singers have certain expectations.
If you are ever in Los Angeles on a Monday night,
and want to attend a midnight sight-singing session,
(shape note singing)
let
Am Fr., 1. Nov. 2019 um 15:34 Uhr schrieb Karsten Reincke :
> does anyone has / know about an example of a define-markup-command
> implementation
> using a variable number of arguments / parameters?
Nope, optional arguments are not possible using define-markup-command.
> Unfortunately, in my
Il some output problems occur, please try:
\version "2.19.83"
#(define-markup-command (ric-mkp layout props note)(ly:music?)
(interpret-markup layout props
#{
\markup {
\override #'(baseline-skip . 1.5)
\left-column
{
\line { \hspace #1 \teeny\bold
Dear friends;
does anyone has / know about an example of a define-markup-command
implementation
using a variable number of arguments / parameters?
Unfortunately, in my system (Linux Ubuntu 19.10 with Lilypond 2.18...) the
normal
GUILE / scheme syntax (define (x y . args) ) (doanythingwith
On 01.11.19 13:57, David Kastrup wrote:
Usually there are either separate voices (in which case you want
separate stems) or not (like in a piano extract done with the voice
combiner). This kind of an optional bass octave at deliberation of the
singer is sort of a weird middle case.
Not in
You're welcome Ben.
Simply enter values of "b" (which should remain the same) from full to 16th
note. Minimum is 3 values, so 3 dots. Either e.g. b16( b b) or b16( 16 16)
is ok.
Higher values (32, 64, 128) won't show thinner spaces.
If only two values are entered, (e.. b16( 16)) the output does
Simon Albrecht writes:
> On 01.11.19 00:10, David Olson wrote:
>> This is for sight-singing fun; I'll hand out a song sheet, we'll
>> spend 2 or 3 minutes on this, once through, then sing something
>> else.
>>
>> So, for the basses who take the profound option, it would be nice if
>> there was a
On 01.11.19 00:10, David Olson wrote:
This is for sight-singing fun; I'll hand out a song sheet, we'll spend
2 or 3 minutes on this, once through, then sing something else.
So, for the basses who take the profound option, it would be nice if
there was a slur symbol right where their eyes are
On 31.10.19 15:32, DJF wrote:
\relative c'' {
\key f \major
<<{bes2 ~ 8 4} \\
{r4 ~ \hideNotes 8 \unHideNotes s8 s4 } >>
}
Code formatting matters. The above may be legible to LilyPond, and maybe
you’re used to that style, but if you’re sharing code, please stick to
the standards evident
> Am 2019-11-01 um 12:16 schrieb J Martin Rushton
> :
>
> On 01/11/2019 10:45, Henning Hraban Ramm wrote:
>> BTW there is _no_ copyright on the design of sheet music, even if some music
>> publishers claim it.
>
> This depends upon the country. In the UK: "The typographical
> arrangement of
On 11/1/2019 6:00 AM, Pierre Perol-Schneider wrote:
Simplified:
\version "2.19.83"
#(define-markup-command (ric-mkp layout props note)(ly:music?)
(interpret-markup layout props
#{
\markup {
\override #'(baseline-skip . 1.5)
\left-column
{
\line {
On 01/11/2019 10:45, Henning Hraban Ramm wrote:
>
>
> BTW there is _no_ copyright on the design of sheet music, even if some music
> publishers claim it.
>
This depends upon the country. In the UK: "The typographical
arrangement of a published edition lasts for 25 years from first
> Am 2019-10-31 um 03:15 schrieb Carl Sorensen :
>
> In the US, a typeface is not copyrightable. But a computer program that
> makes a font or its glyphs is copyrightable.
The "program code" of fonts is juristically not regarded a program, because it
is usually auto-generated by a design
Simplified:
\version "2.19.83"
#(define-markup-command (ric-mkp layout props note)(ly:music?)
(interpret-markup layout props
#{
\markup {
\override #'(baseline-skip . 1.5)
\left-column
{
\line { \hspace #2 \teeny\bold "ric." }
\score {
Just upgraded to Fedora 31.
Maybe this is not the right place to report this, but I'm seeing this in
my terminal when updating my packages:
Problem 1: package frescobaldi-3.0.0-10.fc31.noarch requires
python3-sip, but none of the providers can be installed
- package
24 matches
Mail list logo
