Am 30.06.2014 08:41, schrieb Janek Warchoł:
You're welcome :)
Maybe i should add this function to official LilyPond?
Good idea, I think!
Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi LilyPonders,
This afternoon I had to write a short polyphonic piece to illustrate some
literature and I found it fun to use the parallelMusic mode for the very
first time.
I choose a short menuet with repeats and discovered that the use of repeats
could be problematic in this mode.
See a forme
On 29/06/14 21:42, Br. Samuel Springuel wrote:
Attached is a small sample project which attempts to exploit the
\include statement in lilypond in a lilypond-book project. The goal
(and why I have two scores in this small sample) is to be able to
place in Format.lyi those pieces of the lilypond
On 30/06/14 15:09, Pierre Perol-Schneider wrote:
Hi LilyPonders,
This afternoon I had to write a short polyphonic piece to illustrate
some literature and I found it fun to use the parallelMusic mode for
the very first time.
I choose a short menuet with repeats and discovered that the use of
r
On 30/06/14 07:54, Urs Liska wrote:
Am 30.06.2014 08:41, schrieb Janek Warchoł:
You're welcome :)
Maybe i should add this function to official LilyPond?
2014-06-30 3:29 GMT+02:00 Javier Ruiz-Alma :
user error!
Reviewed the cited LSR instead of staying at openlilylib...my bad.
Thanks for no
Hi James,
2014-06-30 18:28 GMT+02:00 James :
> On 30/06/14 07:54, Urs Liska wrote:
>> It seems that the snippet-description field is suboptimal as it only
>> states to typeset the text _below_ the hairpin.
>
> Do we need to change the texidoc string for this snippet then? And if so to
> what - I a
Looking in those directories, I find no *.log files and the *.texi file
simply contains a list of @image commands which point at the generated
eps files (with @c eof at the end) and thus doesn't seem to be of much
use. Is there some option flag to force the *.log file?
On the issues of the in
Hi,
I was wondering if anyone knows how to override the
default numbering format for string numbers
(default is circled arabic numbers) and use roman
numerals instead.
An example would be something like this:
{ e''\2 } which is an e played on the second
string. The default shows a circled 2 ab
Hi Philip
2014-06-30 21:32 GMT+02:00 philip :
> I was wondering if anyone knows how to override the
> default numbering format for string numbers
> (default is circled arabic numbers) and use roman
> numerals instead.
> An example would be something like this:
> { e''\2 } which is an e played on
Hi James,
2014-06-30 18:21 GMT+02:00 James :
>
> So are you saying we need to update the documentation?
>
Yes, I think it could be a good thing to add somehow explanations for
repeats in parallelMusic mode.
But I'll send an email to the bug list regarding this.
> Remember that tagging LSR exa
Hello,
On Mon, Jun 30, 2014 at 2:32 PM, philip wrote:
> Hi,
> I was wondering if anyone knows how to override the
> default numbering format for string numbers
> (default is circled arabic numbers) and use roman
> numerals instead.
>
>
Try this:
\version "2.19.8"
#(define (string-number::ca
Hi List,
I re-wrote this snippet in parallelMusic mode since I think it is much more
convenient for guitar transcriptions.
Cheers,
Piere
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On 01/07/14 05:32, philip wrote:
Hi,
I was wondering if anyone knows how to override the
default numbering format for string numbers
(default is circled arabic numbers) and use roman
numerals instead.
An example would be something like this:
{ e''\2 } which is an e played on the second
string. Th
On Mon, 30 Jun 2014 19:32:44 + (UTC)
philip wrote:
> Hi,
> I was wondering if anyone knows how to override the
> default numbering format for string numbers
> (default is circled arabic numbers) and use roman
> numerals instead.
> An example would be something like this:
> { e''\2 } which
Roman numerals are very much the convention for string indications for the
violin family.
On 07:13, Tue 01 Jul 2014, Nick Payne wrote:
> Date: Tue, 01 Jul 2014 07:13:47 +1000
> From: Nick Payne
> Subject: Re: string numbers (fingering instructions) as roman numerals?
> To: lilypond-user@gnu.org
2014-06-30 22:25 GMT+02:00 David Nalesnik :
> Hello,
>
>
> On Mon, Jun 30, 2014 at 2:32 PM, philip wrote:
>
>> Hi,
>> I was wondering if anyone knows how to override the
>> default numbering format for string numbers
>> (default is circled arabic numbers) and use roman
>> numerals instead.
>>
>>
Hi,
On Mon, Jun 30, 2014 at 4:15 PM, David Raleigh Arnold
wrote:
>
>
> How do I indicate strings by letter-pitch instead of
> numbers, the way Villa Lobos did? Regards, Rale
>
>
You could do something like the following:
\version "2.19.8"
#(define strings "EBGDAE")
#(define (string-numbe
On Mon, Jun 30, 2014 at 4:55 PM, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
>
>
> If you don't need any circle you can write (including David's code) :
>
> {
> \override StringNumber.text = #string-number::calc-roman-text
> \override StringNumber.stencil = #ly:text-inter
Lily ponders:
With the help from the list I have the .ly file that I use quite often. Many
thanks lily ponders.
Is it possible to modify the code do not display the tied note?
example in the attached .ly file:
i.e. (1) do not display second ⓢ & third ⓢ because it is the tied notes
(2) do not dis
On 14-06-30 06:53 PM, MING TSANG wrote:
Lily ponders:
With the help from the list I have the .ly file that I use quite
often. Many thanks lily ponders.
Is it possible to modify the code do not display the tied note?
example in the attached .ly file:
i.e. (1) do not display second ⓢ & third ⓢ be
Hi, Colin:
Message: 3
Date: Mon, 30 Jun 2014 19:15:15 -0600
From: Colin Campbell
To: lilypond-user@gnu.org
Subject: Re: solfege display for tie & slur
Message-ID: <53b20ba3.2080...@shaw.ca>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 14-06-30 06:53 PM, MING TSANG wrote:
>
On 14-06-30 07:39 PM, MING TSANG wrote:
Hi, Colin:
<><><><>
Thank you for the suggestion. But I want to preserve what is code in
the staff. I do not want to display second ⓢ and third ⓢ above the
staff (the same way midi track just extend the beats without playing
it). The same for second ⓕ
Hi Pierre and Harm,
Schneidy wrote
>> Examples of three different ways to scale a staff to twice its size:
>>
>
> Thanks for the tip Paul.
> Il keep it for a future snippet in the LSR v2.20 (just 2 ways if you don't
> mind).
You're welcome, and sounds good, I don't mind. I think it would be go
Simon Albrecht-2 wrote
>> The set-global-staff-size approach also seems
>> to leave the staff lines and stems proportionally thinner at larger
>> sizes.
> … which is a good thing, since it preserves the optical impression
> instead of keeping the numerical proportions.
> If the proportions would r
24 matches
Mail list logo
