-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-17 17:46, IEM - network operating center (IOhannes m
zmoelnig) wrote:
due to a scheduled network maintainance, puredata.info and
associated services (including the pd related mailinglists) will be
offline tomorrow, wednesday starting at
due to a scheduled network maintainance, puredata.info and associated
services (including the pd related mailinglists) will be offline
tomorrow, wednesday starting at 10:00 (CEST).
we hope to be online again within two hours.
sorry for the inconvenience.
fgasdr
IOhannes
--
IEM - network
see i thought that as well
but pd starts and will not let me edit a patch
issuing
sudo ifconfig lo up
did not work.
i know this is OT, but any tips might help
pp
Martin Peach [EMAIL PROTECTED] wrote:
Mathieu Bouchard wrote:
On Fri, 14 Dec 2007, Martin Peach wrote:
bigswift
Hi,
Looks like your 'lo' isn't set up correctly on boot, something similar
is here:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/110144
Martin Peach wrote:
bigswift wrote:
Hi
When using pd onsite without a network connection i cannot edit files with
pd-extened RC5 on
bigswift wrote:
Hi
When using pd onsite without a network connection i cannot edit files with
pd-extened RC5 on Ubuntu Gutsy. If a ethernet cable is connected i can edit
files, but if i am not wired in i cannot make new connections or edit a
file. Is there a way to workaround this?
Put the
Mathieu Bouchard wrote:
On Fri, 14 Dec 2007, Martin Peach wrote:
bigswift wrote:
When using pd onsite without a network connection i cannot edit files
with
pd-extened RC5 on Ubuntu Gutsy. If a ethernet cable is connected i can
edit
files, but if i am not wired in i cannot make new connections
hi list,
i'm sending control data to a vline~ object over the network. those
are precisely timed messages. i can hear uncontinuous errors in the
output, some messages seem to be delayed.
when i use OSC the timing is pretty bad. now i use netserver/
netclient and it's getting better, but
Max Neupert wrote:
hi list,
i'm sending control data to a vline~ object over the network. those
are precisely timed messages. i can hear uncontinuous errors in the
output, some messages seem to be delayed.
when i use OSC the timing is pretty bad. now i use netserver/
netclient and it's
I think the best way would be to put some kind of timestamp in the
messages and have the receiver hold the received message until the
timestamped time occurs. That should get rid of any jitter at the
expense of a second or so of delay.
In fact that's an interesting point related to OSC. OSC
Hallo,
Roman Haefeli hat gesagt: // Roman Haefeli wrote:
as a crude solution to limit bandwidth in netpd, i made the attached
abstraction [list-fifo]. i am not sure, if it is a suitable name.
@frank
if you think, that fits into your list-abs-collection, feel free to
add/modify it.
Thanks
On Mon, 2006-12-18 at 13:47 +0100, Frank Barknecht wrote:
Hallo,
Roman Haefeli hat gesagt: // Roman Haefeli wrote:
as a crude solution to limit bandwidth in netpd, i made the attached
abstraction [list-fifo]. i am not sure, if it is a suitable name.
@frank
if you think, that fits
On Sun, 17 Dec 2006, Roman Haefeli wrote:
netpd's major problem is the occurence of many dropouts in certain
situations. one reason is the way how all (at least all i know) network
related objects in pd handle buffer overruns. when the buffer of a
network object is full, the whole pd
hi all
netpd's major problem is the occurence of many dropouts in certain
situations. one reason is the way how all (at least all i know) network
related objects in pd handle buffer overruns. when the buffer of a
network object is full, the whole pd processing is stopped until the
buffer gets
13 matches
Mail list logo
