Martin Peach wrote:
IOhannes m zmoelnig wrote:
nevertheless i think it might be very good if i could distinguish between the 3 "types" of timetags)
That's a difficult problem. What's the difference between zero and zero? I mean how does one tag no delay as being different from a delay of zero without adding another outlet?
OK, I changed packOSC to output negative delays and it's now obvious, even on the same machine a "current" time tag always has a slight negative delay, whereas an "immediate" time tag is always exactly zero. That leaves the slight problem of a "future" message that arrives exactly on time... Martin
On Jul 12, 2007, at 11:33 AM, martin.peach@sympatico.ca wrote:
Martin Peach wrote:
IOhannes m zmoelnig wrote:
nevertheless i think it might be very good if i could distinguish between the 3 "types" of timetags)
That's a difficult problem. What's the difference between zero and zero? I mean how does one tag no delay as being different from a delay of zero without adding another outlet?
OK, I changed packOSC to output negative delays and it's now obvious, even on the same machine a "current" time tag always has a slight negative delay, whereas an "immediate" time tag is always exactly zero. That leaves the slight problem of a "future" message that arrives exactly on time... Martin
Wow, nice work! That sounds like it'll be quite easy to use timetags now. Is there anyway to generate timetags with Pd yet?
.hc
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith