Re: Two possible bugs when dealing with Automatic note splitting
Gilberto Agostinho gilbertohasn...@googlemail.com writes: I think I found two possible bugs when dealing with Automatic note splitting. 1) when a note has an accidental and it has to be split, the ligaturas look out of place. 2) when a note has an accidental (regular accidental, or forced accidental with an !, or even due to *dodecaphonic style*) and it has to be split, these accidentals appear in all repeated notes. So are these bugs or am I misusing the rhythm splitting? Bugs. Regressions. In 2.16.0, everything looks fine except for the repeated forced accidentals (those have always been overlooked, I guess). Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
David Kastrup d...@gnu.org writes: Gilberto Agostinho gilbertohasn...@googlemail.com writes: I think I found two possible bugs when dealing with Automatic note splitting. 1) when a note has an accidental and it has to be split, the ligaturas look out of place. 2) when a note has an accidental (regular accidental, or forced accidental with an !, or even due to *dodecaphonic style*) and it has to be split, these accidentals appear in all repeated notes. So are these bugs or am I misusing the rhythm splitting? Bugs. Regressions. In 2.16.0, everything looks fine except for the repeated forced accidentals (those have always been overlooked, I guess). Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. Huh. git log -p lily/completion-note-heads-engraver.cc turns up the following as the first non-trivial suspect: commit 49e8c80e3282cefff91ad1b5aaff5d91b443ba5e Author: Benkő Pál benko@gmail.com Date: Sat Apr 14 10:21:02 2012 +0200 Issue 2470: introduce completionUnit enable Completion_heads_engraver to work in sub-bar units Except that this commit definitely is already included in 2.16.0. So it must be something else that interferes here. Interesting. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
- Original Message - From: David Kastrup d...@gnu.org To: Gilberto Agostinho gilbertohasn...@googlemail.com Cc: bug-lilypond@gnu.org; lilypond-user lilypond-u...@gnu.org Sent: Wednesday, October 02, 2013 6:03 PM Subject: Re: Two possible bugs when dealing with Automatic note splitting Gilberto Agostinho gilbertohasn...@googlemail.com writes: I think I found two possible bugs when dealing with Automatic note splitting. 1) when a note has an accidental and it has to be split, the ligaturas look out of place. 2) when a note has an accidental (regular accidental, or forced accidental with an !, or even due to *dodecaphonic style*) and it has to be split, these accidentals appear in all repeated notes. So are these bugs or am I misusing the rhythm splitting? Bugs. Regressions. In 2.16.0, everything looks fine except for the repeated forced accidentals (those have always been overlooked, I guess). Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup It was between 2.17.4 and 2.17.9 - I don't have the intervening versions installed. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
Phil Holmes m...@philholmes.net writes: Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup It was between 2.17.4 and 2.17.9 - I don't have the intervening versions installed. Excellent. I'll take it from there. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
David Kastrup d...@gnu.org writes: Phil Holmes m...@philholmes.net writes: Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup It was between 2.17.4 and 2.17.9 - I don't have the intervening versions installed. Excellent. I'll take it from there. Uh oh. Looking at the logs in between, issue 2745 would seem like a prime suspect. Let's see whether that helps me speed up the bisection. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
Phil Holmes m...@philholmes.net writes: Bugs. Regressions. In 2.16.0, everything looks fine except for the repeated forced accidentals (those have always been overlooked, I guess). Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup It was between 2.17.4 and 2.17.9 - I don't have the intervening versions installed. It's 2.17.2. 6c98920d868524eee3e809578ad4389d409a566a is the first bad commit commit 6c98920d868524eee3e809578ad4389d409a566a Author: Mike Solomon m...@apollinemike.com Date: Mon Sep 10 08:53:09 2012 +0200 Avoids script-tie collisions Ties are now issued at their correct beginning time step and are suicided if they are ultimately unused. This allows the Script_engraver to acknowledge them at the correct timestep and register them as supports for the side-position-interface. :04 04 ec4bcbb1fb06bceb3e902f4716a37e0219857011 2441130dcb35fd0cfc4bed7e5c5e980862e4a834 M input :04 04 d6bf3f5b36a91f18517db1aed64ad71ed02b8397 84ace5a143d17a09e4f0cd8b087343fc9cc8dcfc M lily -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LM 4.5: dead link
Hello,
2013/9/30 Trevor Daniels t.dani...@treda.co.uk
It seems a backslash in a node name causes no problems for
references within the same manual, but cross-references across
manuals fail. The correct way of dealing with this is to drop the
backslash from the node name and encode it using the bs{}
macro in the heading. Here's an example from changing-defaults.itely:
@node The set command
@subsection The @code{@bs{}set} command
I see there are several node names in the documentation that include
native backslashes, but only the one noted above is used in a
reference across manuals. I'll fix ref_check.py to check for backslash
in note names to give a warning, and amend all the instances in the
documentation. Oh, and add a note to the CG.
@bug Squad: could you please raise an issue to track this
This has been added as
http://code.google.com/p/lilypond/issues/detail?id=3590
--
Marek
bug squad member
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two possible bugs when dealing with Automatic note splitting
Thanks a lot, guys. Since I work with algorithm composition, the option to split notes is very handy to me. Please let me know if I can be of any help with this bug. Regards, Gilberto On Wed, Oct 2, 2013 at 7:17 PM, David Kastrup d...@gnu.org wrote: Phil Holmes m...@philholmes.net writes: Bug squad, can you file the original report and the examples? And can people who have some version of 2.17 installed narrow this in some more? I don't really fancy bisecting all the way from 2.16. -- David Kastrup It was between 2.17.4 and 2.17.9 - I don't have the intervening versions installed. Excellent. I'll take it from there. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
