-
radarsat1 committed revision 178 to the LibLO SVN repository, changing 2 files.
2009-12-10 18:34:30 UTC by radarsat1
-
radarsat1 committed revision 177 to the LibLO SVN repository, changing 2 files.
2009-10-02 20:58:45 UTC by radarsat1
-
radarsat1 committed revision 176 to the LibLO SVN repository, changing 6 files.
2009-09-17 15:50:29 UTC by radarsat1
-
radarsat1 committed revision 175 to the LibLO SVN repository, changing 17 files.
2009-09-17 15:50:22 UTC by radarsat1
-
Hi! I agree that automatically deferring messages according to timestamp precludes using LibLo for this type of application. However, since LibLo was designed with ease-of-use in mind, automatically handling timestamp-based message deferral seemed like a logical default. I think it would be nice to provide an opt-in way to mark message handlers as not deferred, for example. Would this solve...
2009-09-16 17:19:23 UTC by radarsat1
-
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...
2009-09-14 19:10:03 UTC by ojaii
