Hi,
The goal was to allow all (or at least many) spanners to be able to
cross voices, but I started with dynamics since the engraver seemed
relatively simple. I also looked at slurs because of its existing
support for simultaneous slurs (in one voice).
After experimenting with these with some
Hi Francisco,
David Kastrup gave me some feedback on the code I wrote for the
project, which needs to be revised/better documented. I haven't had
much time to do that, although I am hoping to start the revision after
I finish my final examinations. At the moment, I can't give any ETA,
but I
Hi,
I am almost done moving multiple/cross-voice spanner code out of specific
engravers into the Spanner_engraver class. I just want to make sure this
approach is on the right track before finishing up and submitting the patch:
New instances of the engraver are created to handle
> \new Staff { << { g\=Staff.1( a b } >> << { c,\newCommand d e\=Staff.1) } >> }
> Without the command indicating the slur's change in voice, the d and e
> would not be acknowledged by the slur, since it would still belong to
> the voice it started in.
Correction: the c and d would not be
Hello,
On Tue, Jul 19, 2016 at 3:20 PM, Trevor Daniels wrote:
> You're now a developer AFA SourceForge is concerned, which means you can add
> Issues. There are a few more hoops to jump through before you can submit
> patches.
I have uploaded the patch, thanks.
Thank you Simon, Phil, Trevor for the advice
On Tue, Jul 19, 2016 at 3:20 AM, Phil Holmes wrote:
> AFAICS you don't have permission yet to create issues on Allura. If you
> create a SourceForge account and request permission for that account on this
> mailing list, Trevor
Hello,
I have (except for one question below) finished adapting
Dynamic_engraver and Dynamic_align_engraver to work cross-voice. I
plan to continue with other spanners (perhaps slurs next), but I want
to make sure I am on the right track. I organized my current progress
in the gsoc-2016-spanners
Hello,
A quick question regarding the key-list argument to \= : if the list
only has one key, it is assumed to be the id, as the share context is
optional. When both the context and id are given, however, should the
order of the keys be (context id) or (id context)? I initially
implemented the
Hello,
(@David: I did not know about that function, thanks)
I'm wondering how Dynamic_align_engraver should deal with cross-voice
dynamic spanners. I don't have any good ideas at the moment (the best
possibility I thought of is to have a DynamicLineSpanner follow a
cross-voice dynamic to the
On Tue, Jul 5, 2016 at 1:54 AM, David Kastrup <d...@gnu.org> wrote:
> Nathan Chou <starry...@gmail.com> writes:
>> That is a good point; I might agree with spanner id's not being shared
>> across voices if nothing has been indicated. To make this less
>> tedious,
On Fri, Jul 1, 2016 at 12:48 AM, David Kastrup wrote:
> But that means that you can no longer let people write individual parts
> with several spanner ids independently even when there never is even
> going to be any cross-Voice spanner. Spanner-ids like \=1 \=2 are not
> likely to
Thanks David and Urs for replying.
>> There is a detail I would like to clarify. David suggested allowing \=
>> to optionally specify the parent context in which a cross-voice
>> spanner's information is shared (although I am not sure how that would
>> be done with a key-list, since I think the
Hello,
I have tried the same idea with context properties, and it seems to
work just as well as my previous approach with a static member. (To
summarize: cross voice spanners and the voice they currently belong to
are stored in a property of some context containing both voices, like
Score. Each
Thank you Dan, David, Jan-Peter; I will try the suggestions out.
Nathan
On Sun, Jun 26, 2016 at 8:43 AM, Jan-Peter Voigt wrote:
>
>
> Am 26. Juni 2016 17:06:51 MESZ, schrieb David Kastrup :
>>Jan-Peter Voigt writes:
>> ...
>>> Whenever you are up
Hello,
Just wanted to update on my progress for the GSoC cross-voice spanners
project. The approach I am currently trying uses the existing
spanner-id property (which can be set like { c\=hello\< d\=hello\! });
spanners with an id are handled as potentially being cross-voice. Each
engraver
it basically does the same thing as the hidden voice
workaround?
Thanks again!
Nathan
On Mon, May 16, 2016 at 12:50 AM, David Kastrup <d...@gnu.org> wrote:
> Nathan Chou <starry...@gmail.com> writes:
>
>> Hello,
>>
>> I have somewhat looked at the code and
Hello,
I have somewhat looked at the code and want to confirm my
understanding of the current behavior:
* While the file is parsed in Scheme, spanners cause a START and STOP
event with an appropriate type to be created in the context they
belong to
* After creation of the Music objects, where
Hello all,
I am a second-year student studying computer science at UCLA, and I
will be working on the cross-voice spanners project this summer as
part of the Google Summer of Code program. I'm glad to have this
opportunity to contribute to Lilypond---I've written music with
Lilypond before and
Thank you for your suggestions!
I started looking at issue 3947. I found that adjusting baseline-skip can
be added to commands like \small in define-markup-commands.scm. But I'm not
sure where to look to adjust baseline-skip whenever font-size is overridden
not via one of those commands.
Also
Hello,
I am a second-year student looking to contribute for Google Summer of Code
(and perhaps afterward). I've used Lilypond to make some relatively simple
scores before, and have some experience in C/C++ (not yet familiar with
Scheme, but learning).
I've downloaded LilyDev and successfully
20 matches
Mail list logo