Pd-list December 2007

pd-list@lists.iem.at

129 participants
239 discussions

honk abstractions
by Johannes Kreidler 14 Dec '07

14 Dec '07

hi list, over the last months, i've been programming a couple of abstractions to enhance faster and comfortable programming in pd. maybe they're useful for anyone else out there. some ideas arent't new, of course, and there might exist similar objects. i called the collection "honk abstractions". download: http://www.kreidler-net.de/honk.zip documentation: http://www.kreidler-net.de/honk.html or http://www.kreidler-net.de/honk.pdf some of them require [at least] pd-extended 0.38 help is inside the patches. it contents: ----GLUE---- linvert - inverts order of atoms of a list listerize-fifo - like "serialize" but for symbols, turns a list of symbols into a list, in order: first in first out listerize-lifo - like "serialize" but for symbols, turns a list of symbols into a list, in order: last in first out mergerize-fifo - turns a stream of symbols into one symbol, in order: first in first out mergerize-lifo - turns a stream of symbols into one symbol, in order: last in first out nbangs - sequence incoming bangs schange - like "change" but for symbols, outputs its input only when it changes ----TIME---- malibu - counts in a certain speed zetro - random metronome ----MATH---- noreprand - exactly like "random", but without repetitions. outputs random numbers in given range. ----TABLES---- ntables - creates a certain number of tables in subpatch ----GUI----- bak - like bang, but size can be given by argument dac - comfortable control of audio output display - displays a number or symbol in variable size hamp - comfortable horizontal potentiometer hr - like horizontal radio, but number of buttons can be given by argument gop - comfortable graph-on-parent control hs - horizontal slider with range as arguments sf - soundfile-player for different formats (wav, mp3, ogg) tok - like toggle, but size can be given by argument vamp - comfortable vertical potentiometer vr - like vertical radio, but number of buttons can be given by argument vs - vertical slider with range as arguments vum - quick-to-build VU-Meter ----MISC---- klist - text-based sequencer with absolute time destinations midi2symbol - MIDI tone numbers to german tone name conversion ----AUDIO GLUE---- compress~ - every amplitude that lies under a certain threshold will be amplified to a reference amplitude limit~ - every amplitude that lies over a certain threshold will be dampened to a reference amplitude pitchshift~ - granular transposition ----AUDIO OSCILLATORS---- sinesum~ - oscillator with various partials waveform~ - waveform oscillator (sine/saw/triangle/square/pulse/random) regards, johannes -- www.kreidler-net.de -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

5 5

Gem, arguments to particle domains.
by PSPunch 14 Dec '07

14 Dec '07

Hi, all. Below is an excerpt from the help file to [part_source] I found in the latest Pd-extended (stable), describing the arguments understood by the object. --- From here --- <domain>: one of "point", "line", "triangle", "plane", "box", "sphere", "cylinder", "cone", "blob", "disc", "rectangle" <arguments>: up to 9 floats, defining the specified domain (like "x y z" for "point", "x1 y1 z1 x2 y2 z2" for "line", "x y z r" for "sphere", ...). The meaning of the arguments depends -of course- on the domain. --- Up to here --- As far as I know, there is a lot left unexplained in this particular help file attached to Pd, especially on how many arguments each domain likes to eat and what the floats represent. Embracingly, I did not know till a few days ago that there is another API which is the mother of Gems's particle handler and that the arguments are explained in its documents. For example, I've just learned this morning that "sphere" takes 4 arguments and their purpose seem to correspond to what is said in the API manual. Am I just going through unnecessary trouble because of me not knowing of a manual pakced with Gem, or shall I be taking notes of my discoveries so that I can perhaps commit to the help file? -- David Shimamoto

1 1

Inlet Proxy object example
by Mike McGonagle 13 Dec '07

13 Dec '07

Hello everyone, Over the weekend, I was "given" a huge lesson in both PD and humility... Anyway, what this is is an example of how to create an inlet proxy object to handle arbitrary list input on a cold right inlet. It is something that was extracted from the 'x_list.c' source, and generalized to be just a raw object. The example is not a useful object, but illustrates how the C source framework is designed. I posted the files to ( http://puredata.info/Members/mjmogo ). Feedback is welcome and expected... Mike -- Peace may sound simple—one beautiful word— but it requires everything we have, every quality, every strength, every dream, every high ideal. —Yehudi Menuhin (1916–1999), musician

5 5

Another simple gemmouse query
by Rebecca Schatz 13 Dec '07

13 Dec '07

Hi All, thanks for everyone's responses last time, they were really helpful. I'm just wondering if anyone can explain (as though I'm a five year old) how I would use gemmouse to control the speed at which a sound sample is playing (presuming its looping)?? Thanks in advance! Rebecca.

2 1

coll object
by Donal Carey 13 Dec '07

13 Dec '07

Hi all Apoligies if this is not the correct place for asking these sorts of questions. Can the 'coll' object read items from a text file? What I want to do is have several messages stored in a textfile, load them into coll and then output them one at a time. Is this possible, everytime I try and load a text file into coll I get the error ... "coll: bad atom error (miXed): coll: error reading text file 'C:/Documents and Settings/Donal/Desktop/pd project/clips/masterText.txt" Thanks and regards Donal

5 5

SQL Object Model was: [psql] object hand-holding
by Mike McGonagle 12 Dec '07

12 Dec '07

(As the other thread seemed to diverge greatly in topic, I figured this might be a time to branch off and discuss what we are trying to implement) So, can we take a step back and figure out exactly what we are doing? It seems that even within the thread itself, we have changed the Object Model a LOT... From what I have read, this is what I now understand the model to be... [mySQL-Connection id-symbol <connection info>] <-- a PD object representing connection [SQL-Query id-symbol <sql statement>] <-- an SQL query object The first object, the Connection, takes a symbol that identifies itself to PD, and optionally the connection info. The second takes a symbol linking it to a Connection object (this linking can also be changed to point to another connection using a control message), and an optional SQL statement for Placeholder Inlet creation. This method will "bind" those inlets into the SQL statement. If there is no SQL statement, no binding is allowed using that object, and all SQL come to a cold inlet, using PD messages (variable stuff can be put into the statement via PD's $ mechanism). The connection object responds to the following open/connect - to open a file (in an embedded database) or connects to server close/disconnect - close the file or breaks the connection As the connection object can represent any database, its named <dbname-connect>. A MySQL database would be [MySQL-connect ...], sqlite would be [sqlite-connect ...], etc. A connection object provides a single outlet to provide status about the connection (similar to a [netsend] object). There is a single inlet used to control the connection object. The query object responds to the following buffer - to change the size of the SQL input buffer results - to change the size of the results buffer bang - submits the initial query, and outputs a result set for each bang clear - clears the SQL buffer addsemi - appends a semicolon to the SQL buffer addcomma - appends a comma to the SQL buffer adddollar - appends a dollar sign to the buffer (do we need this?) If the query is created with an embedded statement, any placeholders will generate an inlet. No cold inlet for SQL will be created. If the query does not have an embedded statement, it will provide an arbitrary inlet that accepts SQL to process. The query object has 3 outlets, the first outputs a list for each result set (on each subsequent bang, very much like a [textfile] object), the second will outlet a float representing the ROWID of the last insert statement, and the third outlet indicates the status of the query, with a bang indicating the end of the result sets, a symbol or a list is a status message from the database. ************************* Does this sound about right? I would like to have a clear outline before I start coding anything. Thanks, Mike

2 2

VOSIM with a tiny bug
by Frank Barknecht 12 Dec '07

12 Dec '07

Hi, attached is some stretched phasor~ fun for your classic synthesis methods class: an implementation of the VOSIM algorithm for speech synthesis etc. as invented by Kaegi/Templaars. My implementation is almost correct, but has a slight bug, which you can see if you set M and T to the values indicated by message boxes, set N to 2 or 3 and and set b to be larger than 0. Then the step function which scales the amplitude of the sin^2 pulses starts irregularily. I'm quite sure this comes from the way I use [samphold~] inside [vosim~] as it sometimes samples the wrong value. However I don't yet know of a proper workaround. (One workaround would be to just omit the samhold-step, but the result would not be VOSIM according to the textbooks.) So anybody with a good idea? Ciao -- Frank Barknecht _ ______footils.org__

11 14

Pd 39.3 ext mapping library
by James Hearon 12 Dec '07

12 Dec '07

Hi, Having a tough time of it with Pd 39.3 extended from sourceforge on windows vista and mapping library. help/browser/5.reference/mapping/ several files crashing: ex. breakpoint-help.pd curve-help.pd etc. Seems to be just the patches with the colored slider boxes in them. They crash as soon as I try to move the slider. example: Problem signature: Problem Event Name: APPCRASH Application Name: pd.exe Application Version: 0.0.0.0 Application Timestamp: 47148d16 Fault Module Name: ntdll.dll Fault Module Version: 6.0.6000.16386 Fault Module Timestamp: 4549bdc9 Exception Code: c0000005 Exception Offset: 00061884 OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033 Additional Information 1: e8c9 Additional Information 2: f1bc4d2e93e0a544f8d5f094db4ab1f4 Additional Information 3: 7904 Additional Information 4: 8995bb1fd0f10ecf9be0b075535aed7f Cool library, and works fine on Mac. _________________________________________________________________ The best games are on Xbox 360. Click here for a special offer on an Xbox 360 Console. http://www.xbox.com/en-US/hardware/wheretobuy/

2 1

Re: [PD] [psql] object hand-holding
by Hans-Christoph Steiner 12 Dec '07

12 Dec '07

I cc'ed the list since I think this is valuable discussion: On Dec 10, 2007, at 7:39 PM, Mike McGonagle wrote: > > > On 12/10/07, Hans-Christoph Steiner <hans(a)eds.org> wrote: > It is useful to represent the pieces in Pd space, so you can > understand what's going on. That's one reason why I advocate > having the core object represent the connection to the database > rather than a query. Otherwise, it's starts to become more like > Max/MSP's mega-objects (coll, zl, etc) that are really like mini- > applications than programming. > > > At the same time, while you seem to want to abstract the query from > the database connection objects, SQL is not SQL to all databases. > One thing I have noticed is that in SQLite, you would create an > autoincremented ID/index field using: > > CREATE TABLE MINE ( > id integer primary key autoincrement not null > ); > > While in MySQL (from what I remember) you do this: > > CREATE TABLE MINE ( > id INT auto_increment not null > PRIMARY KEY(id) > ); > > (Please not the difference in spelling "autoincrement".) So, while > I can understand you desire to abstract these concepts out, I > wonder if it would be possible. Also, I don't think that it should > be the task of the external to "normalize" what SQL gets entered. > One of the original design goals was to NOT have to actually parse > the SQL, relying on the user to know what they are doing, and just > feed the SQL into the database. > > I can see that from this thread alone, that this is not going to be > possible. Plus, if we are going to implement the idea of > "placeholders", that Yes, we will need to be parsing some SQL. > > > There still can be query objects, they would just be designed to > feed to the core database objects. These query objects would then > be usable if we maintain the same interface. > > > And yet, the differences between databases might actually make this > difficult at best. That is why I still think there will end up > being a different object for 'sqlite', postgres, mysql, etc... I agree with you. Ideally, there would be a common SQL, but there is not. We could try to make a common SQL, I think things like Perl:DBI do that (I could be wrong), but I think that would be a version 2 kind of thing. We can leave that till later, or perhaps never. I still think we can make a common query object that just handles the placeholders, and otherwise just passed the SQL statements thru. .hc > > Mike > > > .hc > > > > ---------------------------------------------------------------------- > ------ > > > > News is what people want to keep hidden and everything else is > publicity. - Bill Moyers > > > > > > -- > Peace may sound simple—one beautiful word— but it requires > everything we have, every quality, every strength, every dream, > every high ideal. > —Yehudi Menuhin (1916–1999), musician ------------------------------------------------------------------------ ---- I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler

1 0

Refactoring a PD patch
by Mike McGonagle 12 Dec '07

12 Dec '07

Hey, I was contemplating the idea of what it would take to write a program that reads a PD abstration and produces something that "TRIES" to clean up the appearance of the patch. From the discussion of segmented lines, and from seeing some other people's patches, it made me wonder if anyone else has tried to write a program that will attempt to clean up the tangled mess that some patches come to... I have some ideas about how to do this, but wanted to first check out to see if others have already attempted this sort of thing, and if they found it to be fruitful. Thanks, Mike -- Peace may sound simple—one beautiful word— but it requires everything we have, every quality, every strength, every dream, every high ideal. —Yehudi Menuhin (1916–1999), musician

2 2

← Newer
1
...
12
13
14
15
16
17
18
...
24
Older →

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 December 2007