Hello
2011/8/15 Javier Ruiz-Alma
> I'm working with a multi-score lilypond file.
> I'd like to be able to set arbitrary filenames for each midi, instead of
> having lilypond derive the midi filenames from the .ly filename.
>
>
http://lilypond.org/doc/v2.14/Documentation/notation/output-file-name
Am 15.08.2011 04:57, schrieb Evan Laforge:
On Sun, Aug 14, 2011 at 7:27 PM, Kieren MacMillan
wrote:
Hi Evan,
I'm guessing both of these are possible, but I don't know quite the
right knobs to tweak to modify a voice in this way. And I imagine it
must be a fairly common problem, so surely so
Hello List,
I use a file "papier.ly" for my global definitions. If I extend the
search path with the -I option, lilypond may find this in more than one
place: Beside the current file and in my own include folder. The same
applys for included EPS-files - and if lily finds files of that name
mo
sorry to be a pedant, but...
traditionally, 4. [8 8 8] is the exception to the rule that you subdivide the
8ths 2,2,2 in a 3/4 bar
Mozart, Haydn, Beethoven, Schubert, Chopin, Liszt, Brahms and Ravel do this
consistently. It is also normal for Debussy apart from in the late violin
sonata .
the
Damian leGassick writes:
> I'm sorry to contradict David but you'll be hard pushed to find many
> published examples of 4. 8 [8 8] that don't have mitigating phrasing
> circumstances.
If you take a look at the comments of the bug report, you'll see that
you come in second for contradicting me, m
On 14 août 2011, at 23:47, Werner LEMBERG wrote:
>
>>> Here are the messages I get in the console:
>>>
>>> warning: no PostScript font name for font
>>> `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz'
>>
>> It's improbable that you want to use an X11 font with LilyPond.
>
> To be more precise: L
>> To be more precise: LilyPond only handles outline fonts. A proper
>> filter to ensure that is still missing. Reason is that the
>> FontConfig interface doesn't provide a means to implement it.
>> IIRC, there is already a bug tracker issue which covers this.
>
> I don't see why pango or fontc
Hi Damian,
I am looking at my copy of the famous Scherzo opus 4 of Brahms. (Kalmus
Edition) The beaming is clearly r4 r8 8[ 8 8] all over the place, since
the main them is r4 r8 8[ 8 8]. I see this as an expediting right hand
of Mr. Brahms, I bet 100 euros that the original manuscript is beamed
Here is my code for a C minor scale on a 6 string guitar 2+ octaves. Is
there a way to make the numbers smaller to fit inside the 'dots'? Is there
a way to place dots between the strings to mark the inlays at frets 3 5 7 9
12 etc?
Thank you so very much.
http://old.nabble.com/file/p32255163/Cmi
This is quite easy. You just make a fret diagram with a specified number of
frets and a specified number of strings, with all the strings open. You
then need to set the open-string indicator to " ".
Here's a sample:
%% start of cut and paste code
\version "2.11.64"
\storePredefinedDiagram \
At Mon, 15 Aug 2011 12:00:20 -0400,
lilypond-user-requ...@gnu.org wrote:
> Subject: Re: Misleading autobeaming in 3/4
>
> I am looking at my copy of the famous Scherzo opus 4 of Brahms. (Kalmus
> Edition) The beaming is clearly r4 r8 8[ 8 8] all over the place, since
> the main them is r4 r8 8[ 8
Hi List.
I have a 40-bar LilyPond piano score notated in
3-staff systems (to accomodate a leaping-over
left hand). Occasionally one staff in a system,
either the middle or upper, contains rests only.
I want to exclude such staves from the output,
and so have defined my \score block as follows,
PMA-2 wrote:
>
> Hi List.
>
> Occasionally one staff in a system,
> either the middle or upper, contains rests only.
>
> I want to exclude such staves from the output,
> and so have defined my \score block as follows,
> following Notation & Snippets Ref. suggestions.
>
> \score {
>\new Pi
Hi,
I'm trying to create a file using multiple tags. Inside the music
typed, that is not a problem, but the \keepWithTag command only
accepts one tag to filter.
I would like to do:
\keepWithTag #'a #'b { music }
or
\keepWithTag #'a { \keepWithTag #'b { music } }
but either
harm6 wrote:
PMA-2 wrote:
Hi List.
Occasionally one staff in a system,
either the middle or upper, contains rests only.
I want to exclude such staves from the output,
and so have defined my \score block as follows,
following Notation& Snippets Ref. suggestions.
\score {
\new PianoStaf
PMA-2 wrote:
>
> No difference from the original output.
> But thanks for "StaffGroup". I'll experiment more.
>
> P
>
I tested:
\version "2.14.2"
upper = {
\relative c' {
a1\break
b \break
R1\break
R1\break
Nicolas Sceaux wrote a brilliant \keepWithTags function that does the first
option:
http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00635.html
--Steven
-Original Message-
From: lilypond-user-bounces+panteck=hotmail@gnu.org
[mailto:lilypond-user-bounces+panteck=hotmail@
On 15 August 2011 21:10, PMA wrote:
>
> Hi List.
>
> I have a 40-bar LilyPond piano score notated in
> 3-staff systems (to accomodate a leaping-over
> left hand). Occasionally one staff in a system,
> either the middle or upper, contains rests only.
>
> I want to exclude such staves from the outp
Xavier Scheuer wrote:
>
> \RemoveEmptyStaffContext has been replaced by \Staff \RemoveEmptyStave
> in version 2.13.something.
> Cheers,
> Xavier
>
Hi,
I didn't found \RemoveEmptyStaffContext in the docs, but there is a
definition in engraver-init.ly (version 2.14.2) for it ! So I'm a little b
On Mon, Aug 15, 2011 at 02:21:11PM -0700, harm6 wrote:
>
> Xavier Scheuer wrote:
> > \RemoveEmptyStaffContext has been replaced by \Staff \RemoveEmptyStave
> > in version 2.13.something.
>
> I didn't found \RemoveEmptyStaffContext in the docs, but there is a
> definition in engraver-init.ly (vers
At Mon, 15 Aug 2011 17:23:00 -0400,
lilypond-user-requ...@gnu.org wrote:
> From: PMA
> To: lilypond-user@gnu.org
> Subject: \RemoveEmptyStaffContext (?)
>
> I have a 40-bar LilyPond piano score notated in
> 3-staff systems (to accomodate a leaping-over
> left hand). Occasionally one staff in a sy
Graham Percival-3 wrote:
>
> umm, did you try reading the lines immediately above it?
>
>
> %% Keep the old definitions in here for compatibility (they erase
> %previous
> %% settings to the corresponding context!).
> %% For new scores, one should simply insert the \RemoveEmptyStaves
> %settin
harm6 wrote:
Graham Percival-3 wrote:
umm, did you try reading the lines immediately above it?
%% Keep the old definitions in here for compatibility (they erase
%previous
%% settings to the corresponding context!).
%% For new scores, one should simply insert the \RemoveEmptyStaves
%settings
harm6 wrote:
Graham Percival-3 wrote:
umm, did you try reading the lines immediately above it?
%% Keep the old definitions in here for compatibility (they erase
%previous
%% settings to the corresponding context!).
%% For new scores, one should simply insert the \RemoveEmptyStaves
%settings
24 matches
Mail list logo
