-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/06/15 21:21, Gilberto Agostinho wrote:
> Currently, the MIDI output from LilyPond uses a hard coded value to
> calculate the duration for the grace notes (1/4 of their duration
> according to the documentation or 9/40 according to David Kastrup).
> It would be really nice to allow the users to set this proportion
> themselves, since depending on the type of score one is engraving
> the grace notes can be either too fast or too slow, and the only
> solution right now is to manually create a different score with
> different values for the grace notes in order to produce a good
> MIDI file.
> 
> For the thread which originated this request, see: 
> http://lilypond.1069038.n5.nabble.com/grace-note-duration-td177682.html
>
>
> 
_______________________________________________
> bug-lilypond mailing list [email protected] 
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
> 
> 

Note that you can adjust the value directly (I believe - I am not a
programmer) in the ../ly/articulate.ly script itself although I assume
this would be global for the entire score.

As it states in the articulate.ly script file itself

- --snip--

% What proportion of an ordinary grace note's time should be stolen
% from preceding notes (as opposed to stealing from the principal note).
% Composers' intentions for this vary.  Taking all from the preceding
% notes is LilyPond's built-in behaviour for MIDI output.
#(define ac:defaultGraceBackwardness 1)

- --snip--

So unless you can set that #(define ...) each time, independently -
again I defer to my developer colleagues to suggest a way - you can at
least change the value from the 'default'.

James
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVenqcAAoJEP8yVoKoS9i+P/EQAMXPTCmTD1q0Nh0ek7qFe33U
6WiApRtjkG6NnDTi0Chr81YmQnJLj5p9L4rzDAepjIiEVg/ibkziTDxgFNS7Tyie
rokw+m5JzPrg+kkR6sf59ncrqXn5TQM1jM1e5BBt+EgH9fATA/AxaOZlSFyU5jFo
a8lzMLUh6o2tPKEHnLGMqVu4D1YUYgpAnm/zBw5qBF8ln/sQQqWzz2vAokI7uolJ
S+MiHT2g0xQsqexG/Iv3cHvxP/Ic/euEPVRNAc1LhXD1HEW+VkevOrvCmUvG3Ozx
mQaBRFCNA7TUpGWn6NvTjKh/Ycowxoz1GvLtSAdSWrj3IkHYwIwPfutMF4ZQFm8u
V6kCuMq+McOAT7Rr99hrwtsrhsGHoJsz6PZvdMl49Yn5uj26ONI3Vp1VtPM8mhyN
5FQpN8G94mmsbjR36g4JvBG7Z4IzvoYabbB7Q0mLlNbqzAzucquOgj7iEeI4xIlY
X2VlejeUePYq/YlrrNmDzXAwFIY1amPChvERdDcrPklHr66f+mwCDIjX+HQyXQS8
iGemnSGasgCZpJvefnmJZrrygSdo+78g3HXigkXPcmqzksaGAGGZJalMQ0CgzkJi
KIYn/CitshjneUJb4+jB2WJfJBoAr5Su8OOn9UcoYrs6/5QT9fKNNFilOc5ruKmR
MVg2vruLQpoan3KDjGDf
=/Cp5
-----END PGP SIGNATURE-----

_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to