Re: OMG - performance issue with Scheme engraver

[David Kastrup]

Urs Liska <address@hidden> writes:

> Am 11.07.2018 um 11:55 schrieb David Kastrup:
>> Urs Liska <address@hidden> writes:
>>
>>> Am 10.07.2018 um 19:48 schrieb Urs Liska:
>>>> This seems to confirm that I should *not* break out of the for-each
>>>> loop that iterates over all-grobs in process-acknowledged.
>>>>
>>>> Does that mean that resetting the all-grobs list in
>>>> start-translation-timestep is the right approach#
>>> It's obviously not: while it reliably reduces processing time to what
>>> it should be it equally reliably misses all annotations except on the
>>> very first timestep.
>> Which is not the problem of resetting all-grobs in
>> start-translation-timestep but the asinine clearing of all-grobs inside
>> of the loop.
>
> I either don't understand or partially disagree.
> While I see now how clearing the list inside the loop causes a problem
> I don't see how it produces the behaviour I observe.

>> But it seems like you may be much better off just hooking into the Score
>> level process-acknowledged phase.  You are, after all, doing a global
>> kind of operation here.
>
> Well, except that I need to access each grob context's name and id (as
> discussed in the other thread).

Nobody forces you to only store the grob but not its originating
context.

-- 
David Kastrup