convert-ly on macosx 10.4
I just noticed that convert-ly does not work from the lilypond.app menu item in osx 10.4. I have python installed. convert-ly works from the terminal, but here are the problems with the menu item. • If I update the convert-ly file to be: env python, lilypond does not find python. That's not unreasonable, the GUI versions of most command-line applications don't load the path properly. (It's a known issue with programs like Emacs.app or Aquamacs.app) • If I update the convert-ly file to be the exact path to my python installation (in this case /Users/jamesebailey/bin/python), lilypond finds python, but reports the error: 'import site' failed; use -v for traceback Traceback (most recent call last): File "/Users/jamesebailey/Applications/LilyPond.app/Contents/ Resources/bin/convert-ly", line 14, in import os ImportError: No module named os With either modification, running convert-ly from the terminal works without problem. Can this be resolved, or should convert-ly simply be removed from the menu in 10.4? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: an LM update
I realise it's only been a week since this was last discussed, but:
a) no one who can say whether or not this can be implemented has
responded (ever)
b) it's an open issue since apparently October. I just added it as a
user feature request.
c) Can we just make the change so that more people aren't confused by
the issue. (I've answered another question related to this in the
last week)
While we're on the subject, can I put in my two cents that voices
don't just up and die when they don't have anything to do? Having to
keep voices alive is sometimes annoying.
El 28.02.2009, a las 10:33, Trevor Daniels escribió:
James
We discussed this last October, and I agreed to make the change in
2.13, but then the suggestion was made (by Mats):
Better yet, why can't the shorthand automatically "do the right
thing"? i.e.,
<< {} \\ {} >>
should be translated automagically into
<< {} \new Voice {} >>
I'd rather not waste time changing the documentation now if this
code change is likely to be implemented. So, what's the chance
this change will be made? I've no idea whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ; "lilypond-
devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven't heard any feedback, I thought I would post to the
- devel list as well. Incidentally, I've answered questions
directly related to this twice in the last week or so.
Since the NR has the wonderful introduction to single-staff
polyphony, can this be simply inserted into the LM at the
appropriate point. I'm sure new users will have a much easier
time of engraving their music, and many problems can be avoided
later if this topic is presented in the LM the same way it's
presented in the NR. Unless, of course, there's a fundamental
reason not to. In which case, okay.
___
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: an LM update
James E. Bailey wrote Friday, March 06, 2009 8:31 AM
I realise it's only been a week since this was last discussed,
but:
a) no one who can say whether or not this can be implemented has
responded (ever)
b) it's an open issue since apparently October. I just added it as
a user feature request.
Good
c) Can we just make the change so that more people aren't confused
by the issue. (I've answered another question related to this in
the last week)
Yes, but I have lots of things on my to-do list and
little spare time available to do things, especially
things which might be invalidated shortly after.
While we're on the subject, can I put in my two cents that voices
don't just up and die when they don't have anything to do?
Well, temporary voices commonly used in piano music do.
Having to keep voices alive is sometimes annoying.
Another feature request - \set Voice.keepAlive = ##t ?
El 28.02.2009, a las 10:33, Trevor Daniels escribió:
James
We discussed this last October, and I agreed to make the change
in 2.13, but then the suggestion was made (by Mats):
Better yet, why can't the shorthand automatically "do the right
thing"? i.e.,
<< {} \\ {} >>
should be translated automagically into
<< {} \new Voice {} >>
I'd rather not waste time changing the documentation now if this
code change is likely to be implemented. So, what's the chance
this change will be made? I've no idea whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ;
"lilypond- devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven't heard any feedback, I thought I would post to
the - devel list as well. Incidentally, I've answered questions
directly related to this twice in the last week or so.
Since the NR has the wonderful introduction to single-staff
polyphony, can this be simply inserted into the LM at the
appropriate point. I'm sure new users will have a much easier
time of engraving their music, and many problems can be
avoided later if this topic is presented in the LM the same
way it's presented in the NR. Unless, of course, there's a
fundamental reason not to. In which case, okay.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: an LM update
El 06.03.2009, a las 10:51, Trevor Daniels escribió:
Yes, but I have lots of things on my to-do list and
little spare time available to do things, especially
things which might be invalidated shortly after.
Ah, I totally understand. I don't really want to make work that will
be for naught.
While we're on the subject, can I put in my two cents that voices
don't just up and die when they don't have anything to do?
Well, temporary voices commonly used in piano music do.
And that's exactly where I use this shorthand. I like it there.
Having to keep voices alive is sometimes annoying.
Another feature request - \set Voice.keepAlive = ##t ?
That would be awesome.
El 28.02.2009, a las 10:33, Trevor Daniels escribió:
James
We discussed this last October, and I agreed to make the change
in 2.13, but then the suggestion was made (by Mats):
Better yet, why can't the shorthand automatically "do the right
thing"? i.e.,
<< {} \\ {} >>
should be translated automagically into
<< {} \new Voice {} >>
I'd rather not waste time changing the documentation now if this
code change is likely to be implemented. So, what's the chance
this change will be made? I've no idea whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ;
"lilypond- devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven't heard any feedback, I thought I would post to
the - devel list as well. Incidentally, I've answered questions
directly related to this twice in the last week or so.
Since the NR has the wonderful introduction to single-staff
polyphony, can this be simply inserted into the LM at the
appropriate point. I'm sure new users will have a much easier
time of engraving their music, and many problems can be
avoided later if this topic is presented in the LM the same
way it's presented in the NR. Unless, of course, there's a
fundamental reason not to. In which case, okay.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: smaller distance between first Staff and TimeSig
Dear Neil,
I think I have solved the problem with the vertical distance, but now
the time-signatures don't disappear in the staves and I don't
understand why!
\version "2.12.0"
\paper {
ragged-last-bottom = ##f
page-limit-inter-system-space-factor = 1.3
#(set-paper-size "a4" )
system-separator-markup = \slashSeparator
}
\layout{
\context {
\type "Engraver_group"
\consists "Time_signature_engraver"
\consists "Text_spanner_engraver"
\consists "Text_engraver"
\consists "Dynamic_engraver"
\consists "Axis_group_engraver"
\name "TimeSig"
\override TimeSignature #'font-size = #3
\override TimeSignature #'break-align-symbol = #'staff-bar
\override TimeSignature #'X-offset: =
#ly:self-alignment-interface::x-aligned-on-self
\override TimeSignature #'self-alignment-X = #CENTER
}
\context {
\Score \accepts TimeSig
}
\context { \Staff
\remove "Time_signature_engraver"
}
\context { \TimeSig \override VerticalAxisGroup
#'keep-fixed-while-stretching = ##t
\override VerticalAxisGroup #'Y-extent = #'(-33 . 0)
\override VerticalAxisGroup #'minimum-Y-extent = ##f
%durch diese Einstellung wird gewährleistet, dass die Taktartkangabe
immer im gleichen Abstand über der Partitur erscheint!
}
}
\layout {
\context {
\RemoveEmptyStaffContext
}
\context { \Staff \override VerticalAxisGroup #'remove-first = ##t }
}
%%ENDE Layout!
global = { \time 3/4 s2. \time 4/4 s1 \break \time 5/4 s4*5 \time 4/4 s1 }
melodie = \relative { c4 c c c c c c R 4*5 R1}
nochnemelodie = \relative { R2. R1 e4 e e e e e e e e }
instrumentA = \new Staff { \melodie }
instrumentB = \new Staff { \nochnemelodie }
tempotakt = \new TimeSig
% \with { \override VerticalAxisGroup #'keep-fixed-while-stretching = ##t }
{ \override Score.TimeSignature #'style = #'( ) %heißt: die
Viervierteltakte werden nicht altmodisch angezeigt
%\override Score.BarNumber #'break-visibility = ##(#t
#t #t) %jede Taktzahl wird gezeigt, spaeter wieder loeschen!!
\override TimeSig.VerticalAxisGroup #'minimum-Y-extent
= #'(-0 . 1)
% \override Score.VerticalAlignment #'max-stretch =
#ly:align-interface::calc-max-stretch
\global }
\score { <<
\tempotakt
\instrumentA
\instrumentB
>> }
2009/3/6, Neil Puttock :
> 2009/3/5 Stefan Thomas :
>> Dear Lilypond-users,
>> I have the problem, in the below quoted example, that I can't reduce
>> the distance
>> between the TimeSig and the first Staff of the Score.
>> How can I do it? I tried it with
>> \override VerticalAxisGroup #'keep-fixed-while-stretching = ##t
>> but without success.
>
> You want to prevent the spacing engine from pulling the first stave
> away from the time signature, so you need to set
> 'keep-fixed-while-stretching in the Staff context *below* TimeSig (see
> the relevant docs here:
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing-inside-a-system#Vertical-spacing-inside-a-system)
>
>> \override TimeSignature #'X-:set =
>> #ly:self-alignment-interface::x-aligned-on-self
>
> Should be #'X-offset. Lilypond won't report a type-check failure here
> since the garbled property (#'X-:set) is set to a procedure.
>
> Regards,
> Neil
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: smaller distance between first Staff and TimeSig
Dear all,
I forgot to switch on
\override Score.VerticalAlignment #'max-stretch =
#ly:align-interface::calc-max-stretch
If I do so, the distance between topmost-Staff and TimeSig is too
large, in my opinion.
2009/3/6, Stefan Thomas :
> Dear Neil,
> I think I have solved the problem with the vertical distance, but now
> the time-signatures don't disappear in the staves and I don't
> understand why!
>
> \version "2.12.0"
> \paper {
>
> ragged-last-bottom = ##f
>
> page-limit-inter-system-space-factor = 1.3
>
>
> #(set-paper-size "a4" )
>system-separator-markup = \slashSeparator
>
> }
>
> \layout{
> \context {
> \type "Engraver_group"
>\consists "Time_signature_engraver"
> \consists "Text_spanner_engraver"
> \consists "Text_engraver"
> \consists "Dynamic_engraver"
> \consists "Axis_group_engraver"
> \name "TimeSig"
>\override TimeSignature #'font-size = #3
> \override TimeSignature #'break-align-symbol = #'staff-bar
>
> \override TimeSignature #'X-offset: =
> #ly:self-alignment-interface::x-aligned-on-self
> \override TimeSignature #'self-alignment-X = #CENTER
> }
> \context {
> \Score \accepts TimeSig
> }
>
>
> \context { \Staff
>\remove "Time_signature_engraver"
> }
> \context { \TimeSig \override VerticalAxisGroup
> #'keep-fixed-while-stretching = ##t
>\override VerticalAxisGroup #'Y-extent = #'(-33 . 0)
> \override VerticalAxisGroup #'minimum-Y-extent = ##f
> %durch diese Einstellung wird gewährleistet, dass die Taktartkangabe
> immer im gleichen Abstand über der Partitur erscheint!
>
> }
> }
> \layout {
> \context {
> \RemoveEmptyStaffContext
> }
> \context { \Staff \override VerticalAxisGroup #'remove-first = ##t }
> }
>
>
> %%ENDE Layout!
>
> global = { \time 3/4 s2. \time 4/4 s1 \break \time 5/4 s4*5 \time 4/4 s1 }
> melodie = \relative { c4 c c c c c c R 4*5 R1}
> nochnemelodie = \relative { R2. R1 e4 e e e e e e e e }
> instrumentA = \new Staff { \melodie }
> instrumentB = \new Staff { \nochnemelodie }
> tempotakt = \new TimeSig
> % \with { \override VerticalAxisGroup #'keep-fixed-while-stretching = ##t }
> { \override Score.TimeSignature #'style = #'( ) %heißt: die
> Viervierteltakte werden nicht altmodisch angezeigt
> %\override Score.BarNumber #'break-visibility = ##(#t
> #t #t) %jede Taktzahl wird gezeigt, spaeter wieder loeschen!!
> \override TimeSig.VerticalAxisGroup #'minimum-Y-extent
> = #'(-0 . 1)
> % \override Score.VerticalAlignment #'max-stretch =
> #ly:align-interface::calc-max-stretch
> \global }
> \score { <<
> \tempotakt
> \instrumentA
> \instrumentB
>>> }
>
>
> 2009/3/6, Neil Puttock :
>> 2009/3/5 Stefan Thomas :
>>> Dear Lilypond-users,
>>> I have the problem, in the below quoted example, that I can't reduce
>>> the distance
>>> between the TimeSig and the first Staff of the Score.
>>> How can I do it? I tried it with
>>> \override VerticalAxisGroup #'keep-fixed-while-stretching = ##t
>>> but without success.
>>
>> You want to prevent the spacing engine from pulling the first stave
>> away from the time signature, so you need to set
>> 'keep-fixed-while-stretching in the Staff context *below* TimeSig (see
>> the relevant docs here:
>> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing-inside-a-system#Vertical-spacing-inside-a-system)
>>
>>>\override TimeSignature #'X-:set =
>>> #ly:self-alignment-interface::x-aligned-on-self
>>
>> Should be #'X-offset. Lilypond won't report a type-check failure here
>> since the garbled property (#'X-:set) is set to a procedure.
>>
>> Regards,
>> Neil
>>
>
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
\bracket has no properties?
Hi all, Does the \bracket markup command have no user-settable properties? I'd like to change the thickness of the bracket, but don't want to roll my own... Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \bracket has no properties?
Unfortunately, it seems hard coded for the moment, but there's a comment in the file scm/define-markup-commands.scm about exactly this issue. /Mats Kieren MacMillan wrote: Hi all, Does the \bracket markup command have no user-settable properties? I'd like to change the thickness of the bracket, but don't want to roll my own... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \bracket has no properties?
> Kieren MacMillan wrote: >> Does the \bracket markup command have no user-settable properties? >> I'd like to change the thickness of the bracket, but don't want to roll my >> own... 2009/3/6 Mats Bengtsson : > Unfortunately, it seems hard coded for the moment, but there's a comment in > the > file scm/define-markup-commands.scm about exactly this issue. A possible job for a Frog? Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \bracket has no properties?
Hi all, Unfortunately, it seems hard coded for the moment, but there's a comment in the file scm/define-markup-commands.scm about exactly this issue. A possible job for a Frog? I'm officially jumping into the 'Pond on Wednesday of next week (after my two big deadlines on Sunday and Monday, and a day off on Tuesday) — if no one has taken the initiative by then, maybe I'll use that as my first non-doc task. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Again: stemBoth problem
2009/3/5 胡海鹏 - Hu Haipeng :
> I don't
> want to assign two separate voices with plenty of confusing spacer notes.
> \relative c' {
> \stemUp c8(^"I" d e f g a b c | )(_"II" \stemDown c b a g f e d | c1)
> }
Unfortunately, I'm afraid the only proper way to do it is to use
spacer notes. At least, that is what do anywhere I have such things
(yes, it is a bit painful to write, but the result is so perfect that
I never regret having spent time typing it).
The only other way I could see would be to write a function that
automatically turns the other voice into spacer notes (without having
to type it again, I mean). But I'm not sure it's worth it (anyway, I
haven't felt the need for such a function when typesetting my
400-pages opera).
Regards,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Editorial Annotation
2009/3/4 Neil Puttock :
> \relative c' {
> \once \override ParenthesesItem #'font-size = #0
> c1-\parenthesize \trill
> }
Now that *is* awesome.
Added to
http://lsr.dsi.unimi.it/LSR/Item?id=421
I think I have my "Snippet of the week" for the new LilyReport :)
Regards,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Again: stemBoth problem
2009/3/5 Robin Bannister : > Maybe these are trivial difficulties compared to those you constantly > cope with, but, as a general priciple, I would have thought you would be > better off going with the flow: > not fighting Lilypond but rather > letting Lilypond do its graphic thing as much as possible. Oh, I hadn't seen your reply. Sorry for the noise (but I'm glad we had the same reaction :-) Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: New ConTeXt module
Henning Hraban Ramm wrote: > > It works now with LilyPond 2.12 > i only found 2.10 keywords - where is 2.12? -- View this message in context: http://www.nabble.com/New-ConTeXt-module-tp22352883p22382461.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
