Re: Slurs going both directions
Look at the examples, tips & trickx andregression tests - I seem to remember exactly that situation in one of them. Specifically check http://lilypond.org/development/input/test/out-www/test.html (or http://lilypond.org/stable/input/test/out-www/test.html) and search for slur ... /Hans ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: multiple \scores in a lily-book included file?
I agree to a certain extent. Judicious use of < music > and { music } and
\break - along with a very strict naming rules (drawing on years of large
project s/w coding experience) - helped me recently (70+ page Cantata).
You are however quite correct - the source score blocks are very, very
ugly.
I could also request the reverse - having an external file containing the
music assigned to an Identifier, I'd love to be able to 'extract bars 3-8'
into the current score.
/Hans
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Slurs going both directions
Is this possible? The music I'm typesetting has a voice going from the right-hand staff to the left-hand staff. (I'm using the \translator function.) Four quarter-notes are slurred together, the first two on the upper staff with stems down, the second two on the lower staff with stems up. The slur should be between the staves. It should have it's left end tilted up, and its right end tilted down. Is this possible? -- Daniel Ashton PGP key available http://Daniel.AshtonFam.org mailto:[EMAIL PROTECTED] http://ChamberMusicWeekend.org mailto:[EMAIL PROTECTED] ICQ# 9445142 http://ZephyrBrass.com ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Brackets
Hello,
How can I put accidentals in between brackets? And is there a
better way to achieve this on articulation (and how to center it):
g4^#'(columns ((font-relative-size . 1) ("[ ")) ((raise . 0.8) (music
"scripts-mordent")) ((font-relative-size . 1) ("]")) )
--
Best regards,
Jérémie mailto:[EMAIL PROTECTED]
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Clef change before first note
Graham Percival wrote: On Sat, 15 Mar 2003 18:21:13 -0500 Daniel Ashton <[EMAIL PROTECTED]> wrote: I need an organ right-hand staff in which the first symbols are G clef, key signature, time signature, F clef, eight rest, notes, etc The G clef is not visible. How can I force the G clef to show up, then display the F clef as a (smaller) clef-change symbol? You could probably get it with a spacer note: \clef G \key a \major \time 17/16 \partial 16 s16 \clef F r8 True, and I hadn't thought of it. Thanks. However, you get a barline. I added \bar "" to get rid of it. \partial 8 s8 \bar "" This seems to render a fairly acceptable result, but it really feels like a hack. Is there a less convoluted solution? Notice that the problem is only seen when doing a temporary clef change before the first note or rest. After the first note or rest the clef change works just fine, leaving the initial clef visible as expected. Thanks again for your ready answers, Graham. -- Daniel Ashton PGP key available http://Daniel.AshtonFam.org mailto:[EMAIL PROTECTED] http://ChamberMusicWeekend.org mailto:[EMAIL PROTECTED] ICQ# 9445142 http://ZephyrBrass.com ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Clef change before first note
On Sat, 15 Mar 2003 18:21:13 -0500 Daniel Ashton <[EMAIL PROTECTED]> wrote: > I need an organ right-hand staff in which the first symbols are > >G clef, key signature, time signature, F clef, eight rest, notes, etc > > The G clef is not visible. How can I force the G clef to show up, then > display the F clef as a (smaller) clef-change symbol? You could probably get it with a spacer note: \clef G \key a \major \time 17/16 \partial 16 s16 \clef F r8 HTH, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Clef change before first note
I need an organ right-hand staff in which the first symbols are G clef, key signature, time signature, F clef, eight rest, notes, etc The G clef is not visible. How can I force the G clef to show up, then display the F clef as a (smaller) clef-change symbol? -- Daniel Ashton PGP key available http://Daniel.AshtonFam.org mailto:[EMAIL PROTECTED] http://ChamberMusicWeekend.org mailto:[EMAIL PROTECTED] ICQ# 9445142 http://ZephyrBrass.com ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: multiple \scores in a lily-book included file?
On Sat, 15 Mar 2003 10:49:28 -0700 Hans Forbrich <[EMAIL PROTECTED]> wrote: > Any reason for needing separate 'score' starts. It seems you want to > use the'sequential' capability, something like The scale example was the simplest to explain, but I agree that it doesn't really need seperate score entires. However, other things _do_ need multiple score blocks. For example, consider a Minuet and Trio. In some (or most?) publications (I'm thinking of Mozart stuff, rather than baroque music), there's a block of music which is the trio, then a line break and a new block of music. Something like this: minuet :||: =:|| trio === :||: ==|| That's simple to do with two \score blocks, but it'd be extremely difficult to do with only one \score block. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 1.7 fixes
I've used 1.7.13 since release (+ about 1 week), 1.7.12 for about 1 month
before 13 - absolutely no crashes, no unexpected output, etc. I am very
pleased.
My environment is Linux - SuSE 8.0, and I rebuilt the latest version of all
the prerequisite programs (needed Bison 1.875a to complete the 1.7.13 install
... thanks for figuring that out, Jan)
All of my use has been traditional church-choir-vocal Guitar-Chords + Solo +
SA + TB + Piano (2 voices each hand) and I recently completed a 70+ page
Cantata that needed selective transposing. No issues, no glitches, beautiful
output, and only one thing requiring future attention (stem alignment for
stemUp when mixing notehead sizes).
For other uses, I can not comment.
The incentive to move to 1.7 was the fixed chordnames. The benefits included
a much better chord mode << >>, very clearly handling multiple voices in one
voice line using < {} \\ {} >, much nicer markup, and the new \transpose
syntax.- to name a few. (In fairnes, the multiple voice capability might have
been there in 1.6 - I didn't check).
There are a few things I'd like to see before 1.8, including having a 'macro'
to call up the rehearsal-mark font, similar to \small, \italic, \large, etc.
(should give an idea of my opinion of the required improvements).
So for the use described, I encourage upgrading to 1.7 ...
/Hans
David Bobroff wrote:
> ability to put text markup over block rests. How stable is it? I'm
> currently running 1.6.8 on Cygwin. To run 1.7 I'd have to run it on Linux
> (just have to rearrange some furniture) wouldn't I?
>
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: multiple \scores in a lily-book included file?
Any reason for needing separate 'score' starts. It seems you want to use the
'sequential' capability, something like
\score {
\transpose c'{ \scale }
\transpose g' { \scale }
\transpose d'{ \scale }
}
This would run the c' scale, followed immediately by then the g', etc. Or,
by putting a \break after each \scale you could have each scale on a separate
line as well.
BTW, I really like the 1.7 transpose syntax - \transpose c' g' { } (from and
to) - you can link the transpose request to the key change, for example
\tranpose aes d {}
/Hans
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 1.7 fixes
Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: ...>If the \mark had a two digit number the lack of quotes didn't cause any problems. Putting in the quotes fixed it. This is a bug which I fixed in 1.7 CVS. So in 1.7 are the quotes necessary? I'd like to move up to 1.7.x for the ability to put text markup over block rests. How stable is it? I'm currently running 1.6.8 on Cygwin. To run 1.7 I'd have to run it on Linux (just have to rearrange some furniture) wouldn't I? It's fairly stable. We're moving towards a 1.8 release now. The downside is that it requires GUILE 1.6, so you will have to install that by hand. Guile 1.6 is packaged at Debian unstable. LilyPond 1.6.6-2 in Debian unstable depends on Guile-1.6 (or Guile-1.4) How far away is Lily 1.8 for Debian unstable? Or were you only referring to Cygwin? Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 1.7 fixes
> "David" == David Bobroff <[EMAIL PROTECTED]> writes: David> I'd like to move up to 1.7.x for the ability to put text David> markup over block rests. How stable is it? My experience with the 1.5-1.6 transition is that 1.5 was "stable" over most of it's life in the sense of not producing terrible output. And on the rare occasions where a bug did cause terrible output, it got fixed in a very timely manner. Unfortunately, there were still input syntax changes being made quite late in the 1.5 cycle, so that a lot of the work I did on 1.5.x can't be compiled with either the 1.4 or the 1.6 "stable" versions. This is a major problem for the stuff that's on my website. When people find transcription errors, I can't just change the note and say "make" to get a corrected version. And also unfortunately, convert-ly isn't maintained in the sense that all syntax changes, or even all minor syntax changes for which conversion would be easy, are added as conversions to the appropriate version. So my current advice is that for production work, you should only use a version labeled "stable". I believe that there's a commitment that the input syntax doesn't change between releases of a stable version. For something you expect to do this week and use next week and never look at again, you should use any version that has features you like, and it would be virtuous to use the development version to provide feedback on it to the developers. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
1.7 fixes
[EMAIL PROTECTED] writes: > >...>If the \mark had a two digit number the lack of quotes > >> didn't cause any problems. Putting in the quotes fixed it. > > > >This is a bug which I fixed in 1.7 CVS. > > So in 1.7 are the quotes necessary? I'd like to move up to 1.7.x for the > ability to put text markup over block rests. How stable is it? I'm > currently running 1.6.8 on Cygwin. To run 1.7 I'd have to run it on Linux > (just have to rearrange some furniture) wouldn't I? It's fairly stable. We're moving towards a 1.8 release now. The downside is that it requires GUILE 1.6, so you will have to install that by hand. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
1.7 fixes
>...>If the \mark had a two digit number the lack of quotes >> didn't cause any problems. Putting in the quotes fixed it. > >This is a bug which I fixed in 1.7 CVS. So in 1.7 are the quotes necessary? I'd like to move up to 1.7.x for the ability to put text markup over block rests. How stable is it? I'm currently running 1.6.8 on Cygwin. To run 1.7 I'd have to run it on Linux (just have to rearrange some furniture) wouldn't I? Thanks, David Bobroff The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
\mark fixed
[EMAIL PROTECTED] writes: > > After a bit of looking at it I saw that I did not always have quotes around > the rehearsal mark. If the \mark had a two digit number the lack of quotes > didn't cause any problems. Putting in the quotes fixed it. This is a bug which I fixed in 1.7 CVS. thanks for the report. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
\mark fixed
>>In the following Lilycode there are two instances of "\mark". They are >>generating errors: >> >>*** >>error: syntax error, unexepected DIGIT: \mark 1 (\mark 2) >>*** >> >> >> >Are you sure the digit wasn't in quotes the times it worked? I know that: > >\mark "1" > >works for me and is shown that way in the manual under Writing Parts/ >Rehearsal marks. > After a bit of looking at it I saw that I did not always have quotes around the rehearsal mark. If the \mark had a two digit number the lack of quotes didn't cause any problems. Putting in the quotes fixed it. Thanks, David The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Repeats and ties
Hi.
If have such a score:
\repeat volta 2 {d1 c} \alternative {{~c d c}{~c}}
I would like that the ~c in the second alternative was tied to the last c
before alternatives and not to the last c in the first alternative. How to
produce it?
--
Marco
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: \mark error
David Bobroff wrote: In the following Lilycode there are two instances of "\mark". They are generating errors: *** error: syntax error, unexepected DIGIT: \mark 1 (\mark 2) *** Are you sure the digit wasn't in quotes the times it worked? I know that: \mark "1" works for me and is shown that way in the manual under Writing Parts/ Rehearsal marks. Have fun, Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
\mark error
In the following Lilycode there are two instances of "\mark". They are
generating errors:
***
error: syntax error, unexepected DIGIT: \mark 1 (\mark 2)
***
I can't figure this out as this is *exactly* how I've done it in two other
files which process just fine. Here is the offending code:
\score{
\notes \relative c, {
\property Score.MultiMeasureRest \override #'expand-limit = #9
\property Score.breakAlignOrder = #'(
instrument-name
left-edge
ambitus
span-bar
breathing-sign
clef
staff-bar
key
time-signature
)
\property Score.RehearsalMark \override #'molecule-callback =
#(make-molecule-boxer 0.15 0.3 0.3 Text_item::brew_molecule)
\clef F
\property Score.skipBars = ##t
\property Voice.subdivideBeams = ##t
\time 6/8
\key f \major
R2.*12 %% NEEDS TEMPO MARKING!! --> Allegro vivace
a8->-\ff r r r4 r | R2. %% NEEDS "Vuota"
R2.*14 | f8->-\ff r r r4 r8
\bar "||"
\mark 1
R2.*12 %% NEEDS TEMPO MARKING!! --> Molto più lento
\bar "||"
R2.*12 %% NEEDS TEMPO MARKING!! --> Iº Tempo
\mark 2
R2.*9
Thanks,
David Bobroff
Lilypond 1.6.8 on Cygwin
The irony is that Bill Gates claims to be making a stable operating system
and Linus Torvalds claims to be trying to take over the world.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: improving docs (was: Break_Align_Order-3)
On Fri, 14 Mar 2003 23:48:21 -0700 Paul Scott <[EMAIL PROTECTED]> wrote: > I can certainly do some of that. My next concern/question would be > concerning versions. I use whatever is packaged for Debian unstable - > currently 1.6.6. Is there much point improving that documentation when > the development is done on a later version? I see the online manual is > actually 1.6.0. That's a bit misleading -- IIRC, the "version number" of the manual is simply a string in the .itely or .tely file. The manual _has_ been updated since 1.6.0. About what version to document: 1.6.x is frozen (apart from major bug fixes), and that unfortunately applies to the documentation too. So doc patches would need to apply to 1.7.x. However, most things that were hard to learn for 1.6.6 (which is what's in Debian right now) will still be hard to learn for 1.7.x, so you could still work on the documentation for 1.7.x although you just use 1.6.6. Alternately, you could work on other things -- the "tricks" examples, or an entirely seperate document about common problems, or a FAQ, or something ilke that. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
