Dear Kieren,
thanks for Your advice.
But what can I do with my version of the program?
2008/9/7 Kieren MacMillan <[EMAIL PROTECTED]>
> Hi Stefan,
>
> in the below quoted example I can't see the "crescendo"
>> and I don't know why. Does someone know a solution?
>>
>
> At least with version 2.11.5
Oops... sorry.. for each staff I should have provided
Staff.shortInstrumentName ="X"
Then short instrument name will be printed on second and subsequent
system...
Daryna
On Mon, Sep 8, 2008 at 12:24 PM, Daryna Baikadamova <
[EMAIL PROTECTED]> wrote:
> Now I have turned on empty staff hi
Now I have turned on empty staff hiding using:
\layout {
\context { \RemoveEmptyStaffContext }
}
However now I have a second problem. When a staff is hidden from a system,
the system with hidden staff does not print the Staff.instrumentName again
for the visible staff on that system. The condu
> "Reinhold" == Reinhold Kainhofer <[EMAIL PROTECTED]> writes:
Reinhold> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Reinhold> That, and you should add \transposition
Reinhold> displayPitchOfYourNote to the beginning of your original
Reinhold> score in some strange display pitch. This tell
Hello,
Thanks to you two for the quick reply. So basically, it is just the other
way round. And instead of defining exceptions for every combination, a
solution that approaches eralier sounds cleaner to me (and more
future-proof). But as I am working on this for a long time now, a dirty hack
would
Hi Thomas,
Use a chord name exception list perhaps?
I don't think that will work, unfortunately… With an exception list,
you can change what comes after the base/root name itself (e.g.,
display C7 or C[seven] or Cvii), but not the base/root name or its case.
=(
Cheers,
Kieren.
_
Use a chord name exception list perhaps?
See
http://lilypond.org/doc/v2.9/Documentation/user/lilypond/source/input/regression/collated-files#chord-name-exceptions.ly
--
View this message in context:
http://www.nabble.com/Make-moll-chords-small%2C-again-tp19356071p19361144.html
Sent from the Gnu
Am 07.09.2008 um 18:30 schrieb Neil Puttock:
2008/9/7 CJ Bell <[EMAIL PROTECTED]>:
On Sun, Sep 7, 2008 at 12:12 PM, Neil Puttock <[EMAIL PROTECTED]>
wrote:
Remove the << >> brackets; you're forcing the volte to be
simultaneous, so they're placed on top of each other.
That is my intention.
> OK, if you want them together, you have to heed the warning in the
> docs about grace synchronization:
> http://kainhofer.com/~lilypond/Documentation/user/lilypond/Grace-notes.html#Grace-notes.
Ah, right. Thanks! (bleh; I've even read that warning before...)
-cj
__
2008/9/7 CJ Bell <[EMAIL PROTECTED]>:
> On Sun, Sep 7, 2008 at 12:12 PM, Neil Puttock <[EMAIL PROTECTED]> wrote:
>> Remove the << >> brackets; you're forcing the volte to be
>> simultaneous, so they're placed on top of each other.
>
> That is my intention. I'm trying to combine two parts. (and
> \p
On Sun, Sep 7, 2008 at 12:12 PM, Neil Puttock <[EMAIL PROTECTED]> wrote:
> Remove the << >> brackets; you're forcing the volte to be
> simultaneous, so they're placed on top of each other.
That is my intention. I'm trying to combine two parts. (and
\partcombine isn't working any better)
[attached
2008/9/7 Jonathan Kulp <[EMAIL PROTECTED]>:
> Sorry, Neil, it was negligent of me not also to say "thanks for fixing this
> bug"! Thanks! :)
Thank you. :)
It's unfortunate that you have to change your tweaks, but it's in the
nature of using extra-offset; it's blind to any bugfixes which change
s
Hi CJ,
2008/9/7 CJ Bell <[EMAIL PROTECTED]>:
> For now, can anyone find a workaround?
Remove the << >> brackets; you're forcing the volte to be
simultaneous, so they're placed on top of each other.
Regards,
Neil
<>___
lilypond-user mailing list
lilypo
Sorry, Neil, it was negligent of me not also to say "thanks for fixing
this bug"! Thanks! :)
Jon
Neil Puttock wrote:
Hi Jon,
>
This is a result of my fix (#666) for the broken 'avoid-slur behaviour
when set to 'around (which is the case for Fingering).
--
Jonathan Kulp
http://www.jonathank
I've tried the below example in 2.10.10 and 2.11.57-1 and both
generate the warning "already have a volta spanner, ending that one
prematurely" and place the grace note in it's own volta spanner.
For now, can anyone find a workaround?
Thanks!
-cj
\version "2.10.10"
%\version "2.11.57"
\score {
Hi Stefan,
in the below quoted example I can't see the "crescendo"
and I don't know why. Does someone know a solution?
At least with version 2.11.57, you need to use the following:
\version "2.11.57"
{
\crescTextCresc
\override DynamicTextSpanner #'dash-period = #1.0
a
Dear Lilypond-users,
in the below quoted example I can't see the "crescendo" and I don't know
why. Does someone know a solution?
\version "2.11.49"
{
\set crescendoSpanner = #'text
\override DynamicTextSpanner #'dash-period = #-1.0
a'2\< a a a\mf }
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 7. September 2008 schrieb Daryna Baikadamova:
> So do you mean that I should leave the original score alone (i.e. *not* to
> create a concert pitch version of the part by using \displayLilyMusic
> \transpose) and in the driver lilypond file
Am 07.09.2008 um 10:19 schrieb Daryna Baikadamova:
Thanks! However I am new to lilypond, could you please point me to
an example illustrating how global block is used in this way. I
guess this situation should be common in orchestral scores, although
many projects in mutopia (including t
Hello,
I have come up with this topic before, but it always stranded somehow.
What am I looking for?
I want to have moll chords printed lowercase and without the "m", so a:m
should be printed "a" instead of "Am". This is the notation standard for our
songs and we do not want to change it now. As
Daryna Baikadamova wrote:
Thanks! However I am new to lilypond, could you please point me to an
example illustrating how global block is used in this way. I guess this
situation should be common in orchestral scores, although many projects in
mutopia (including the the I received) don't do thes
Thanks! However I am new to lilypond, could you please point me to an
example illustrating how global block is used in this way. I guess this
situation should be common in orchestral scores, although many projects in
mutopia (including the the I received) don't do these kind of things
properly
Am 07.09.2008 um 09:40 schrieb Daryna Baikadamova:
So do you mean that I should leave the original score alone (i.e.
*not* to create a concert pitch version of the part by using
\displayLilyMusic \transpose) and in the driver lilypond file that
uses the score to print the separate part, I
Daryna Baikadamova wrote:
Now I have another problem. Suppose I want to insert tempo to the
conductors score at specific places (not only at the beginning of the
score), and I want these tempo marks (e.g. Allegretto crotchet = 76) printed
only *once* on top of the system on the conductor's score
Now I have another problem. Suppose I want to insert tempo to the
conductors score at specific places (not only at the beginning of the
score), and I want these tempo marks (e.g. Allegretto crotchet = 76) printed
only *once* on top of the system on the conductor's score, but these tempo
marks must
On Sun, Sep 7, 2008 at 6:47 PM, James E. Bailey <[EMAIL PROTECTED]>wrote:
>
> Am 07.09.2008 um 06:10 schrieb Daryna Baikadamova:
>
>> when we enter new scores, should we enter in concert pitch?
>>
> I think you should enter the score in whatever pitch is easiest. If your
> source score is transpos
26 matches
Mail list logo
