Re: beginner problem

On 02/12/13 13:18, Siena wrote: SoundsFromSound gmail.com> writes: Siena wrote Hi all - I just downloaded LilyPond, ran the test which worked fine, and now I'm trying to follow the tutorial, and ran into a problem right off at the command line section. When I open LilyPond, a command prompt

Re: beginner problem

On 12/01/2013 06:51 PM, Siena wrote: Hi all - I just downloaded LilyPond, ran the test which worked fine, and now I'm trying to follow the tutorial, and ran into a problem right off at the command line section. When I open LilyPond, a command prompt box opens, which is I assume where I'm suppose

Re: beginner problem

Siena wrote > SoundsFromSound > > gmail.com> writes: > >> >> Siena wrote >> > Hi all - I just downloaded LilyPond, ran the test which worked fine, >> and >> > now >> > I'm trying to follow the tutorial, and ran into a problem right off at >> the >> > command line section. When I open LilyPond

Re: beginner problem

SoundsFromSound gmail.com> writes: > > Siena wrote > > Hi all - I just downloaded LilyPond, ran the test which worked fine, and > > now > > I'm trying to follow the tutorial, and ran into a problem right off at the > > command line section. When I open LilyPond, a command prompt box opens, > >

Re: beginner problem

Siena wrote > Hi all - I just downloaded LilyPond, ran the test which worked fine, and > now > I'm trying to follow the tutorial, and ran into a problem right off at the > command line section. When I open LilyPond, a command prompt box opens, > which is I assume where I'm supposed to type the com

beginner problem

Hi all - I just downloaded LilyPond, ran the test which worked fine, and now I'm trying to follow the tutorial, and ran into a problem right off at the command line section. When I open LilyPond, a command prompt box opens, which is I assume where I'm supposed to type the command "lilypond test.ly

Gittip (was: Frescobaldi Project Support)

SoundsFromSound wrote > I wonder how the [Gittip] system works and how effective it could be for > FLOSS development. I have been keeping my eye on Gittip. It's basically a tool that lets individuals make ongoing weekly payments to other individuals (or organizations) to support whatever work the

Re: Problems with LilyJAZZ.ily

Thomas Morley writes: > 2013/11/26 Federico Bruni : > >> If Marc or Harm are reading this message, I've just compiled bendtest.ly >> with 2.17.96 and there's a problem in measure 10: a beam appears and I get >> this warning: >> >> Drawing systems... >> >> bendtest.ly: warning: no viable initial c

Re: Problems with LilyJAZZ.ily

Hi, 2013/12/2 Thomas Morley : > 2013/11/26 Federico Bruni : > >> If Marc or Harm are reading this message, I've just compiled bendtest.ly >> with 2.17.96 and there's a problem in measure 10: a beam appears and I get >> this warning: >> >> Drawing systems... >> >> bendtest.ly: warning: no viable in

Re: Problems with LilyJAZZ.ily

2013/11/26 Federico Bruni : > If Marc or Harm are reading this message, I've just compiled bendtest.ly > with 2.17.96 and there's a problem in measure 10: a beam appears and I get > this warning: > > Drawing systems... > > bendtest.ly: warning: no viable initial configuration found: may not find >

Re: text accidentals [was Re: film score example]

2013/11/30 Joseph Rushton Wakeling : > On 30/11/13 12:30, Janek Warchoł wrote: >> >> We'll see how to split the amount between sponsors when i'm finished - >> i originally intended to do just flat, natural and sharp, so doing all >> microtonal accidentals may take me extra time. > > > Why don't we

Re: Supporting my work on LilyPond financially

David Kastrup schrieb: >SoundsFromSound writes: > >> The biggest complaint I've heard from many of my peers (when it comes >> to possibly switching from Finale/Sibelius) is that "LilyPond looks >> like way too much work" and "Text input?? That makes absolutely no >> sense for music. You're n

Re: Supporting my work on LilyPond financially

SoundsFromSound writes: > The biggest complaint I've heard from many of my peers (when it comes > to possibly switching from Finale/Sibelius) is that "LilyPond looks > like way too much work" and "Text input?? That makes absolutely no > sense for music. You're not writing a book! It's a score!".

Re: Supporting my work on LilyPond financially

Kieren MacMillan wrote >> How does that compare to their reaction to Lilypond? I would guess >> amazement at how much Lilypond gets right, but frustration with how >> relatively complicated it is to enter a score and see the results? And >> probably overwhelming frustration when they hit the poin

Re: Supporting my work on LilyPond financially

Martin Tarenskeen writes: > On Sun, 1 Dec 2013, Kieren MacMillan wrote: > >> I am looking forward to examining Denemo, once my current project >> load diminishes to the point where “free time” is a reality. > > Denemo is mentioned several times in this thread. > > I have installed and tried Denem

Re: Supporting my work on LilyPond financially

Kieren MacMillan writes: > Hi David, > >> I'm always a bit surprised about the low resonance on features like >> >> http://code.google.com/p/lilypond/issues/detail?id=3648> >> Issue 3648: Patch: Isolated durations in music sequences now stand for >> unpitched notes > > It’s a nice feature… but a

Re: Supporting my work on LilyPond financially

Henning Hraban Ramm writes: > Am 2013-12-01 um 19:15 schrieb David Kastrup : > >> I'm always a bit surprised about the low resonance on features like >> >> http://code.google.com/p/lilypond/issues/detail?id=3648> >> Issue 3648: Patch: Isolated durations in music sequences now stand for >> unpitc

Re: Supporting my work on LilyPond financially

Richard Shann writes: > On Sun, 2013-12-01 at 11:41 +0100, David Kastrup wrote: >> > In my opinion, there are only two things that will ever change this: >> > 1. A real, live, useable, full-functioned GUI (so that users *never* >> > have to see Lilypond “code”); >> >> According to the advertisin

Re: Supporting my work on LilyPond financially

On Sun, 2013-12-01 at 17:27 +0100, Martin Tarenskeen wrote: > > On Sun, 1 Dec 2013, Kieren MacMillan wrote: > > > I am looking forward to examining Denemo, once my current project load > > diminishes to the point where “free time” is a reality. > > Denemo is mentioned several times in this thre

Re: Supporting my work on LilyPond financially

On Sun, 1 Dec 2013, Kieren MacMillan wrote: I am looking forward to examining Denemo, once my current project load diminishes to the point where “free time” is a reality. Denemo is mentioned several times in this thread. I have installed and tried Denemo several times recently and in the p

Re: Supporting my work on LilyPond financially

Am 01.12.2013 12:04, schrieb Kieren MacMillan: Hi Urs, If anybody is interested in this and has experience with Python and/or MusicXML please contact us I have no Python experience, but lots of XML/XSL(T) experience — and, of course, a proven willingness to financially support Lilypond. Will

Re: RehearsalMark and MetronomeMark together…again…

Follow-up… Cancel the bounty call for now: I’ve hacked my way through the problem manually. I’ll post a feature request (and new bounty offer) some time next month. Thanks, Kieren. On 2013-Dec-1, at 09:46, Kieren MacMillan wrote: > Hello all, > > This is *killing* my productivity on my current

Re: Supporting my work on LilyPond financially

Hi Richard, > Ha! It's funny you should mention this, but I just added a command to > Denemo to create a staff complete with time signature changes and empty > measures for a score (for a completely different reason). Synchronicity! > Front-end stuff is so easy to do with a pre-processor like De

Re: formatting a text before the score

Thanks a lot for the tips which work perfectly. I would like to understand how the \hspace #0 can impact the height of a line or the way it is wrapped. Is that explained anywhere in the documentation? -- View this message in context: http://lilypond.1069038.n5.nabble.com/formatting-a-text-befor

Re: Supporting my work on LilyPond financially

On Sun, 2013-12-01 at 09:19 -0500, Kieren MacMillan wrote: > > On the other hand, something really useful — and helpful in getting > users “out of the code” — would be the ability to say: > > lastCymbalCrash = { > \atMoment (256 . 1) b4\accent\sff > } > > and then output a 256-measure part (co

Re: Supporting my work on LilyPond financially

Hi Richard, > They had posted the musicXML too, so I imported it into Denemo > and re-typeset it with LilyPond. The result was this: > > http://imslp.org/wiki/Oboe_Sonata_in_C_major_(Albinoni,_Tomaso) > > I didn't need to tweak it with LilyPond, and, for fun, I transposed it > up a minor third f

Re: RehearsalMark and MetronomeMark together…again…

Hello all,This is *killing* my productivity on my current [extremely-high-pressure, past-due] project…For one example (hardly the worst), here’s Lilypond’s default output from one section of my bass part:Can someone please whip me up a helper function which does the following:   1. automatically of

Re: Supporting my work on LilyPond financially

> How does that compare to their reaction to Lilypond? I would guess amazement > at how much Lilypond gets right, but frustration with how relatively > complicated it is to enter a score and see the results? And probably > overwhelming frustration when they hit the point of wanting to tweak >

Re: Supporting my work on LilyPond financially

Am 2013-12-01 um 19:15 schrieb David Kastrup : > I'm always a bit surprised about the low resonance on features like > > http://code.google.com/p/lilypond/issues/detail?id=3648> > Issue 3648: Patch: Isolated durations in music sequences now stand for > unpitched notes I hear you - as a magazine

Re: Supporting my work on LilyPond financially

Hi David, > I'm always a bit surprised about the low resonance on features like > > http://code.google.com/p/lilypond/issues/detail?id=3648> > Issue 3648: Patch: Isolated durations in music sequences now stand for > unpitched notes It’s a nice feature… but applicable, I would imagine, to a spect

Re: Supporting my work on LilyPond financially

On Sun, Dec 1, 2013 at 3:03 PM, Joseph Rushton Wakeling < joseph.wakel...@webdrake.net> wrote: > On 01/12/13 14:56, immanuel litzroth wrote: > >> Here's a nice example. >> > > That's almost certainly someone writing to full score (which has > particular spacing properties) and auto-exporting to pa

Re: Supporting my work on LilyPond financially

Am 2013-12-01 um 15:26 schrieb Urs Liska : > I think it hasn't been stressed enough yet that the text input by itself is a > huge hurdle. I mean, not the syntax but the plain fact. > If you're looking at a real-world score's input file it's overwhelmingly > daunting. And if you look at { c d e

Re: Supporting my work on LilyPond financially

On 01/12/13 14:56, immanuel litzroth wrote: Here's a nice example. That's almost certainly someone writing to full score (which has particular spacing properties) and auto-exporting to parts without ever actually looking at them. Surprise to surprise, the horizontal spacing issues are differ

Re: Supporting my work on LilyPond financially

On 01/12/13 14:13, immanuel litzroth wrote: I follow a music education program that requires me to play in a combo 1 hour a week. The scores there are prepared by paid professionals, usually in Sibelius. They are invariably late, and usually unreadable when they arrive. Chords on top of each othe

Re: Supporting my work on LilyPond financially

Kieren MacMillan writes: > Hi Joseph, > >> The default output of Finale is indeed ugly, and I was reminded that >> Sibelius too has its problems when I recently received a score from >> a friend which would surely have looked much better done in >> Lilypond. >> >> The thing is, though, both are

Re: Supporting my work on LilyPond financially

On Sun, Dec 1, 2013 at 12:32 PM, Joseph Rushton Wakeling < joseph.wakel...@webdrake.net> wrote: > On 01/12/13 09:45, David Kastrup wrote: > >> Finale output is ugly to the degree where it is distracting readability, >> particularly for instrumentalists. Sibelius' corporate parent has fired >> its

Re: how to move TextScript closer to the staff?

karol wrote >> what do you mean by that - example? > > Take a lok here: > http://lilypond.1069038.n5.nabble.com/fingering-overlap-bug-td154572.html > >> maybe you can adapt http://lsr.dsi.unimi.it/LSR/Item?id=637 to your needs >> (see the file below) > > The numerals are not centered, but that's

Re: Supporting my work on LilyPond financially

On Sun, 2013-12-01 at 11:41 +0100, David Kastrup wrote: > > In my opinion, there are only two things that will ever change this: > > 1. A real, live, useable, full-functioned GUI (so that users *never* > > have to see Lilypond “code”); > > According to the advertising, that's Denemo. I hope noth

Re: Supporting my work on LilyPond financially

On 01/12/13 14:00, Kieren MacMillan wrote: I disagree somewhat… and so do most of my Finale- and Sibelius-using friends and colleagues, who complain endlessly about how much time it takes to tweak scores and parts. How does that compare to their reaction to Lilypond? I would guess amazement

Re: Supporting my work on LilyPond financially

Hi Joseph, > The default output of Finale is indeed ugly, and I was reminded that Sibelius > too has its problems when I recently received a score from a friend which > would surely have looked much better done in Lilypond. > > The thing is, though, both are so easy to tweak, it doesn't matter.

Re: Supporting my work on LilyPond financially

On 01/12/13 12:49, David Kastrup wrote: I don't think this sort of preplanning works out well. Mostly it just leads to people going away until the stuff they are not interested in is done. We need to figure out better ways to work on parallel and partly conflicting goals. Yes, I guess that's

Re: how to move TextScript closer to the staff?

OK, got it! \version "2.17.96" #(define-markup-command (fingerMod layout props arg) (markup-list?) (interpret-markup layout props (markup (#:translate (cons 0.75 0) (#:right-align (#:override '(baseline-skip . 1.5) (#:finger

Re: Supporting my work on LilyPond financially

Joseph Rushton Wakeling writes: > On 30/11/13 21:40, David Kastrup wrote: >> The backend is much less coherent, so expertise is harder to acquire, >> people tend to work with partial knowledge, and progress is a lot >> more fragile. We need to get those four months down, and yes, a >> shouting m

Re: how to move TextScript closer to the staff?

> karol wrote > > Because LilyPond does not handle fingaring notation well, I wrote markup > > command: > > what do you mean by that - example? Take a lok here: http://lilypond.1069038.n5.nabble.com/fingering-overlap-bug-td154572.html > maybe you can adapt http://lsr.dsi.unimi.it/LSR/Item?id=63

Re: Supporting my work on LilyPond financially

On 01/12/13 09:45, David Kastrup wrote: Finale output is ugly to the degree where it is distracting readability, particularly for instrumentalists. Sibelius' corporate parent has fired its core developer team in the UK, including its original authors. Steinberg does not yet have a finished produ

Re: Supporting my work on LilyPond financially

On 30/11/13 21:40, David Kastrup wrote: The backend is much less coherent, so expertise is harder to acquire, people tend to work with partial knowledge, and progress is a lot more fragile. We need to get those four months down, and yes, a shouting match is not going to help. What will help is

Re: how to move TextScript closer to the staff?

karol wrote > Because LilyPond does not handle fingaring notation well, I wrote markup > command: what do you mean by that - example? > The drawback is that the numerals are not centered on notehead. > > Now, take a look at the example. My question is: how can I improve the > code to have this T

Re: Supporting my work on LilyPond financially

Jan Nieuwenhuizen writes: > Kieren MacMillan writes: > >> (so that users *never* have to see Lilypond “code”); or > > and this is what I don't understand. > > My idea is exactly the opposite: to show people the corresponding text > input also, "also" > so that they have a very easy way to learn

Re: Supporting my work on LilyPond financially

Hi David, > we'll probably need some open discussion of common problems and > imaginary input that would make it considerably easier for people to > overcome them. I’m right in the middle of an immense engraving project — I have lots of fodder and examples for such a discussion. > LilyPond's ri

Re: Supporting my work on LilyPond financially

Hi Urs, > If anybody is interested in this and has experience with Python and/or > MusicXML please contact us I have no Python experience, but lots of XML/XSL(T) experience — and, of course, a proven willingness to financially support Lilypond. Will those help? Kieren. _

Re: Supporting my work on LilyPond financially

Kieren MacMillan writes: >> I think it hasn't been stressed enough yet that the text input by >> itself is a huge hurdle. I mean, not the syntax but the plain fact. > > Amen. > >> If you're looking at a real-world score's input file it's >> overwhelmingly daunting. > > …even for me, and I’m one o

Re: Supporting my work on LilyPond financially

Kieren MacMillan schrieb: >Hi David, > >>> 1. A real, live, useable, full-functioned GUI >> According to the advertising, that's Denemo. > >Perhaps when I’ve got a little time to spare, I’ll give that a look — >if it’s really all that, it might become part of my standard >“proselytizing” packa

Re: Supporting my work on LilyPond financially

Hi Jan, > This is *exactly* why I've been playing/experimenting with GUI > backends/frontends since 2004. If you haven't done so, please have > a look at Schikkers List > >http://lilypond.org/schikkers > > and come help me out! If only to lure people over to LilyPond, > increase its potent

Re: Supporting my work on LilyPond financially

Hi David, >> 1. A real, live, useable, full-functioned GUI > According to the advertising, that's Denemo. Perhaps when I’ve got a little time to spare, I’ll give that a look — if it’s really all that, it might become part of my standard “proselytizing” package. > "LilyPond for output only" is n

Re: Supporting my work on LilyPond financially

Kieren MacMillan writes: >> The situation is not really all that unfavorable for LilyPond. > > Having been “in the trenches” perhaps more than most others on this > list, I can tell you the situation *is* really all that unfavorable > for Lilypond. > > In my opinion, there are only two things that

Re: Supporting my work on LilyPond financially

Kieren MacMillan writes: > Hi David, > >> The situation is not really all that unfavorable for LilyPond. > > Having been “in the trenches” perhaps more than most others on this > list, I can tell you the situation *is* really all that unfavorable > for Lilypond. > > In my opinion, there are only

Re: Supporting my work on LilyPond financially

Hi David, > The situation is not really all that unfavorable for LilyPond. Having been “in the trenches” perhaps more than most others on this list, I can tell you the situation *is* really all that unfavorable for Lilypond. In my opinion, there are only two things that will ever change this: 1

Re: Supporting my work on LilyPond financially

> I think it hasn't been stressed enough yet that the text input by itself is a > huge hurdle. I mean, not the syntax but the plain fact. Amen. > If you're looking at a real-world score's input file it's overwhelmingly > daunting. …even for me, and I’m one of Lily’s biggest users in terms of n

Re: how to move TextScript closer to the staff?

Federico, I'd like to avoid adding extra-offset. I'm looking for general solution.   Dnia 1-12-2013 o godz. 10:27 Federico Bruni napisał(a): 2013/12/1 Karol Majewski Because LilyPond does not handle fingaring notation well, I wrote markup command: \version "2.17.96" #(define-m

Re: how to move TextScript closer to the staff?

2013/12/1 Karol Majewski > Because LilyPond does not handle fingaring notation well, I wrote markup > command: > > \version "2.17.96" > > #(define-markup-command > (fingerMod layout props arg) > (markup-list?) > (interpret-markup layout props > (markup > (#:left-align > (#

Re: Supporting my work on LilyPond financially

Am 01.12.2013 09:45, schrieb David Kastrup: This means that the first hurdle is overcoming the inertia of "I > already have x, why should I switch? Which leads to (2) even if I can > demonstrate that LP overcomes the technical difficulties of another > notation program, people are going to be rel

Re: Supporting my work on LilyPond financially

Carl Peterson writes: > On Dec 1, 2013 1:47 AM, "David Kastrup" wrote: >> >> Noeck writes: > >> > I personally don't understand why LP is not common at music >> > universities but that's probably a chicken-or-the-egg thing and the >> > lack of large scale marketing. But this would also need off

how to move TextScript closer to the staff?

Because LilyPond does not handle fingaring notation well, I wrote markup command: \version "2.17.96" #(define-markup-command (fingerMod layout props arg) (markup-list?) (interpret-markup layout props (markup (#:left-align (#:override '(baseline-skip . 1.5)