[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: triggering translation from engraver
From: |
David Kastrup |
Subject: |
Re: triggering translation from engraver |
Date: |
Wed, 23 Aug 2017 17:57:28 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
David Kastrup <address@hidden> writes:
> Jan-Peter Voigt <address@hidden> writes:
>
>> Do you have another idea how to do that?
>
> Timing is established by iterators and they work on music expressions,
> not events. So you need to have an iterator in the race from the start.
> Few iterators have variable length. The sequential iterator can have an
> elements-callback delivering music expressions. Those can have a
> structure and/or length determined at callback time.
>
> Kicking this into orderly operation does not seem like it would be
> reasonably workable.
>
> Iterators are not user-definable at the moment. Either a general
> facility or a more specific "wait-iterator" would seem warranted.
You might want to use \lyricsto to add your private control context to
the Score context. When switching off everything that can track
melismata, you might get woken up once per event regardless of how long
your actual expressions are.
But it might make more sense to work on actual infrastructure for this
rather than fudging around with existing facilities not intended for it.
--
David Kastrup
- triggering translation from engraver, Jan-Peter Voigt, 2017/08/23
- Re: triggering translation from engraver, David Kastrup, 2017/08/23
- Re: triggering translation from engraver,
David Kastrup <=
- Re: triggering translation from engraver, David Kastrup, 2017/08/23
- Re: triggering translation from engraver, David Kastrup, 2017/08/23
- Re: triggering translation from engraver, Jan-Peter Voigt, 2017/08/23
- Re: triggering translation from engraver, David Kastrup, 2017/08/23
- Re: triggering translation from engraver, Jan-Peter Voigt, 2017/08/24
Re: triggering translation from engraver, Kieren MacMillan, 2017/08/23