Pd-list January 2007

pd-list@lists.iem.at

139 participants
222 discussions

polypoly's second inlet
by Phil Stone 19 Jan '07

19 Jan '07

Hello listers (and Frank B. in particular), I've been converting a PD synth I've been using from an [nqpoly] voice manager to Frank's new [polypoly]. Mostly, it's working well for me, but one thing about it seems less than optimal, and I wonder if it is intentional. The first inlet sends its {note, amp} pairs to one and only one instance of the polypoly'd abstraction. The second inlet broadcasts its message to *all* instances (see attached patch for simple illustration). I can see reasons for wanting it to work that way, so if it was intentional, so be it. It would work much better for my selfish purposes -- I like to send a big list of parameters to the voice that's about to be fired off -- if it only connected to the same instance that the first inlet connects to. (As an aside, it occurs to me that [polypoly] would be much more generalizable if the first inlet could send a list *of any size* to the poly-allocated abstraction, instead of a hardwired {note, amp} pair. Then I would be happy to see the second inlet be "global", because I wouldn't need it anymore. I'd just send a big list, including note and amplitude as well as all my other parameters, to the first inlet. The drawback is that this would require a custom version of [poly], since [poly] assumes {note, amp} pairs.) I get lost in the auto-creates and auto-connects in [polypoly]'s innards, so I can't figure out how to play with this. I'm awfully grateful for this powerful object, though. If I can get it working, my synthesizer patch will work great for process music (which is all nqpoly can really do), *and* live playing. Thanks, Frank. Phil Stone UC Davis #N canvas 264 37 332 200 10; #X obj 38 56 pack 60 120; #X obj 63 5 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1 ; #X obj 63 26 t b b; #X obj 38 88 polypoly 12 1 polytestvox; #X obj 123 56 pack 1 2 3 4 5 6 7; #X connect 0 0 3 0; #X connect 1 0 2 0; #X connect 2 0 0 0; #X connect 2 1 4 0; #X connect 4 0 3 1; #N canvas 314 159 340 257 10; #X obj 59 49 inlet; #X obj 164 49 inlet; #X obj 164 89 print 2ndInlet; #X obj 59 89 print 1stInlet; #X obj 62 161 outlet~; #X obj 142 161 outlet~; #X connect 0 0 3 0; #X connect 1 0 2 0;

2 1

Re: [PD] [cyclone] Pd-0.39.2-extended-test7 released
by Steffen 18 Jan '07

18 Jan '07

On 18/01/2007, at 16.28, Miguel Cardoso wrote: > ok! > thats the object i cannot create. i thought this was solved on > test7, or renamed to something else in this version > > so for now I can only use the objects in the library. i cannot load > max files yet, right? I think so, yes, since i think it highly unlikely that it should have been renamed. Also the Makefile doesn't mention that it is. I could of cause miss something as i'm not an expert. You could (try to) build it your self, but that i surely can't help you with as i just failed trying to do so.

1 0

Patchmatrix Execution Order Issues
by Luke Iannini (pd) 18 Jan '07

18 Jan '07

OK, this is about the 16th hour (2 nights now) I've spent attempting to debug this, so I'm capitulating and asking for help : ). There was a discussion of a signal patchmatrix a while back. I'm attempting to make a message-based version of the same thing. Attached is a version completely stripped of all but the essentials, to demonstrate the issue hopefully as clearly as possible: I'm using IEMMatrix to store the patchbay configuration. In the example, there are 3 inputs and 3 outputs. The "patmatel" object is simply to set matrix elements to 1 or 0. When an input comes in a particular inlet, say inlet 1, column 1 is retrieved from the matrix. The contents of column 1 enable or disable the 3 outlets. E.g., if inlet 1 is meant to go to outlets Y and Z (but not X), column 1 would contain 0 1 1. Next, inlet 1's actual value is sent to the 3 spigots, which either allow it through or block it. This will of course all be clearer if you are viewing the patch. Assuming you are now: in column 1 of the patchmatrix on the upper left, enable outputs 2(Y) and 3(Z) (such that the matrix looks like this: 0 0 0 1 0 0 1 0 0 ). Now, in the top right, send "10101" to input A (this is an arbitrary value for demonstration). Over on the right, you'll see that it reaches output Z but not output Y. This (as it is easier to determine now - my actual configuration is a 9inx17out matrix that connects most of my library of patches, hence the 16 hours of debugging) is because: output Z feeds back to input C, thus retrieving column 3 of the patchmatrix, which is set to send to no outlets at all (0 0 0). Apparently, by the time "10101" reaches output Y's spigot, it has already closed. If anyone is still following... how can I make this work? I guess I need to delay the inputs from arriving until the outlets are finished transmitting, but I'm a bit lost as to how to do that elegantly. P.S. An [mtx_spigot] object would be great for this type of thing : ). I have it on my list to attempt an abstraction of such an object. [mtx_mul~] works just like I'd want the message-based version to.

2 3

Glitches during audio test on Mac OS X (newbie)
by Joseph Wilk 18 Jan '07

18 Jan '07

Greetings everyone, Thank you for your consideration in my problems getting going with Pd. I am currently running Pd version 0.40-2 for Mac OS X 10.4 (PPC & Intel). On this computer, I have Mac OS X 10.4.8 running on a 1.67 GHz PowerPC G4 with 1 GB of RAM. I am using my built-in audio drivers. When I try to run the audio test or any other audio-based patch, I get terrible glitches. Usually, they are spaced evenly in a 1-2-3-4 1-2-3-4 rhythm (only occasionally breaking that rhythm before settling back). No matter what I set the delay to, I get these glitches in the sound. No other audio program (like Ableton Live) is having any issues with the on-board sound card I am not running any other programs at the time of Pd. I can reproduce this issue faithfully through several releases back, even with special "extended" compiles. Does anyone have any suggestions for how I can continue troubleshooting or correct this problem? Thank you kindly! Best wishes, Joseph Wilk

4 4

[PD-announce] multiblob for GridFlow
by Mathieu Bouchard 17 Jan '07

17 Jan '07

Here's multiblob for GridFlow. http://gridflow.ca/gallery/multiblob.png It's actually my own implementation: it's not been ported from anywhere else. Each cross is centered on the centroid (1st order moment) of its corresponding region ("blob"), and the size of the cross is the square root of the area of the region. I will make another version which will use rotated rectangular crosses. The two lines of each cross will represent the two radiuses of the standard deviation of the region, and the angle will represent the angle of the standard deviation. I will use [#moment_polar], an abstraction based on [lti.Jacobi]. _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada _______________________________________________ PD-announce mailing list PD-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

1 0

Vista
by sam iravanian 17 Jan '07

17 Jan '07

Hi, I'm new to PD and currently use a windows based laptop for patching. Vista being around the corner I had a question: Is Vista compatible to PD? I've heard some nasty things about Vista, specially when you're dealing with the inboard security checks. This is a small article explaining the issue: http://news.com.com/FAQ+Vistas+strong,+new+antipiracy+protections/2100-1025… Do you think is safe to upgrade my system, has anyone done it? Thanks, Sam

5 4

Re: [PD] [lanbox] and [tcpclient]
by IOhannes m zmoelnig 17 Jan '07

17 Jan '07

Oli44 wrote: > IOhannes m zmoelnig <zmoelnig(a)iem.at> wrote .. >> Oli44 wrote: >>> Hi list, >>> >>> but I cant find a working [tcpclient] for Linux (Debian sid) nor for >> OSX in order to communicate with the Lanbox. Any idea or link? >> hi. >> where have you looked for [tcpclient]? >> try http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net/ hi. please always reply to the mailing list, unless it is something very private... >> > hallo, > > > i've downloaded it, since i'm a very average Linux user, I havent managed to compile! well, i keep saying for years that the build system is too complicated. but whenever i do changes, i should have asked before ;-) anyhow, the most simple way to get tcpclient currently is to download the entire pd-extended binary, and extract whatever you need. if you feel like building yourself, then the "simplest" way would be to check out the entire pd-cvs, then go to externals/mrpeach and do a "make". the more sophisticated version would be to check out /externals/mrpeach/ and /externals/Makefile and /packages and do a "make" the best version would be to provide a simple makefile for people who don't want to spend days checking out or downloading binaries. but this is likely to break everything. ok, rant-mode should be turned off now... mfg.asdr IOhannes > > > trying currently to get help from a debian package maintainer via Jabber, hope we can fix it and maybe turn it into a .deb? > > > ++ > O > > > > >> mfg.asdr >> IOhannes >

2 3

Re: Re: [PD] [lanbox] and [tcpclient]
by martin.peach＠sympatico.ca 17 Jan '07

17 Jan '07

> > IOhannes m zmoelnig <zmoelnig(a)iem.at> wrote .. > >> Oli44 wrote: > the more sophisticated version would be to check out /externals/mrpeach/ > and /externals/Makefile and /packages and do a "make" > > the best version would be to provide a simple makefile for people who > don't want to spend days checking out or downloading binaries. > but this is likely to break everything. > Even simpler: I usually use a shell script instead of a makefile if there is only one or two source files to build. Somthing like this works on linux, but probably could be extended: #! /bin/bash echo "Hello" gcc -O2 -DPD -shared -o midifile.pd_linux -I/usr/local/include/ midifile.c -L /usr/local/lib echo "done" Martin

1 0

Re: [PD] [lanbox] and [tcpclient]
by Oli44 17 Jan '07

17 Jan '07

IOhannes m zmoelnig <zmoelnig(a)iem.at> wrote .. > > hi. > please always reply to the mailing list, unless it is something very > private... hello world ;-) > >>> I cant find a working [tcpclient] for Linux (Debian sid) nor for > >> OSX in order to communicate with the Lanbox. Any idea or link? > >> hi. > >> where have you looked for [tcpclient]? > >> try http://pure-data.cvs.sourceforge.net/pure-data/externals/mrpeach/net/ > > > i've downloaded it, since i'm a very average Linux user, I havent managed > to compile! Now, I managed compiling it using the most bandwidth consuming method, that is, I checked out the whole CVS, then the "Make" command in the ~/puredata/cvs/externals/mrpeach/ directory ran without a glitch. Now i've got a working [tcpclient] therefore a working [lanbox] : fiat lux! I'll work the osX version tomorrow. Thx a lot, O.

1 0

[lanbox] and [tcpclient]
by Oli44 17 Jan '07

17 Jan '07

Hi list, I'm working on a multimedia/dance performance, until now we've kept the audio & video (Pd+Gem) running separately from the light. We've recently purchased a lanbox, it would be great to avoid using Midi on that project, that's wy we chose the LCX model.I've tried to have a connection setup following that thread http://elists.resynthesize.com/pd-list/2006/09/1636340/ but I cant find a working [tcpclient] for Linux (Debian sid) nor for OSX in order to communicate with the Lanbox. Any idea or link? Olivier

2 1

← Newer
1
...
9
10
11
12
13
14
15
...
23
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 January 2007