Pd-list February 2008

pd-list@lists.iem.at

133 participants
202 discussions

Start a nNew thread

ogg/theora in Gem
by jim 03 Feb '08

03 Feb '08

Is there support for pix_film or pix_movie to play back theora video files? (in Linux). Thanks, Jim

1 0

ostavte mena v pokoe
by Геннадий Романчев 02 Feb '08

02 Feb '08

-- Геннадий Романчев. -- Steel Giants - новая ролевая игра с элементами стратегии. Укроти строптивую планету! http://sg.rambler.ru/

1 0

speed
by marius schebella 02 Feb '08

02 Feb '08

hey frank/list, somehow I managed to get luagl working. (I did a fink install lua51 and lua51-dev and the rest (luagl/opengl) was still there from one of my earlier attempts - I am still trying to reconstruct the installation process... running the patch, that you posted some time ago (with the colored lines) I get an amazing speed advantage for lua. is this a valid performance test? because with lua I can draw 20000 lines at a cpu usage of 80%, the gem part eats up 80% already with 2000 lines (10:1). cheers, marius.

3 5

Alpha release of Controctopus and Semento (MIDI to OSC system)
by Luke Iannini (pd) 02 Feb '08

02 Feb '08

Hallo, Here's the very-alpha release of Controctopus and its required habitat of Semento (my augmented Memento). Controctopus is a learning-MIDI-controller to OSC-discovery automapper. Anything that can be state-saved with Memento can be state-saved and controlled with Semento and Controctopus. By telling Semento the desired range of your parameter, Controctopus will helpfully map your 0-127 controller values to, for example, the 0-20000 values of a filter cutoff parameter*. Controctopus maps (that is, the definitions of which CCs go to which OSC destinations over which MIDI channels) can themselves be saved with Semento. The OSC parameters of your system are auto-discovered and conveniently listed with [midi-tentacle] for very very quick assignment. If you're already using Memento, it's a pretty easy switch to Semento (a find and replace will cover the first half, then a manual going-through to add parameter ranges). SSSAD is also a relative-to-some-things-ly easy switch. Semento includes support for local-sub-state saving (which was part of Memento but never finished), managed by the additional (included) object [polaroid]. [cc-learner] is also a handy standalone midi-cc learn module. Anyway, you'll probably get a better idea by having a look at [controctopus-help]. Adding both included folders to your path is probably the fastest way to get going. New and much more usable releases coming soon! Cheers Luke proyekto.net>sndrft (oh, you'll need at least zexy, list-abs, mrpeach's OSC objects, thomas grill's pool, and bbogart's popup, and maybe a couple more. http://grrrr.org/ext/beta/pd/ for the latest pool, which fixes a bug with very large strings that Controctopus loves to generate. Thanks again Thomas!) *there's a currently-undocumented "constraint" system as well, for when you'd like to map 0-127 to a subrange like 1000-2000 of the full 0-20000.

1 0

[comb~] help please
by Andy Farnell 02 Feb '08

02 Feb '08

Has anyone a helpfile or parameter list for the [comb~] object? No idea what lib it came from I'm afraid. -- Use the source

3 2

ldelay
by marius schebella 02 Feb '08

02 Feb '08

hey frank/list, I tested the lua examples from the cvs and get errors with ldelay and ldelay2. the rest is working fine. error: lua: error in dispatcher: [string "ldelay"]:34: attempt to index field 'clock' (a nil value) do I miss something? marius.

2 1

about fiddle~
by matteo sisti sette 01 Feb '08

01 Feb '08

Hi, Is there a place where one can find detailed documentation about how fiddle~ behaves? For example, a less cryptic explanation of the meaning of the "vibrato" parameters than is found in the help patch? And of how it decides when to output a new "cooked" picth value? I already checked M.Puckette's article cited in the help patch, but it doesn't explain much more (from a behaviour/usage point of view of course). Another question about fiddle. I'd like to be able to distinguish between a signal with a pitch and a signal without a picth. It seems to me that fiddle always outputs its "best guess" no matter how reliable it is. Is there a way to tell it to output a pitch when it thinks it is reliable, and a 0 when it thinks it isn't? I think some pitch tracking algorithms do provide an estimation of the "quality" of the calculated pitch - i guess it is not the case of fiddle, is it? Any suggestion to obtain an estimation of whether the signal has a pitch or not? I thought I may use the third outlet and evaluate whether it outputs a very randomly-varying number; however, with a [noise~] as input, it mostly outputs values between 90 and 110 and some 0 every once in a while..... Thanks in advance m. -- Matteo Sisti Sette matteosistisette(a)gmail.com http://www.matteosistisette.com

6 10

Re: [PD] Font rendering quite CPU expensive in GEM (Jerome Tuncer)
by Timon Botez 01 Feb '08

01 Feb '08

> Font rendering quite CPU expensive in GEM (Jerome Tuncer) Its also down to what typeface you are using. The more complex the curve, the higher the polygon count. Straight edge/polygon faces such as Gridnik (http://www.foundrytypes.co.uk/foundry_gridnik/ gridnik.html) or Citizen (http://www.myfonts.com/fonts/emigre/citizen/ familytree.html) tend to speed things up. These are not gratis if you are not so fussy, but there are plenty of free ones (http://www. 1001freefonts.com/). Simple pixel based fonts also speed up, but they look shit in 3d. Stay away from the serif - unless you do like cyrill suggest - and go for texture mapping. Helps turning off antialiasing too. T.

2 2

Re: [PD] "Structured" Data Flow?
by matteo sisti sette 01 Feb '08

01 Feb '08

I think the original post was not about "good style" but about methods/techniques for "structured" patching, that is (as I interprete it and I may be wrong), how to "write" mantainable, reusable, scalable (etc.) "code" in PD. I do understand that the two things are related, as "good style" improves readability, and readability is essential for mantainability, reusability and scalability (etc.). Let me do a parallelism with "coding" programming languages. Suppose we were talking about a book on object-oriented programming techniques. The subjects discussed in the book would not be such things as when to use upper or lower case in method/class names, nor indentation, nor whether/when it is more elegant to use for vs. while, or switch vs. if... else if... The subjects discussed would be things like: using private variables and get/set methods vs. using public variables; defining and implementing interfaces vs. extending classes; singletons vs. static classes.... etc. Things that are less subject to personal tastes and can be analysed at a more "objective" level - although OF COURSE everything is always questionable. Also, one thing that had been mentioned as an aim was avoiding spaghetti, and this is reasonably objective, although the amount of spaghetti cannot be scientifically measured of course :) Just my 0.2 cents m. IOHannes wrote: -------------------------- Hans-Christoph Steiner wrote: > This all makes me think that we should write a Pd book that covers > things like good form. Perhaps we could make it a decentralized > collaborative effort with strange consensus decisionmaking to mirror > the Pd community :D i guess that Pd might be out of existence when the book will be ready... seriously, i do think that there are fundamentally (and not so fundamentally) different views on "good form" (as all the flaming on [t a] vs. [trigger anything] shows), and i don't think that we would come to a conclusion. so i see 2 approaches to such project: - a collection of several individiual "good style" articles; possibly contradictory (e.g. in the way of the "beautiful code" book that primarily shows how differently "beauty" is perceived) - a single (group of) person(s) that write(s) the book and can decide on their definition of "good style"; since they do all the work, they have all the right to ignore (or whatever) other opinions i personally would favour #1, but i think both approaches are legitimate

1 0

"Structured" dataflow?
by Dudley Brooks 01 Feb '08

01 Feb '08

Can anyone direct me to articles on constructing clear, modular, non-spaghetti patches in pd or other visual dataflow languages? Especially if the articles derive their recommendations from theoretical analysis (as with the investigations that led to structured programming in imperative languages), rather than just rules-of-thumb -- although the latter are useful also. Or is some amount of spaghetti unavoidable in dataflow languages, perhaps because it is inherent in the situation being modeled, rather than being an artifact of the language? Thanks.

7 9

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 February 2008