On Wed, 20 Nov 2019 00:26:58 +, "Urs Liska"
wrote:
> This was just shared on Facebook, and I want to forward it here since -
> while not related to music engraving directly - it may be useful to
> people on this list.
>
>
First off, further apologies for accidentally posting a follow-up via an
second email address.
Aaron, thanks for all of this. Helpful to have the demonstration of
column-formatted note names from pitches, along with evidence of
something called "note-name->markup"; maybe that's all I need if
Quite comfortable with such cheek. Thank you.
Still, I will try to package up a more formally named version of that
little function. A translating map or loop will then be needed to
extract note names and render them in more conventional form, but that
won't require inscrutable-for-me ly:xxx
This was just shared on Facebook, and I want to forward it here since - while
not related to music engraving directly - it may be useful to people on this
list.
https://bit.ly/2qouMtH?fbclid=IwAR2kWD64268-n2cqKagJ5AxVntbxRsPFN48q61aZ8ORwB6s54vGmHeWJNZU
This points to an archive on Dropbox,
Stephen Cummings writes:
> Am I missing a basic LilyPond command/directive--something built-in
> that takes music as input and returns note names as text? Such a
> functionality would seem to be useful in all kinds of
> annotations/quotations. I know about \displayMusic but its output only
>
On 2019-11-19 10:58 am, Matt Wallis wrote:
So, I have added the line (in place of your call to format):
subtitle = #(guile-user-lookup 'subtitle "...")
in order to get back into the world of lilypond variables, and it all
works.
As you discovered, you do need to explicitly define a new
On 19/11/2019 15:39, Aaron Hill wrote:
On 2019-11-19 3:37 am, Matt Wallis wrote:
I want to pass the subtitle into lilypond on the command line because
it is also required by other programmes (e.g. sox needs the subtitle
to create a tag for the mp3 it creates).
[ . . . ]
But I now get the
Am 19.11.19 um 18:34 schrieb Павел Буданов:
<<
{ \partial 4*3 b b b b b b b }
\\
{ R1*3/4 R1 }
How to solve subject problem? I did not find the answer in the archive.
A partial measure is partial, not full, so why do you want a full
measure rest?
In 4/4 time the rest
<<
{ \partial 4*3 b b b b b b b }
\\
{ R1*3/4 R1 }
>>
How to solve subject problem? I did not find the answer in the archive.
On 2019-11-19 6:05 am, Stephen Cummings wrote:
Am I missing a basic LilyPond command/directive--something built-in
that takes music as input and returns note names as text?
There is the NoteNames context, but its functionality is wrapped up in
C++ code and is not easily customizable.
On 2019-11-19 3:37 am, Matt Wallis wrote:
I want to pass the subtitle into lilypond on the command line because
it is also required by other programmes (e.g. sox needs the subtitle
to create a tag for the mp3 it creates).
[ . . . ]
But I now get the warning:
Parsing...WARNING: #f: imported
Am I missing a basic LilyPond command/directive--something built-in that
takes music as input and returns note names as text? Such a
functionality would seem to be useful in all kinds of
annotations/quotations. I know about \displayMusic but its output only
goes to the console/output stream
Andrew Bernard writes:
> In my scores, when I use make-dynamic script as per the MWE here,
> setting DynamicText.font-size in Score context affects normal dynamic
> marks but not scripts. Is this a limitation, or my error?
I have no idea what you are talking about. Set the font-size to #-10 in
I want to pass the subtitle into lilypond on the command line because it
is also required by other programmes (e.g. sox needs the subtitle to
create a tag for the mp3 it creates).
Looking at
Ah, well I guess reading the NR Section New Dynamic Marks explains
this. Perhaps I am hoping for too much from the \override
DynamicText.font-size command.
Andrew
In my scores, when I use make-dynamic script as per the MWE here,
setting DynamicText.font-size in Score context affects normal dynamic
marks but not scripts. Is this a limitation, or my error?
Andrew
%
\version "2.19.83"
fpocoText = \markup {
\center-align \line {
\hspace #0.1 f
Hello Yoann,
Maybe starting this way:
\version "2.19.83"
{
% initial shared music
c'1 e |
% the two alternatives
\override Staff.StaffSymbol.line-count = 0
\stopStaff \startStaff
\hide Staff.BarLine
<<
\new Staff {
\hide Staff.Clef
\hide Staff.KeySignature
Oups, answered the wrong post, sorry…
JM
> Le 19 nov. 2019 à 09:43, Jacques Menu a écrit :
>
> Hello Steve,
>
> Maybe starting this way:
>
> \version "2.19.83"
>
> {
> % initial shared music
> c'1 e |
>
> % the two alternatives
> \override Staff.StaffSymbol.line-count = 0
>
Hello Steve,
Maybe starting this way:
\version "2.19.83"
{
% initial shared music
c'1 e |
% the two alternatives
\override Staff.StaffSymbol.line-count = 0
\stopStaff \startStaff
\hide Staff.BarLine
<<
\new Staff {
\hide Staff.Clef
\hide Staff.KeySignature
19 matches
Mail list logo
