Ok, I think I nailed it with lots of help from #tcl on freenode. It not
only seems to fix the intermittent problem, but also seems to be a bit
faster, due to using Tcl properly. I attached the patch I just
committed to pd-extended. The while {[info complete]} loop did a lot of
extra work becaus
On Jan 23, 2012, at 12:54 AM, Miller Puckette wrote:
>
> On Mon, Jan 23, 2012 at 12:45:09AM -0500, Mathieu Bouchard wrote:
>> Le 2012-01-22 à 21:16:00, Miller Puckette a écrit :
>>
>>> There's not much way around this. One possibility (if indeed this
>>> is a serious efficiency issue) would be
On the 64-bit build of Pd-extended 0.43.1 on Mac OS X 10.6/Intel, I get this
error from tclpd whenever I start it:
/Applications/Pd64-0.43.1-extended-20120119.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin:
dlopen(/Applications/Pd64-0.43.1-extended-20120119.app/Contents/Resource
On Jan 23, 2012, at 12:42 PM, Mathieu Bouchard wrote:
> Le 2012-01-22 à 21:54:00, Miller Puckette a écrit :
>> On Mon, Jan 23, 2012 at 12:45:09AM -0500, Mathieu Bouchard wrote:
>>> That's called a newline... not preceded by a backslash. The thing
>>> with fconfigure -buffering line is that it doe
Bugs item #3477797, was opened at 2012-01-23 10:09
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3477797&group_id=55736
Please note that this message will contain a full copy of the co
On Mon, Jan 23, 2012 at 6:41 AM, Mathieu Bouchard wrote:
>>> If you remove the [info complete] bracket from pd_readsocket, there are
>>> these intermittent Tcl stacktraces causes by messages from 'pd' to 'pd-gui'
>>> that get split in the wrong spot.
>
>
> yes, [info complete] is a potential major
Le 2012-01-22 à 21:54:00, Miller Puckette a écrit :
On Mon, Jan 23, 2012 at 12:45:09AM -0500, Mathieu Bouchard wrote:
That's called a newline... not preceded by a backslash. The thing
with fconfigure -buffering line is that it doesn't care about
backslashes, whereas eval does, and if you use bot
On Jan 23, 2012, at 12:45 AM, Mathieu Bouchard wrote:
> Le 2012-01-22 à 21:16:00, Miller Puckette a écrit :
>
>> There's not much way around this. One possibility (if indeed this is a
>> serious efficiency issue) would be for Pd to append a "done" message to each
>> batch up tcl to up-send.
>
On Jan 23, 2012, at 12:41 AM, Mathieu Bouchard wrote:
> Le 2012-01-22 à 21:16:00, Miller Puckette a écrit :
>
>> Quick guess; the socket itself (at the OS level) has a fixed buffer size
>> and if the sending process exceeds it it is suspended until the receiving
>> process eats at least some of
