[EMAIL PROTECTED] wrote:
Message: 6
Date: Wed, 11 Jul 2007 17:34:40 +
From: Martin Peach [EMAIL PROTECTED]
Subject: [PD-cvs] externals/mrpeach/osc packOSC-help.pd, 1.6, 1.7
packOSC.c, 1.6, 1.7 unpackOSC.c, 1.3, 1.4 routeOSC-help.pd, 1.2,
1.3
To: [EMAIL PROTECTED]
Martin Peach wrote:
one solution might be to use negative delays: delaying objects, such as
[delay] and [pipe] just ignore negative values (so they behave the same
as when fed with 0), but the user has the option to determine whether
the message arrived to late and can act accordingly (e.g.
IOhannes m zmoelnig wrote:
another question:
in osc, timetags are per-bundle (not per message).
is the scheduling information sent to the outlet for each message or
only once for each bundle?
The delay is output exactly once for each time tag. packOSC generates a time
tag whenever a bundle
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
On Jul 12, 2007, at 11:33 AM, [EMAIL PROTECTED] 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
Hans-Christoph Steiner wrote:
Martin Peach wrote:
IOhannes m zmoelnig wrote:
OK, I changed packOSC to output negative delays and it's now
Oops, that should say unpackOSC...
obvious, even on the same machine a current time tag always has a
slight negative delay, whereas an
