Guitar stroke fingering is lower case, but with the orientation set to up,
the p is not correctly aligned with the other characters in a succession of
fingering indications, and with the orientation set to down, the i is
similarly misaligned.
This doesn't look pleasing to the eye, and indeed, whe
thanks guys. you guys are a great help. this is an awesome community.
I've always thought music notation software are ugly and pixelated. the pretty
ones are finale which have $$$ prices -_-
found lilypond recently. love it
wonder how lilypond developers make a livelihood if they charge nothing.
huy nguyen wrote:
well, if I didn't use the \voiceOne command, and the remove staff
performer on the \midi, I would get piano voice instead of violin and
viola. so I don't know how to do that.
Regarding the midi problem: If you add "Staff" to the midiInstrument
setting it will make the instrum
Oops.
\slurSolid needs to be added to the beginning
of the music function in case \slurDashed was
called before \slurSolidDashed (as an example).
- Mark
\version "2.13.0"
halfAndHalfSlur =
#(define-music-function
(parser location switch-point start-dashed?)
(number? boolean?)
#
huy nguyen wrote:
I've attached the file. you can try to compose it. you'll see that
the rests are placed in weird places, I've figured that the \voiceOne
command did that. If I don't use the \voiceOne command, and the
remove staff performer command in the \midi, it will just give piano
sounds an
I've attached the file. you can try to compose it. you'll see that the rests
are placed in weird places, I've figured that the \voiceOne command did that.
If I don't use the \voiceOne command, and the remove staff performer command in
the \midi, it will just give piano sounds and not strings sou
On Mon, Apr 13, 2009 at 04:47:29AM +0800, huy nguyen wrote:
> I'm a string player, so all the questions here about violins and violas.
>
> ok first of all, the program places the beam for eight notes in weird
> places. sometime they don't even beam all of the sixteen notes together. so I
> see 4
huy nguyen wrote:
I'm a string player, so all the questions here about violins and violas.
ok first of all, the program places the beam for eight notes in weird
places. sometime they don't even beam all of the sixteen notes together. so I
see 4 beamed 16th notes, and then 4 separate
I'm a string player, so all the questions here about violins and violas.
ok first of all, the program places the beam for eight notes in weird places. sometime they don't even beam all of the sixteen notes together. so I see 4 beamed 16th notes, and then 4 separate ones.. although it don't matt
Simon Bailey wrote Sunday, April 12, 2009 1:12 PM
On 12 Apr 2009, at 13:42, Trevor Daniels wrote:
LGTM. Pushed to git origin/master,
lgtm?
Looks good to me. A Han-Wen-ism.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://li
hi,
On 12 Apr 2009, at 13:42, Trevor Daniels wrote:
LGTM. Pushed to git origin/master,
lgtm?
Editing docs is fun, isn't it ;)
yeah. ;) something i don't get to do too much of in my own projects --
too much coding, not enough time for docs. :/
regards,
sb
__
Mark Polesky wrote:
MonAmiPierrot wrote:
Is there any way to have a half-dashed-half-solid Slur, i.e. a slur that
begins dashed and at a certain point turns solid (or viceversa?)
Piero,
here's one solution. Personally, I don't think it
looks quite as good as it should, but maybe you're
Look
>> order in which the fingering indications appear above the stave doesn't
>> match the pitch order of the notes they are applied to.
Just to be clear, that wasn't happening for me... the order was fine,
it was just that the fingering indications in one voice were colliding
with note heads/stems o
Thanks Simon
LGTM. Pushed to git origin/master,
Editing docs is fun, isn't it ;)
Trevor
- Original Message -
From: "Simon Bailey"
To: "Neil Puttock"
Cc: "Trevor Daniels" ; "lilypond-user
Mailinglist"
Sent: Sunday, April 12, 2009 11:01 AM
Subject: Re: LilyPond midi extension
Nick Payne wrote Sunday, April 12, 2009 12:10 PM
I find the same thing happens with guitar fingering - that
sometimes the
order in which the fingering indications appear above the stave
doesn't
match the pitch order of the notes they are applied to.
Do you have an example which shows this ha
I find the same thing happens with guitar fingering - that sometimes the
order in which the fingering indications appear above the stave doesn't
match the pitch order of the notes they are applied to. I just use \tweak on
the fingerings to fix it.
Nick
> -Original Message-
> From: lilypon
On 11 Apr 2009, at 15:22, Neil Puttock wrote:
insert the following line before the start of the @code{\score} block:
Simon, this line isn't quite right, since users might place the option
setting inside a \book or \bookpart block, resulting in a syntax
error. It would be better to advise pla
Tim,
thanks for reply. Meanwhile I got it.
It was a typo in the mail. But you get the link
http://lilypondtool.organum.hu/fileadmin/lilypondtool/LilyPondTool.zip
at http://lilypondtool.organum.hu/ -> Install -> LilyPondTool.zip
that gives 404 too.
Reading the LilyPondTool documentation I fou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sonntag, 12. April 2009 07:11:26 James E. Bailey wrote:
> Wow, I should really not answer questions when I'm not awake.
>
> Lyrics need to be associated with a voice context. Regardless of
> whether or not you name them, lilypond creates its own con
Mark Polesky wrote:
> here's one solution.
same function with leaner code.
Got rid of about 15 lines.
- Mark
\version "2.13.0"
halfAndHalfSlur =
#(define-music-function
(parser location switch-point start-dashed?)
(number? boolean?)
#{
% set 'layer to -2 if you're also using
20 matches
Mail list logo
