Yes, that did it! Thank you very much. I had forgotten I had even used
that line of code; I took it directly from the Snippets, which said it was
used for suppressing collision warnings in the log, but never said anything
about it actually influencing collision detection. Now it looks beautiful
Neil Puttock wrote Sunday, December 13, 2009 1:43 PM
2009/12/13 Trevor Daniels :
If you look at the full score which Glendan attached you'll see
the missing
bits, and also see that there are voices nested within voices in
the full
score. This seems to be a requirement to demonstrate this
2009/12/13 Trevor Daniels :
> James
>
> If you look at the full score which Glendan attached you'll see the missing
> bits, and also see that there are voices nested within voices in the full
> score. This seems to be a requirement to demonstrate this bug, although I
> haven't the time to narrow i
.
Trevor
- Original Message -
From: "James Bailey"
To: "Glendan Lawler"
Cc:
Sent: Sunday, December 13, 2009 10:52 AM
Subject: Re: Can't Resolve Colliding Noteheads...
No matter how hard I try, I can't seem to reproduce this problem.
With, or without the
No matter how hard I try, I can't seem to reproduce this problem.
With, or without the markup (which includes a variable which hasn't
been described in the snippet), or the notecolumn markup, I still get
the expected output, with the notes properly shifted. Can you send an
example which sho
workaround that might be acceptable:
% \once \override NoteColumn #'extra-offset = #7.5
s2*1/256 gis2*255/256
Trevor
- Original Message -
From: "Glendan Lawler"
To:
Sent: Saturday, December 12, 2009 10:15 PM
Subject: Can't Resolve Colliding Noteheads.
Hey everybody, I'm having a problem with noteheads in different voices
colliding, and I can't seem to fix it. I tried the standard fix from the
notation: \once \override NoteColumn #'force-hshift = # , which worked fine
in a test case I did, but for some reason has zero effect in the document.
He
