Pd-dev August 2002

pd-dev@lists.iem.at

25 participants
32 discussions

outlet_* in threaded externals?
by Olaf Matthes 02 Aug '02

02 Aug '02

Hi, since the outlet_*() functions in Pd are not threadsafe, what's the best way to output data in a threaded external? I've used a t_clock that gets called (clock_delay(x->x_outclock, 0)) from the child thread (in oggcast~ for example). But my externals using this method tend to crash after a while (with a segfault in pd.dll under Win2k). Sometime after a few minutes, sometimes it takes several hours. I've now deleted this functions and it seems to work. But I've lost output! Is there any other way to do this? I could use a t_clock that calls itselfe over and over again, lets say every 10 milliseconds and check the variables for changes... Any other ideas? Or any other ideas what the reason for the crashes might be? Olaf PS: a short list of precautions I've (not successfully) tried to get the t_clocks perform all right: - locking the mutex before calling outlet_* - unsetting the t_clock before setting it (in case it's already set and not yet executed by the scheduler) BTW, is there a way to test if a t_clock is already set? - making local copy of variables to output

1 0

Re: [PD-dev] STL & C++ & platforms - a question
by Andrew W. Schmeder 02 Aug '02

02 Aug '02

<quote who="mark"> > I assume that STL is ok and not a pile of garbage that everyone avoids like > the > plague. I am currently using STLPort quite heavily in a large application. It runs on both linux, windows and sgi with good performance. It is threadsafe, in fact fully reentrant, and I'd say its quite indispensible for any serious work in C++. --andy ----------------------- Andrew W. Schmeder andy(a)e-molecule.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev August 2002