Pd-dev June 2004

pd-dev@lists.iem.at

20 participants
17 discussions

Re: [PD] please test: threaded soundfiler & garray locks
by Tim Blechmann 17 Jun '04

17 Jun '04

thanks for your report... > it seemed to work. but when I run PD with my .pdrc it get a > segmentation fault immediately. When I remove the .pdrc from the > equation i get the PD main window, but all the menu's are empty and > nothing works. > Did I do something wrong here? are there options in the makefile that there is definitely something really strange going on ... i'd like to see the output of pd -verbose ... i'll also add some debug messages ... seems to be related to the helper thread initialization ... i'll let you know, when i know more... cheers ... (btw moving to the pd-dev list) -- Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac

1 0

dsp_add(...)
by Tim Blechmann 13 Jun '04

13 Jun '04

hi all, will i get proper results from sys_getblksize() after adding an object to the dsp tree: foo_dsp(...) { dsp_add(...); int block = sys_getblksize() /* do something with block */ } and will this return the blocksize of a subpatch or the blocksize devided by the overlap? cheers... -- Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac

1 0

Re: PD-cvs digest, Vol 1 #269 - 7 msgs
by Thomas Grill 08 Jun '04

08 Jun '04

> Today's Topics: > > 7. externals/grill/pool makefile.pd-mingw,NONE,1.1 config-pd-mingw.txt,NONE,1.1 (carmen rocco) Hi Carmen, hi all, i'm happy when someone is contributing to my stuff but the problem is that i have a cvs server that is mirrored to the SF cvs every night, so changes to the externals/grill tree of the SF cvs are either overwritten or not recognized by me. I therefore recommend that you send me the patches/contributions so that i add them to the project structure. many thanks, Thomas

1 0

displaying a waveform like an audio editor
by Cournapeau David 07 Jun '04

07 Jun '04

Hi there, I am quite new in PD, and I am going through the different docs I can find about PD. I am trying to make a small app, with would display a waveform of an audio file, like an audio editor. I would like to be able to display a big wavefile, being able to go back and further, with zooming possibilities. The graph array seems a bit limited for that. Should I use something like Gem ? Or write a PD extension ? I am still no clear about the way to extend the GUI capabilities of PD. Thnaks, David

2 1

Audio Regression and Unit Testing
by abez 04 Jun '04

04 Jun '04

I apologize if this is the inappropriate forum for this discussion Reading through the archives I noticed there were attempts at regression testing Pd but I couldn't find any concrete results of these tests. I suspect the scope of the problem might have been beyond the scope of Pd itself thus it wasn't worth the effort. I do not as I am an outsider to this project. What I'd like to know is what functionality would one want to test and provide regression tests for in Pd? What has been done in the past? What difficulties have arisen in unit testing or regression testing. If one wanted to unit test what type of assertions would one need, and if one wanted to regression test what kind of functionality would be required from the test framework? When you're developing your applications and instruments do you ever wish you didn't have to listen to it over and over again to verify nothing serious has changed? Do you ever wish you could just test a filter or generator to see if it was producing the right sound rather than listening to it. Do you ever wish you could apply test first methodologies to your filters, signals generators and instruments? Such a tool would be great but how would you want to use it? Would you want to integrate it into your testing framework or would you prefer it provides it's own test framework. What would you want the test to cover. Would you want it to cover IPC and latency issues? What common functionality would you want from it. What kind of assertions would you like to see. There are difficulties in testing audio, you need complex functions to figure out: how loud it is; whether or not certain frequencies are too loud; is it producing a proper distribution of elements,. What paradigms would like it to use. Would you prefer a procedural interface or an OO interface. What languages would want the test suite to directly support? It's an interesting problem and if it sufficiently explored and implemented it could definitely help the audio programming community. If you are interesting in providing input regarding the requirements of such a system please read the attached Invitation Letter as I am executing a study on what the open source audio community would like to see in the way of audio testing. abram ========= Invitation Letter ============= Dear Potential Participant: Hello, my name is Abram Hindle; I am currently a masters student in the faculty of Computer Science at the University Of Victoria. I am investigating the requirements of a Audio Testing Suite. as part of a directed studies course supervised by Dr. George Tzanetakis . The purpose of this research is to extract the testing requirements of audio programmers. By gathering the requirements from potential users of an audio test suite we can build an effective audio test suite. This will help enable audio programmers regression test their code as well as employ test first methodology to audio development. Participants should be experienced in computer instrument design or audio programming. Participants will be asked to fill out a questionnaire. Data from the questionnaire will be recorded for future use but the results anonymized to protect the participants identity. Participation in this study is completely voluntary and the participant may withdraw at any time without any consequences. Data will be collected only with your consent. Participants will participate semi-anonymously. Your participation is very important as it can improve the state of software engineering in the audio domain. You may contact the PI, Abram Hindle by email abez(a)uvic.ca or by telephone 250 721 9066 for further information about the research. Thank you for your assistance. You may participapate by visiting http://abez.ca/~abez/audiotest/ Sincerely, Abram Hindle Graduate Student of the Faculty of Engineering Department of Computer Science University of Victoria Ph: (250)-721-9066 -- abez ------------------------------------------ http://www.abez.ca/ Abram Hindle (abez(a)abez.ca) ------------------------------------------ abez

1 0

Slight change to OSCroute and one last OSC license issue
by Frank Barknecht 04 Jun '04

04 Jun '04

Hallo, for your information: The OSCroute object in CVS has a slight change in its behaviour compared to earlier versions. This change actually shouldn't affect anyone (besides me) because it removed a feature that was undocumented anyways. (Earlier versions of OSCroute allowed wildcards in the test-pattern like /s* which was matching /sequence as well.) The current version does not match things like /seq on /s* anymore. The only wildcard allowed in the test-pattern is the string "/*" which splits off the first path component. Note that all kinds of wildcards in the incoming message are of course still allowed and evaluated. The second issue is regarding the licence of some files. These pd-specific source files still have the non-profit clause in it, which makes them non-free: OSCroute.c dumpOSC.c htmsocket.c sendOSC.c I'd like to remove that clause and replace it with the upstream (Matt's) free license. So please if you contributed to one of these files, speak up now. I'd also like to suggest to make the Sourceforge OSC for Pd the canonical OSC for Pd. There already are several imporant changes done only there, I believe. If someone (Bryan?) isn't a Sourceforge developer yet but wants to directly update Pd-OSC just ask on pd-dev or me directly to get a dev account for Pd-CVS. That's it for now. Ciao -- Frank Barknecht _ ______footils.org__

2 1

Flite config file
by Ian Smith-Heisters 01 Jun '04

01 Jun '04

Hi Bryan, list, I'm not sure what the status of the flite external is these days, but I just compiled 0.01 on debian and have a suggestion for the makefile. On my debian system the flite headers (flite.h) are in /usr/include/flite where apt-get put them. Invoking configure like this: "./configure --with-flite-dir=/usr/include/flite" still yeilds a "flite.h not found" error because of lines 2636 and 2637 in the configure, which are "IFLAGS="$IFLAGS -I${FLITE_DIR}/include" LFLAGS="$LFLAGS -L${FLITE_DIR}/lib"" or something like that (I only have an altered version on hand so that's from memory, but the line numbers are certainly correct). To install on my system, and I suspect most apt-get managed systems, I needed to remove the inlcude and lib subdirectories from these statements. I just thought there might be some way to make this easier or more straightforward would is needed, as I only happened across these lines by dumb luck. Thanks, Ian Smith-Heisters

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 June 2004