On Wed, 9 Oct 2013, Tim McNamara wrote:
Thanks for having a bash at that. As a matter of taste, I think I
prefer not having the font's sharps and flats used in the chord names
because they look disproportionately large compared to the text, whereas
the default accidentals look fine to my
On Thu, 10 Oct 2013, Martin Tarenskeen wrote:
Maybe it could even be possible to design a music font that improves the
reading skills for people who have always had trouble to read music.
Something comparable to that special text font that was designed for people
with dyslexia:
Jacques Menu jacques.m...@epfl.ch writes:
After struggling with irregular bars, I've been working on a Python3 tool that
transforms a spec such as:
[...]
into a ready-to-compile Lilypond source file.
Very interesting. It reminds me of something I considered a while ago:
a kind of meta-staff
Am 09.10.2013 23:36, schrieb Pierre Perol-Schneider:
2013/10/9 Раул Апонт raulapo...@bk.ru mailto:raulapo...@bk.ru
Hello.
Hi Раул
If you could send me an example, it would be great.
Here it is :
[...]
stringTunings = #bass-tuning
stringTunings = #bass-five-string-tuning
if
Am 10.10.2013 01:56, schrieb Thomas Morley:
2013/10/9 Urs Liska u...@openlilylib.org:
[...]
One more thing which might be useful for the technical issues you are
talking about:
I started a snippet to switch program execution based on the used LilyPond
version
Am 10.10.2013 08:10, schrieb Martin Tarenskeen:
On Wed, 9 Oct 2013, Tim McNamara wrote:
Thanks for having a bash at that. As a matter of taste, I think I
prefer not having the font's sharps and flats used in the chord names
because they look disproportionately large compared to the text,
On Thu, Oct 10, 2013 at 01:40:06AM +0200, Thomas Morley wrote:
Hi,
this is another font and simply installing the font doesn't changes
accidentals in chords with alterations.
True, I intentionally showed LilyPond's standard chordname
formatting.
I customize the look of my chord symbols
hi,
this sounds similar to reinhold kainhofer's orchestralily package:
http://kainhofer.com/orchestrallily/
i'm not sure if reinhold is still actively maintaining it, but it might
also be worth a look.
regards,
sb
On Thu, Oct 10, 2013 at 8:22 AM, Johan Vromans jvrom...@squirrel.nl wrote:
Hello Johan,
Leave me a week or two to have a version I can make available.
Will keep you informed!
JM
Le 10 oct. 2013 à 08:22:32, Johan Vromans jvrom...@squirrel.nl a écrit :
Jacques Menu jacques.m...@epfl.ch writes:
After struggling with irregular bars, I've been working on a Python3
2013/10/10 Paul Morris p...@paulwmorris.com:
This is a familiar problem that tripped me up at first as well. It's an
easy fix. Instead of pointing it to the LilyPond app:
/Applications/LilyPond.app
You need to point it here:
/Applications/LilyPond.app/Contents/Resources/bin/lilypond
This
Thanks Harm for the report and Marc for the suggestion.
Actually when reading your first email I had already noticed and fixed
the issue.
I'm somewhat frustrated how this could have happened. Originally I typed
that function correctly and I would have sworn someone has modified it
afterwards.
Am 10.10.2013 11:34, schrieb Urs Liska:
...
OK, it's fixed now and extended by the other predicates:
https://github.com/openlilylib/snippets/blob/master/general-tools/lilypond-version-predicates.ily
Sorry, wrong link.
___
lilypond-user mailing
Thanks Michael - I should investigate the blog more.
Regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Simon Bailey si...@bailey.at writes:
this sounds similar to reinhold kainhofer's orchestralily package:
http://kainhofer.com/orchestrallily/
A quick glance on this impressive(!) project learns that it is about
maintaining scores and (horizontal) parts ( = voices ).
What I have in mind is
Hello all,
I found what can possible be an ugly issue regarding the bar lines when
changing the staff line-count. I might be wrong on this one, but shouldn't
the first bar line in the example below cover the whole 5 lines?
\version 2.17.28
\relative c'' {
f4 d g, e |
\stopStaff
Hi again everyone, I'm making a title page and I'd like one line of text to
overlap another line (see attached png). However nothing I've tried (\raise
or \translate) will force the text above the previous line. This is the code
I'm using at the moment:
\bookpart {
\markup
{
Hi Ed,
FYI: the font in your PNG is nothing like that which I am seeing here on my
end with your code. When I input your code, I see no place for the line of
text to overlap /to /- the Y is inline with other letters of the word and
so I'm confused how you want to tuck the other line of text up
I see you included
\fontsize #16 \override #'*(font-name . Aniron)* Ýkjur
in your code, but I haven't downloaded that font on my machine. It's
probably on dafont.com somewhere...I'll see if I can track it down so I can
visualize what you're after a bit more clearly.
I'll try to come up with
Hi Ben yes sorry I should have attached that font to my message, if you've
not found it yet then I've attached it to this one...
anirb___.ttf
http://lilypond.1069038.n5.nabble.com/file/n152077/anirb___.ttf
anirm___.ttf
http://lilypond.1069038.n5.nabble.com/file/n152077/anirm___.ttf
Ed:
Did you want something like this?
http://lilypond.1069038.n5.nabble.com/file/n152078/LikeThis.jpg
EdBeesley wrote
Hi Ben yes sorry I should have attached that font to my message, if you've
not found it yet then I've attached it to this one...
anirb___.ttf
I've got a longer answer for later when I have lilypond at hand,
but have you tried \override #'(baseline-skip . 0) ?
Jim
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hello:
When the instructions for Ossia
(http://www.lilypond.org/doc/v2.16/Documentation/notation/modifying-single-s
taves#ossia-staves) are followed, a key signature is not included. This may
be because all of the examples are in c major.
Perhaps the documentation could include a notation
That may help do the trick Jim!
Also Ed, I wasn't able to view that PNG you tried sending earlier (it was
over 1400px wide and I couldn't see what you were wanting).
Does my image look close to what you want?
Ben
Jim Long wrote
I've got a longer answer for later when I have lilypond at
Apologies...forgot to attach png
http://lilypond.1069038.n5.nabble.com/file/n152074/text.png
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Overlap-markup-tp152073p152074.html
Sent from the User mailing list archive at Nabble.com.
On Thu, Oct 10, 2013 at 12:04:06PM -0700, EdBeesley wrote:
Hi again everyone, I'm making a title page and I'd like one line of text to
overlap another line (see attached png). However nothing I've tried (\raise
or \translate) will force the text above the previous line. This is the code
I'm
Jim, I'm afraid your example doesn't overlap on my 2.16, is this a change in
2.17?
Ben...that is /exactly/ what I was looking for! How did you do it?!
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Overlap-markup-tp152073p152083.html
Sent from the User mailing list
EdBeesley edplaysdr...@gmail.com writes:
Hi again everyone, I'm making a title page and I'd like one line of text to
overlap another line (see attached png). However nothing I've tried (\raise
or \translate) will force the text above the previous line. This is the code
I'm using at the
EdBeesley edplaysdr...@gmail.com writes:
Jim, I'm afraid your example doesn't overlap on my 2.16, is this a change in
2.17?
Ben...that is /exactly/ what I was looking for! How did you do it?!
Probably use 2.17.19 or later.
URL:http://code.google.com/p/lilypond/issues/detail?id=3330
--
Version?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@
https://lists.gnu.org/mailman/listinfo/lilypond-user
Sorry David, one of these days I'll remember to include that in my first
post!
2.16.2
--
View this message in context:
EdBeesley edplaysdr...@gmail.com writes:
Sorry David, one of these days I'll remember to include that in my first
post!
2.16.2
Backspacing was not really convincingly supported before 2.17.19. It's
likely possible to get the desired result in 2.16 using \combine and
\translate or other
David Kastrup wrote
Backspacing was not really convincingly supported before 2.17.19. It's
likely possible to get the desired result in 2.16 using \combine and
\translate or other constructs, but it's not necessarily pretty.
--
David Kastrup
Would you recommend exporting it as a graphic
On Thu, 10 Oct 2013, EdBeesley wrote:
Or alternatively I could just start using 2.17, I'm assuming code written in
2.16 won't compile in 2.17 without a bunch of changes?
convert-ly
--
MT
___
lilypond-user mailing list
lilypond-user@gnu.org
Martin Tarenskeen m.tarensk...@zonnet.nl writes:
On Thu, 10 Oct 2013, EdBeesley wrote:
Or alternatively I could just start using 2.17, I'm assuming code written in
2.16 won't compile in 2.17 without a bunch of changes?
convert-ly
Most changes are backward-compatible. As long as you are
Actually I managed to get it working with \combine and \lower. It's a bit
'hacky' though as you can see from the random spaces I had to put in:
\bookpart {
\markup
{
\fill-line
{
\column
{
\raise #-8
Gilberto Agostinho-3 wrote
I found what can possible be an ugly issue regarding the bar lines when
changing the staff line-count. I might be wrong on this one, but shouldn't
the first bar line in the example below cover the whole 5 lines?
Any thoughts on this?
that's probably arbitrary -
EdBeesley wrote
Would you recommend exporting it as a graphic from Photoshop and putting
it in that way?
Ed:
You don't need Photoshop, I'd say if you want to export something out of
LilyPond make it an SVG file. That way you can just use a free program like
Inkscape and take 3 seconds to drag
Mark Stephen Mrotek wrote
When the instructions for Ossia
(http://www.lilypond.org/doc/v2.16/Documentation/notation/modifying-single-s
taves#ossia-staves) are followed, a key signature is not included. This
may
be because all of the examples are in c major.
or because it's a new staff and
EdBeesley edplaysdrums at gmail.com writes:
Actually I managed to get it working with \combine and \lower. It's a bit
'hacky' though as you can see from the random spaces I had to put in:
Out of curiosity I'd love to hear if there are 'cleaner' ways of doing
it
Using \combine seems the
Eluze,
Thank you for your interest in this matter.
An ossia is an alternative passage which may be played instead of the
original passage. As such it should (must?) have the same key signature.
Attached are two files. One does not have the key signature in the ossia
(without.ly) and the other has
On Thu, Oct 10, 2013 at 7:28 PM, Mark Stephen Mrotek
carsonm...@ca.rr.comwrote:
Eluze,
An ossia is an alternative passage which may be played instead of the
original passage. As such it should (must?) have the same key signature.
Certainly not must. There are pieces (e.g., in the Bartok
Mr. Palmer,
Thank you for your response.
Yes, compositions with various instruments involved in polytonality would have
different key signatures. These cases would not be considered an example of an
“ossia.” As I stated below an ossia is an alternative to an original passage.
Both the
Hello!
I am new to lilypond, and I'm trying to layout a psalm chanted in
plainsong, so that the output should look something like this:
https://dl.dropboxusercontent.com/u/84432/psalm_example.png
So far I have this:
https://gist.github.com/gmoothart/6929479
which renders like so:
Hi Gabe,
Welcome to LilyPond!
If you'd like to put a note in parenthesis, simply add this command:
\parenthesize
...to whichever pitches you which to enclose.
http://www.lilypond.org/doc/v2.16/Documentation/notation/inside-the-staff#parentheses
If you want to put simple text/characters below
In NR 1.7.1, Selecting notation font size, I have:
Font size changes are achieved by scaling the design size that is closest
to the desired size.
What is design here?
All the pararagraph is well explained, except for this sentence.
Can you help me?
Thanks
Federico
44 matches
Mail list logo
