bounty hack for some (non-Mike) Schemer out there
Hello all! A few weeks ago, in response to Mike Solomon's call for features and bugs, I posted a request: >> 2. Allowing a text markup (especially a MetronomeMark) to have a "minimum >> measure length". This would avoid collisions, particularly where there are >> lots of multi-measure rests (e.g., orchestral parts). His response was: > #2 is doable via a hack. Minimum lengths can only work if you use spanners, > but you can hijack the tempo print function for a text spanner (and suppress > the line afterwards) and then create a scheme engraver for text spanner that > uses whatever as the left bound and the next bar line's non-musical paper > column as the right bound. Or you could just use the existing engraver and > use the last note in the measure as a bound, although this will potentially > create uneven spacing in a measure. > > You'll have to manually put this TextSpanner in the topmost context and/or > use ly:side-position-interface::move-to-extremal-staff (I'd recommend the > former, as the latter is powerful but falls in the category of LilyPond black > magic). Make sure to use springs and rods and set a minimum-length - there's > an example in the docs with a hairpin or glissando or something spanner-y > that does this. Is there anyone out there who can work on this with me? I've got some money to put towards the implementation. Thanks! Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cron jobs - redirecting output question
- Original Message - From: "Graham Percival" To: "Phil Holmes" Cc: "Devel" Sent: Monday, February 04, 2013 7:58 AM Subject: Re: Cron jobs - redirecting output question On Sun, Feb 03, 2013 at 03:10:38PM -, Phil Holmes wrote: I understand that this means that all output is sent to the null device - i.e. discarded. Is there any reason not to send it to a file, to aid debugging should there be any problems? My thinking would be that the filename wouldn't change, so it would be over-written each time the script is run. No clue, but go ahead and experiment. Please check it once a day or at the beginning just to make sure that it is indeed overwriting the same file and not chewing up disk space, since we don't own the server. But I don't anticipate any problems with it. Cheers, - Graham Works fine - reveals a lot of errors in the make website shell script - about 300 similar to this: rsync: failed to set permissions on "/[directory redacted]/ties-scoring-example.png": Operation not permitted (1) Any ideas how to fix this? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Ugly images in learning
In http://www.lilypond.org/doc/v2.17/Documentation/learning/style-sheets the metronome mark is shifted so far it moves off the left of the image... -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Ugly images in learning
2013/2/4 Phil Holmes : > In > > http://www.lilypond.org/doc/v2.17/Documentation/learning/style-sheets > > the metronome mark is shifted so far it moves off the left of the image... > > -- > Phil Holmes Was ugly in the 2.14.2-LM, too. But nice with 2.12.3 I wonder why the MetronomeMark is offset via 'extra-offset. Why not use: \override MetronomeMark.break-align-symbols = #'(left-edge clef time-signature) and/or an override for 'self-alignment-X -Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cron jobs - redirecting output question
On Mon, Feb 04, 2013 at 03:09:02PM -, Phil Holmes wrote: > rsync: failed to set permissions on "/[directory > redacted]/ties-scoring-example.png": Operation not permitted (1) > > Any ideas how to fix this? It's probably an issue of whether the file/directory is owned by graham, hanwen, or jan, and what the unix permissions are. However, in the case of any wrong owner/permissions, I'm not certain how to go about fixing it. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [gmane.comp.gnu.lilypond.general] Re: Transposing instruments
David Kastrup gnu.org> writes:
> Shouldn't we have a command
>
> \transposing f { ... }
>
> (better naming suggestions welcome) that does transposition and Midi
> correction in lockstep?
I assume the command would produce the music that we currently get from
{\transposition f \transpose f c' {...}}
In that case it seems like a good idea, because it serves the
second-most-common of the three use-cases:
1) Make the sounding pitches (for midi and cues) different from written.
Such as when transcribing existing music, or when writing for transposing
instruments where you need to consider the instrument capabilities. Often
the transposition changes in the middle of the music, because transposing
instruments are the ones that performers most often need to exchange, so
it is good that this is done with a property-set in \transposition
2) Transpose written pitches, but leave sounding pitches alone.
Such as when arranging music (written at concert pitch) among different
instruments:
{\transposition bes \transpose bes c' {...} }
3) Shift pitches, both sounding and written.
When producing an alternate score at higher pitch, maybe for a particular
singer's range, if the music involves cues or midi. Except for the
complications of issue 754, this is done with simply \transpose c d {...}
Maybe documenting the existing \transpose and \transposition better would
be enough. In any case, the first thing to do is resolve issue 754.
Documenting transposing instruments in LilyPond is tricky with that bug,
because we either run into the bug, or teach how to depend on the bug.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
