21 Jun
2005
21 Jun
'05
1:31 p.m.
Stéphane Letz <letz(a)grame.fr> writes:
Le 21 juin 05 à 02:15, ian esten a écrit :
They would each need a scheduler, but that could be very simple.
Maybe just a future event queue sorted by time. On each process()
call, send the ones that apply to the current period. The trickiest
part is handling the memory allocation and deallocation.
Someone (perhaps libjack) could provide a standard set of functions to
manage this, while still doing it all in the client's address space.
The advantage is that future events are easily cancelled, when needed.
--
joq
would it not be possible to have the midishare to
jack bridge buffer
events that are timestamped in the future, and then schedule them in
realtime in the process callback?
ian
This would require *each* client to have its own scheduler... (since
events may be sent out of order by the application in the MidiShare
model). Crazy ! The proper model would be to have the scheduler at
the server level of course...