|
|
Created:
10 years, 1 month ago by hanwenn Modified:
5 years, 2 months ago Reviewers:
Visibility:
Public. |
DescriptionDecrease space between vertical beams by length-fraction.
This causes 16th and higher grace beams to be closer together.
Thanks to Daniel Spreadbury for noting this in blog,
http://blog.steinberg.net/2015/03/development-diary-part-10/
Patch Set 1 #Patch Set 2 : comment #Patch Set 3 : another try #
Total comments: 1
Patch Set 4 : fix regression in grace-start.ly #Patch Set 5 : fix regression in grace-start.ly #Patch Set 6 : fix regression in grace-start.ly #Patch Set 7 : fix regression #Patch Set 8 : fix stem length regressions #Patch Set 9 : also handle length-fraction > 1 #MessagesTotal messages: 30
comment
Sign in to reply to this message.
another try
Sign in to reply to this message.
I don't think we have explicit test coverage for this, but not sure what it would look like.
Sign in to reply to this message.
On 2015/03/14 14:53:37, hanwenn wrote: > I don't think we have explicit test coverage for this, but not sure what it > would look like. Ping?
Sign in to reply to this message.
https://codereview.appspot.com/214250043/diff/40001/lily/beam.cc File lily/beam.cc (right): https://codereview.appspot.com/214250043/diff/40001/lily/beam.cc#newcode127 lily/beam.cc:127: ? (2 * staff_space + line - beam_thickness/fract) / 2.0 Is there some point to writing the stuff in a manner where the result comes about by a lot of cancellation? Here we have (2 * staff_space + line - beamthickness/fract) / 2.0 * fract instead of either (staff_space + line/2.0)*fract - beamthickness/2.0 or staff_space*fract + (line*fract - beamthickness)/2.0 and I don't see that we get better results by all that cancellation. Also it becomes fragile against things like fract being zero.
Sign in to reply to this message.
hanwenn@gmail.com writes: > On 2015/03/14 14:53:37, hanwenn wrote: >> I don't think we have explicit test coverage for this, but not sure > what it >> would look like. > > Ping? > > https://codereview.appspot.com/214250043/ Is there a corresponding Google code issue? -- David Kastrup
Sign in to reply to this message.
On 2015/03/24 12:02:06, dak wrote: > mailto:hanwenn@gmail.com writes: > > > On 2015/03/14 14:53:37, hanwenn wrote: > >> I don't think we have explicit test coverage for this, but not sure > > what it > >> would look like. > > > > Ping? > > > > https://codereview.appspot.com/214250043/ > > Is there a corresponding Google code issue? > > -- > David Kastrup There is now https://code.google.com/p/lilypond/issues/detail?id=4329 James
Sign in to reply to this message.
Passes make, make check and a full make doc. Reg test diffs here: https://www.hightail.com/download/UlRRWGJIcVh5UkhIRHRVag
Sign in to reply to this message.
Thanks for the test diffs. Looking at the regression tests, I see some degradations. . The second beam in `grace-start' is too far offset from the staff. Ditto for grace-`stem-length' and others. Note that I got similar glitches earlier too in my real-life scores but was never be able to reduce them to a minimum example, since it seems to be highly dependent on the surrounding grobs. So maybe this is another bug that just has become more visible here. . Regarding `magnifyMusic-dots-beamlets' I wonder whether a minimum distance between beam lines for a given beam thickness should be retained to avoid the visual clash shown in the first beam. . `quote-cue-event-types' now shows too short stems for the grace notes IMHO.
Sign in to reply to this message.
On 2015/03/25 06:14:00, lemzwerg wrote: > Thanks for the test diffs. Looking at the regression tests, I see some > degradations. the test diffs expired. Are they still available? > . The second beam in `grace-start' is too far offset from the staff. Ditto for > grace-`stem-length' and others. Note that I got similar glitches earlier too in > my real-life scores but was never be able to reduce them to a minimum example, > since it seems to be highly dependent on the surrounding grobs. So maybe this > is another bug that just has become more visible here. I have been looking at this for a bit. The problem is that the flat symbol is thought to have [-.38, 1.20] as extents, which brings it at distance of 0.2 to the beam. From visual inspection, it seems that the bounding box is a little too large, which is confirmed by looking at feta20.dvi. We could make the flat bbox tight around the glyph, but it wouldn't solve the problem. We should also scale down the padding (which is set to 0.5 in the details property). The beam length-fraction is decreased by a factor 0.8, but the font size for accidentals is decreased more strongly, by a factor 0.63 (magstep -4). > . Regarding `magnifyMusic-dots-beamlets' I wonder whether a minimum distance > between beam lines for a given beam thickness should be retained to avoid the > visual clash shown in the first beam. > > . `quote-cue-event-types' now shows too short stems for the grace notes IMHO.
Sign in to reply to this message.
fix regression in grace-start.ly
Sign in to reply to this message.
fix regression in grace-start.ly
Sign in to reply to this message.
fix regression in grace-start.ly
Sign in to reply to this message.
fix regression
Sign in to reply to this message.
On 2015/04/06 22:33:18, hanwenn wrote: > fix regression PTAL. I fixed the grace-start issue. Are the other ones serious enough that I should look into them too?
Sign in to reply to this message.
On 2015/04/06 22:20:24, hanwenn wrote: > On 2015/03/25 06:14:00, lemzwerg wrote: > > Thanks for the test diffs. Looking at the regression tests, I see some > > degradations. > > the test diffs expired. Are they still available? No. I'll have to re-run the make check and update the issue tracker.
Sign in to reply to this message.
Hanwen, Passes make, make check and a full make doc Reg test diffs here https://www.hightail.com/download/UlRRZUNxa0RCMTZybHNUQw James
Sign in to reply to this message.
Thanks again for the regtests. All my previous comments still hold, unfortunately.
Sign in to reply to this message.
This patch has been put back to 'needs work' based on Werner's comments above.
Sign in to reply to this message.
fix stem length regressions
Sign in to reply to this message.
also handle length-fraction > 1
Sign in to reply to this message.
On 2015/05/10 22:58:54, hanwenn wrote: > also handle length-fraction > 1 PTAL * I had a further look at the short stems, and should have fixed more cases by disabling forbidden beam quanting in case of grace notes. * magnifyMusic: can you show examples of what music at 50% scale should look like in print? I agree that the blotting may not be very desirable, but then again magnifying music at 50% is fairly uncommon. It seems that you are asking for a separate beam-gap-fraction variable? * quote-cue-event is actually fixed by this change: CueVoice specifies magstep -4 for stemlength, ie. 63%. That puts the ideal stem length for a beam at 2.205. The stems shown in the new image are very close to that. If you think CueVoice should use larger stems, that is a separate feature request IMO.
Sign in to reply to this message.
> * I had a further look at the short stems, and should have fixed > more cases by disabling forbidden beam quanting in case of grace > notes. Yes, everything looks OK now, thanks. > * magnifyMusic: can you show examples of what music at 50% scale > should look like in print? No, I can't. My observation was not targeted at anything particular. > It seems that you are asking for a separate beam-gap-fraction > variable? No, I don't :-) To be serious: I suggest working on such a feature only in case someone *really* needs it.
Sign in to reply to this message.
Patch on countdown for May 16th
Sign in to reply to this message.
Patch counted down - please push to Staging branch
Sign in to reply to this message.
should I do this myself? On Sat, May 16, 2015 at 8:41 AM, <pkx166h@gmail.com> wrote: > Patch counted down - please push to Staging branch > > https://codereview.appspot.com/214250043/ -- Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
Sign in to reply to this message.
On 2015/05/17 09:09:59, hanwenn wrote: > should I do this myself? > > On Sat, May 16, 2015 at 8:41 AM, <mailto:pkx166h@gmail.com> wrote: > > Patch counted down - please push to Staging branch > > > > https://codereview.appspot.com/214250043/ > > > > -- > Han-Wen Nienhuys - mailto:hanwenn@gmail.com - http://www.xs4all.nl/~hanwen Sure. I assume you have push permissions ;) James
Sign in to reply to this message.
Please push to staging (you'll need to rebase by now though)
Sign in to reply to this message.
Patch counted down - please push
Sign in to reply to this message.
pushed to staging. On Mon, May 25, 2015 at 1:48 PM, <pkx166h@gmail.com> wrote: > Patch counted down - please push > > https://codereview.appspot.com/214250043/ -- Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
Sign in to reply to this message.
|