Hans-Christoph Steiner wrote:
Hey all,
I am thinking of changing my license to GPLv3. The only forseeable
problem would be if people have taken out the or (at your option)
any later version from the standard GPLv2 text, thereby tying the
code to only the GPLv2.
is there a reason for
Hallo,
IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
is there a reason for this switch? (apart from staying current)
i haven't followed the discussion about GPLv3 in the last month, but
last time i did it was _very_ controversial...
It's not that controversial anymore as I
[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]
Bugs item #1752221, was opened at 2007-07-11 16:52
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=478070aid=1752221group_id=55736
Please note that this message will contain a full copy of the comment
On Thu, 12 Jul 2007, Hans-Christoph Steiner wrote:
I am thinking of changing my license to GPLv3. The only forseeable
problem would be if people have taken out the or (at your option) any
later version from the standard GPLv2 text, thereby tying the code to
only the GPLv2.
Does anyone know
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
Bugs item #1752995, was opened at 2007-07-12 14:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=478070aid=1752995group_id=55736
Please note that this message will contain a full copy of
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
11 matches
Mail list logo
