gt; Bengtsson <[EMAIL PROTECTED]>
> Betreff: Re: What to do when \\> and \\< produce text
> 2008/10/30 Trevor Daniels <[EMAIL PROTECTED]>:
>
> > In my experience (vocal music), cresc and dim without a dashed
> > line is used almost universally. Hairpins are u
2008/10/30 Trevor Daniels <[EMAIL PROTECTED]>:
> In my experience (vocal music), cresc and dim without a dashed
> line is used almost universally. Hairpins are used when an extent
> is being indicated.
I have the same impression (choir music).
> I vote for not adding the dashed line to these co
Mats Bengtsson wrote Thursday, October 30, 2008 9:03 AM
Valentin Villenave wrote:
2008/10/29 Reinhold Kainhofer <[EMAIL PROTECTED]>:
\decresc ... Starts a text decrescendo
This one wasn't available earlier, but can of course easily be added if
there's consensus
about it. For the macros tha
Valentin Villenave wrote:
2008/10/29 Reinhold Kainhofer <[EMAIL PROTECTED]>:
\cresc ... Starts a text crescendo
\dim ... Starts a text diminuendo
Already done, as I mentioned in an earlier email.
\decresc ... Starts a text decrescendo
This one wasn't available earlier, but can of
2008/10/29 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> \cresc ... Starts a text crescendo
> \decresc ... Starts a text decrescendo
> \dim ... Starts a text diminuendo
> All of these would simply be ended by \!.
I agree, but in this case we'd have to first have a convert rule that turns
\version "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 29. Oktober 2008 schrieb George_:
> Well, shouldn't the file be changed for future versions of Lilypond so that
> the \cresc command produces the text crescendo, and the \< \! produces the
> hairpin one? They are separate commands, and in
Mats Bengtsson-4 wrote:
>
>
> This is exactly what happens if you use the command in version
> 2.10 or earlier, so the current behaviour in 2.11 is a regression
> bug.
>
> I have modified the definitions in the GIT source code repository so
> that \cresc and \dim only give one-time text dynam
George_ wrote:
...
As I said before (and I am even
more certain about this now) I think the \cresc and \dim should be changed
in future versions of Lilypond (especially with the stable release coming
up) to make them into one-time text dynamics.
This is exactly what happens if you use the comman
On Wed, Oct 29, 2008 at 11:59 AM, George_ <[EMAIL PROTECTED]> wrote:
>
> The exclusion of the command \cresc and \dim from this section, and the fact
> that there are actual commands giving a text crescendo (\crescTextCresc,
> \dimTextDecresc, \dimTextDecr, and \dimTextDim) sort of implies that \cr
Valentin Villenave wrote:
>
>
> cresc = {
>#(ly:export (make-event-chord (list cr)))
>\set crescendoText = \markup { \italic "cresc." }
>\set crescendoSpanner = #'text
> }
>
> I don't know why George used \cresc in the first place though.
>
>
Well, shouldn't the file be changed
> > The \cresc macro is defined in ly/spanners-init.ly and is preceded
> by a comment:
> >
> > % STOP: junkme!
> >
> > so it's clearly not well-supported It's certainly intended to
> generate a text style crescendo "cresc.".
> > However, at the time the macro was implemented, any setting of
> c
Valentin Villenave wrote:
2008/10/29 Brett Duncan <[EMAIL PROTECTED]>:
as clearly shown in Notation Reference 1.3.1, it there really a need to keep
it? I can't say that I've seen many instances of the text "cresc." without
the dashed line, but perhaps others have.
AFAICS it is used
2008/10/29 Brett Duncan <[EMAIL PROTECTED]>:
> as clearly shown in Notation Reference 1.3.1, it there really a need to keep
> it? I can't say that I've seen many instances of the text "cresc." without
> the dashed line, but perhaps others have.
AFAICS it is used quite a bit in one of our example
Valentin Villenave wrote:
Use the Source, Luke...
ly/spanners-init.ly, line 21:
cresc = {
#(ly:export (make-event-chord (list cr)))
\set crescendoText = \markup { \italic "cresc." }
\set crescendoSpanner = #'text
}
Okay, that makes things clearer (for me, at least).
I don't know w
Brett Duncan wrote:
The problem was that George had used the \cresc command in his file,
but had \crescHairpin command _before_ the \cresc command. Moving
\crescHairpin appears to have solved his problem.
I couldn't find \cresc in the Notation Reference, but it does appear
in the Internals
2008/10/29 Brett Duncan <[EMAIL PROTECTED]>:
> I couldn't find \cresc in the Notation Reference, but it does appear in the
> Internals Reference, where it is listed simply as an alternative notation
> for \<. From George's file, it appears to not only generate a text crescendo
> but also switch th
2008/10/29 Brett Duncan <[EMAIL PROTECTED]>:
> George's file was linked to in his previous email:
> http://www.nabble.com/file/p20216702/T.ly
Oh, it was hidden by a quoting format.
> From George's file, it appears to not only generate a text crescendo
> but also switch the display of crescendos t
Francisco Vila wrote:
2008/10/28 George_ <[EMAIL PROTECTED]>:
I did some tests and they came out perfectly fine, so it has to be something
wrong with my ly file, right? Except I can't find anything in there that I
did differently between the crescendo that came out right and the ones that
starte
2008/10/28 George_ <[EMAIL PROTECTED]>:
>
> I did some tests and they came out perfectly fine, so it has to be something
> wrong with my ly file, right? Except I can't find anything in there that I
> did differently between the crescendo that came out right and the ones that
> started coming out wr
2008/10/28 George_ <[EMAIL PROTECTED]>:
>
> I did some tests and they came out perfectly fine, so it has to be something
> wrong with my ly file, right? Except I can't find anything in there that I
> did differently between the crescendo that came out right and the ones that
> started coming out wr
I did some tests and they came out perfectly fine, so it has to be something
wrong with my ly file, right? Except I can't find anything in there that I
did differently between the crescendo that came out right and the ones that
started coming out wrong. The file includes one crescendo done correct
2008/10/28 George_ <[EMAIL PROTECTED]>:
>
> I didn't change anything in between the times when the crescendi came out as
> hairpins and when they came out as text. In any event, the crescendi don't
> revert to hairpins when I put in \crescHairpin. So, now I'm just confused...
>
> George
Try to iso
I didn't change anything in between the times when the crescendi came out as
hairpins and when they came out as text. In any event, the crescendi don't
revert to hairpins when I put in \crescHairpin. So, now I'm just confused...
George
Valentin Villenave wrote:
>
> 2008/10/28 George_ <[EMAIL P
2008/10/28 George_ <[EMAIL PROTECTED]>:
> For some reason, about 15 bars into typesetting a piece, whenever I use and
> \< to typeset crescendi, Lilypond outputs this with the word 'cresc.' This
> doesn't happen with \>, the decrescendo prints normally, and it only started
> occurring, as I said,
24 matches
Mail list logo
