Strange TextScript behaviour?
Hello,
I found that TextScript requires some extra-offset when set above
slurred note AND has more than one symbol. Just take a look:
% -
%
%
%
\version 2.10.20
soprano = \relative c'' {
%
\voiceOne
%
% Text would be 7 units below it's original position...
\override TextScript #'padding = #-7
%
% ... but this padding forces the same position
% for all TextScripts above Staff:
\override TextScript #'staff-padding = #1.0
%
% Shift them a bit left:
\override TextScript #'extra-offset = #'(-3.0 . 0)
%
%
% Markup (two symbols -- no slur) -- no problem,
% as expected:
e4 f ^ \markup { \bold 11 }
g a
%
% Two symbols, slurred note -- 'staff-padding is ignored:
e4 f( ^ \markup { \bold 11 }
g a)
%
\break
%
% Well, 'slur-padding is ignored too?
\once \override TextScript #'slur-padding = #-7
%
e4 f( ^ \markup { \bold 11 }
g a)
%
% But _one symbol_ markup _with slur_ is great,
% with no 'slur-padding :
e4 f( ^ \markup { \bold 1 }
g a)
%
}
{ \soprano }
\paper {
indent = 0
}
% -
Very probably, I have missed something important -- please, tell me.
And, btw, is there other way to get all TextScripts positioned at the
same distance from staff?
Thanks,
--
_,-=._ /|_/|
`-.} `=._,.-=-._., @ @._,
`._ _,-. ) _,.-'
`G.m-^m`m'Dmytro O. Redchuk
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beginning-of-measure padding value?
Since you want to change the spacing after the time signature, you should
modify the space-alist property for the TimeSignature:
\override TimeSignature #'space-alist = #'(
(first-note . (fixed-space . 12.0)) ; Default = 2.0
(right-edge . (extra-space . 0.5))
(staff-bar . (minimum-space . 2.0)))
/Mats
Trevor Bača wrote:
Hi Kieren, hi Mats,
As long as we're somewhat on the topic, how do we get more space
before the first note of each *line* (as opposed to each measure)?
Here's an example:
%%% BEGIN %%%
\version 2.11.20
\new Score \with {
\override BarLine #'space-alist = #'(
(time-signature extra-space . 0.75)
(custos minimum-space . 2.0)
(clef minimum-space . 1.0)
(key-signature extra-space . 1.0)
(key-cancellation extra-space . 1.0)
(first-note fixed-space . 10.3)
(next-note semi-fixed-space . 10)
(right-edge extra-space . 0.0))
} {
\new Staff {
c'4 c'4 c'4 c'4
d'4 d'4 d'4 d'4
}
}
%%% END %%%
There's more space before the ds (because of next-note); but how can
we get more space before the cs?
(Side question: isn't there some way to set individual pairs in an
alist separately? I seem to remember there being a way to do that, but
can't find anything on a quick manual scan.)
--
=
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: midi2ly: makeshift patch
On 4/9/07, Graham Percival [EMAIL PROTECTED] wrote: Alexander Hanysz wrote: Below is a patch for what on my system is the file /usr/local/lilypond/usr/bin/midi2ly (I'm using version 2.10.20). Fixed (?): the --key command line argument is recognised; key signatures and time signatures now appear correctly; rests are visible. Do you have a test file for this? If I can easily verify that this works, I'll commit these changes. Not tested: changes of key or time within a piece. To do: correct notation for syncopated notes and for rests that span more than one bar; the --output argument doesn't seem to work. Unfortunately I won't have time to continue working on this. (I'm up against a deadline, so I have to go back to using Finale to finish my arrangement :-( ) But someone who actually knows what they're doing shouldn't find it too hard to fix this up. Unfortunately the main developers are very busy at the moment; we don't have time to fix up patches. If any users here know python and are interested in helping, we welcome any assistance; otherwise this work will go to waste. Speaking from experience, python is an easy language to learn. If any users here are interested in helping out but don't know any programming languages, python (and midi2ly) would be a great place to start. Cheers, - Graham I'm also a bit time limited, but I have some knoledge in python. Could one of you send me the patched version and a description of the buggy parts. I could be able to fix it enough to insert it into the code ...well I hope so :) Yota ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange TextScript behaviour?
I don't follow exactly what you try to do. However, the vertical position is
determined based on one of a number of different rules, depending on which
one sets the strictest limits. In your case,
- The staff-padding detemines the minimum distance to the stave.
- The padding determines the minimum distance to the closest
object (stem or stave or note head or whatever). In your particular
example the stem is the closest object.
- The slur-padding determines the minimum distance to the slur,
if the text script extends above the slur. In your example, the difference
between 1 and 11 is that LilyPond thinks that the former is only
above the stem, not the slur, whereas 11 extends so far to the right
that it's considered to be above the slur.
If you want a fixed distance to the stave, just set a large enough value
of staff-padding, so that this setting dominates the other ones.
Also, instead of using the extra-offset to change the horizontal position,
you may want to set
\override TextScript #'self-alignment-X = #RIGHT
As you will notice, this setting changes many of your conclusions, for
example
since LilyPond will no longer think that any of the text scripts is
above any slur.
I recommend you to remove all your other \override:s as a starting point.
Note also, that your score will look different if you upgrade to the latest
development version (or when you upgrade to version 2.12 when it will
be released some time in the future).
/Mats
Dmytro O. Redchuk wrote:
Hello,
I found that TextScript requires some extra-offset when set above
slurred note AND has more than one symbol. Just take a look:
% -
%
%
%
\version 2.10.20
soprano = \relative c'' {
%
\voiceOne
%
% Text would be 7 units below it's original position...
\override TextScript #'padding = #-7
%
% ... but this padding forces the same position
% for all TextScripts above Staff:
\override TextScript #'staff-padding = #1.0
%
% Shift them a bit left:
\override TextScript #'extra-offset = #'(-3.0 . 0)
%
%
% Markup (two symbols -- no slur) -- no problem,
% as expected:
e4 f ^ \markup { \bold 11 }
g a
%
% Two symbols, slurred note -- 'staff-padding is ignored:
e4 f( ^ \markup { \bold 11 }
g a)
%
\break
%
% Well, 'slur-padding is ignored too?
\once \override TextScript #'slur-padding = #-7
%
e4 f( ^ \markup { \bold 11 }
g a)
%
% But _one symbol_ markup _with slur_ is great,
% with no 'slur-padding :
e4 f( ^ \markup { \bold 1 }
g a)
%
}
{ \soprano }
\paper {
indent = 0
}
% -
Very probably, I have missed something important -- please, tell me.
And, btw, is there other way to get all TextScripts positioned at the
same distance from staff?
Thanks,
--
=
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: beginning-of-measure padding value?
On 4/11/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
Since you want to change the spacing after the time signature, you should
modify the space-alist property for the TimeSignature:
\override TimeSignature #'space-alist = #'(
(first-note . (fixed-space . 12.0)) ; Default = 2.0
(right-edge . (extra-space . 0.5))
(staff-bar . (minimum-space . 2.0)))
Ah, good. This is what I was looking for.
Reference example of moving over first note on the line (when there's
a time signature):
%%% BEGIN %%%
\version 2.11.20
\new Score \with {
\override TimeSignature #'space-alist = #'(
(first-note fixed-space . 10.0)
(right-edge extra-space . 0.5)
(staff-bar minimum-space . 2.0))
} {
\new Staff {
c'4 c'4 c'4 c'4
d'4 d'4 d'4 d'4
}
}
%%% END %%%
Incidentally, if you remove Time_signature_engraver, the TimeSignature
#'space-alist does nothing:
%%% BEGIN %%%
version 2.11.20
\new Score \with {
% this override does nothing ...
\override TimeSignature #'space-alist = #'(
(first-note fixed-space . 10.0)
(right-edge extra-space . 0.5)
(staff-bar minimum-space . 2.0))
} {
\new Staff \with {
% ... because of this remove
\remove Time_signature_engraver
} {
c'4 c'4 c'4 c'4
d'4 d'4 d'4 d'4
}
}
%%% END %%%
However, since the order of preferatory material is [clef - time
signature - key signature], and since there is now neither a key
signature nor time signature, it's still possible to scoot the first
note over using the first-note attribute in the Clef #'space-alist:
%%% BEGIN %%%
\version 2.11.20
\new Score \with {
\override Clef #'space-alist = #'(
(ambitus extra-space . 2.0)
(staff-bar extra-space . 0.7)
(key-cancellation minimum-space . 3.5)
(key-signature minimum-space . 3.5)
(time-signature minimum-space . 4.2)
(first-note minimum-fixed-space . 15.0) % this is the scooted value
(next-note extra-space . 0.5)
(right-edge extra-space . 0.5))
} {
\new Staff \with {
\remove Time_signature_engraver
} {
c'4 c'4 c'4 c'4
d'4 d'4 d'4 d'4
}
}
%%% END %%%
So the relevant observation seems to be: there's no general way to say
move the first note of the lline over 12 units; instead, first
figure out what the last (rightmost) preferatory grob is
(immediately before the first note) and then change the first-note
attribute of the #'space-alist of that rightmost preferatory grob.
Thanks, Mats.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
How to show chord symbols inside a staff?
I have been looking for a way to print chord symbols inside a stafff, to no avail. This is common for jazz combo and big band arrangements for solo parts, because it saves space. Does anyone have tips on how to do this? TIA, Henk van Voorthuijsen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to show chord symbols inside a staff?
Do you mean that the chord symbols should be printed overwriting the staff lines? Do you have any example that you can refer to (preferably a link to some web page)? /Mats Henk van Voorthuijsen wrote: I have been looking for a way to print chord symbols inside a stafff, to no avail. This is common for jazz combo and big band arrangements for solo parts, because it saves space. Does anyone have tips on how to do this? TIA, Henk van Voorthuijsen ___ 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: How to show chord symbols inside a staff?
Quoting Mats Bengtsson [EMAIL PROTECTED]: Do you mean that the chord symbols should be printed overwriting the staff lines? Do you have any example that you can refer to (preferably a link to some web page)? When I took jazz theory and arranging at university we used to do symbols on top and roman numerals in the bar lines, a really handy way of laying out a chart for improvising. You can easily see the chords and a reminder of their context. That would be dead cool to be able to score in lilypond, but might be a bit of a fringe case ... Thanks for your tips Mats! iain ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: producing archival scores
On Mon, Apr 09, 2007 at 11:29:28PM -0400, Jason Merrill wrote: (snip) There is not now, nor ever will be, some universal music language. MusicXML is an option, but not one everybody will choose. One could ask the exact same question by replacing 'lilypond' with 'MusicXML'. The issue with archival (it seems to me) is a format whose source will always be readable and whose output will always be viewable. Seems to me Lilypond and MusicXML are the only ones that provide both of these. They also seem to me to be the only two options that are non-proprietary so others will not have purchase anything to access your work. Whether you prefer MusicXML or Lilypond is a matter of taste, methinks. Obviously the people on this list are going to have a marked bias towards Lilypond, but that is indeed another question. I could argue that Finale is also a music interchange format that is widely supported. MusicXML is just one more way of encoding music. Any format that uses plain text as source and a non-proprietary compiler I think is a perfectly decent archival option. There's an important distinction to be drawn here. MusicXML vs Lilypond is not just a matter of taste because the two clearly have different goals. MusicXML is objectively a terrible format for inputting music from a computer keyboard. However, according to Wikipedia, MusicXML is supported to varying degrees by over 75 different notation programs, including the two leading scorewriting programs, Finale and Sibelius. Because it is supported by many different programs of all types (graphical and ascii, free and non-free, etc.), and because it is open so that any project can add support for it, MusicXML is currently a viable interchange format. Lilypond is not readable by such a large array of programs, and so is currently a less viable interchange format. Now, it is possible (but seemingly not likely) that in the future all these and other programs will adopt support for lilypond, which would make it a viable interchange format. Barring that, though, and in it's current state, lilypond is something of a black hole. You can turn anything else into lilypond via MusicXML, but once you've worked on it in lilypond, there's no obvious way to get it back into a different editable format. Luckily, this problem could be entirely addressed on Lilypond's end if it could be compiled to a suitable interchange format. Figuring out if there was already a way to do this was the intent of my original question. In my opinion, being able to get a file into an interchange format as I've described here is one property (certainly not the only property) that helps make it archival. (snip) I should say that I make no claims about MusicXML being in some way ideal for interchange. It may or may not have inherent features that make it better than lilypond or other formats for interchange. The only things it has going for it that I know or care about are that it is open, and that it has done a good enough job marketing itself that it is already widely supported. The latter is, I suspect, no small task, which is why one might satisfy themselves with using MusicXML for interchange rather than trying to make their favorite format into an interchange format by convincing everyone else in the world to support it. A few years ago Chris Cannam interviewed Jan and Han-Wen about the LilyPond project, and there was some discussion about the shortcomings of MusicXML and how it differs from LilyPond. I'm not sure if it adds much to this discussion, but it might be relevant. The interview itself has disappeared, but it was Slashdotted and some kind soul posted the text of the article (and was promptly modded -1 Troll, but there you go.) If you want to have a look, go to http://slashdot.org/comments.pl?sid=100385cid=8559721 If you can get past the GNAA trolls there were a few interesting comments made, too. Have a look at http://slashdot.org/article.pl?sid=04/03/13/2054227 -- = Cameron Horsburgh = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
