So, to answer this post as well as H.C.'s previous query on the topic, I had a look at the dumpOSC code and indeed it doesn't handle the timetags.
The only related code is the following: /* Print the time tag */ #ifdef DEBUG printf("[ %lx%08lx\n", ntohl(*((unsigned long *)(buf+8)) ), ntohl(*((unsigned long *)(buf+12)))); #endif In which the timetag is so nicely ignored completely. Torsten, I suggest you have a look at the OSC objects in the "mrpeach" folder, as I think they have better support for timetags among other things. I may play around with creating abstractions using mrpeach objects to replace dumpOSC and sendOSC, as it seems this is about due. Steve On 8/30/07, Torsten Anders <[EMAIL PROTECTED]> wrote: > Dear all, > > I am sending OSC messages from the UNIX app sendOSC to Pd using the > Pd object [dumpOSC] -- it worked out of the box, very nice! > > However, it seems that [dumpOSC] always reacts immediately -- > regardless of any time stamp (16 figure hex number according to OSC > specs). Is it at all possible that Pd delays the processing of > received OSC messages because of some time tag which lies in the > future? I planned to let Pd do the actual scheduling, because I > figured its timing will be rather reliable... > > Thank you! > > Best > Torsten > > -- > Torsten Anders > Interdisciplinary Centre for Computer Music Research > University of Plymouth > strasheela.sourceforge.net > www.torsten-anders.de > > > > > > _______________________________________________ > PD-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list