Because you have changed the number of lines in the staff the text won't
line up.
If you added something like
\once \override TextScript #'Y-offset = #-4.15
before the markup for 'five' this would align it to the baseline of the
surrounding text markup. Or you could put this sort of thing
Another follow-up multi-comment message:
Am Montag, den 22.04.2013, 10:49 +0200 schrieb Urs Liska:
> > [...] MusicXML [...]
> >
> > indeed.
> > ;)
> I'd actually say it is crucial to have that in order to get LilyPond a
> foot in the publishing world. We can't expect publishing houses to
> easily
Hi all,
trying to catch up on all the stuff written lately.
Obviously I somewhat lack the overview, so I try to do my best to do
everybody justice (knowing it won't work out ...)
###
Structure/Outline of the paper
Am Montag, den 22.04.2013, 10:09 -0400 schrieb Carl Peterson:
> B
Thanks much to all of you for your detailed replies.
Cheers,
Pierre
2013/4/24 m...@mikesolomon.org
>
> On 24 avr. 2013, at 15:58, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
> Thanks Mike, looks interesting.
> Do you think that this notation is often used by modern com
Hi everyone,
I've come to a problem I don't know how to fix involving the way that markups
are aligned to one another. I think there might be some scheme hacking involved
in getting the result I need, although potentially there might be an override
which I've overlooked that would do the same t
On Wed, 24 Apr 2013, Federico Bruni wrote:
> The next Debian stable, which is going to be released in a few days,
> will have 2.14 again. Hopefully 2.16 will be added to backports in
> the next future. But it's in experimental since september:
> http://packages.qa.debian.org/l/lilypond.html
>
> I
I've just happened to update an old score from 2.13.x to latest version
2.17.7
The following custom tuning:
\set TabStaff.stringTunings = #'(2 -3 -5 -8 -13 -20)
has been converted to:
\set TabStaff.stringTunings = #`(,(ly:make-pitch 0 1 NATURAL)
,(ly:make-pitch -1 5 NATURAL) ,(ly:make-pitch -1
On 24/04/2013 21:03, Federico Bruni wrote:
You can find an explanation here:
http://lilypond.org/doc/v2.16/Documentation/usage/common-errors#an-extra-staff-appears
Thanks Federico, I wasn't aware of this one. I appreciate the pointer.
the right input is:
\version "2.17.11"
\paper { ragged
2013/4/24 Roman Stawski
> Hi folks
>
> I've just comme across this in 2.17.11
>
> ---
> \version "2.17.11"
>
> \paper { ragged-right = ##t }
>
>
> {
>
>\new PianoStaff <<
>
> \new Staff \relative c'' { a1 }
>
> \new Staff \relative c' { f1 }
>
>>>
>
>\break
>
>\new Piano
Hi folks
I've just comme across this in 2.17.11
---
\version "2.17.11"
\paper { ragged-right = ##t }
{
\new PianoStaff <<
\new Staff \relative c'' { a1 }
\new Staff \relative c' { f1 }
>>
\break
\new PianoStaff <<
\new Staff \relative c'' { b1 }
\new St
On 24 avr. 2013, at 15:58, Pierre Perol-Schneider
wrote:
> Thanks Mike, looks interesting.
> Do you think that this notation is often used by modern composers ?
> Have you seen it elsewhere ?
>
>
> 2013/4/24 m...@mikesolomon.org
> On 24 avr. 2013, at 16:31, Pierre Perol-Schneider
> wrote:
And, you can't easily markup the score with a pencil... I don't think
Avid Scorch supports annotations as yet, either.
This is relevant to lilypond discussions, as having lilypond target fine
printed output is going to be valid for a very long time to come, I reckon.
Andrew
On 24/04/13 3:11
Again, maybe I am out of date but I need to see a full page of music,
and even a full two page spread to see what's coming up and what's gone
past when playing, not two or three systems, so that I have a wide
musical context. And US Letter is still narrow.
But then again, to show I am not just
In landscape orientation, the width of the iPad screen is about 7.75 inches
(don't have one personally, but using the Pythagorean theorem on a 9.7"
diagonal), which is about a quarter-inch wider than a line of a US-Letter
size printing with 1/2 inch margins (7.5" line length, about 190 mm). So
you
Andrew Bernard writes:
> Call me old-fashioned or antique, but despite their ubiquity, iPads
> and Kindles are just too small to read music from at any proper
> distance. There is a reason music scores are on large paper -
> readability. When iPads get to 235 x 310 mm screens (Klavierformat
> pia
Call me old-fashioned or antique, but despite their ubiquity, iPads and
Kindles are just too small to read music from at any proper distance.
There is a reason music scores are on large paper - readability. When
iPads get to 235 x 310 mm screens (Klavierformat piano score paper size)
then maybe
- Original Message -
From: Peter Toye
To: Wim van Dommelen
Cc: lilypond-user@gnu.org
Sent: Tuesday, April 23, 2013 9:35 PM
Subject: Re: Alignment problem with instrument name
Thanks. As a newbie I'm a bit surprised that Lilypond doesn't do that
automatically. But at least I've got a wor
2013/4/24 Francisco Vila :
>>It seems a shame, because the Tex source probably contains all
>> the information one would need to produce a nice e-book)
> Maybe this http://www.latex2html.org/ can help, if you can customise
> it for your needs.
Also google for "latex to epub" and many options aris
2013/4/24 Vaughan McAlley :
> (As an aside, I’ve lately been learning Tex by publishing my mother’s
> autobiography. The book should look great. If I want to create a
> version for e-readers, it looks like I have to get to ePub via HTML
> format. It seems a shame, because the Tex source probably co
On 04/24/2013 04:36 PM, Owain Sutton wrote:
> Another common option is simply indicating 'vib.', 'senza vib.', 'molto vib.'
Depends how precise a visual indicator you want to have of the type of vibrato,
particularly with respect to precise indication of the 'vertical' extent (i.e.
the range of pi
2013/4/24 Klaus Föhl :
> Carlo Stemberger schrieb:
>> Il 23/04/2013 17:49, Klaus Föhl ha scritto:
>>
>>Hello,
>>
>>Just snooping around and discovering that this markup:
>>\relative c' { f d f a d f e d cis a cis e a g f e }
>>now [works on|has been enabled for] mediawiki i.e. en.wi
David,
Thanks. I'd not discovered that yet. But I've only been using Lilypond for
about a week.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Wednesday, April 24, 2013, 3:26:21 PM, you wrote:
Hi Peter,
On Wed, Apr 24, 2013 at 9:23 AM, Peter Toye w
Another common option is simply indicating 'vib.', 'senza vib.', 'molto vib.'
etc.
On 09:07, Wed 24 Apr 2013, David Nalesnik wrote:
> Date: Wed, 24 Apr 2013 09:07:51 -0500
> From: David Nalesnik
> Subject: Re: Off-topics : vibrato
> To: Pierre Perol-Schneider
> Cc: lilypond-user
> List-Id: Lil
Hi Peter,
On Wed, Apr 24, 2013 at 9:23 AM, Peter Toye wrote:
> I find that the "Hauptstimme" and "Nebenstimme" signs as used by
> Schönberg can be useful. They can save time in rehearsal letting players
> know who should be on top.
>
> Any chance of getting them put into Lilypond?
>
The LSR (
I find that the "Hauptstimme" and "Nebenstimme" signs as used by Schönberg can
be useful. They can save time in rehearsal letting players know who should be
on top.
Any chance of getting them put into Lilypond?
Regards,
Peter Toye
mailto:lilyp...@ptoye.com
www.ptoye.com__
Hi Pierre,
On Wed, Apr 24, 2013 at 8:58 AM, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> Thanks Mike, looks interesting.
> Do you think that this notation is often used by modern composers ?
> Have you seen it elsewhere ?
>
Graphic notations of vibrato are fairly common.
Thanks Mike, looks interesting.
Do you think that this notation is often used by modern composers ?
Have you seen it elsewhere ?
2013/4/24 m...@mikesolomon.org
> On 24 avr. 2013, at 16:31, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
> Hi List,
> Does anyone know a mode
On 24 avr. 2013, at 16:31, Pierre Perol-Schneider
wrote:
> Hi List,
> Does anyone know a modern notation to indicate a vibrato ?
> Thanks,
> Pierre
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lily
Hi List,
Does anyone know a modern notation to indicate a vibrato ?
Thanks,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Carlo Stemberger schrieb:
> Il 23/04/2013 17:49, Klaus Föhl ha scritto:
>
>Hello,
>
>Just snooping around and discovering that this markup:
>\relative c' { f d f a d f e d cis a cis e a g f e }
>now [works on|has been enabled for] mediawiki i.e. en.wikipedia.org
>
> Commands like \t
Hi Peter,
> As a newbie I'm a bit surprised that Lilypond doesn't do that automatically.
1. It places the left edge of the music automatically. When you think about it,
this makes far more sense than having the left edge placed according to the
width of the instrument names (and thus potentiall
Urs Liska writes:
> Am Mittwoch, den 24.04.2013, 11:05 +0200 schrieb David Kastrup:
>> Urs Liska writes:
>>
>> > Hi all,
>> >
>> > just a quick (and urgent) question:
>> >
>> > \shape Slur #'((0 . 0)(0 . 0)(0 . 0)(0 . 0))
>> >
>> > should be correct syntax? Or am I blind?
>> > At least LilyPond
Am Mittwoch, den 24.04.2013, 11:05 +0200 schrieb David Kastrup:
> Urs Liska writes:
>
> > Hi all,
> >
> > just a quick (and urgent) question:
> >
> > \shape Slur #'((0 . 0)(0 . 0)(0 . 0)(0 . 0))
> >
> > should be correct syntax? Or am I blind?
> > At least LilyPond 2.17.16 hits me
> >
> > "
> > e
Am Mittwoch, den 24.04.2013, 11:05 +0200 schrieb Jan-Peter Voigt:
> Hi Urs,
>
> the order of the arguments changed in 2.17:
> \shape #'((0 . 0)(0 . 0)(0 . 0)(0 . 0)) Slur
> should work. The second argument now also may be music, so that you can
> use in a tweak fashion:
> c-\shape #'((0 . 0)(0 .
Urs Liska writes:
> Hi all,
>
> just a quick (and urgent) question:
>
> \shape Slur #'((0 . 0)(0 . 0)(0 . 0)(0 . 0))
>
> should be correct syntax? Or am I blind?
> At least LilyPond 2.17.16 hits me
>
> "
> error: wrong type for argument 2. Expecting symbol list or music, found
> ((0 . 0) (0 . 0)
Hi Urs,
the order of the arguments changed in 2.17:
\shape #'((0 . 0)(0 . 0)(0 . 0)(0 . 0)) Slur
should work. The second argument now also may be music, so that you can
use in a tweak fashion:
c-\shape #'((0 . 0)(0 . 0)(0 . 0)(0 . 0)) ( d)
HTH
best,
Jan-Peter
Am 24.04.2013 10:57, schrieb Urs
Hi all,
just a quick (and urgent) question:
\shape Slur #'((0 . 0)(0 . 0)(0 . 0)(0 . 0))
should be correct syntax? Or am I blind?
At least LilyPond 2.17.16 hits me
"
error: wrong type for argument 2. Expecting symbol list or music, found
((0 . 0) (0 . 0) (0 . 0) (0 . 0))
\shape Slur
Vaughan McAlley writes:
> (As an aside, I’ve lately been learning Tex by publishing my mother’s
> autobiography. The book should look great. If I want to create a
> version for e-readers, it looks like I have to get to ePub via HTML
> format. It seems a shame, because the Tex source probably contai
Helge,
Sorry - yes. My email client appended the whole message.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Wednesday, April 24, 2013, 6:37:16 AM, you wrote:
I reply inline...
2013/4/23 Peter Toye
Thanks Urs and all others who pointed out what I'd m
2013/4/24 David Kastrup
> > The next Debian stable, which is going to be released in a few days,
> > will have 2.14 again.
>
> "Again"?
>
> Current Debian stable has 2.12.3. So we are making progress.
yes, you are right
however, having 2.16 would be a better progress
lilypond is not in the bac
Federico Bruni writes:
> Speaking about LilyPond on Linux... yesterday I've seen that version
> 2.16 is still in debian experimental:
> http://packages.debian.org/search?keywords=lilypond
>
> The next Debian stable, which is going to be released in a few days,
> will have 2.14 again.
"Again"?
David Kastrup writes:
>> Ask Wilbert about the LyBoek project...
>
> Is that a "work title"?
Yes.
> The official title is Liedboek, as in http://www.liedboek.nl/>
Indeed.
> An exposition of the project logistics would be interesting, yes.
Yes, there are plans for a writeup of the project.
Ja
42 matches
Mail list logo
