Pd-list August 2001

pd-list@lists.iem.at

47 participants
85 discussions

controlling pd with midi footcontrolers
by Nano Rosas 30 Aug '01

30 Aug '01

Hi list Have anybody trie to control pd via midi footcontroles?? Does it woks fine?? Im just looking to a roland fc-200...... would work well?? thankx Nano

1 0

back to memory allocation troubles
by Krzysztof Czaja 30 Aug '01

30 Aug '01

hi again, Miller Puckette wrote: ... > Although Krzysztof has shown me wrong about how Pd is using > memory allocation...! no no, I would not say that! At least not without careful memory profiling. I finally managed to do some testing, but not enough to make any `statements' (what I can only say is that the basic design is beautifully logical and reading Pd code is a pleasure :-) Please treat what follows as loose remarks which might need to be trashed after closer inspection. Also appologies for somewhat technical subject -- if you do not like such talk, then trash this right away... Krzysztof [Now the techie part:] Generally speaking, the main source of memory (de/re)allocation activity are `binbufs', especially the one pointed to by inbinbuf static pointer (s_inter.c) used in parsing messages received from the gui process. Most of the time this constant creating-growing- -shrinking-deleting of inbinbuf contents is not causing much harm, since allocation sequence repeatedly reuse the same location or alternate between two locations. But whenever this sequence is intertwined with object creation etc. there could be some danger of memory fragmentation (how serious it is depends on os). I have no idea how to limit this activity. The binbuf manipulation belongs to the very foundation of Pd and touching it has to be risky. A safer approach would be to define a nonshrinking (or rarely shrinking) binbuf variant to be substituted for the most active binbufs. But then most of the routines in m_binbuf.c would need to have nonshrinking versions. One ad hoc improvement is probably to make a histogram of binbuf sizes generated by binbuf_text() routine (after shrinking) and choose the best (probably smaller then currently used size of 16 atoms?) initial value for nalloc variable. During testing I also found a few memory leaks. One -- the leaking of local binbuf in save routine -- could partly explain the save-close-open-crash mystery reported by Gregorio García and Greg Rippin. This leakage can be quite large, depending on currently saved patch size. It is also very easy to stop -- canvas_saveto() of g_canvas.c is lacking a closing call of + binbuf_free(b); } There is also a very small (18 bytes) leak which happens every time any window is closed. The two binbufs: t_editor::e_connectbuf and t_editor::e_deleted should be freed in editor_free() of g_canvas.c: + binbuf_free(x->e_connectbuf); + binbuf_free(x->e_deleted); freebytes((void *)x, sizeof(*x)); Finally there is a small (40-byte) memory amount leaking every time toplevel patch is closed. It is due to not freeing memory allocated to parent `container' object in canvas_new(): t_subcanvas *y = (t_subcanvas *)pd_new(subcanvas_class); This is small, infrequent, and probably not worth the fuss, although there could be some danger of future bugs lurking here. To stop this leak the canvas destruction in canvas_menuclose(): - pd_free(&x->x_pd); should be changed to parent subcanvas destruction: + pd_free(&x->x_parent->x_ob.ob_pd); but this creates another problem -- subcanvas class is patchable, and pd_free() routine assumes that patchable objects should have a valid binbuf pointer, while this binbuf is never created for toplevel parent subcanvases. There are three options: 1. create the binbuf for toplevel parent subcanvas: + if (!super) y->x_ob.ob_binbuf = binbuf_new(); 2. use a nonpatchable variant of subcanvas class for toplevel parent; 3. add a check for empty binbuf pointer to pd_free(): + if (((t_object *)x)->ob_binbuf) binbuf_free(((t_object *)x)->ob_binbuf);

2 1

Re: [Csnd] [max-msp] Csound instruments translated to Max/MSP
by Larry Troxler 30 Aug '01

30 Aug '01

Hey - what about PD? Or would these patches be easy to port to PD? (I don't now much about the porting issue, since I've never used Max). (adding pd-list to the CC, and apologies in advance if this is off-topic to the "spectro" list, which I don't know anything about but was in the original CC) Regards Larry Troxler PerVillez(a)aol.com wrote: > > I am glad that Rick is trying to push the connection between Csound and > Max/Msp. There are so many things in common that can easily be translated > between both environments. This is a very positive way to go. > > Per Villez > London College of Music and Media > Thames Valley University > Ealing > London > -----Original Message----- > From: Dr. Richard Boulanger [mailto:csound@mediaone.net] > Sent: 27 August 2001 22:13 > To: max-msp(a)cycling74.com > Cc: Spectro; CsoundList > Subject: Re: [max-msp] Csound instruments translated to Max/MSP > > Spectro, > > Four Chapters from The Csound Book translated in > Max/MSP patches by Jahwan Koo are repaired and > reposted to: > > http://csounds.com/jahwan > > I hope that they inspire some of you to make > the Max-MSP/Csound Connection and share your > work with both the Max and the Csound Mailing lists > > Dr. B. > > >They look like they could be interesting, but unfortunately, while the > files > >unzip OK, the text looks (to my untrained eye) like Windows text with lots > >of control characters and Max definitely won't open them as patches. > > > >S. > > -- > ________________________________________________________ > > Dr. Richard Boulanger > Professor - Music Synthesis Department > Berklee College of Music > 1140 Boylston Street - Boston, MA 02215-3693 > Office Phone: (617) 747-2485 Office Fax: (617) 747-2564 > Email: csound(a)mediaone.net OR rboulanger(a)berklee.edu > _________________________________________________________ > > Everything Csound http://csounds.com/ > The Csound Book http://csounds.com/book/ > The Csound Catalog with MP3 Audio http://csounds.com/catalog/ > The Csound Book (2nd Printing) CD-ROMS http://www.csounds.com/cdroms/ > The Csound FrontPage @ MIT Press http://www.csound.org/ > __________________________________________________________ > > -- > To unsubscribe, send email to csound-unsubscribe(a)lists.bath.ac.uk

4 3

Can't get PD/RME9652 even close to working
by Nick Rothwell 30 Aug '01

30 Aug '01

I'm trying and totally failing to get PD working with a Hammerfall 9652. (System: Red Hat 7.1 - kernel 2.4.2. Using the PD 0.33P2 RPM.) The rme96xx module doesn't install cleanly. "make install" seems broken due to a macro fault in the Makefile: install -m 644 rme96xx.o /lib/modules/#include <linux/rhconfig.h>/kernel/drivers/sound /bin/sh: linux/rhconfig.h: No such file or directory I copied it by hand, but got complaints about unresolved symbols when doing a modprobe/insmod. Sometimes it seems to work, sometimes it refuses, sometimes it complains "No such device". The docs claim that this module release is compatible with this kernel version. The rmectrl program doesn't seem to work either: the X11 version shows lots of options but they can't be changed. In fact, they're also wrong: the card is shown at 48KHz when my Roland desk has clearly locked to it at 44.1. The ALSA support in PD doesn't match that which comes with Red Hat 7.1 so I get: warning: Pd compiled for Alsa version 0.9 appears to be incompatible with the installed version of ALSA. Here is what I found in /proc/asound/version: Advanced Linux Sound Architecture Driver Version 0.5.11. Compiled on Aug 27 2001 for kernel 2.4.2-2 with versioned symbols. snd_pcm_open (input): Sound protocol is not compatible snd_pcm_open (output): Sound protocol is not compatible audio I/O stuck... closing audio Tried building PD from source, specifying --enable-rme. So tried "pd -rme" which gives: RME9652: failed to open /dev/rme9652/C0da1 writeonly RME9652: failed to open /dev/rme9652/C0ad1 readonly RME9652: configuring 0, fd=0, sr=44100 , dac=0 RME9652: Could not set sampling rate for device RME9652: Could not set DSP format RME9652: Could not set channels RME9652: configuring 0, fd=0, sr=44100 , dac=1 RME9652: Could not set sampling rate for device RME9652: Could not set DSP format RME9652: Could not set channels RME: ioctl on output device 0 failedRME: ioctl SOUND_PCM_GETOSPACE says 1 buffsize audio I/O stuck... closing audio Where do the /dev entries come from? MAKEDEV doesn't know about them. Does this require a kernel build? (Aside: PD's "make install" is broken if /usr/local/include doesn't exist; it creates it as a plain file and breaks gcc.) Built with ALSA 0.5x, PD gets are far as trying 1 input/1 output and then just gives screeds of file descriptor error messages. Would someone please try to persuade me that I'm not just completely wasting my time? -=- MIME -=- This is a multi-part message in MIME format ------VistoMail999032707511 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Nick Rothwell Cassiel.com Limited nick(a)cassiel.com http://www.cassiel.com _________________________________________________________________________= __ Visit http://www.visto.com. Find out how companies are linking mobile users to the=20 enterprise with Visto. ------VistoMail999032707511 Content-Type: text/plain; name="MOAN" Content-Transfer-Encoding: base64 SSdtIHRyeWluZyBhbmQgdG90YWxseSBmYWlsaW5nIHRvIGdldCBQRCB3b3JraW5nIHdpdGgg YSBIYW1tZXJmYWxsIDk2NTIuCgpTeXN0ZW06IFJlZCBIYXQgNy4xIChrZXJuZWwgMi40LjIp LgoKVGhlIHJtZTk2eHggbW9kdWxlIGRvZXNuJ3QgaW5zdGFsbCBjbGVhbmx5LiAibWFrZSBp bnN0YWxsIiBpcyBicm9rZW4KZHVlIHRvIGEgZmF1bHQgaW4gdGhlIE1ha2VmaWxlOgoKCWlu c3RhbGwgLW0gNjQ0IHJtZTk2eHgubyAvbGliL21vZHVsZXMvI2luY2x1ZGUgPGxpbnV4L3Jo Y29uZmlnLmg+L2tlcm5lbC9kcml2ZXJzL3NvdW5kCgkvYmluL3NoOiBsaW51eC9yaGNvbmZp Zy5oOiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5CgpJIGNvcGllZCBpdCBieSBoYW5kLCBi dXQgZ290IGNvbXBsYWludHMgYWJvdXQgdW5yZXNvbHZlZCBzeW1ib2xzLCBidXQKYWZ0ZXIg YSBmZXcgdHJpZXMgbW9kcHJvYmUvaW5zbW9kIHNlZW1zIHRvIGRvIGl0IGFueXdheSwgYnV0 IEknbSBub3QKY29udmluY2VkIGl0J3Mgd29ya2luZyBhdCBhbGwuCgpUaGUgcm1lY3RybCBw cm9ncmFtIGRvZXNuJ3Qgd29yayBlaXRoZXI6IHRoZSBYMTEgdmVyc2lvbiBzaG93cyBsb3Rz IG9mCm9wdGlvbnMgYnV0IHRoZXkgY2FuJ3QgYmUgY2hhbmdlZC4gSW4gZmFjdCwgdGhleSdy ZSBhbHNvIHdyb25nOiB0aGUKY2FyZCBpcyBzaG93biBhdCA0OEtIeiB3aGVuIG15IFJvbGFu ZCBkZXNrIGhhcyBsb2NrZWQgdG8gaXQgYXQgNDQuMS4KClNvIEkgdHJpZWQgUEQgYW55d2F5 LCB1c2luZyAicGQgLWluY2hhbm5lbHMgOCAtb3V0Y2hhbm5lbHMgOCIgYW5kIGdvdAoKCXRy aWVkIDQsIGdvdCAyCgl0cmllZCAyLCBnb3QgMgoJdHJpZWQgNCwgZ290IDIKCXRyaWVkIDIs IGdvdCAyCgl3YXJuaW5nOiBvdmVyaWRpbmcgYmxvY2tzaXplIHRvIDY0IQoJT1NTOiByZXF1 ZXN0ZWQgYXVkaW8gYnVmZmVyIHNpemUgMjQwNjQgbGltaXRlZCB0byAxNjM4NAoJdHJpZWQg NCwgZ290IDIKCXRyaWVkIDIsIGdvdCAyCglPU1M6IHNhbXBsaW5nIHJhdGU6IHdhbnRlZCA0 NDEwMCwgZ290IDQ0MTAxCglQZDogc3lzdGVtIGNhbGwgdGltZWQgb3V0CgkvZGV2L2RzcCAo cmVhZG9ubHkpOiBJbnRlcnJ1cHRlZCBzeXN0ZW0gY2FsbAoKSSBkb24ndCBrbm93IHdoeSBp dCdzIHVzaW5nIE9TUyAoYW5kIHByZXN1bWFibHkgd2hhdGV2ZXIgU291bmQgQmxhc3Rlcgpj YXJkIEkgaGF2ZSBzaXR0aW5nIGluIHRoZSBtYWNoaW5lKS4gSSBkb24ndCBrbm93IGhvdyB0 byBnZXQgaXQgdG8gdXNlCnRoZSBSTUUgaW5zdGVhZCwgYW5kIGNhbid0IGZpbmQgYW55IGRv Y3VtZW50YXRpb24gYWJvdXQgdGhpcy4KClNvIEkgd2VudCB0aHJvdWdoIGFsbCB0aGUgZWZm b3J0IG9mIGdldHRpbmcgdGhlIEFMU0EgZHJpdmVycyBpbiBwbGFjZQphbmQgdHJpZWQgInBk IC1hbHNhIiAoYW5kICItYWxzYWRldiAwIiwgIjEiLCAiMiIpLCBnZXR0aW5nCgoJd2Fybmlu ZzogUGQgY29tcGlsZWQgZm9yIEFsc2EgdmVyc2lvbiAwLjkgYXBwZWFycyB0byBiZSBpbmNv bXBhdGlibGUgd2l0aAoJdGhlIGluc3RhbGxlZCB2ZXJzaW9uIG9mIEFMU0EuICBIZXJlIGlz IHdoYXQgSSBmb3VuZCBpbiAvcHJvYy9hc291bmQvdmVyc2lvbjoKCUFkdmFuY2VkIExpbnV4 IFNvdW5kIEFyY2hpdGVjdHVyZSBEcml2ZXIgVmVyc2lvbiAwLjUuMTEuCglDb21waWxlZCBv biBBdWcgMjcgMjAwMSBmb3Iga2VybmVsIDIuNC4yLTIgd2l0aCB2ZXJzaW9uZWQgc3ltYm9s cy4KCXNuZF9wY21fb3BlbiAoaW5wdXQpOiBTb3VuZCBwcm90b2NvbCBpcyBub3QgY29tcGF0 aWJsZQoJc25kX3BjbV9vcGVuIChvdXRwdXQpOiBTb3VuZCBwcm90b2NvbCBpcyBub3QgY29t cGF0aWJsZQoJYXVkaW8gSS9PIHN0dWNrLi4uIGNsb3NpbmcgYXVkaW8KCndoaWNoIGlzIGNs ZWFybHkgYWxzbyBicm9rZW4uIEFsc28sIG9uY2UgdGhlIEFMU0EgbW9kdWxlcyBoYXZlIGJl ZW4KbG9hZGVkIGFuZCB1bmxvYWRlZCB0aGUgcm1lOTZ4eCBvbmUgY29tcGxhaW5zIGFib3V0 IG5vdCBmaW5kaW5nIHRoZQpjYXJkIGF0IGFsbC4KClRyaWVkIGJ1aWxkaW5nIFBEIGZyb20g c291cmNlLCBzcGVjaWZ5aW5nIC0tZW5hYmxlLXJtZS4KU28gdHJpZWQgInBkIC1ybWUiLCBn aXZlczoKClJNRTk2NTI6IGZhaWxlZCB0byBvcGVuIC9kZXYvcm1lOTY1Mi9DMGRhMSB3cml0 ZW9ubHkKUk1FOTY1MjogZmFpbGVkIHRvIG9wZW4gL2Rldi9ybWU5NjUyL0MwYWQxIHJlYWRv bmx5ClJNRTk2NTI6IGNvbmZpZ3VyaW5nIDAsIGZkPTAsIHNyPTQ0MTAwCiwgZGFjPTAKUk1F OTY1MjogQ291bGQgbm90IHNldCBzYW1wbGluZyByYXRlIGZvciBkZXZpY2UKUk1FOTY1Mjog Q291bGQgbm90IHNldCBEU1AgZm9ybWF0ClJNRTk2NTI6IENvdWxkIG5vdCBzZXQgY2hhbm5l bHMKUk1FOTY1MjogY29uZmlndXJpbmcgMCwgZmQ9MCwgc3I9NDQxMDAKLCBkYWM9MQpSTUU5 NjUyOiBDb3VsZCBub3Qgc2V0IHNhbXBsaW5nIHJhdGUgZm9yIGRldmljZQpSTUU5NjUyOiBD b3VsZCBub3Qgc2V0IERTUCBmb3JtYXQKUk1FOTY1MjogQ291bGQgbm90IHNldCBjaGFubmVs cwpSTUU6IGlvY3RsIG9uIG91dHB1dCBkZXZpY2UgMCBmYWlsZWRSTUU6IGlvY3RsIFNPVU5E X1BDTV9HRVRPU1BBQ0Ugc2F5cyAxIGJ1ZmZzaXplCmF1ZGlvIEkvTyBzdHVjay4uLiBjbG9z aW5nIGF1ZGlvCgpTbyBjbGVhcmx5IHRoYXQncyBicm9rZW4gYXMgd2VsbC4gV2hlcmUgZG8g dGhlIC9kZXYgZW50cmllcyBjb21lIGZyb20/Ck1BS0VERVYgZG9lc24ndCBrbm93IGFib3V0 IHRoZW0uCgooT2g6ICJtYWtlIGluc3RhbGwiIGlzIGJyb2tlbiBpZiAvdXNyL2xvY2FsL2lu Y2x1ZGUgZG9lc24ndCBleGlzdDsgaXQKc3RvcHMgZ2NjIHdvcmtpbmcuKQoKQnVpbHQgd2l0 aCBBTFNBIDAuNXgsIFBEIGdldHMgYXJlIGZhciBhcyB0cnlpbmcgMSBpbnB1dC8xIG91dHB1 dCBhbmQKdGhlbiBqdXN0IGdpdmVzIHNjcmVlZHMgb2YgZmlsZSBkZXNjcmlwdG9yIGVycm9y IG1lc3NhZ2VzLgoKQ2FuIHNvbWVvbmUgcGxlYXNlIHRyeSB0byBwZXJzdWFkZSBtZSB0aGF0 IEknbSBub3QganVzdCB3YXN0aW5nIG15CnRpbWU/Cg== ------VistoMail999032707511-- -- Nick Rothwell Cassiel.com Limited nick(a)cassiel.com www.cassiel.com systems - composition - installation - performance

3 4

Equalizer
by Álvaro Castro 30 Aug '01

30 Aug '01

Hi all!! Some days ago I posted an e-mail asking for help for building an equalizer. I didn't get many help, that's the reason I write again. If I'm writing to the wrong list, please tell me. I just want to know the basics of an equalizer so I can start working. As you see, I'm a beginner, but I don't know how to start. I choosed to learn PD instead of other sound programs or programming languages because I thought it was very powerful and not very difficult to learn. But when I started working with PD I discovered that one of the most important things for me (the low and high pass filters) don't work very powerfully. I tried filtering a sample and I realized that the filters didn't cut TOTALLY the frequencies they just decreased the amplitude a little bit. Finally, I would like to know what's the best way to work with pure (or almost pure) frecuencies. That's the reason I want to build an equalizer. I would like to add, increase, delete or decrease specific frecuencies. Is that posible with Pure-data?? Thank you very much for your time! I will appreciate any answer, because I don't know what to do now!! _____________________________ :::::::Ãlvaro Castro Castilla _______________________________________________________________ Do You Yahoo!? Yahoo! Messenger: ComunicaciÃ³n instantÃ¡nea gratis con tu gente - http://messenger.yahoo.es

5 4

"-path" and subdirs
by David McCallum 29 Aug '01

29 Aug '01

Is there anyway to make the -path flag include subdirs within the specified path(s)? I categorise my abstractions in separate dirs, and don't want to have to specify a new -path dir every time I've created a new abstraction. If this feature isn't available... then count it in for the Pd wishlist. David McCallum

4 3

inserting dsp blocks (or arrays) into arrays
by G.G Karman 29 Aug '01

29 Aug '01

Hi list, I was wondering if it's possible to write dsp blocks into arrays starting at a specific position instead of having to write a whole string of dsp blocks until the array is full or you stop the recording (like with tabwrite~). I would like to have a behaviour like the tabwrite (without tilde) where you can specify the index at where you want to write the floats. For example, write a 64 sample block in arrayX starting at array index 100. The data from index 100 to 163 would be overwritten and the rest of the data in the array would remain unchanged. I couldnt figure out how to do this with tabwrite~ or tabsend~. thnks for your patience

2 1

Re: [PD] help! my patch breaks pd!
by Greg Rippin 29 Aug '01

29 Aug '01

Hello Miller and Yves and others, After reformatting and rebuilding my system (a formidable task when using Windows, to be sure), my patch loaded without a hitch. PD seems to be running quite a bit faster, too (a much bigger improvement than I expected to see, even with a freshly cleaned system). There must have been something on my system that either ate up tons of memory or conflicted with PD in some way. Virus scanner, perhaps? In any case, thank all of you for all of your help. If this thing still loads properly in a week, I'll be happy with the conclusion that the problem existed somewhere in my system outside of pd. Thanks again, Greg Yves Degoyon wrote: > ok, now that I've upgraded my CPU to a Celeron 800, > I don't have ANY problems loading your patch > neither on Windows ( ME ) nor Linux ( Redhat 7.0 ). > > I did not remove any comment, no. > > Yves. > > Yves Degoyon wrote: > > > The problem i ran into with -rt option > > was certainly because of my poor CPU ( Cyrix 200 ), > > i'm gonna change it right away !! > > > > ( I wanted to do that for a while, so time's up !!! ) > > > > Yves. > > > > Miller Puckette wrote: > > > > > Hi Greg, > > > > > > Well, I downloaded your patch and tried it both on my linux machine and > > > on a nearby w98 machine... no visible problems. The w98 machine did have > > > 256meg on it. On Linux, my process had 24 megs allocated to it; I couldn't > > > figure out how to get that information out of w98. > > > > > > I wasn't able to get the linux machine to fail with -rt, even... > > > > > > cheers > > > Miller -- Greg Rippin, Graduate Assistant Music Technology Program New York University 35 West 4th Street, Suite 777 New York, NY 10012 phone 212-998-5422 fax 212-995-4043 musictechgrad.info(a)nyu.edu www.nyu.edu

1 0

gemshot gallery
by Ulrich Kehrer 28 Aug '01

28 Aug '01

hi list, we've just started a gemshot-platform =a collection of gem-screen-shots the idea is to share gem-output with other users http://www.softpink.com/gem/ feel free to post something rainer ulrich

1 0

dsp_add and perform confusion ...
by CK 28 Aug '01

28 Aug '01

hi, I'm currently trying to write some dsp externals and have some problems with dsp_add and the perform routine of my objects, as soon as I start the dsp pd segfaults, could someone give me a quick intro into dsp_add and explain what the perform routine must implement (or return) which in my case seems to be never entered , dsp_add is the last call before pd crashes ... regards x -- chris(a)lo-res.org Postmodernism is german romanticism with better http://pilot.fm/ special effects. (Jeff Keuss / via ctheory.com)

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list August 2001