time signature outside repeat bars in bagpipe music
In 2.7.10 I used:
[this is the opening measure of "The 79th's Farewell to Gibraltar";
there are bunches of stuff before this invoking default.ly which has
bagpipe.ly in it, and providing header information.]
{
% this is a bagpipe music default
\hideKeySignature
% set time
\time 2/4
% set length (in fractional notes) of the partial for any intro notes
% gracenotes need to go *before* \partial
%\grg \partial 8 c16.[ d32]
% \skip = invisible rest; this particular tap dance is to get the opening
% repeat bar line to both show up and be to the right of the time signature
\partial 32 \skip 32
\repeat volta 2 {
\grg \partial 8 c16.[ d32]
% notes go here
\grg e8.[ f16] \dble e8[ c8] |
\grg a4 \taor a8[ A8] |
\hdblf f8[ e16. c32] \grg e16.[ f32 \grg e16. d32] |
\dblc c8[ \grg b8] \taor b8[ \grg c16. d32] |
\grg e8.[ f16] \dble e8[ c8] |
\grg a4 \taor a8[ A8] |
\hdblf f8[ e16. c32] \grg e16.[ f32 \grg e16. d32] |
\dblc c8[ \gre a8] \wbirl a8 |
}
\break
% and the other three measures go here.
In 2.8.1 (on linux), this processes but I get an enormous empty space,
about 150% of the size of the other bars of music, between the time
signature and the repeat bar line, with subsequent bad side effects on
everything else.
This leads me to believe that the kludge I'm using to get the time
signature to be to the left of the repeat bar line (which is what the
College of Piping books use, so I conclude it's the approved bagpipe
music style) is the wrong way to do that.
What's the _right_ way to do that?
Thanks!
Graydon
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ADV: Re: time signature outside repeat bars in bagpipe music
On Sat, Apr 08, 2006 at 07:56:28PM +0200, Mats Bengtsson scripsit: > To get a |: printed at the start of the piece, use an > explicit \bar "|:". I've been using \set Timing.whichBar = "|:" to (so far as I understand it) over-ride the default Timing value of 'no bar' for the initial bar, which looks like it's working. Is there a reason to set it explicitly instead of doing it that way? > To get time signatures before bar lines instead of after, > you can do [snip] That works beautifully; thank you! Next silly question -- Many pipe tunes have an initial partial bar and a final partial bar in the measure, which should between them total an entire bar. Is there an existing way to barcheck this by telling lilypond that the first partial and the final partial should be considered together? So far as I can tell, there isn't. Thanks! Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Producing postscript for custom paper size (9x12" manuscript paper)?
On Mon, Apr 10, 2006 at 09:15:59AM -0700, Rick Hansen (aka RickH)
scripsit:
> I really need to be able to print my work on standard 9x12 sheet music
> paper too. But I dont understand how to make the code changes you've
> done without breaking my installation. I'm presuming it works for you
> now and the PDF is behaving itself in Adobe Reader.
% lilypond paper default is A4
\layout {
%#(set-default-paper-size "letter")
#(set-default-paper-size "letter" 'landscape ) }
is what I do -- in the defaults.ly file included via
\include "../defaults.ly"
in all the music I do to get letter, instead of A4 paper. The
"'landscape" is to print across the width instead of 'portrait'.
If -- as I think is the case -- your problem is that you don't have a
"concert' to replace the "letter" with, in paper.scm -- which is in
/pathtotoplevel/lilypond/usr/share/lilypond/current/scm on linux -- you
need to add the 'concert' paper type, as below.
(define-public paper-alist
;; don't use decimals.
;; ISO 216 has a tolerance of +- 2mm
'(("a7" . (cons (* 74 mm) (* 105 mm)))
("a6" . (cons (* 105 mm) (* 149 mm)))
("a5" . (cons (* 149 mm) (* 210 mm)))
("a4" . (cons (* 210 mm) (* 298 mm)))
("a3" . (cons (* 298 mm) (* 420 mm)))
("legal" . (cons (* 8.5 in) (* 14.0 in)))
("letter" . (cons (* 8.5 in) (* 11.0 in)))
("11x17" . (cons (* 11.0 in) (* 17.0 in)))
("concert" . (cons (* 9.0 in) (* 12.0 in)))
))
Once you've done that,
\layout { #(set-default-paper-size "concert" ) }
in your defaults.ly file ought to do it.
-- Graydon
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: UTF-8 encoding problems
On Sat, Apr 22, 2006 at 11:06:16AM -0700, jimmy2 scripsit: > I am trying to put french accents into my lyrics, and I am able to > enter these characters in the .ly file, but lilypond is not able to > process it correctly. I suspect that my editors (on linux) are not > saving the file with correct UTF-8 encoding. I tried with nedit, pico, > and vi. Does anyone know what is going wrong? What linux distribution are you using? (and what lilypond, too?) I've just tried putting some accented characters in the 'composer' and 'arranger' fields on Fedora Core 5 and it worked fine; I would expect absolutely anything that came out in the last three years to be fine for utf-8 handling. Any recent linux distro will be utf-8 by default; console editors (like nedit, pico, and vim) don't have the option of using any other encoding. (Well, vim does, but if you'd set that up you'd know it.) How are you entering the accented characters? Are you sure they're being entered as utf-8 and are not being cut-and-pasted from a file in a different encoding? If you're using vim, you should be able to use the 'ga' command on a character to get the encoding, so that (for example) é will show (in the lower left, if you get out of insert mode and use 'ga' as a command when the cursor is on the é) <é> 233, Hex 00e9, Octal 351 Is that what you're seeing? What are you seeing in the output? Blank spaces? the wrong character? multiple wrong characters per character? -- Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: UTF-8 encoding problems
On Sat, Apr 22, 2006 at 04:15:35PM -0700, jimmy2 scripsit: > Here is an example, e with accent aigue: é. It appears as it is > supposed to in my usual editors (pico, nedit). On the other hand, in > a working example with German accents which I downloaded from > lilypond, the special characters don't look like what they are > supposed to represent in these editors. I need to figure out how to > generate the characters I want in the correct encoding. Do you have > any suggestions? Are you sure you're viewing them in a console which is capable of handling the necessary glyphs? (konsole, from KDE, certainly is, but I can't speak to much else.) There are two obvious ways -- One is to use the 'Multi_key' feature of X11 and compose the characters -- this is a handy thing to map the keyboard "Windows" keys to -- as Multi_key + char + char; to get e accent aigue, I would type Windows + e + '. The other is to use the Unicode character picker in Open Office, (Insert->Special Character) which will certainly give you the right code point. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond packages now available in Fedora Extras
On Tue, May 23, 2006 at 11:17:37PM +0200, Jan Nieuwenhuizen scripsit: > Quentin Spencer writes: > > I mentioned on this list a while ago that I was trying to get > > lilypond into Fedora Extras. The first packages were released > > yesterday and they should now be installable using "yum install > > lilypond". > > That's grand, thanks! And for the very limited values of 'test' implied by a couple-six pipe tunes, it works dandy. Thanks! Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: can't install 2.8.4-1 on Fedora Core 5
On Tue, Jun 06, 2006 at 10:16:01AM -0500, Quentin Spencer scripsit: [snip] > Maybe the easiest solution to this is to use the lilypond rpms that are > now included in Fedora Extras. The current version is 2.8.3, but I'll > probably be updating to 2.8.4 soon. I have successfully used them with > SELinux enabled. By using the Fedora rpms, you will get an older version > of ghostscript (8.15 instead of 8.50), but in most cases it should be > adequate. I have Quentin's rpm running fine on a current FC5 box with SELinux set to enforcing. Haven't hit any ghostscript problems but am not doing anything complicated, either. -- Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barline problem
On Tue, Jun 13, 2006 at 01:15:35AM -0700, Dewdman42 scripsit: > Printing looks fine. I tried installing 3 different third party pdf > viewers, none of which looked any good at all..they all had drastic > line connection and line width issues. Perhaps someone can explain > this to me or tall me a pdf viewer that knows how to display properly > PDF's which have been rendered by lilypond. kpdf -- which won't do you any good if you're not running linux -- works fine for the lilypond output I generate. > I have created many PDF's myself through other programs that looked > WYSIWYG perfect. Apparantly lilypond is not that greatest at > producing PDF's. The printer output was excellent though. PDF's display elements are a proper subset of postscript, and you can (wiht the right software) go round-trip from each format through the other one without loss. Many display programs don't handle _all_ the postscript vector constructs; it's the usual tradeoff between fast and complete. Printer drivers, on the other hand, are expected to handle all of it. They're not going to _add_ information that isn't there in the original PDF, after all. -- Graydon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
