Pd-dev August 2002

pd-dev@lists.iem.at

25 participants
32 discussions

TCL/TK tags
by Thomas Grill 07 Nov '02

07 Nov '02

Hi all, as i am new to TCL/TK, i encounter problems with it all the time. Here is a simple example, the creation of two rectangles (please don't mind the strange specifiers... they are generated from pointer values) ----------------- .x8ff8c8.c create rectangle 69 64 169 164 -tags ec0858GUI -width 2 -fill #00ff00 -outline #00ff00 .x8ff8c8.c create rectangle 89 84 139 134 -tags ec08c8GUI -fill #0000ff that's just ok... the second (slightly smaller one) is displayed on top of the first one. ------------------- Now, i'd like to add an additional tag (ec0728GRP) to each of them, to e.g. move them with a single command .x8ff8c8.c create rectangle 69 64 169 164 -tags ec0858GUI -width 2 -fill #00ff00 -outline #00ff00 .x8ff8c8.c addtag ec0728GRP withtag ec0858GUI .x8ff8c8.c create rectangle 89 84 139 134 -tags ec08c8GUI -fill #0000ff .x8ff8c8.c addtag ec0728GRP withtag ec08c8GUI Now, only the first (larger) one is visible... why? ------------------------------ many thanks, Thomas

11 16

i need some help with this
by J. Scott Hildebrand 03 Sep '02

03 Sep '02

first off i think you can forget about the first email i sent. i've included the .c code and the pd patch. all the convolution stuff is commented out so you can compile and it try this if you want. i almost have a working convolver to put in there, but i first need to make sure i can get 1 mono file go into my external, and have the two convolved signals outputted. right now something screwy is going on and i can't get the stereo signal. thanks for any help! scott -------------------------------------------------------------------- "640K ought to be enough for anybody." -- Bill Gates, 1981 --------------------------------------------------------------------

4 4

convolution code i'm working on
by J. Scott Hildebrand 30 Aug '02

30 Aug '02

the gist of what's going on is in the perform function, and i have some basic pd stuff in the subpatch. what i'm trying to do is bring in 256 samples at once, do my convolution and then send 4 64-size sample blocks to the soundcard. i was told that the outlet~ from the subpatch would convert the sample size and send each 4 blocks to the dac~ object. i keep getting seg faults and i don't know why. it's not much code in the external so if somebody could take a look at what i did i'd appreciate it. thanks! scott -------------------------------------------------------------------- "640K ought to be enough for anybody." -- Bill Gates, 1981 --------------------------------------------------------------------

1 0

Fw: [PD-dev] float & symbol in second inlet
by Thomas Grill 29 Aug '02

29 Aug '02

Hi Mathieu, It's only a sketch, actually fragments from flext code. good luck, Thomas ---------------------------------------- As stated before, you need proxy objects which (actually their method) receive the messages for the non-left inlets. This is a proxy object, just like a normal one > static t_class *px_class; > > struct px_object > { > t_object obj; > int index; // this holds the inlet index > }; This is the class setup which defines the proxy class > px_class = class_new(gensym("flext_base proxy"),NULL,NULL,sizeof(px_object),CLASS_PD|CLASS_NOINLET, A_NULL); > > // bind a method (except any message) to the class > class_addanything(px_class,px_method); // for other inlets px_method looks like that... it's for anything messages. > void px_method(px_object *obj,t_symbol *s,int argc,t_atom *argv) > { > // in obj->index there's the number of the inlet! > } In the object setup function you construct the proxies for all non-left inlets (or for whatever inlet you like) > for(ix = 0; ix < inlets; ++ix) { > // all inlets except the leftmost > inlets[ix] = (px_object *)pd_new(px_class); > inlets[ix]->index = ix; > inlet_new(&x_obj->obj,&inlets[ix]->obj.ob_pd, 0,0); // 0,0 to accept all types of messages > }

1 0

Re: Fw: [PD] namespaces :: out now
by IOhannes zmoelnig 29 Aug '02

29 Aug '02

Thomas Grill wrote: > Hi all, > >>as a by-product, it is very likely that the (discussed) >>namespacing-mechanism ([zexy::abs~] vs. [Gem::abs~]) would have to be >>implemented anyway. > > > Please!! Let's not use :: as the : is reserved in MacOS and then i can't > emulate the namespace features for Max. > Let's use . which is already common. > ok ! i've made some minor changes to the pd-sources (namely m_imp.h, s_loader.c, m_class.c) to allow namespaces when loading libraries. they are attached. the namespace-delimiter is "::" for now, but it can easily be changed via the "#define NAMESPACE" line in m_imp.h i am still not sure of if macOS-X allows the typing of ":" inside pd. if not, we might have to change it to "." or something. i really do not like the idea of "." since it is a filename delimiter. anyhow: explanation with zexy:: the zexy class [list2symbol] is declared (in the zexy-code) with class_new("list2symbol") it has an alternative name [l2s] class_addcreator("l2s") when the patched pd loads zexy, the primary name of the class becomes "zexy::list2symbol" following alternatives (creators) are also created: "list2symbol" "zexy::l2s" "l2s" this shouldn't really break anything, but enable the explicit use of an external inside an object. a side-effect: zexy includes a "tabread4"-class, which is unusable since pd>0.32, because miller has finally imcluded it in pd. with the patched pd, it is possible to load zexy's version with [zexy::tabread4] (which gives a warning about being obsolete) and the native version with just [tabread4]. generally, native pd object-classes are left alone. the helpsymbol (pd-patch) is not affected by the patch. i think it might be a good idea to include it into pd, since it might bring a (final ?) solution to the namespace thread. (of course it might not prove optimal, but which solution would be ? i think this is the cleanest solution from a programmers point of view) anyhow, i have only tested it on linux, it might prove problematic under macOS(?) and windows. is it true, that the native-objects in pd are loaded from the pd.dll under win ? we might (but not necessarily must) get a problem then with "pd::object" mfg.casd.asdf IOhannes diff pd-0.35-0_namespace/src/m_class.c pd-0.35-0/src/m_class.c 18,24d17 < #ifdef NAMESPACE < static char *library_name = 0; < void set_library_name(char *libname){ < library_name=libname; < } < #endif < 151,153d143 < #ifdef NAMESPACE < t_symbol *S=gensym(s->s_name); < #endif 176,187d165 < < #ifdef NAMESPACE < if (library_name){ < char namespacename[MAXPDSTRING]; < namespacename[0]='\0'; < strcat(namespacename, library_name); < strcat(namespacename, NAMESPACE); < strcat(namespacename, s->s_name); < s=gensym(namespacename); < } < #endif < 207,209d184 < #ifdef NAMESPACE < c->c_name = c->c_helpname = S; < #else 211d185 < #endif 232,240d205 < < #ifdef NAMESPACE < // like a class_addcreator < if (library_name){ < class_addmethod(pd_objectmaker, (t_method)newmethod, S, < vec[0], vec[1], vec[2], vec[3], vec[4], vec[5]); < } < #endif < 271d235 < 274,286d237 < < #ifdef NAMESPACE < if (library_name){ < char namespacename[MAXPDSTRING]; < namespacename[0]='\0'; < strcat(namespacename, library_name); < strcat(namespacename, NAMESPACE); < strcat(namespacename, s->s_name); < s=gensym(namespacename); < } < class_addmethod(pd_objectmaker, (t_method)newmethod, s, < vec[0], vec[1], vec[2], vec[3], vec[4], vec[5]); < #endif diff pd-0.35-0_namespace/src/m_imp.h pd-0.35-0/src/m_imp.h 52,57d51 < // IOhannes : added namespace support for libraries < #define NAMESPACE "::" < #ifdef NAMESPACE < void set_library_name(char *libname); < #endif < diff pd-0.35-0_namespace/src/s_loader.c pd-0.35-0/src/s_loader.c 131,133d130 < #ifdef NAMESPACE < set_library_name(classname); < #endif

2 2

RNG
by Krzysztof Czaja 28 Aug '02

28 Aug '02

hi Miller and others, as I have resumed cyclone hacking today (after a long break), I would like to finish coding the 'random' family first. Not being even close to an expert on random number generators, I have borrowed the two used in the 'random' and 'noise~' builtins. Today, just in order to have a quick try, I have used them to produce an input for the 'diehard' set of tests. Now I have three questions: 1. Before I start learning how to correctly interpret all the results -- have been such, or similar, or any kind of tests, performed for the Pd rngs? 2. Seeing that the one used in noise~ (d_osc.c) has suboptimal period length (2^{30}), I wonder if this does matter for the `whiteness' of the output, or does not? (The multiplier a = 435898247 fails the property of b = a - 1 being a multiple of 4 -- this is in Knuth 3.2.1.2, at least in a Polish translation:) 3. Waiting for a return of our mac used for checking things in max/msp, I am not able yet to check what kind of output max/msp rng produces. Any hint? thanks, Krzysztof

3 3

un-subscribe
by Yong-Jin Jeong 28 Aug '02

28 Aug '02

un-subscribe --------------------------------- Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes

1 0

writing wrapper objects in C
by Nicola Bernardini 27 Aug '02

27 Aug '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry if this is a really trivial question that has been answered a number of times: it must have escaped me. Should that be the case, please be patient and give me a pointer to previous threads. With the SOb group in Verona we are building some really cool physical model objects which are soon going to be turned in the pool of pd externals available to everybody to use. These models work really well, but they are really hard to use: they have lots of tweaking parameters which need to be used by (really) expert people. So here's what I am trying to do: while preserving the full fledged object for experimentation, I would like to build some wrapper modules in C which hide a lot of the number-crunching done for control and show to users some less abstract parameters. I would like to use the DSP code 'as-is' (= without rewriting any of it) and keeping the data hiding operated by it (e.g. without unnecessary exporting of data structures and/or functions). I have seen that this task is not trivial. I would like to know if: a) it is at all possible b) anyone has already done something like that so that I can look at the code c) there is some documentation about how to do it someplace Thank you very much in advance nicb +--------------------------------------------------------------------+ |Nicola Bernardini | |E-mail: nicb(a)centrotemporeale.it | |GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910| |Neither MS-Word nor MS-PowerPoint attachments please: | |http://www.fsf.org/philosophy/no-word-attachments.html | +--------------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE9az9SkGzPrk1l2RARAuYoAKDb8UAI38T7iuEbn+vhoCtcxyPeOQCfaMO5 NEe9S0uOBPzeYqNdK7Oub4E= =suhL -----END PGP SIGNATURE-----

2 1

OS X 10.2, m_pd.h, & cabs()?
by tigital 27 Aug '02

27 Aug '02

hiya, ...just upgraded to 10.2 this weekend, and have started back in on GEM...when right off the bat, there's now a definition problem with something in m_pd.h...specifically: #ifdef MACOSX #define cabs() smerdyakov(void) #endif ...this now conflicts with: /* * BSD math library entry points */ extern double cabs ( _complex z ); ...which is included from /usr/include/math.h in the CoreFoundation.framework...is it ok to remove the old define in m_pd.h in favor of this new (hopefully correct) implementation? tanx, jamie

1 0

Pd on OSX - how to compile?
by Olaf Matthes 26 Aug '02

26 Aug '02

Hi, I'm having problems to compile Pd libraries on OS X. Compiling single externals with a modified Linux makefile works (using cc from the project builder package) but I can't figure out how to compile libraries! I've used a modified linux makefile as starting point but still get a lot of unresolved symbols... any help very appreciated! - I'd like to release the next version of maxlib for OS X as well... ;-) Some (already compiled) externals for OS X (freeverb~, multiverb~ and limiter~) can be found at http://www.akustische-kunst.org/puredata/freeverb/ thanks, Olaf

2 1

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