James Harkins writes:
> - The wow factor. There isn't much software that truly knocks my socks
> off *every time* I use it. Supercollider totally changed the way I
> approach composing. Lilypond has done something I thought was
> impossible when I was using -- hm, that's not right, let's try
> "f
J Ruiz writes:
> I'm setting the printKeyCancellation to false, to avoid Lilypond
> printing naturals when switching keys, but no luck; Lily still prints
> the cancellation naturals.
> What am I missing?
>
> \version "2.14.2"
> \score{
> \new Staff {
> \override Staff.Clef #'full-size-change
Han-Wen Nienhuys writes:
> On Mon, May 28, 2012 at 3:17 PM, David Kastrup wrote:
>> It would be nice to have fewer incompatible modes, and simpler ways of
>> extending them.
>>
>> And "the C++ must go" with regard to how LilyPond can be extended. If
>> parts of LilyPond require "object orientat
On Tue, May 29, 2012 at 2:46 AM, wrote:
> James Harkins writes:
>
>> I'm attaching a couple of samples of today's typesetting work. The
>> first is pretty well marked up. The second is mostly just the notes
>> for now (needs articulation, dynamics and some adjustments of tie
>> curves -- later).
Tim McNamara schrieb:
> On May 28, 2012, at 1:46 PM, Hannes Kuhnert wrote:
> > On the other hand donations to a non-profit organisation would give the
> > contributor a benefit on income tax (think as higher donations at same
> > effort).
>
> That's not a bad point an there is some truth to that, b
I'm setting the printKeyCancellation to false, to avoid Lilypond printing
naturals when switching keys, but no luck; Lily still prints the cancellation
naturals.
What am I missing?
\version "2.14.2"
\score{
\new Staff {
\override Staff.Clef #'full-size-change = ##t
\relative c''{
\cadenz
Greetings Marcel,
You wrote:-
+++
In this piece, I want to add bar lines between staves where bar line
is "||" or "|.", but not when bar lines are "|" or ":".
+++
A bit
On Mon, May 28, 2012 at 03:38:28PM -0700, lilyp...@umpquanet.com wrote:
> On Mon, May 28, 2012 at 09:48:29AM -0400, Louis Guillaume wrote:
> >
> > There is, however, one thing that I find impossible, that is, having two
> > of the same tension in the chord symbol expression. There is a single
>
On Mon, May 28, 2012 at 09:48:29AM -0400, Louis Guillaume wrote:
>
> There is, however, one thing that I find impossible, that is, having two
> of the same tension in the chord symbol expression. There is a single
> case I can think of and that is having both flat-nine and sharp-nine on
> a dom
Tim McNamara writes:
> On May 28, 2012, at 1:17 PM, David Kastrup wrote:
>>
>>> As great as Lilypond's output is, there is a long way to go in terms
>>> of simplification and usability (the syntax needs to be simplified
>>> dramatically; a lot of the code users have to write is pretty ugly and
>
Tim McNamara writes:
> On May 28, 2012, at 1:46 PM, Hannes Kuhnert wrote:
>> Tim McNamara schrieb:
>>> Sending money directly to developers instead of to a central Lilypond
>>> account cuts a lot of costs and eliminates much of the need for
>>> organizational bureaucracy (e.g., an accounting depa
Hi,
> \mark \markup {
> \musicglyph #"scripts.segno" } is just printing a nice graphic.
and imho it does that better than any other program I used.
best regards
Kai
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/lis
On Mon, May 28, 2012 at 11:38 PM, Tim McNamara wrote:
> I was thinking about simplification like being able to put in a coda with
> \coda or a segno with \segno instead of things like
>
> \mark \markup { \musicglyph #"scripts.segno" }
>
> and so on. The more complicated the incantations are, th
On May 28, 2012, at 1:17 PM, David Kastrup wrote:
>
>> As great as Lilypond's output is, there is a long way to go in terms
>> of simplification and usability (the syntax needs to be simplified
>> dramatically; a lot of the code users have to write is pretty ugly and
>> is going to scare off poten
On 28 mai 2012, at 20:55, Dossy Shiobara wrote:
> On 5/28/12 9:48 AM, Louis Guillaume wrote:
>> In chord mode:
>>
>>c:7.9-.9+
>>
>> In regular markup:
>>
>>
>>
>> Both of these produce a chord symbol AND chord without the flat-nine.
>> It seems to only accommodate one 9th, and uses
On May 28, 2012, at 1:46 PM, Hannes Kuhnert wrote:
> Tim McNamara schrieb:
>> Sending money directly to developers instead of to a central Lilypond
>> account cuts a lot of costs and eliminates much of the need for
>> organizational bureaucracy (e.g., an accounting department).
>
> On the other ha
Am 2012-05-28 um 21:26 schrieb David Kastrup:
Hannes Kuhnert writes:
Tim McNamara schrieb:
Sending money directly to developers instead of to a central
Lilypond
account cuts a lot of costs and eliminates much of the need for
organizational bureaucracy (e.g., an accounting department).
O
Hannes Kuhnert writes:
> Tim McNamara schrieb:
>> Sending money directly to developers instead of to a central Lilypond
>> account cuts a lot of costs and eliminates much of the need for
>> organizational bureaucracy (e.g., an accounting department).
>
> On the other hand donations to a non-profi
On 5/28/12 9:48 AM, Louis Guillaume wrote:
> In chord mode:
>
> c:7.9-.9+
>
> In regular markup:
>
>
>
> Both of these produce a chord symbol AND chord without the flat-nine.
> It seems to only accommodate one 9th, and uses the last one encountered.
>
> Is there a way to do work around
Tim McNamara schrieb:
> Sending money directly to developers instead of to a central Lilypond
> account cuts a lot of costs and eliminates much of the need for
> organizational bureaucracy (e.g., an accounting department).
On the other hand donations to a non-profit organisation would give the
co
On Mon, May 28, 2012 at 8:34 PM, David Kastrup wrote:
> GLISS is going to be about taking account, and seeing where we want to
> be heading. But we will still need to tackle every step on the way.
> GLISS itself will not be changing things, it will only outline changes.
> And when somebody then i
Janek Warchoł writes:
> On Mon, May 28, 2012 at 7:21 PM, Tim McNamara wrote:
>> As great as Lilypond's output is, there is a long way to go in terms
>> of simplification and usability (the syntax needs to be simplified
>> dramatically;
>> a lot of the code users have to write is pretty ugly and
On Mon, May 28, 2012 at 7:21 PM, Tim McNamara wrote:
> As great as Lilypond's output is, there is a long way to go in terms
> of simplification and usability (the syntax needs to be simplified
> dramatically;
> a lot of the code users have to write is pretty ugly and is going to scare
> off pote
Tim McNamara writes:
> FWIW with today's exchange rate for Americans, the €15 I sent = US
> $19.37 (minus fees). I don't know what the going hourly rate for
> developers is where David lives;
If you pay by the hour, ridiculous (sth like €120 is not rare), but
there are jobs paid by the "guessed
James Harkins writes:
> I'm attaching a couple of samples of today's typesetting work. The
> first is pretty well marked up. The second is mostly just the notes
> for now (needs articulation, dynamics and some adjustments of tie
> curves -- later). As in earlier work on this piece, it's kind of
>
On May 28, 2012, at 9:29 AM, James Harkins wrote:
>
> Related: I can't say I read the list very closely, so somehow I overlooked
> the fact before that David K.'s livelihood comes from working on Lilypond. I
> had assumed Lilypond was almost completely a volunteer effort (like
> SuperCollider,
Hi!
I'm working out a set of chord symbols to suit my needs, based primarily
on pop-chords.ly. For the most part everything works beautifully, and
I'm sure any issues with alignment, spacing etc. can be sorted out using
the tools. Very nice!
There is, however, one thing that I find impossibl
James Harkins writes:
> Really, it blows me away. It's insane that notation software should be
> so smart. The LOMUS award is absolutely well-deserved. Many, many
> thanks and congratulations to the developers.
>
> Related: I can't say I read the list very closely, so somehow I
> overlooked the f
Hi all,
Again, please have a look at http://pastebin.com/uxvQGR7y
In this piece, I want to add bar lines between staves where bar line
is "||" or "|.", but not when bar lines are "|" or ":". I already
tried to use SemiChoirStaff [1], but that didn't work out properly, I
think because I moved "Def
"Philip Thomas" writes:
> For example, some trials that didn't work included the following (the
> context is correctly Staff, I think, and not Score, because I moved
> the Volta_engraver from the Score to Staff context so that it would
> appear on each line in the vocal score):
>
> \override Staf
>On 21/5/2012 Philip Thomas wrote:
>> At any rate, my problem with the colliding volta bracket remains.
>On 21 May 2012 Thomas Morley replied:
>Perhaps you may want to try the code below, in which I used the break-
>visibility-property to deal with a TimeSignature.
>It's _very_ hackish and dirt
Am 28.05.2012 11:40, schrieb David Kastrup:
-Eluze writes:
m...@apollinemike.com wrote:
Try:
\set tupletFullLength = ##t
\set tupletFullLengthNote = ##t
r
unfortunately this doesn't help here
as a workaround you can use \hideNotes r8 \unHideNotes iso of the spacer.
Maybe \once \hid
-Eluze writes:
> m...@apollinemike.com wrote:
>>
>>
>>
>> Try:
>>
>> \set tupletFullLength = ##t
>> \set tupletFullLengthNote = ##t
>>
>> r
>>
>>
>
> unfortunately this doesn't help here
>
> as a workaround you can use \hideNotes r8 \unHideNotes iso of the spacer.
Maybe \once \hideNotes r
m...@apollinemike.com wrote:
>
>
>
> Try:
>
> \set tupletFullLength = ##t
> \set tupletFullLengthNote = ##t
>
> r
>
>
unfortunately this doesn't help here
as a workaround you can use \hideNotes r8 \unHideNotes iso of the spacer.
I've tracked this as bug, see
https://code.google.com/p/li
-- Forwarded message --
From: Stefan Thomas
Date: 2012/5/28
Subject: Re: tuplet bracket starts too late after shorter-rest
To: "m...@apollinemike.com"
It has no effect, unfortunately
2012/5/28 m...@apollinemike.com
> On 28 mai 2012, at 09:52, Stefan Thomas wrote:
>
> > Dear
On 28 mai 2012, at 09:52, Stefan Thomas wrote:
> Dear community,
> I have a problem within the below quoted snippet.
> The Tupletbracket starts to late, I think because of the shorter-rest. What
> do I have to do to get the full-length?
> Here is the snippet:
> %%
> \version "2.1
Dear community,
I have a problem within the below quoted snippet.
The Tupletbracket starts to late, I think because of the shorter-rest. What
do I have to do to get the full-length?
Here is the snippet:
%%
\version "2.14.2"
le = { \change Staff="left" }
ri = { \change Staff="right"
37 matches
Mail list logo
