Pd-list November 2004

pd-list@lists.iem.at

150 participants
258 discussions

using root_window (x11)
by patrick 01 Dec '04

01 Dec '04

hi, in gem / pdp / gridflow: would it be possible for me to output visual in the root_window of x11? (like most xscreensaver with argument -root) patrick

5 4

Gem and two firewire inputs
by shree 01 Dec '04

01 Dec '04

is it possible to use 2 firewire cameras with GEM? i am on a Mac OS X Patrick Pagano, B.S., M.F.A. candidate Research And Development Assistant Digital Worlds Institute University Of Florida (352) 294-2082

2 1

Error Loading Gem.pd_linux
by Lee Colleton 01 Dec '04

01 Dec '04

Hello, I'm using pd and gem as packaged with the Ubuntu Linux distribution Pd version 0.37.cvs1-4 Gem version 0.888 When I try to load pd with gem I get an error. This prevents me from creating the [gemwin] object, which makes me sad. Can anyone offer me advice? $ pd -lib /usr/lib/pd/extra/Gem.pd_linux couldn't open MIDI input device 0 couldn't open MIDI output device 0 opened 0 MIDI input device(s) and 0 MIDI output device(s). /usr/lib/pd/extra/Gem.pd_linux: can't load library -- Lee Colleton <lee(a)colleton.net>

3 2

Gem - Texturing? UV Mapping? etc.
by Christian Klotz 01 Dec '04

01 Dec '04

Hi list, playing around with Gem and some obj models a few questions came to my mind. - when I started a bit texturing obj models, I asked myself how to get even a bit more complex 3d objects (think of a car or something like that) textured with gem. Did anyone already try something like this or know how to deal with it? I would really like to work with gem doing things like that ;) is there some uvmap support under development? I am asking because even a cylinder exported to obj had a completely different texture behaviour compared to a gem cylinder and I didnt get both of them textured the same way (???) - another thing. I read a post of 2002 about adding multitexturing and bump mapping - which where added to the prior to do list. have they ever been implemented? I think its quite important for people doing graphic stuff with pd - and as it seems to me by reading the mailinglists every day, there is more and more interest in using pd together with gem. I'll appreciate any suggestions. regards christian --- Christian Klotz Kunsthochschule Kassel / School of Arts Kassel ::digitalpool

2 2

Re: [PD-announce] space~ - object for spatialization of audio sources
by oliver oli 30 Nov '04

30 Nov '04

Hi Shahrokh, nice external, seems to run stable, but my machine is a little bit slow to handle more than 2 quad space~ objects. as i don't know much about spetialization in general, what should i do with the reverb outlet? the x=0,y=0 is in the center of the room? seems that the sound jumps from inside to outside on -1 * length/2 (stereo setup). funny effect. did you think about writing a ladspa or dssi plugin? i like the idea that the speakers are windows to an outer room. i just shortly tried it, but it seems the image is much more stable than with panning if you walk through the room. now i have to get a faster machine to do something serious with it :-) oli Shahrokh Yadegari wrote: > Hi All, > > I have just put up an alpha version of space~, which is a real-time > implementation of the cmusic's space unit generator with many > improvements. I have recently added a considerable amount of code for > room management. So use it carefully. > > You can download compiled versions for Linux and Mac OS X (Darwin) at: > http://www.crca.ucsd.edu/~yadegari/space.html > > I have not compiled it for windows yet. > > enjoy, > Shahrokh. > -------------- > > Notes for version 0.4alpha > -------------------------- > Lots of code has been added to this version recently for room > management and treatment of the reflections when the source is > outside of the virtual space. Generally you should not allow the > source to go outside of the virtual source. While I have tried to > accomodate for the source to be outside of the virtual space and > thus have the sense of a source being far apart, you should not > depend on this effect to stay the same. As usual reports of bugs > and suggestions are welcome. Send me mail at (sdy(a)ucsd.edu). > > > space~ - A module for spatialization of audio sources > ----------------------------------------------------- > Based on an algorithm and a partial implementaion by F. Richard Moore > in "cmusic" as part of the Computer Audio Research Laboratory (CARL) > package. > > Real-time implementation, port to Pd, and new improvements by Shahrokh > Yadegari. > > With the help of Ted Apel , Anthony Burr , Harry Castle, and Miller > Puckette. > > Space~ is a real-time implementation of a general model for > spatialization of audio sources. The central conceit of the algorithm > is that of a room within a room. The inner room is the space > delimited by the speakers which contains the listeners. The model > simulates the behavior of the sound source within a user-defined > virtual outer room, as heard from the inner room. The speakers > act as "windows" throug which sound from the outer room passes. > > > NOTE: In this implementation both the inner and outer rooms are > assumed to be squares. Also keep in mind that the simulation of a > source in the listening room is not as good as when the source is > in the virtual space and currently one hears sudden changes to the > level of audio on opposite speakers when a sources passes through > an inner wall. > > > The syntax to space~ is a follows: > ---------------------------------- > space~ [card] [stereo|quad] [inner-room-size outer-room-size] > > - card - indicates that the cardiod pattern information is supplied > for the audio source > - stereo|quad - specifies the diffusion mode (quad is the default) > - inner room size - is the size of the inner room in meters > - outer room size - is the size of the outer room in meters > > (When inner room size and outer room size are not specified, sizes > 4 and 50 meters are assumed.) > > All inlets and outlets of space~ are of type signal > > Outputs for stereo > ------------------ > 1 - Front Left > 2 - Front Right > 3 - to be connected to Reverb > > Outputs for quad > ---------------- > 1 - Front Left > 2 - Front Right > 3 - Rear Left > 4 - Rear Right > 5 - to be connected to Reverb > > Inputs > -------- > 1 - audio source > 2 - X coordinate in meters > 3 - Y coordinate in meters > 4 - amplitude (not in db) > > > Additional inputs when "card" is specified > ------------------------------------------ > 5 - Theta (in radians) - source radiation direction > 6 - Back - radiation level in the opposite direction (0 <= Back <= 1) > > > Methods > ------- > stop - stop spatial processing (for saving cpu cycles > start - start processing > theta - source radiation direction (when "card" is not specified) > back - radiation level in the opposite direction of theta (when "card" > is not specified) > direct - affecting the power laws for calculating the direct ray > attenuation > reflect - affecting the power laws for calculating the reflected ray > attenuation > TH (also "th" or "threshold") - threshold value for ray diffraction > simulation > CF (also "cf" or "crsossfade") - crossfade form for ray diffraction > simulation > > > _______________________________________________ > PD-announce mailing list > PD-announce(a)iem.at > http://iem.at/cgi-bin/mailman/listinfo/pd-announce >

1 0

non-leaky symbols
by ix 30 Nov '04

30 Nov '04

im wondering how others go about avoiding memory leaks caused by excessive symbol generation. recently, ive found zexy-l2s to be the 'savior' to a lot of problems, such as: .pool loses symbols embedded in lists after load/save .@list in toxy does not work with variable length lists .other objects work on symbols or float but not variable-length lists.. (or no way to toggle distribution to inlets) .qlist wont work with absolute timestamps..but oh wait, l2s & pipe does the trick! .want to insert 2, or maybe 3 or 4 elements, into a list after the first 2 elements .want to insert an entire list into another message, so use l2s and $1, etc... everything works out but the catch is chew 1 mb RAM a minute or more, just from all the symbols being generated. im not sure i really need all them to stick around in some hash table after theyre handed off to another object or split up anyways..

7 8

Re: [PD-announce] new [hid] release + simple mapping objects
by B. Bogart 30 Nov '04

30 Nov '04

Hey Hans, What "smoothing" algo are you thinking of? I've been very very happy with the low-pass method that Thomas suggested some time ago. Gives you a great feeling of enertia. I'm looking forward to a proper HCI tablet driver for OSX or dirrect wacom support in HID. I think this is a great project. I will find the auto-scaling stuff very useful in the near future I think... Thanks for your efforts. Ben > > This version of [hid] fixes the crasher bug when you try to open a > non-existant device. > > I am currently working on making a suite of objects for mapping > controller data. I am making a number of objects like [mouse], > [joystick], etc. which all output range (0 to 1 for axes). Then the > mapping objects all take data of this range and output 0 to 1 so that > the data can be easily mapped and scaled to parameters. Included are > log, square root, and cube root; and exponent, square, and cube; as > well as a basic smoothing object. > > The overarching idea for these objects is to make clearly defined, > high-level objects for beginners and for rapid prototyping when using > external controllers in Pd patches. At least point I am looking for > ideas, comments, etc. about other possible mapping functions > > http://puredata.org/Members/hans/downloads > > .hc > > > > ________________________________________________________________________ > ____ > > "[W]e have invented the technology to eliminate scarcity, but we are > deliberately throwing it > away to benefit those who profit from scarcity." > -John Gilmore

5 7

sfplay and file length
by Matthew Shanley 30 Nov '04

30 Nov '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'm starting to use zexy's sfplay, and it seems great. I'm interested in using the "goto <byte>" feature, but I'm having a hard time figuring out how to determine the length of the sound file so I know the range I can jump around within. Any suggestions? While I'm at it, what's the right inlet in sfplay for? Thanks matt - -- Matthew Shanley little secrets records and stuff http://littlesecretsrecords.com/ E-mail: matthewshanley(a)littlesecretsrecords.com GnuPG Public Key ID: 0x4DA4915C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBq/8kIrtD7k2kkVwRArb8AJ0be8bYGGVmrqsdFoSbLlXgyDgHIwCgl8dt ro+vTVBItYrAzQiECYRn5cY= =3+Zg -----END PGP SIGNATURE-----

2 1

strange behavior upon loading dsp abstraction....
by chunlee 30 Nov '04

30 Nov '04

hi there: there has been this strange behavior on loading up my dsp abstractions that is bugging me for the last few days and i finally worked out a way to describe and reproduce it and i wonder if anyone can help to explain. to reproduce it: 1. make a example abstraction like this and call it say, test.pd: [osc~ 440] | | [*~ 0.5] |\ | \ [dac~] #N canvas 0 0 450 300 10; #X obj 150 93 osc~ 440; #X obj 177 159 *~ 0.5; #X obj 205 206 dac~; #X connect 0 0 1 0; #X connect 1 0 2 0; #X connect 1 0 2 1; 2. make sure the compute audio is on before loading [test] 3. open a new patch and load [test] as an abstraction. at this point, shouldn't i be able to hear the [osc~]? but i don't! however, if i load another [test] in the same patch, i can then hear [osc~]. if i load up [test] as a patch, it works fine. so, somehow, when [test] is loaded for the first time, nothing happens. but in the second time, it functions as expected. can anyone help to explain? i got the feeling that its something really basic about Pd that i don't know yet. many thanks CHUN

2 1

Fullscreen and real video
by Luisa Lamas 30 Nov '04

30 Nov '04

4 6

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