Thomas Morley wrote
2013/1/30 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
http://lsr.dsi.unimi.it/LSR/Item?u=1id=865
would you mind putting the affected objects in color?!
Done.
thanks (although I'd choose another color)...
another point - will there be any output in the LSR later,
Eluze elu...@gmail.com writes:
Thomas Morley wrote
2013/1/30 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
http://lsr.dsi.unimi.it/LSR/Item?u=1id=865
would you mind putting the affected objects in color?!
Done.
thanks (although I'd choose another color)...
There is always one more
On Thu, Jan 31, 2013 at 6:24 AM, Jan Nieuwenhuizen jann...@gnu.org wrote:
Adam Spiers writes:
Would be nice to say hello to any other Lilypond hackers / users who
are there!
+1
Great, it will be a honour to meet you :)
___
lilypond-user mailing
I just realized one problem with having cross-stave lines everywhere is that it makes crescendos and decrescendos and dynamic markings problematic. What a tough nut this is. Going off of several of your suggestions and trying to understand David Kastrup's point about "cross-voice" (David, I'm not
2013/1/31 Eluze elu...@gmail.com:
Thomas Morley wrote
2013/1/30 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
http://lsr.dsi.unimi.it/LSR/Item?u=1id=865
would you mind putting the affected objects in color?!
Done.
thanks (although I'd choose another color)...
Suggestion?
another
Dear All,
I have a piano staff that is using \autochange. The notes are just running
16ths throughout. In a beamed group, sometimes the notes are all in the upper
staff, sometimes they are all in the lower staff, and sometimes they are in
both. What I really want to do is force the beam to be
Dear All,
It seems that with proportional notation even strict spanning does not allow
collisions of notehead and accidentals. Is it possible to allow any collision
such that the resolution and accuracy are exact no matter what? Or maybe I am
missing something
Many thanks in advance,
Dear LilyPond users,
I believe I have encountered a complex bug involving the interaction
between horizontal brackets and outside-staff-priority. It is both obscure
and easy to work around, so it's not urgent, but I thought I would send it
here anyway. It requires two files to reproduce. Rather
On Thu, Jan 31, 2013 at 1:08 AM, Adam Spiers
lilypond-u...@adamspiers.org wrote:
I'm heading to FOSDEM in Brussels this weekend:
I'm going to go (on Saturday) as well. I'll be spending most of my
time near the OpenPhoenux stand (in AW, IIRC) talking to fellow
GTA04-owners.
Anyone interested in
Curt accou...@museworld.com writes:
I just realized one problem with having cross-stave lines everywhere
is that it makes crescendos and decrescendos and dynamic markings
problematic. What a tough nut this is.
Going off of several of your suggestions and trying to understand
David
Am 31.01.2013 12:14, schrieb Phil Holmes:
If you've moved the right hand to the lower stave, the upper stave
should have spacer rests, rather than visible rests. Visible rests
imply that something (the right hand...) is resting.
The melody line _is_ resting, so I wouldn't touch this aspect.
Thomas Morley wrote
2013/1/31 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
2013/1/30 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
http://lsr.dsi.unimi.it/LSR/Item?u=1id=865
would you mind putting the affected objects in color?!
Done.
thanks (although I'd choose another color)...
Kevin Patrick Barry wrote
Dear LilyPond users,
I believe I have encountered a complex bug involving the interaction
between horizontal brackets and outside-staff-priority. It is both obscure
and easy to work around, so it's not urgent, but I thought I would send it
here anyway. It requires
On 01/30/2013 09:42 AM, Wim van Dommelen wrote:
That is why the low-bass-clarinet stencil exists. That is (as I reverse
engineer it) intended for bass-clarinet toward low-C (the concert model) whereas
the bass-clarinet is the low-Ees (streetmodel).
Well, my point is that low-bass-clarinet
Greetings -
I'm running 2.16.2, under Ubuntu 12.4.
When I upgraded to 2.16.1, my emacs support for lilypond-mode disappeared,
and I can't figure out how to get it back. Does anyone have a suggestion? I
can't even figure out how to enter lilypond-mode once I've got emacs open.
I believe I still
Ralph Palmer palmer.r.vio...@gmail.com writes:
Greetings -
I'm running 2.16.2, under Ubuntu 12.4.
When I upgraded to 2.16.1, my emacs support for lilypond-mode
disappeared, and I can't figure out how to get it back. Does anyone
have a suggestion? I can't even figure out how to enter
El 30/01/2013 17:23, Guy Stalnaker jimmyg...@gmail.com escribió:
Thanks everyone who replied. I understand the relationship between
/transpose and /transposition now. FYI the proper commands that produce the
expected outcome is:
/transpose f c' {
/transposition c {
}
}
Yes but
Francisco,
\transpose was working as expected -- the horn parts were rendered the expected
5th higher. The issue was the midi output. It, too, was 'rendered' a fifth
higher. I could not figure out how to use \transpose and also get the correct
midi output. David Kastrup explained how
2013/1/31 Eluze elu...@gmail.com:
Thomas Morley wrote
2013/1/31 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
2013/1/30 Eluze lt;
eluzew@
gt;:
Thomas Morley wrote
http://lsr.dsi.unimi.it/LSR/Item?u=1id=865
would you mind putting the affected objects in color?!
Done.
thanks
On 30 January 2013 19:47, David Kastrup d...@gnu.org wrote:
There is a Midi-only command for _then_ telling LilyPond that the
instrument is transposed. So you need to place your horn part within
\transpose f c' { \transposition f ... }
in order to have the visuals go up one fifth, and have
Hi Jeffrey and Ben,
On Wed, Jan 16, 2013 at 2:13 PM, SoundsFromSound
soundsfromso...@gmail.comwrote:
I agree - you have done an amazing job with this, thank you so much!
Ben
Jeffrey Trevino wrote
Hi David,
I really hope this ends up in Lilypond; you've clearly put a ton of work
If I change the fingering font, how can I get the bold version of the
selected font to be used. In the example below, overriding the font and
the font-size works ok, but overriding the font-series to bold doesn't.
\version 2.17.11
\relative c'' {
c-3
\override Fingering.font-name = #'Arial
Hi,
in some situations I used to override the Y-extent of the Clef.
With 2.17.10 it doesn't work any more.
\version 2.16.1
%\version 2.17.10
#(ly:set-option 'debug-skylines #t)
verticalSpace = {
% None of the following commands work with 2.17.10
\override Staff.Clef #'Y-extent
I'm working on a saxophone fingering chart, but I have some problems:
1) If trying to place an accidental next to a note (B\flat, C\sharp, etc.)
my only two (apparent) options are to include it in a column, in which case
the accidental appears below the letter, or I have to leave the note name
I have noticed that the last few versions of the unstable Lilypond
releases, if I just click on the download link (eg
http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.17.11-1.linux-64.sh),
then instead of a dialog asking for the location to place the download,
the script
On 01/02/13 14:09, Nick Payne wrote:
If I change the fingering font, how can I get the bold version of the
selected font to be used. In the example below, overriding the font
and the font-size works ok, but overriding the font-series to bold
doesn't.
\version 2.17.11
\relative c'' {
c-3
26 matches
Mail list logo
