Re: Sponsored feature request--partially-tied chords
On Thursday 24 August 2006 17:39, Han-Wen Nienhuys wrote: Steve D wrote: On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Werner LEMBERG then asked: Just wondering what the much simpler syntax c~ e~ g b~ costs... Han-Wen Nienhuys responded: I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. Aside from being clear and simple (to the end user), it can save a lot of typing, especially because when lots of partially-tied chords appear in a piece of music as the result of a rhythmic or other motive. SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) After some thought, I agree with Werner (as usual), and I've changed the implementation to do this. Erik, can you look over my use of stream events vs. events in tie-engraver.cc? I have the feeling that the dichotomy between both is a bit ugly, but is there currently another way? With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? -- Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals tied over a line break
Markus: That's a way to manually suppress accidentals after a line break; thanks. But I need a way to do it automatically. Is the example in Section 9.3.7: Difficult Tweaks of any help? Kieren: That looks like it might be helpful, but I don't understand the syntax well enough to adapt the tweak on that page. ( http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Difficult-tweaks.html ) It seems like it might be possible to modify that tweak with Markus's accidental-suppression -- \once \override Staff.Accidental #'transparent = ##t -- but I can't figure out how to do this. Any tips? Thanks, Marcus P.S. Actually, I'm not sure that will be enough. It looks like transparent accidentals still take up space; I'd rather suppress the accidental *and* its allotted space. Surely there should be an easier way, even if it's possible to hack it somehow in the meantime. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Changing TimeSignature numerator and denominator
Actually, the order matters as well, so my solution works
if you keep the property setting after the \time command
(which internally also sets the same property in the Timing
context, among others).
/Mats
Trevor Bača wrote:
Oops. You were basically right, Mats. Here's a bit that works:
%%% BEGIN
\version 2.9.10
\new Staff {
\set Staff.timeSignatureFraction = #'(7 . 16)
\time 2/4
c'4
c'4
}
%%% END
Thanks as always!
(Right property, different context. Has nothing to do with .9.10
versus .9.13 differences.)
On 8/24/06, Trevor Bača [EMAIL PROTECTED] wrote:
Alas ...
%%% BEGIN
\version 2.9.10
\new Staff {
\set Timing.timeSignatureFraction = #'(7 . 16)
\time 2/4
c'4
c'4
}
%%% END
... interprets with no errors, but still prints as 2/4 ...
Perhaps because 2.9.10 ... I'll check with .13 in a bit ...
On 8/24/06, Mats Bengtsson [EMAIL PROTECTED] wrote:
Try
\time 2/4
\set Timing.timeSignatureFraction = #'(7 . 16)
/Mats
Quoting Trevor Bača [EMAIL PROTECTED]:
Hi,
Is there a way to change the printed numerator and denominator of a
time signature?
Seems like something here should do it, but all versions print as
2/4.
%%% BEGIN %%%
\version 2.9.13
\new Staff {
%\once \override TimeSignature #'fraction = #'(7 . 16)
%\once \override Staff.TimeSignature #'fraction = #'(7 . 16)
\once \override Score.TimeSignature #'fraction = #'(7 . 16)
\time 2/4
c'4 c'4
}
%%% END %%%
--
Trevor Bača
[EMAIL PROTECTED]
--
Trevor Bača
[EMAIL PROTECTED]
... like the dew, or like lightning ...
Click here to call me:
http://try.click-and-connect.com/cnc/4/1753206736/
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Midi block syntax?
LilyPond 2.9.16, Windows XP
I get the following error messang:
error: syntax error, unexpected \tempo
\midi {
\tempo 4=104}
Has the syntax changed since 2.9.15?
Thomas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
tweak of the crescendotext
Hi,
I have some notes where a poco a poco cresc. must be inserted...
so I put
\set crescendoText = \markup { \italic poco a poco cresc. }
\set crescendoSpanner = #'dashed-line
r4 \times 2/3 { a8-( \accent \ bes a) \!} r4
and it worked, but the text is too long, it goes over the end of the page
and the vertical position make it collide with the \accent.
Well with a little vertical padding and a centered alignment it should do
the trick.
But I'm not fluent enough with contexts and properties stuff, and the
documentation keeps confusing me.
is such a dynamic indication a TextScript or a DynamicText or something else
?... I tried some tweaks but everything failed.
A quick example would be welcome
thx
--
View this message in context:
http://www.nabble.com/tweak-of-the-crescendotext-tf2161916.html#a5974890
Sent from the Gnu - Lilypond - User forum at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi block syntax?
Did you try to upgrade the syntax using convert-ly?
Normally, such changes should also be present in the
NEWS file, but it seems that the new method to specify
MIDI tempo hasn't made it there.
/Mats
Thomas Scharkowski wrote:
LilyPond 2.9.16, Windows XP
I get the following error messang:
error: syntax error, unexpected \tempo
\midi {
\tempo 4=104}
Has the syntax changed since 2.9.15?
Thomas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi block syntax?
I tried to convert a 2.9.15 file using convert-ly before I sent the
message to the list: no change!
But... conversion works with older files!
Thomas
Did you try to upgrade the syntax using convert-ly?
Normally, such changes should also be present in the
NEWS file, but it seems that the new method to specify
MIDI tempo hasn't made it there.
/Mats
Thomas Scharkowski wrote:
LilyPond 2.9.16, Windows XP
I get the following error messang:
error: syntax error, unexpected \tempo
\midi {
\tempo 4=104}
Has the syntax changed since 2.9.15?
Thomas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Clef Markup
How can one print a markup over a clef sign? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clef Markup
I guess thishttp://www.lilypond.org/doc/v2.8/Documentation/user/lilypond/Text-marks.htmlanswer to your question On 8/25/06, Kamal [EMAIL PROTECTED] wrote: How can one print a markup over a clef sign? ___lilypond-user mailing listlilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Printing tempo marks on every part
I would like to specify things like tempo marks, double bars, rehearsal makrs in one part only (say piano part) but print them on very part. I want to print as below but only have to specify the details in one part == (Vn 1 part: ) Andante ... [A] . [B] Vn 1 music . == (Vn 2 part: ) Andante ... [A] . [B] Vn 2 music . == (Score: ) Andante ... [A] . [B] Vn 1 music . Vn 2 music . etc etc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Erik Sandberg wrote: With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? yes, I think I lost it in the din. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing tempo marks on every part
concerning the bars you may use a global part containing only skips and barsyou can then combine them as you wish (in a part or for all the parts).have a look at http://www.mutopiaproject.org/ftp/BachJS/BWV1068/bach-air/bach-air-lys.zipor http://www.lilypond.org/doc/v2.6/input/mutopia/E.Satie/petite-ouverture-a-danser.ly.txt I don't know if it works with rehearsal marks, but please test and publish your resultsOn 8/25/06, Andrew Black - lists [EMAIL PROTECTED] wrote:I would like to specify things like tempo marks, double bars, rehearsal makrs in one part only (say piano part) but print them on very part.I want to print as below but only have to specify the details in one part==(Vn 1 part: )Andante ... [A] . [B] Vn 1 music .==(Vn 2 part: )Andante ... [A] . [B]Vn 2 music .==(Score: )Andante ... [A] . [B] Vn 1 music .Vn 2 music .etc etc___lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing tempo marks on every part
You can also use \addquote and filter only desired events using
Staff.quotedEventTypes.
(http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Quoting-other-voic
es.html#Quoting-other-voices)
In pseudo code this would look like this:
somevoice = { }
partWithAllMarksAndStuff = {}
\addquote framework \partWithAllMarksAndStuff
\new Staff
\set Staff.quotedEventTypes =
#'(mark-event % Add more as needed
)
\context Voice = somevoice \somevoice
\context Voice = somevoice
\quoteDuring #framework { #(ly:export (skip-of-length
partWithAllMarksAndStuff)) }
Markus
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
yota wrote:
Hi,
I have some notes where a poco a poco cresc. must be inserted...
so I put
\set crescendoText = \markup { \italic poco a poco cresc. }
\set crescendoSpanner = #'dashed-line
r4 \times 2/3 { a8-( \accent \ bes a) \!} r4
and it worked, but the text is too long, it goes over the end of the page
and the vertical position make it collide with the \accent.
Well with a little vertical padding and a centered alignment it should do
the trick.
As a musician I would be very confused if you used centered
alignment, since I wouldn't realize exactly where you want
the crescendo to start. As far as I can recall from printed
music, the text is normally broken over the line break in
such situations, at least if the crescendo is long (your example
seems like an extremely short crescendo to be able to do
poco a poco). Another possibility would be to do
\markup{\italic \column {\line {poco a poco} cresc. }}
But I'm not fluent enough with contexts and properties stuff, and the
documentation keeps confusing me.
is such a dynamic indication a TextScript or a DynamicText or something else
?... I tried some tweaks but everything failed.
DynamicText should be the relevant object.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals tied over a line break
In the source code, I found a comment saying: TODO: insert support for smaller cautionaries, tie-break-reminders. ... which indicates that this is a feature that is not yet implemented. I made some quick attempts to solve the problem by redefining Accidental #'after-line-breaking but didn't manage. /Mats Marcus Macauley wrote: Hello, Currently, if a note with an accidental is tied over a line break, the accidental is repeated on the new line. Is there any way to turn off this behavior? I looked in the manual; 9.1.1 Automatic accidentals would seem to be the relevant section, but it doesn't say anything about tied accidentals. There's a regression test called accidental-tie.ly, but it merely explains that an accidental is present if the line is broken at the tie, which happens for the G sharp, without mentioning any way of turning off this behavior. It took me a while to find an instance of a note with accidental tied over a line break in the Henle edition of the Bach Well-Tempered Clavier, but when I eventually found one, the accidental was not repeated after the line break. (Book I, Fugue in B minor, measures 56-57. It happens to be a G-sharp.) So if my own desire to not repeat the accidental isn't enough, there's an example from G. Henle Verlag.* Thanks, Marcus (In fairness, the second instance I found did repeat the accidental: Book I, Fugue in C-sharp minor, measures 40-41, an A-sharp. Anyway, I think the user should be able to choose whether or not accidentals are displayed in these situations. And if they are repeated, the ties should not collide, as the currently do. The aforementioned A-sharp provides a good example of how a tie can avoid an accidental in such a case.) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals tied over a line break
Mats Bengtsson wrote: In the source code, I found a comment saying: TODO: insert support for smaller cautionaries, tie-break-reminders. ... which indicates that this is a feature that is not yet implemented. I made some quick attempts to solve the problem by redefining Accidental #'after-line-breaking but didn't manage. the right approach is to add an option to accidental-engraver.cc to ignore tied notes completely. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
ok I got ityou're right... with a centered alignment, the dynamic indication become too imprecise to be readable. But putting the text on two lines give a nice result.\set crescendoText = \markup{\italic \column {\line {poco a poco} {cresc.} }}
\set crescendoSpanner = #'dashed-line
r4 \times 2/3 {\once \override DynamicLineSpanner #'staff-padding = #1 a8-( \accent \ bes a) \!} r4
\repeat unfold 9 { r4 \times 2/3 { a8-( \accent bes a) } r4}I really would like to have an automatic line break, diplaying poco a poco on the end of the first staff and the cresc. at the start of the next staff. Well I could also do it by hand but it's a bit dirty
About the vertical positioning of the crescendotext. the property is in fact hidden in dynamiclinespanner #'staff-padding (even if there is no line span)that was the tip of the day :p
On 8/25/06, Mats Bengtsson [EMAIL PROTECTED] wrote:
yota wrote:Hi,I have some notes where a poco a poco cresc. must be inserted...so I put\set crescendoText = \markup { \italic poco a poco cresc. }
\set crescendoSpanner = #'dashed-liner4\times 2/3 { a8-( \accent \ bes a) \!} r4and it worked, but the text is too long, it goes over the end of the pageand the vertical position make it collide with the \accent.
Well with a little vertical padding and a centered alignment it should dothe trick.As a musician I would be very confused if you used centeredalignment, since I wouldn't realize exactly where you want
the crescendo to start. As far as I can recall from printedmusic, the text is normally broken over the line break insuch situations, at least if the crescendo is long (your exampleseems like an extremely short crescendo to be able to do
poco a poco). Another possibility would be to do\markup{\italic \column {\line {poco a poco} cresc. }}But I'm not fluent enough with contexts and properties stuff, and the
documentation keeps confusing me.is such a dynamic indication a TextScript or a DynamicText or something else?... I tried some tweaks but everything failed.DynamicText should be the relevant object.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
yota [EMAIL PROTECTED] wrote:
is such a dynamic indication a TextScript or a DynamicText or something else
?... I tried some tweaks but everything failed.
At the bottom of this page:
http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Dynamics.html#Dynamics
I found the answer to your question. It's the DynamicTextSpanner object
that has to be tweaked. Adding the override below moves your cresc
marking down and to the left (the firs number in the list (-5) moves it
to the left, and the second moves it down).
I personally like the extra-offset property since it allows me to move
an object in any way with only one command. I would assume that 'padding'
and 'center-align' properties would also work. The extra-offset property
is defined in the 'grob-interface' which is inherited by most
objects. The way to find out which preperties can be tweaked for a
particualr object is to look in the documentation (Dynamics in this
case) and check the name of the object. This name is hyperlinked to the
Program Reference in which the properties for this object are
listed. Further, the interfaces supported by that object are linked from
this page and those proerties can also be set through this object. All
that may or may not help you understand the documentation better ;-).
best,
/Henrik
\set crescendoText = \markup { \italic poco a poco cresc. }
\set crescendoSpanner = #'dashed-line
\override DynamicTextSpanner #'extra-offset = #'(-5.0 . -3.0)
r4 \times 2/3 { a8-( \accent \ bes a) \!} r4
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
Quoting Henrik Frisk [EMAIL PROTECTED]: I personally like the extra-offset property since it allows me to move an object in any way with only one command. I would assume that 'padding' and 'center-align' properties would also work. I hope you know that there is an important difference between extra-offset and the other properties that can be used to move things around. If you for example increase the padding, then LilyPond will take that fact into account when it calculates the placement of the next stave, for example, to avoid collisions. However, if you set extra-offset, then only that specific object will move and everything else will stay fixed. Sometimes that's preferable, but sometimes not. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
Mats Bengtsson [EMAIL PROTECTED] wrote: Quoting Henrik Frisk [EMAIL PROTECTED]: I personally like the extra-offset property since it allows me to move an object in any way with only one command. I would assume that 'padding' and 'center-align' properties would also work. I hope you know that there is an important difference between extra-offset and the other properties that can be used to move things around. If you for example increase the padding, then LilyPond will take that fact into account when it calculates the placement of the next stave, for example, to avoid collisions. However, if you set extra-offset, then only that specific object will move and everything else will stay fixed. Sometimes that's preferable, but sometimes not. Thanks Mats, I should of course have mentioned that. It's precisely this fact that makes extra-offset so useful to me. /henrik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Slur Control Points over page breaks?
Hi, Stewart: Is there any way of dealing with slurs over page breaks? Check out http://lilypond.org/doc/v2.9/Documentation/user/lilypond/ Difficult-tweaks.html. Replace Tie with Slur, 'extra-offset with 'control-points, etc. Good luck! Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Jazz Fonts
Recent convert to Lilypond - great work! I see that questions about jazz or ink pen fonts have come up several times over the years. Responses seem to be one of the following forms: - Theoretically, Lily can use other fonts but getting it to work is a lot of effort. - These fonts are not free so we can't test them. The second point is addressed, I think, by some free jazz fonts that are out there. I haven't looked at the specific licensing yet, but an alternative is of course to just design our own font. I'd like to understand the first point better. What's involved in adding support for alternative fonts? I may be able to do some work in this area, as I have need for producing scores with jazz fonts. What's the estimated learning curve for someone new to the codebase to dive in? I have many years of coding experience, especially advanced C++. Is there code documentation anywhere (doxygen, etc.)? Such fonts really do make a difference in performance. Someone mentioned venue lighting a while back and that is a great example. There is also an intangible edginess effect of the script which encourages experimentation in the performer. Thanks again for great software! -Dave ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing tempo marks on every part
yota moteuchi wrote: concerning the bars you may use a global part containing only skips and bars you can then combine them as you wish (in a part or for all the parts). have a look at http://www.mutopiaproject.org/ftp/BachJS/BWV1068/bach-air/bach-air-lys.zip or http://www.lilypond.org/doc/v2.6/input/mutopia/E.Satie/petite-ouverture-a-danser.ly.txt http://www.lilypond.org/doc/v2.6/input/mutopia/E.Satie/petite-ouverture-a-danser.ly.txt I don't know if it works with rehearsal marks, but please test and publish your results It works with rehearsal marks and more. For bigger scores I have global blocks like timing which define the time considerations and rehearsal marks and markup for things like Allegro. I might then have more than one global block for dynamics and things which only apply to some subset of the instruments. This has worked with any necessary padding for the markup and or dynamics set in the individual instrument parts even though I have an example of this which *may* not working in 2.9.15. Paul Scott ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi block syntax?
Strange! When I converted the following file
\version 2.9.15
\midi{\tempo 4=104}
using convert-ly from 2.9.16, the result was:
\version 2.9.16
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 104 4)
}
}
/Mats
Quoting Thomas Scharkowski [EMAIL PROTECTED]:
I tried to convert a 2.9.15 file using convert-ly before I sent the
message to the list: no change!
But... conversion works with older files!
Thomas
Did you try to upgrade the syntax using convert-ly?
Normally, such changes should also be present in the
NEWS file, but it seems that the new method to specify
MIDI tempo hasn't made it there.
/Mats
Thomas Scharkowski wrote:
LilyPond 2.9.16, Windows XP
I get the following error messang:
error: syntax error, unexpected \tempo
\midi {
\tempo 4=104}
Has the syntax changed since 2.9.15?
Thomas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing even eighth notes in a single bar
Quoting Kieren MacMillan [EMAIL PROTECTED]: [ v. 2.9.15 ] Hello, all -- I've got a bar of vocal (choral) text which ends up looking a bit uneven: An alternative to the proposals you already have received is to add a setting like \override LyricText #'minimum-X-extent = #'(0 . 5) in your lyrics. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? Yes, but it will take some time -- first, I'm just returning from a longer trip to Austria, and second, I don't have a Paypal account yet. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tweak of the crescendotext
should I fill a feature request to have long dynamic indications (the textual part, not the dashed line one) automatically splitted to the next staff when the text goes out of the page ? like this : http://img115.imageshack.us/my.php?image=lilypondfi4.pngbecause if I do the line break manually, when the dynamic indication is not at the end of the staff anymore I get strange collisions O_o ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? Yes, but it will take some time -- first, I'm just returning from a longer trip to Austria, and second, I don't have a Paypal account yet. Obviously, this is now obsolete -- pfffew :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with \char #65 ???
Ben Hoefer wrote:
Hi,
how does
\char #integer
work? (See chapter 8.1.6 of the LilyPond Guide.) Whenever I use
something like
copyright = \markup { \char #169 }
This is the right syntax, but there was a bug. This is fixed in the
latest version (2.9.16).
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Friday 25 August 2006 11:45, Han-Wen Nienhuys wrote: Erik Sandberg wrote: With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? yes, I think I lost it in the din. It's attached. This is a copy of the last patch, it's not a patch against the newest lily. === The attached patch makes a couple of further cleanups: - eliminate Grob_info::ultimate_music_cause, Grob_info::music_cause - possible bugfix in figured-bass-engraver: never decrement stop_moment - kill all remaining music refs in engravers; remove music.hh include from engraver.hh - use ASSIGN_EVENT_ONCE in engravers where appropriate - junk try_music in Translator, Translator_group, Context, Context_handle - small cleanup in part-combine-iterator; use an enum to distinguish between the outlet contexts. The only remaining part of the translator cleanup is, AFAIK, to remove obsolete translators. -- Erik es-060802-final-cleanups.diff.bz2 Description: BZip2 compressed data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Embedding lily pdfs in InDesign
Hi, Does anyone have any experience successfully embedding lily pdf output in InDesign? I start by creating a new InDesign doc and then placing the lily-generated pdf in the InDesign doc. Just to test I then export as pdf, and the results are pretty bad. Staff lines, ledger lines, beams and hairpins show up fine; but all noteheads, accidentals, and text are missing. My conclusion is that all font elements are missing (the cheese fonts for the music elements, and New Century Schoolbook for the text). So is there anyone out there putting lily-generated pdfs into InDesign successfully? (I would prefer to keep everything in lily, but using any fonts in lily at all other than New Century Schoolbook causes explosions when I send the pdf to the printers.) -- Trevor Bača [EMAIL PROTECTED] ... like the dew, or like lightning ... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
