9 May
2013
9 May
'13
11:16 p.m.
On Thu, 2013-05-09 at 23:02 +0200, Florian Paul Schmidt wrote:
On 05/09/2013 10:46 PM, David Robillard wrote:
I see, I misread the code. I suppose that works if you need to iterate
over every frame for other reasons.
(Sorry for the late reply, I don't monitor
LAD very closely these days)
You should be able to handle all the events in one loop.
However here you seem to be iterating over all events *for every frame*?
That would cause a problem with loading since you'll issue a ton of
identical load requests, but it also probably isn't what you want for
MIDI either. You'll trigger everything repeatedly and the timing is
wrong. I think you need to unify your two loops here.
Nope, I do not iterate over all events in every frame. Before iterating
over the frames I get the first event and then on every frame I iterate
over those events that have that frame time.. This is similar to how the
jack_midi example code does it.. I do use the worker extension. The only problem I saw
was when I tried
to integrate the patch_set messages in that same loop.
There shouldn't be a difference. Assuming that, in the integrated case,
you're scheduling the exact same work (easy enough to check) nothing
should be any different, unless something is wrong with the asynchronous
work stuff and some really fine timing problems are happening...
everything looks good though, the work stuff shouldn't be affected by /
affect state...
What kind of problem?
-dr