Re: segfault in 2.14.2 debian package
Il 24/10/2011 20:44, Don Armstrong ha scritto: You're not running Debian. This looks like an issue with guile-1.8 which has been fixed in Debian but not in Ubuntu, or you're mixing and matching Debian and Ubuntu packages and have found a API/ABI issue. In any event, this isn't a problem with the Debian packages, so I can't really help you. Believe me, I'm using Debian: # lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux testing (wheezy) Release:testing Codename:wheezy This is the version of guile-1.8: # aptitude show guile-1.8 Package: guile-1.8 State: installed Automatically installed: yes Version: 1.8.8+1-6 I'm not mixing Debian/Ubuntu. Maybe my sources.list is not much clean (http.us.debian.org is a "double entry" and it shouldn't probably be there). I'm asking for help on italian debian users list. Do you tink there's something that may affect lilypond installation? deb http://ftp.it.debian.org/debian/ testing main non-free deb-src http://ftp.it.debian.org/debian/ testing main deb http://security.debian.org/ wheezy/updates main deb-src http://security.debian.org/ wheezy/updates main # Debian Multimedia deb http://www.debian-multimedia.org/ wheezy main non-free # Lumiera Depot deb http://http.us.debian.org/debian/ wheezy main deb http://lumiera.org/debian/ squeeze experimental deb-src http://lumiera.org/debian/ squeeze experimental ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: slightly offtopic,
Am 25.10.2011 um 08:57 schrieb David Rogers: > Francisco Vila writes: > >> 2011/10/25 ole : >>> Option+a did the trick (I'am on Mac OS X using Jedit with LilypondTool), >>> very easy... >> If you newly discovered that, how could you have written it in your email in >> the first place? > > (If the mail client is set for UTF-8 but the editor is not... or if someone > has the feeling "This is Lilypond; I'll have to find hard ways of doing > everything...") :) I just copy & paste it from an .doc in the mail but did not try that with my .ly file (exactly because I thougth that it could not be that easy...:-)) ole ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Updates to bagpipe.ly
On 21 October 2011 00:52, Jon Chalk wrote: > I think I may have found a small problem with bagpipe.ly... Each > embellishment that uses \small should have a \normalsize after it. Man, I can't believe I haven't noticed that before! Or anyone else using bagpipe.ly for that matter. Anyhow, for now, just change line 94 in share/lilypond/VERSION/ly/bagpipe.ly from \grace $notes to \small \grace $notes \normalsize You can also remove all other instances of \small in the file, since they are now redundant. Graham, or anyone on the bug sqad: Do you want me to submit a proper diff for this change? -- Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Making feathered beams more variable
Hi David,
David Nalesnik-2 wrote:
>
> Hi Harm,
>
> On Mon, Oct 24, 2011 at 4:09 PM, Thomas Morley <
> thomasmorle...@googlemail.com> wrote:
> (...)
>> Values like "0" or values greater than the stem-count are faking
>> \override
>> Beam #'grow-direction = #LEFT (RIGHT). (This is not very elegant: switch
>> on
>> the color in \layout).
>>
>
> I'm not sure what I'm supposed to see here -- looks fine to me. (There
> must
> be a way to get around needing to give a non-existent "feather" a length
> of
> 0.001 to avoid division by zero, though, but my head gets a bit tangled up
> thinking about it!)
>
I'm looking for a method to integrate something like:
(if (= number 0)
use: \override Beam #'grow-direction = #LEFT
(if (>= number stem-count)
use: \override Beam #'grow-direction = #RIGHT
otherwise use: \override Beam #'stencil = (grow-beam-var arg)
into the Beam-stencil-override.
I'm aware of the possibility to create a function to do that, but this is
not intended.
So, is it possible to program (grob-property-set! grob 'grow-direction LEFT)
somewhere in a stencil-override?
>>One little problem: With values between 0 and 1 (p.e. 0.5 or 0.8) I
retrieve
>> every time the same output. Well, no one would ever enter such strange
>> values and perhaps I'm a little bit paranoic, but could it be, that
>> there's
>> a problem I can't see?
>>
>
> I think I solved this problem by changing the definition of the variable
> x-L. So now you can create all sorts of questionable subtleties (see
> image)
> :)
>
Thanks a lot for improving my function several times and answering all my
questions about beams!
There are two problems left.
First tiny problem:
The output with kneed-beams is ugly in some cases:
This example gives a overlooking stem at beam-end (test-code only)
xy = \once\override Stem #'french-beaming = ##t
\relative c {
\once\override Beam #'stencil = #(grow-beam-var 5)
f32 [ \xy f''' f,,, \xy f''' f,,, \xy f''' f,,, \xy f''' f,,, \xy
f''']
}
I'm not sure how to fix. 'french-beaming only works with the inner stems.
Is there a default-command I can't find? Should I integrate something into
the definition of grow-beam-var? Or create a separate override for this
stem?
Regarding the following example I'm not sure: should the peak point up or
down? What do you think?
\relative c' {
\override Beam #'auto-knee-gap = #4
\override Beam #'stencil = #(grow-beam-var 16)
c''32 [b a g
f g a b
c b a g
f g a b
e,,, c''' b a
g a b c
d c b a
g a b c]
c1
}
Second problem.
I tried to use \featherDuration with my Definition, but it doesn't work as
expected (seems it works only once a beam):
\relative c'' {
\override Beam #'stencil = #(grow-beam-var 7)
a64 [
\featherDurations #(ly:make-moment 1 2)
{a a a
a a a a}
a
\featherDurations #(ly:make-moment 2 1)
{a a a
a a a a
a a a a
a a a a
a a a a
a a a} a]
a2
}
Any idea?
Many thanks,
Harm
--
View this message in context:
http://old.nabble.com/Making-feathered-beams-more-variable-tp32705102p32718725.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: segfault in 2.14.2 debian package
On Tue, 25 Oct 2011, Federico Bruni wrote: > Il 24/10/2011 20:44, Don Armstrong ha scritto: > >You're not running Debian. This looks like an issue with guile-1.8 > >which has been fixed in Debian but not in Ubuntu, or you're mixing and > >matching Debian and Ubuntu packages and have found a API/ABI issue. In > >any event, this isn't a problem with the Debian packages, so I can't > >really help you. > > Believe me, I'm using Debian: Ah, sorry. If you are running Debian, please file a bug using reportbug against lilypond. That will give me enough additional information that I can at least start to see what is going wrong. Don Armstrong -- Where I sleep at night, is this important compared to what I read during the day? What do you think defines me? Where I slept or what I did all day? -- Thomas Van Orden of Van Orden v. Perry http://www.donarmstrong.com http://rzlab.ucr.edu ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: segfault in 2.14.2 debian package
Il 25/10/2011 20:05, Don Armstrong ha scritto: Ah, sorry. If you are running Debian, please file a bug using reportbug against lilypond. That will give me enough additional information that I can at least start to see what is going wrong. Filed a report here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646632 Hope it's ok. Thanks, Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Updates to bagpipe.ly
On 11-10-25 07:38 AM, Sven Axelsson wrote: On 21 October 2011 00:52, Jon Chalk wrote: I think I may have found a small problem with bagpipe.ly... Each embellishment that uses \small should have a \normalsize after it. Man, I can't believe I haven't noticed that before! Or anyone else using bagpipe.ly for that matter. Anyhow, for now, just change line 94 in share/lilypond/VERSION/ly/bagpipe.ly from \grace $notes to \small \grace $notes \normalsize You can also remove all other instances of \small in the file, since they are now redundant. Graham, or anyone on the bug sqad: Do you want me to submit a proper diff for this change? Yes, please! Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: gregorian.ly omissions
Greetings Trevor, Thank you for the clarification regarding episema usage in LP. There was a bit of confusion here with some things working at cross-purposes, as well as a bit of confusion within my personal CPU! :) It's nicely sorted now, and is working well. If you feel able, could you point me in the right direction to enable making the Gregorian markings 'ictus' 'circulus' etc larger than their defaults? Thanks again, Regards Bill ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Spacing
I just built a hymn under 2.14.2 using the Hymn structure from Learning Lilypond 2.12.3 secn 3.2.3 "Voices & Vocals". The structure is unaltered, except that I have added a \version and a \header (and there are only 2 vv iso 4!). I find that the first system is kind of jammed up against the header line giving the poet and composer, and I'd like some more vertical white space in there. Secondly, the whole thing is in 3 systems, with room for a fourth, so I also have some spare real estate on the page. What directives, commands, instructions etc should I be looking at to put a little more "air" into its appearance? Rgds, GFStC. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing
You wrote...
++
I just built a hymn under 2.14.2 using the Hymn structure from Learning
Lilypond 2.12.3 secn 3.2.3 "Voices & Vocals". The structure is
unaltered, except that I have added a \version and a \header (and there
are only 2 vv iso 4!).
I find that the first system is kind of jammed up against the header
line giving the poet and composer, and I'd like some more vertical white
space in there.
Secondly, the whole thing is in 3 systems, with room for a fourth, so I
also have some spare real estate on the page.
What directives, commands, instructions etc should I be looking at to
put a little more "air" into its appearance?
Rgds, GFStC.
++
There was a query about spacing sometime recently with a response by
Reinhold Kainhofer who has a clever site which allows one to generate
empty music score sheets in a variety of layouts.
From one of these I made use of the following:-
+++
\paper {
left-margin = 20\mm
right-margin = 10\mm
% top-margin = 10\mm
bottom-margin = 10\mm
% oddHeaderMarkup = ##f
% evenHeaderMarkup = ##f
pages=4 %fiddle this to suit
systems-per-page=3 %fiddle this to suit
ragged-bottom=##f
ragged-last-bottom=##f
ragged-last=##f
ragged-right=##f
top-system-spacing #'basic-distance = #7
top-markup-spacing #'basic-distance = #5
last-bottom-spacing #'basic-distance = #10
markup-system-spacing #'basic-distance = #7
top-system-spacing #'stretchability = #60
top-markup-spacing #'stretchability = #40
last-bottom-spacing #'stretchability = #60
markup-system-spacing #'stretchability = #60
system-system-spacing #'stretchability = #40
}
+++
By fiddling with the number of systems per page and the number of pages,
and some of the other values it is possible to make a very pleasing
layout from your existing file...
It would pay to read this paper block in conjunction with the LP manuals
to fully understand what is being done!
Hope this helps
Regards
Bill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
