Pd-list May 2002

pd-list@lists.iem.at

117 participants
212 discussions

working with the outlet_anything() ;
by joge . 08 May '02

08 May '02

i am working on getting a list out of an outlet for an external . the values i am tring to output are both C floats . my problems is that i cant construct the proper t_atom* argument to get the outlet_anything function to work . i am having diffculty making a t_atom* take on a C float value [or a t_float value] . also i have tried just instantiating a t_atom variable with the float value i want assigned to it . no luck there either . so i was wondering if any one had some good demostration code that gives more of a clue about how to take C floats into a t_atom for use wtih the outlet_anything function . thanks . joge .

2 1

Latency
by Enrique Franco 07 May '02

07 May '02

hi all, I'm pluging an electric guitar to pd (adc~) and I have latency problems (about 300ms). How can I solve this or reduce the latency? Cheers Enrique

2 1

hammerfall in
by Jonathan Impett 07 May '02

07 May '02

Hello, We've got pd running happily under rh7.2, with a Hammerfall card, thanks to Gunter's driver. Output is fine, but input (working under Windows, before you ask), is completely deaf. Any ideas as to what we could try? Thanks, Jonathan -- ------------------ Dr Jonathan Impett School of Music University of East Anglia Norwich NR4 7TJ UK +44 (0)1603 592408 j.impett(a)uea.ac.uk

2 1

"grid"-messages
by oliver 07 May '02

07 May '02

hi, yves is there a way to send messages to the "grid"-object to make the red dot move to specific points in the grid ? i'm thinking about "recording" moves just like "hyperprism" does, and having a glance at the code i discovered some sort of messages, but they only seem to move the red dot relatively. thanks for hints oliver

2 1

new in cyclone: switch, gate, and record~
by Krzysztof Czaja 07 May '02

07 May '02

hi all, switch and gate appear to be max-compatible, mostly, apart from not imposing an upper limit for the number of inlets/outlets (10 in max3, 100 in max4). There is also a record~ clone, which is probably not very useful -- xsample.xrecord~ is generally better. But cyclone.record~ is `multichannel': if there are arrays named 0-t..99-t (100 of them) [record~ t 100] should be able to fill them all (using the size of the smallest one as the maximum range). Likewise [record~ t 1] should record into an array `0-t' (but [record t] into `t'). Obviously, it is a not very pretty workaround, and not msp-compatible... Since record~ is a quick patchwork of my other code, it is expected to crash right away on everybody else's computer. Also, it was not fully tested for compatibility yet (not sure how strictly compatible it should be). I am releasing it to gather your views on how best to work multichannel with Pd arrays. Krzyszt-another-pd-list-spammer-to-get-rid-of

1 0

RE: [PD] size of objects
by mark 07 May '02

07 May '02

Hmm - this won't work for the vst~ 'cos I take ALL the arguments and string them together. The H size of the object is a real pain for things like the Halion VST - you can't see the individual outlets. cheers mark -----Original Message----- From: Orm Finnendahl [mailto:finnendahl@folkwang-hochschule.de] Sent: 07 May 2002 11:36 To: pd-list(a)iem.kug.ac.at Subject: Re: [PD] size of objects Am Dienstag, den 07. Mai 2002 um 12:12:00 Uhr (+0200) schrieb Olaf Matthes: > My workaround was to use somtheing like this: [object any_text_to_stretch_it] - That's what I came up with after my post, too. I use a Sequence of underscores as an additional argument. This looks nice. The only problem could arise, when you don't want to initialize an object with arguments but still want to stretch it. And it wastes space if you store the object. It'd be nice, if a (optional) horizontal stretch factor could be saved with the patcher (as integer number on a grid of characterwidth pixel values). -- Orm

1 0

[Anounce] VST~ - and todays fix is....
by mark 07 May '02

07 May '02

Hi, its being anoying the hell out of me for a while now so I finally changed the search path for the vst~ external so that it searches subdirectories as well (like cubase does). So if all your VST's live under one directory then you can just specify that directory: set VST_PATH=C:\Program Files\Steinberg\VstPlugins; ALL subdirectories will be searched as well. You can of course specify several different locations still and them and all of their subdirectories will be searched for plugins. As usual its available from: http://www.junklight.com Oh - there is a tiny tiny memory leak that I can't imagine anyone will notice - it will be fixed in a later version. cheers mark _________________________________________ junklight - dark experimental electronics http://www.junklight.com

1 0

Re: [PD] [announce] extention patch to "gate" of iemlib1
by Orm Finnendahl 07 May '02

07 May '02

Hi Thomas, Am Montag, den 06. Mai 2002 um 01:27:18 Uhr (+0200) schrieb Thomas Musil: > very nice improvement of gate. > but I would change the "max_10_outlet-restriction". I should have thought about it right away. Thanks for the addition... Another question remains: How can the outlets be accessed in the gui? If there are more than 6 outlets even now the outlet connectors get blurred as the width of the object is too small. Is there a way to stretch the object horizontally? > I didnt have any time to test the pd-max compatibility lib. > maybe there will be a conflict with gate-object? > in next-max of the early 90's, the left input was the contol-input, > the same in max-msp (i think). > so i will test the max-compatibility lib and decide to rename gate-object. > the change is in the attachment. > You are right: The inlets are still the other way around in Max. I left it that way mainly for backwards compatibility reasons in pd and because it makes more sense if the control input is the right one. How shall I go about it? It could be changed using a proxy and we could use two different names. For Max compatibility it would be nice if the name for the pd-style object would change (and also the handling of creation arguments), but that would break backwards compatibility in pd. Yours, Orm P.S.: BTW: What about a Max compatible "switch" object? Does something like that already exist in pd? I need something like that all the time.

3 3

[announce] pecycle
by Frank Barknecht 07 May '02

07 May '02

More and more I do like the idea of an announce list, because then I would not disturb the main mailing list anymore with announcements like this of my useless, but fun _ ____pecycle__ _ PD mini application, that is a sample cutter using bonk~ to search for cut-points and also includes a random sample player somehow like the old randomslicer and then plays back the samples at 120 bpm with that little swing added to make it feel a bit like 2step and then you also can change the loops at runtime to fuse sounds nicely. All this is available at http://footils.radio-worldwi.de and it needs only flext's xgroove and a recent PD with GUI's included. ciao, -- Frank Barknecht _ _______footils__

1 0

nVidia Drivers
by David Sabine 07 May '02

07 May '02

FYI: nVidia released a new driver a few weeks ago which, based on their documention, seems pretty incredible. I'm trying it out right now because I thought it might solve a problem I was having rendering GEMwindow on a secondary display. In any case, it seems worth the upgrade. I went looking for a driver update because I couldn't figure out why my GEMwin wouldn't display all my cool video and eyecandy on my secondary display...then I found a note in the pd-list archive written by Andre S. a few months ago: "and remember, when using 2 cards on windows, only card1 (primary display) uses directX/openGL" ahhhh....NOW it all makes sense. Thanks Andre, Regards, Dave Sabine.

3 3

← Newer
1
...
13
14
15
16
17
18
19
...
22
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 May 2002