I've been setting some Carcassi studies. His Op60 No 8 has a pf
dynamic marking at one point (see
http://erato.uvt.nl/files/imglnks/usimg/c/c8/IMSLP34430-PMLP03629-ribs0980_06.pdf,
fifth stave on the first page), which does not exist in Lilypond. I
added the variable definition pf =
This YouTube by Hajo (dl1sdz) claims to have generated a just
intonation MIDI file from a LilyPond file.
BWV-988-Var-12-Just.AVI
http://www.youtube.com/watch?v=-rkaueIngyY
How does one do this?
I can find just intonation in the glossary but not in the rest of
the documentation.
I am
Well, the way we did it was to retune the synthesiser fluidsynth using the
tunings (?) command. It was a slightly different problem because we wanted 19-
ET rather than messing about with pythagorean adjustments, which might have to
change every time you modulate anyway? We found that not many
dadadharma @dslextreme.com dadadha...@dslextreme.com
wrote:
This YouTube by Hajo (dl1sdz) claims to have generated a
just intonation MIDI file from a LilyPond file.
BWV-988-Var-12-Just.AVI
http://www.youtube.com/watch?v=-rkaueIngyY
How does one do this?
Well, disappointingly they didn't
Am Wednesday, 14. September 2011, 06:47:50 schrieb Colin Campbell:
On 11-09-13 09:29 PM, Nick Payne wrote:
Ok, the following small example reproduces the error on my system with
2.15.11:
The minimal example is (the normal fingering -1 does not have any influence,
so it should be removed,
On Wed, 14 Sep 2011 13:29:30 +1000, Nick Payne wrote:
On 14/09/11 08:34, Trevor Daniels wrote:
Nick Payne wrote Tuesday, September 13, 2011 11:25 PM
The problem is that the score is quite large, and the log gives no
indication at all about where the error is coming from. I guess I can
try
Hi list.
This is probably in the manual, but I can't find it so I'm asking you
all. In a sequence like
{ b16. b32 b32 b16. }
the default is to have a beam that connects the two shortest notes,
like the first bar in the attached image. I want the beaming so it
always makes a beamlet point
On Sep 13, 2011, at 11:57 PM, Colin Campbell c...@shaw.ca wrote:
On 11-09-13 10:29 AM, Stan Sanderson wrote:
Thanks. I will recheck the list setting.
Looks like Bugreports will see this twice!
Stan
On Sep 13, 2011, at 11:21 AM, Xavier Scheuerx.sche...@gmail.com wrote:
On 13 September
Hello,
I'd like to add some measures (engraved thanks to LilyPond) to an
existing *scanned* score.
So I begin with a currentBarNumber different from 1, I remove the
TimeSignature stencil at the beginning, etc.
And as there are only a very small number of measures to insert I
compile with
On 14 September 2011 21:30, Xavier Scheuer x.sche...@gmail.com wrote:
What I'd like to get but I did not managed to is to begin the staff
with a _normal bar_ ( \bar | ) at the left edge (because these
measures are to be inserted in the middle of an existing [scanned]
score).
I tried to
Looks like a valid bug report.
Fwd to bug- (it was originally sent to -user).
On 12 September 2011 22:08, Ed Gordijn ed.klari...@gmail.com wrote:
Hi List,
I am working on a piece with three movements. I organized my score in
different files, for the tiny-example let's say two. The fist file
2011/9/14 Neil Puttock n.putt...@gmail.com:
On 14 September 2011 21:30, Xavier Scheuer x.sche...@gmail.com wrote:
What I'd like to get but I did not managed to is to begin the staff
with a _normal bar_ ( \bar | ) at the left edge (because these
measures are to be inserted in the middle of an
On 14 September 2011 22:42, Neil Puttock n.putt...@gmail.com wrote:
Use a SystemStartBar instead (with collapse-height overridden).
Yeah!
Thank you for this quick answer.
SystemStartBar did not come into my mind!
It is indeed a simple and efficient solution (I increased the thickness
of
2011/9/14 Janek Warchoł janek.lilyp...@gmail.com:
Interesting, shouldn't \override Staff.BarLine #'break-visibility =
#'#(#t #t #t) solve Xavier's problem? Should i report this as a bug?
No. An ordinary barline isn't allowed at the start of a system.
Cheers,
Neil
2011/9/14 Neil Puttock n.putt...@gmail.com:
2011/9/14 Janek Warchoł janek.lilyp...@gmail.com:
Interesting, shouldn't \override Staff.BarLine #'break-visibility =
#'#(#t #t #t) solve Xavier's problem? Should i report this as a bug?
No. An ordinary barline isn't allowed at the start of a
2011/9/14 Janek Warchoł janek.lilyp...@gmail.com:
Why shouldn't it be controlled by break-visibility?
See output-lib.scm, bar-glyph-alist and bar-line::calc-glyph-name.
Cheers,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
Hello,
On Wed, Sep 14, 2011 at 7:46 PM, Sven Axelsson sven.axels...@gmail.com wrote:
Hi list.
This is probably in the manual,
http://lilypond.org/doc/v2.14/Documentation/notation/beams#setting-automatic-beam-behavior
--
--
James
___
lilypond-user
On 13 September 2011 23:50, harm6 thomasmorle...@googlemail.com wrote:
modifying some definitions developed by Mike and David in this thread
http://old.nabble.com/shorten-a-broken-hairpin-at-a-linebreak--td32343028.html
I hope this will do the job:
This is a bit complicated. :)
\version
18 matches
Mail list logo
