On Mon, Sep 09, 2013 at 03:51:59AM +, Keith OHara wrote:
>
> It was intentional. There is a reported bug about rehearsal marks
>http://code.google.com/p/lilypond/issues/detail?id=1150
> with lots of evidence that rehearsal marks traditionally go right of the
> clef (and key signature if
Am 2013-09-08 um 21:18 schrieb David Rogers :
> Henning Hraban Ramm writes:
>
>> I’m the one behind the previous lilypond module for ConTeXt and the current
>> LilyPond filter suggestion.
>> For me, it works great (besides the usual layout problems with TeX).
>>
>> I guess the matter is, what
Jim Long umpquanet.com> writes:
> 2.16.2 centers each mark over its alignment symbol (the clef and
> the barline, respectively).
>
> But in 2.17.26, the first mark is left-aligned with the
> centerline of the clef, while the second mark is center-aligned
> over the barline.
>
> Is this intentio
Hello dp:
"Sonatina": Prelude, m.2 should have a third position marking instead of
the second position marking that is in the score at the moment.
I am having some fun playing through these. Has anyone performed them?
Rachael
On 09/08/2013 09:53 AM, Dave Phillips wrote:
Greetings,
Some ti
2013/9/9 Dominic :
> Hi everyone,
>
> Is there any way that I can make a "ralla tempo" that is firmly in
> the Score context, using MetronomeMarks and TextSpanners? I want the
> "ralla tempo" to appear on the top of the score, not on every single
> staff. But I also want to retain t
Hi everyone,
Is there any way that I can make a "ralla tempo" that is firmly in
the Score context, using MetronomeMarks and TextSpanners? I want the
"ralla tempo" to appear on the top of the score, not on every single
staff. But I also want to retain the ability to use TextSpanners
I did a build of 2.17.26 on FreeBSD today to try things out, and
quickly found one change I wanted to inquire about.
Given this code:
\score {
\new Staff \relative c' {
\override RehearsalMark #'break-align-symbols = #'(clef bar)
\mark \default
c1
\mark \default
c1
}
}
2.
Am 08.09.2013 17:18, schrieb David Rogers:
Henning Hraban Ramm writes:
Am 2013-09-06 um 23:12 schrieb David Rogers :
Hello
There have been several methods in the history of LilyPond for
integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
more-flexible system somewhat analo
hi David
is that a question or a statement?
I don't understand why this would fork into different messages
it's just my suggestion as a user - not knowing how it is handled in the
back.
Eluze
Am 09.09.2013 00:20, schrieb David Kastrup:
Eluze writes:
exactly - but if LilyPond knows in
on 2013-09-08 at 16:56 Dave Phillips wrote:
> Since you're a fellow Csounder, can you suggest ways to link that system
> with LP ? IIRC Csound has some support for MusicXML, but I've never
> tested it.
i did something very basic not long ago for a project, parsing the output
of the event-listene
Jan Nieuwenhiuzen:
> David Kastrup writes:
>
> > k...@aspodata.se (Karl Hammar) writes:
> >> Karl Hammar:
> >>> David Kastrup:
> >>> > k...@aspodata.se (Karl Hammar) writes:
> >> Soo, how far off from reality am I?
> >
> > You should probably check with the available documentation for our Midi
> >
Eluze writes:
> exactly - but if LilyPond knows in which mode she actually is why not
> tell it? - just a suggestion
Because we then we have to fork into five or more error messages for the
same problem?
--
David Kastrup
___
lilypond-user mailing l
exactly - but if LilyPond knows in which mode she actually is why not
tell it? - just a suggestion
Eluze
Am 08.09.2013 23:45, schrieb David Kastrup:
Eluze writes:
hi
imo it's not worth to say where we are not - there are many other
modes which could be mentioned!
wouldn't it be clearer t
Eluze writes:
> hi
>
> imo it's not worth to say where we are not - there are many other
> modes which could be mentioned!
>
> wouldn't it be clearer to say: "we are in \notemode" -maybe even
> mention the language - and just tell that this string is recognized
> here!?
Could be chordmode, or IN
hi
imo it's not worth to say where we are not - there are many other modes
which could be mentioned!
wouldn't it be clearer to say: "we are in \notemode" -maybe even mention
the language - and just tell that this string is recognized here!?
btw - I'm quite (am-)used now with/to this message
Hi David,
Am 08.09.2013 23:11, schrieb David Kastrup:
> http://code.google.com/p/lilypond/issues/detail?id=3300>
>
> GNU LilyPond 2.17.26
> Processing `xxx.ly'
> Parsing...
> xxx.ly:1:10: error: unrecognized string, not in text script or \lyricmode
> { b a c'
> h }
Much better!
> It's
Noeck writes:
> Hi,
>
> if I forget to set the language correctly as in this example:
>
> \version "2.16.0"
> %\language "deutsch"
> { b a c' h }
>
> the error message in 2.16.0 was:
>
> error: syntax error, unexpected STRING
> { b a c'
> h }
>
> That told me: The "h" is wrong and I reme
Hi,
if I forget to set the language correctly as in this example:
\version "2.16.0"
%\language "deutsch"
{ b a c' h }
the error message in 2.16.0 was:
error: syntax error, unexpected STRING
{ b a c'
h }
That told me: The "h" is wrong and I remembered to set the language.
In 2.17.19,
On 09/08/2013 12:00 PM, lilypond-user-requ...@gnu.org aka luis jure wrote:
i can't say i read your score with the attention it deserves, but the
first thing i noticed is that starting on m. 52 the rests in the middle
voice seem to be missing (it's the lower part in m. 73). it also called my
att
luis jure writes:
> thanks for sharing, dave.
>
> wow, i imagine umeko must have been very beautiful...
Not in tablature, I'm afraid (but that's not how Dave himself chose to
look at Umeko). I entered a "Type-Ugly" issue as
http://code.google.com/p/lilypond/issues/detail?id=3542>.
It's not qu
David Kastrup writes:
> k...@aspodata.se (Karl Hammar) writes:
>> Karl Hammar:
>>> David Kastrup:
>>> > k...@aspodata.se (Karl Hammar) writes:
>> Soo, how far off from reality am I?
>
> You should probably check with the available documentation for our Midi
> code. Last time I checked, the availa
k...@aspodata.se (Karl Hammar) writes:
> Karl Hammar:
>> David Kastrup:
>> > k...@aspodata.se (Karl Hammar) writes:
>> >
>> > > I can set midi instrument with e.g.
>> >
>> > [...]
>> >
>> > > but can I set where in the stereo left-right sound picture the sound
>> > > will be placed ?
>> >
>>
Karl Hammar:
> David Kastrup:
> > k...@aspodata.se (Karl Hammar) writes:
> >
> > > I can set midi instrument with e.g.
> >
> > [...]
> >
> > > but can I set where in the stereo left-right sound picture the sound
> > > will be placed ?
> >
> > No.
...
> http://home.roadrunner.com/~jgglatt/tech/
Mr. Bailey,
Again thank you for your detailed suggestions. I "opened" both of them and
the second appeared closer to what I want. In addition your
commentary/explanation got me to ask "What if?" So I tried a few other
things and came up with the attached snippet.
As a teacher I appreciate w
Mr. Bailey,
Thank you for your reply and the detailed corrections. I will study both of
them to increase my knowledge.
Mark
From: bina...@gmail.com [mailto:bina...@gmail.com] On Behalf Of Simon Bailey
Sent: Sunday, September 08, 2013 11:30 AM
To: Mark Stephen Mrotek
Cc: lilypond-user Ma
Dave:
Thank you so much for sharing these! They look great. Wonderful examples of
how beautiful engraved scores look using LilyPond.
Ben
Dave Phillips wrote
> Greetings,
>
> Some time ago I wrote to this list with some questions which were
> answered promptly by various members here. Thanks t
hi,
On Sun, Sep 8, 2013 at 8:11 PM, Mark Stephen Mrotek wrote:
> At the end of the second alternative ending in the attached snippet an
> unwanted bar appears and disrupts the meter.
>
> **
>
> I have experimented with placing
>
> \set Timing.measurePosition = #(ly:make-moment 3/8)
> after th
Hello:
At the end of the second alternative ending in the attached snippet an
unwanted bar appears and disrupts the meter.
I have experimented with placing
\set Timing.measurePosition = #(ly:make-moment 3/8)
after the second alternative. Using it restores the meter. It does not
remove the ext
thanks for sharing, dave.
wow, i imagine umeko must have been very beautiful... i had a japanese
girlfriend in the late 1980s, and i still remember her fondly.
i can't say i read your score with the attention it deserves, but the
first thing i noticed is that starting on m. 52 the rests in the
Hi,
do you know GitHub? I think it would be convenient to use it in this
situation - it would be easy to post comments about specific lines of
code, send you patches with suggestions how to improve things etc (i
consider doing this manually to be pretty inconvenient).
Even if you don't know gith
Henning Hraban Ramm writes:
> Am 2013-09-06 um 23:12 schrieb David Rogers :
>
>> Hello
>> There have been several methods in the history of LilyPond for
>> integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
>> more-flexible system somewhat analogous to LaTeX).
>>
>> Right now
Greetings,
Some time ago I wrote to this list with some questions which were
answered promptly by various members here. Thanks to their assistance I
got re-started with LilyPond, and I've been busy using it via the
Frescobaldi program.
I've revised some pieces and added some new things here
Hi all,
following a discussion about LSR and its limitations (e.g. problems
with snippets written for development versions of LilyPond), I've
created a new place to store useful pieces of LilyPond code:
http://github.com/openlilylib/snippets (scroll down to see description)
Note that this is *no
Correct. They're generated automatically.
--
Phil Holmes
- Original Message -
From: Pierre Perol-Schneider
To: Thomas Morley
Cc: lilypond-user
Sent: Sunday, September 08, 2013 12:14 PM
Subject: Re: LSR - How to change images
Thanks for the tip Harm.
Does this mean
Mr. Payne:
Read the documentation. It is an addition to 2.17 that is not in 2.16.2
which is the one that I regularly use.
Mark
From: Nick Payne [mailto:nick.pa...@internode.on.net]
Sent: Saturday, September 07, 2013 10:56 PM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re
Jim:
Thank you for your reply and the second way to accomplish the partial
measure.
Mark
-Original Message-
From: Jim Long [mailto:lilyp...@umpquanet.com]
Sent: Saturday, September 07, 2013 11:30 PM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re: Anacrusis
On Sat, Sep 07
Eluze wrote Sunday, September 08, 2013 10:04 AM
> I can't reproduce the error(s).
>
> I suppose your full code is something like
>
> *code above*
> }
> {\vibestopstaff}
>
> then it compiles perfectly in 2.16.0 and higher.
>
> only when removing or postponing the /\time 2/4/ then errors raise
Thanks for the tip Harm.
Does this mean that one cannot manually change images ?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Am 08.09.2013 11:20, schrieb Henning Hraban Ramm:
Am 2013-09-06 um 23:50 schrieb Marc Hohl :
Am 06.09.2013 19:12, schrieb David Rogers:
Hello
There have been several methods in the history of LilyPond for
integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
more-flexible sys
2013/9/8 Thomas Morley :
> 2013/9/8 Pierre Perol-Schneider :
>> Dear List,
>>
>> I'm trying to propose a new snippet to the LSR :
>> http://lsr.dsi.unimi.it/LSR/Item?id=886
>>
>> My problem comes from the image :
>> 1. it looks a little rough
>> 2. above edge is cutted
>> 3. but, more important, it
Am 2013-09-08 um 16:28 schrieb David Kastrup :
Right now, which is the best choice for putting ConTeXt and LilyPond
together? (Your answer might be "Don't bother, just use LaTeX", if you
have a good reason for saying that.)
>>>
>>> Hehe – just use LaTeX ;-)
>>
>> I would not. Let
2013/9/8 Pierre Perol-Schneider :
> Dear List,
>
> I'm trying to propose a new snippet to the LSR :
> http://lsr.dsi.unimi.it/LSR/Item?id=886
>
> My problem comes from the image :
> 1. it looks a little rough
> 2. above edge is cutted
> 3. but, more important, it does not show what v2.17 or v.2.17
Henning Hraban Ramm writes:
> Am 2013-09-06 um 23:50 schrieb Marc Hohl :
>
>> Am 06.09.2013 19:12, schrieb David Rogers:
>>> Hello
>>>
>>> There have been several methods in the history of LilyPond for
>>> integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
>>> more-flexible s
Dear List,
I'm trying to propose a new snippet to the LSR :
http://lsr.dsi.unimi.it/LSR/Item?id=886
My problem comes from the image :
1. it looks a little rough
2. above edge is cutted
3. but, more important, it does not show what v2.17 or v.2.17 actually make.
My question :
Is there a way to mo
Am 2013-09-06 um 23:50 schrieb Marc Hohl :
> Am 06.09.2013 19:12, schrieb David Rogers:
>> Hello
>>
>> There have been several methods in the history of LilyPond for
>> integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
>> more-flexible system somewhat analogous to LaTeX).
>>
Am 2013-09-06 um 23:12 schrieb David Rogers :
> Hello
> There have been several methods in the history of LilyPond for
> integrating LilyPond scores with ConTeXt documents (ConTeXt is a newer
> more-flexible system somewhat analogous to LaTeX).
>
> Right now, which is the best choice for putting
EdBeesley wrote
> Rachael the version is 2.16.2.
>
> I've now got the code to work, but the fix for this seems rather strange.
> If I put the code before any declared notes in a part it doesn't work,
> e.g:
>
> vibestopstaff = \relative c'' { \time 2/4
> \set Timing.baseMoment = #(ly:make
On 8 sept. 2013, at 10:48, "Phil Holmes" wrote:
> Concerning etiquette - please don't send such large attachments to the
> mailing list. It's trivial to reduce its size below 100k which is far more
> manageable - there are people who help here who are on dial up.
>
> I now understand what yo
EdBeesley writes:
> Rachael the version is 2.16.2.
>
> I've now got the code to work, but the fix for this seems rather strange. If
> I put the code before any declared notes in a part it doesn't work, e.g:
>
> vibestopstaff = \relative c'' { \time 2/4
> \set Timing.baseMoment = #(ly:make
Rachael the version is 2.16.2.
I've now got the code to work, but the fix for this seems rather strange. If
I put the code before any declared notes in a part it doesn't work, e.g:
vibestopstaff = \relative c'' { \time 2/4
\set Timing.baseMoment = #(ly:make-moment 2 4)
\set Timing
Might be an intersting idea, not for the general concept but for Frescobaldi
development.
Should be trivial to append sth like '-draft' when compiling in preview mode.
(Has to be selectable in the preferences of course)
Urs
Helge Kruse schrieb:
>Am 07.09.2013 14:31, schrieb Janek Warchoł:
>
On 2013-09-02 13:50, Urs Liska wrote:
> I'm compiling a selection of examples to show LilyPond's output quality.
> I'm aiming at a collection of ca. 5 examples (1-page excerpts) of
> LilyPond scores tweaked to publication quality and a similar number of
> examples of out-of-the-box engraving.
> The
Am 07.09.2013 14:31, schrieb Janek Warchoł:
Well, there's a concept of "preview mode" and "publish mode" in
Frescobaldi (the second one produces pdfs without point-and-click).
The idea is that when you finish your work, you use "publish mode" to
create final pdf.
When you've done this, have two
53 matches
Mail list logo
