Speaking of workarounds what is wrong with clock_delay(0) implementation of disis_ netreceive when it uses existing facilities, has no noticeable overhead, does not drop packets our crash GUI, and is very easy to implement?
Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Director, L2Ork LinuxLaptop Orchestra Assistant Co-Director, CCTAD CHCI, CS, and Art (by courtesy) Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net
Jeppi Jeppi jeppiot@hotmail.com wrote:
That's exactly what happens, some minutes after clients start sending massive OSC stuff to my server, its GUI freezes but PD works ok and I can operate with sliders and number boxes, though I can't see anything.
Frustrating :)
Josep M
From: hans@at.or.at To: matju@artengine.ca Date: Sun, 7 Aug 2011 18:04:37 -0400 CC: pd-list@iem.at; msp@ucsd.edu; zmoelnig@iem.at; martin.peach@sympatico.ca Subject: Re: [PD] netsend/netreceive + GUI bug
On Aug 7, 2011, at 5:19 PM, Mathieu Bouchard wrote:
On Sun, 7 Aug 2011, Miller Puckette wrote:
Here's a guess... if incoming (vanilla) netreceive traffic is swamping Pd, then since Pd prioritizes input from GUI above output back to GUI, the output never gets scheduled. If that were happening, you'd see the windows freeze but still be able to send Pd events from the GUI (hitting buttons in the patch, for instance.)
That sounds like the same symptom as when there is an extra unquoted open-brace.
What would it take to convince you to port your DD escaping code to Pd 0.43? :-D :-D :-D
.hc
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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list