Pd-list August 2007

pd-list@lists.iem.at

117 participants
152 discussions

up-down-counter.pd
by Steffen Leve Poulsen 04 Dec '07

04 Dec '07

To Kyle mvh Steffen Leve Poulsen #N canvas 254 194 637 394 12; #X obj 240 147 f; #X obj 275 146 + 1; #X obj 240 176 mod; #X obj 240 241 -; #X obj 240 268 abs; #X floatatom 240 309 5 0 0 0 - - -; #X obj 240 35 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X floatatom 403 76 5 0 0 0 - - -; #X obj 403 156 * 2; #X obj 240 63 metro 234; #X obj 306 305 print; #X obj 502 35 16; #X obj 502 9 loadbang; #X connect 0 0 2 0; #X connect 1 0 0 1; #X connect 2 0 1 0; #X connect 2 0 3 0; #X connect 3 0 4 0; #X connect 4 0 5 0; #X connect 4 0 10 0; #X connect 6 0 9 0; #X connect 7 0 3 1; #X connect 7 0 8 0; #X connect 7 0 0 1; #X connect 8 0 2 1; #X connect 9 0 0 0; #X connect 11 0 7 0; #X connect 12 0 11 0; #X connect 12 0 9 0;

7 8

hide menubar on Mac OS X/Pd-extended.app
by Hans-Christoph Steiner 02 Nov '07

02 Nov '07

If you've ever wanted to have Gem be full screen on the primary screen, I have found a way. It's called "LSUIPresentationMode". Basically, using Property List Editor.app, open Pd-extended.app/Contents/Info.plist. Add a "New Child" to "Root". Call that node "LSUIPresentationMode", change the data type to "Number" and set the data to be "4". Then when you launch Pd-extended.app, the Menubar and Dock will auto-hide themselves. Here are some other modes: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/… .hc zen \ \ \[D[D[D[D

5 5

Granular Cross-fader
by Kyle Klipowicz 25 Oct '07

25 Oct '07

Hello listers~ There's been a void of conversation on the list, so I thought I'd pitch my latest idea for a Pd tool: a granular cross-fader. I'm in the pre-planning phase right now, and would love to get some ideas/suggestions for how to implement this. Basically what I'd like to have is similar to a DJ cross fader, but using granular methods to stochastically mix two (or more) signals using various common granular ideas (pitch shifting, time stretching, grain size, randomness parameters, overlap, etc.). This would make transitions much more exciting from a DJ end as well as when mixing two or more signals on a DAW. What are your immediate thoughts/reactions to this? ~Kyle -- http://theradioproject.com http://perhapsidid.blogspot.com (((())))(()()((((((((()())))()(((((((())()()())()))) (())))))(()))))))))))))(((((((((((()()))))))))((()))) ))(((((((((((())))())))))))))))))))__________ _____())))))(((((((((((((()))))))))))_______ ((((((())))))))))))((((((((000)))oOOOOOO

6 8

[PD-announce] DesireData 2007.08.04
by Mathieu Bouchard 16 Oct '07

16 Oct '07

http://artengine.ca/desiredata/download/desiredata-2007.08.04.tar.gz ChangeLog: ------------------8<--------cut-here--------8<------------------ DesireData 2007.08.04 : * Unicode locales * fixed type mismatch bug recently introduced in [unpack]... * fixed lost console posts at startup * turned most fprintf() into post() or error() * added Chinese locale from Chun Lee * added Polish locale from Michal Seta * added object creation history * added arrow keys and mouse clicks to KeyboardDialog * added click drag and copy * added background grid * added snap to grid * added new font selector (in client prefs) _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada _______________________________________________ PD-announce mailing list PD-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

2 2

midi controller advice?
by Conor J Curran 11 Oct '07

11 Oct '07

Hi all, I was looking around recently for a foot controlled midi controller. The more expression pedals the better. I was under the impression that the expression pedals have a range of 0-127 (is this correct?). I was hoping to map as many expression pedals to a controller number each in order for each pedal to control some aspect of an external. The only midi controller I could find which had a decent number of pedals was the fatar mp117. The review in sound on sound didn't really leave me a good impression. Also this model seems to be more about playing an octave of a piano with feet as opposed to arbitrary assignment and control. Anybody have any suggestions? Best regards, Conor

2 2

Re: [PD] midi controller advice?
by adam armfield 08 Oct '07

08 Oct '07

I think the DIY route is a good one, depending on your abilities, you can get a fairly pre-made board from doepfer & attach (screw on) jack sockets for up to 16 pedals (or more with expansion), or you might look at an even more DIY solution if you are good at soldering & building stuff one thing to look out for is the impedance... some generic pedals have an impedance matching circuit which would get round the problem of the board wanting 10k pots and the pedal having 50k ones (for instance) all the best adam ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.ht…

5 4

GEM to SVG/EPS/PDF
by timon 23 Sep '07

23 Sep '07

Hi, I came across this, GL2PS: an OpenGL to PostScript printing library. If it could be incorporated it would make a great addition to the Gem. Dont know anything on how to build PD objects though (sorry, sounds a bit arrogant). Anyway, if its of interest. http://www.geuz.org/gl2ps/ Timon

4 3

pd-ext 39-2 rc4 (deb package) crashing with gop editing
by Kevin McCoy 16 Sep '07

16 Sep '07

Hi Hans, I think that this version is crashing when I edit a patch that uses gops, and then close the window - it asks if I want to discard the changes, and I click yes, then it closes out pd entirely. This only appears to happen when the main patch involves gops - not when it's just regular objects I think. I don't think I noticed this with rc3 - did you ever answer my last question (sorry if it didn't get through to you) which was whether this debian packaged rc4 included code updates over rc3 or whether it is rc4 by virtue of being a deb package alone? The package is totally sweet, it integrates so much more nicely in the system, but I am restarting pd a lot these days because of this little bug ;) I am working almost exclusively with gops now. Is there a log or a way I can maybe give you some more useful info aside from my personal testimony? Can anyone else verify this? Kevin -- ++++ http://pocketkm.blogspot.com

4 6

pd-convention papers
by Alexandre Castonguay 10 Sep '07

10 Sep '07

Hi all, The papers for the convention are online at : http://artengine.ca/~catalogue-pd/ Cheers, Alexandre

4 5

Re: [PD] puredocumentation
by benjah＠free.fr 05 Sep '07

05 Sep '07

Hi all, Jean noel montagne from artsensitif, french NGO, submit the idea of pdpedia a while ago which reach the discussion we had during Pd conf about documentation http://pdpedia.dreamhosters.com/index.php?title=Main_Page maybe this can help... on another side, I would like to ask for funds to the french ministry of culture in 2008 to improve in a collaborative way Pd documentation (in french) and high level patches (in Pd), considering the great job that has already been done by Pdmtl team, hans, frank, jérome...and many others, in order to allow as many artists as possible to get into Pd.... not sure at all about the answer + many thanks to Montreal Pd conv team for this great meeting/event Benjamin - labomedia.net Alexandre Quessy a écrit : > Hi Marius, Tom and all ! > > 2007/8/29, marius schebella <marius.schebella(a)gmail.com>: >> thanks, >> atm I don't know how that works. otoh, can we use the index.txt? that >> seems to contain most of the information. >> that's a great library! >> marius. > > In Pd Montreal Abstractions, it is a patch that parses help file > patches (using pd objects and externals) to look for tags (such as > "Author: ") at the beginning of comments. > > :) > > More people are going to contribute to the PdMtl Abstractions in the > next few months. The format has changed a bit : the dot (".") now > separates the categories and names of abstractions, instead of the > file system path itself. > > a > > > > > > >> Thomas O Fredericks wrote: >>> We implemented something similar forthe help files in PDMTL >>> abstractions. See the pdmtl.inde.maker.pd in >>> https://devel.goto10.org/listing.php?repname=pdmtl&path=%2Ftrunk%2Ftools%2F… >>> <https://devel.goto10.org/listing.php?repname=pdmtl&path=%2Ftrunk%2Ftools%2F…> >>> >>> Tom >>> >>> On 8/29/07, *marius schebella* <marius.schebella(a)gmail.com >>> <mailto:marius.schebella@gmail.com>> wrote: >>> >>> hi, >>> this is the start for the puredocumentation wiki. >>> for all who didn't follow the discussions during the pdconv, here is the >>> latest: >>> some people agreed on building a media wiki for all documentation >>> beyond >>> the pd help patches. some time ago there was the puredatabase, but that >>> is quite dead now. >>> so the idea is, to reanimate something similar, but with the possibility >>> for everyone to commit to it. maybe not everyone but if 5-10% of users >>> help contributing, then I think the project will be successful. >>> one of the reasons why this should be done, is that very often pd users >>> look for a certain feature or object, but don't know the name exactly >>> and need a good search engine. >>> so... the puredocumentation (in planning state) will cover externals and >>> "stable" abstractions. (abstractions that are maintained kind of like >>> externals) >>> additionally to the "wiki for objects" there will be the section for >>> the >>> tutorials, manuals and faq, and hopefully you will be able to type in >>> your search string after "How do I: " and get the right objects, >>> examples and tutorials. >>> My estimation is, that there are more than 3000 objects atm. so for the >>> beginning the tricky part is to build all the basic object pages from >>> the existing documentation (mainly help patches). >>> here is, what I think should be the content of every object page: >>> *objectname* the string name (for example "plus" for "+") of the >>> object/external >>> *opt other name* = abbreviation, +,.. >>> *helpfilename* (can be different than object name), >>> *description* = short description >>> *libraryinfo* purepd,GEM,cyclone... + author + licence >>> *arguments* >>> *inlets/outlets* >>> *examples* what this object is for... that's where you can be creative! >>> *see also* / similar objects >>> *tags* like audio/dsp, math, MIDI, something like a categorization. >>> I want to use python to extract as much information as possible from >>> the >>> help-patches into one big textfile (csv style) from which we can create >>> the wikipages. I hope to get the developers involved in correcting the >>> cvs-textfile before the basic pages are created). this has to be done >>> per library, and I am still trying to figure out, how to do this in >>> detail. for example some help patches have some description in the top >>> letmost corner. so a python script should be able to find that >>> information and put it into the "description" field. >>> there will be an irc session on sep 11 with all the people working on >>> the project. so maybe if you want to join or have suggestions on how to >>> get this done, feel free to respond. >>> addtitional documentation work that probably will also be done: >>> improving help patches by switching to a nice pddp format. >>> creating online video tutorials, or recordings of workshops. >>> one last point: If you know of a school/university or teaching center >>> that would like to get involved (for example by putting pd classes on >>> their schedule or paying people do some documentation work) that would >>> also help the project to be successful... >>> so far. thanks for reading through that all! >>> marius. >>> >>> # this file will look slightly different for every library >>> # write everything into a database like format... (NOT YET!!!) >>> # OBJECTNAME | OPT OTHER NAME | HELPFILE-NAME | DESCRIPTION | TAGS | >>> LIBRARYINFO | ARGUMENTS | INLETS/OUTLETS | EXAMPLES | SEE ALSO >>> # objectname is the string name (for example "plus" for "+") >>> # opt other name = abbreviation, +, >>> # helpfilename (can be different than object name), >>> # description = short description >>> # libraryinfo: purepd or GEM + author + licence >>> # arguments >>> # inlets/outlets >>> # examples : what this object is for... >>> # see also/similar objects >>> # junk >>> # >>> # use X coordinate to sort comments??? >>> >>> import re >>> import os >>> >>> print 'searching all files for comments' >>> >>> searchPattern = "#X text \d+ \d+ " # search for comments >>> replacePattern = searchPattern # what can be deleted of the comments >>> deleteNLPattern = r'\r' # delete cr >>> fileExtension = ".*[.]pd$" # files to look for >>> separator = "|" # separate colomns >>> separator2 = "___" # separate junk >>> fileTo = "test_to.txt" >>> >>> p = re.compile(searchPattern) >>> rep = re.compile(replacePattern) >>> nldel = re.compile(deleteNLPattern) >>> fe = re.compile (fileExtension) >>> >>> f2 = open(fileTo, "w") >>> >>> for fileName in os.listdir("."): >>> m = fe.search(fileName) >>> if m: # only if is it a pd-file >>> f = open(fileName, "r") >>> first = 1 # suppose the first entry is >>> the description >>> for line in f: >>> m = p.search(line) # search in line for pd-comment >>> pattern >>> if m: >>> line = nldel.sub("",line) >>> if first == 1: # help needed! how >>> to sort other than by appearance? write to array? >>> f2.write("\n" + fileName + separator) #need \n >>> for every file but the first. >>> newText = rep.sub("",line) # this should >>> delete the trailing pattern >>> f2.write(newText[:-1]) # this writes >>> without closing nl >>> f2.write (separator) >>> first = 0 >>> else: >>> newText = rep.sub("",line) >>> f2.write(newText[:-1]) >>> f2.write(separator2) >>> f.close() >>> f2.close() >>> >>> #done... >>> _______________________________________________ >>> PD-list(a)iem.at <mailto:PD-list@iem.at> mailing list >>> UNSUBSCRIBE and account-management -> >>> http://lists.puredata.info/listinfo/pd-list >>> >>> >>> >>> >>> -- >>> thomas ouellet fredericks, tof(a)danslchamp.org >>> <mailto:tof@danslchamp.org>, montreal, canada >> >> _______________________________________________ >> PD-list(a)iem.at mailing list >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list >> > >

3 2

Jump to page:

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 2007