LibLO

Hi,

I believe that the way the hi-level API schedules received timestamped
messages is wrong design.

This forbids taking latency into account in a realtime app.

Say that thread A receives a timestamped message, and wants to pass it to
the realtime audio thread called B.

If liblo calls a method in thread A when the timestamp is lower or equal to
the current time, it is already too late for 1. passing the information to
thread B, and 2. for thread B to trigger a sound event in advance according
to the output latency.

Thread B should receive the message ASAP in order to prepare for triggering
the corresponding audio event.

I suppose that one can find a workaround using the low-level API, but IMO
the hi-level API in its current state is unusable for any accurate
timestamped operation.