[OSC_dev] No dumpOSC output in pipe in non-interactive terminal

[Andy W. Schmeder]

There seems to be some confusion here.  The liblo-devel thread you  
referenced earlier appears to discuss an experimental high-level  
feature that implements a scheduler for liblo.  Its been a while  
since I actually coded with liblo, but if you check the docs, the  
time-tag is available as a pair of uint_32 in the lo_timetag struct.   
You should have no problem sending a stream of time-tagged bundles  
using that.

Most implementations provide the timetag in a more or less equivalent  
format.  As for the time stamps themselves, they can be generated off  
of gettimeofday() or however you see fit.


On Sep 9, 2007, at 1:20 AM, Torsten Anders wrote:

> thanks for your reply. It appears we misunderstood each other. I  
> don't want realtime scheduling to be part of the library (nor my  
> application for that matter) exactly because of these complexities.  
> Instead, I want an application designed to care about timing (like  
> Ps or SuperCollider) receive OSC and then care about the scheduling  
> of the events it received.
>
> Therefore, I assumed, I need an OSC library which can send  
> timestamped bundles (i.e. can generate the NTP timestamps, but does  
> not do the scheduling itself). Its seems some OSC libraries (e.g.,  
> Pd's orig [dumpOSC] and liblo -- according to its TODO file) can  
> not encode/decode these time tags.

...


---

Andy W. Schmeder
andy [at] cnmat.berkeley.edu
phone:	+1-510-643-9990 x.313
cell: 	+1-510-717-6653

Programmer/Analyst II
Center for New Music and Audio Technologies
University of California at Berkeley
http://cnmat.berkeley.edu




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.create.ucsb.edu/pipermail/osc_dev/attachments/20070909/c347a83a/attachment.htm