Hallo,
Phil Stone hat gesagt: // Phil Stone wrote:
> From what I can tell, this happens when DSP is already running, and the
> wave tables, which are wrapped in Frank's loadbang-firing-[singleton],
> are not initialized (or at least not finished initializing) before the
> [tabread~] oscillators
Thomas Grill wrote:
> bash build.sh pd clean
> bash build.sh pd
> sudo bash build.sh pd install
well it seems it should be:
bash build.sh pd gcc
# edit buildsys/config-lnx-pd-gcc.txt
bash build.sh pd gcc
# edit config.txt
bash build.sh pd gcc
sudo bash build.sh pd gcc install
Logical when you kn
Am 08.09.2007 um 17:05 schrieb Atte André Jensen:
> Thomas Grill wrote:
>
>> bash build.sh pd clean
>> bash build.sh pd
>> sudo bash build.sh pd install
>
> well it seems it should be:
> bash build.sh pd gcc
> # edit buildsys/config-lnx-pd-gcc.txt
> bash build.sh pd gcc
> # edit config.txt
> bash
Hi Frank,
The [r $1-something] receives are exposed to the outside by design, so
that all parameters can be controlled programatically and not just by
the sliders and controls of the UI. They also permit multiple
synthesizers to be separately addressable. Finally, $1 serves as the
prefix for
federico wrote:
>>hola,
>>
>>
>
>hey!
>
>
>
>>>externs I'm going to commit:
>>>grid: a gui 2d grid editor made esecially for editing/sequencing lists
>>>of floats, it should be a nice frontend for iemmatrix (I'm planning to
>>>add iemmatrix-specific messages, so that is more straightforward)
>>>
Sorry to be so rude as to reply to my own message, but I have thought
more about Frank's original message since my first reply.
I am beginning to see that it might not be a good idea to expose all
those receives, even if the likelihood of name-collision is small. If
all patches were designed t
Hi. I acquired a p5 glove, and the Pd interface I found for it relies on
OSCx. I've been trying to build it, having added -fPIC to it, but I get
this:
make[1]: Entering directory `/home/chuckk/Glove/pd/externals/OSCx/src'
cc -Wl,-export_dynamic -shared -o sendOSC.pd_linux sendOSC.o htmsocket.o
OS
Hi pdlers
i was curious to check out that synth, but i get this error.
the screenshot i from ubuntu, but it was the same on OS X.
Bild 3.png
Description: application/applefile
<>
i am sure you know the trick, thanks luigi___
PD-list@iem.at mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Sep 08, 2007 at 06:48:52PM -0400, Chuckk Hubbard wrote:
> Hi. I acquired a p5 glove, and the Pd interface I found for it relies on
> OSCx. I've been trying to build it, having added -fPIC to it, but I get
> this:
> make[1]: Entering directory
Merhaba Batuhan,
To my knowledge, there are ways to do that in GEM.
- Loading images to see them in a window comes in pretty easy. Just use
the [pix_image] and/or [pix_multiimage} to actually load the stuff (I
personnaly use the tiff format for uncompressed images). Then use
[pix_texture] to a
Hi Luigi,
This is a happening in [polypoly] where it replicates the
[polyWaveVoice~] objects. I can't figure out what the problem is just
from a screen shot, though. Did you get all the dependencies? It looks
like you have at least some of the polypoly objects, but something like
this is of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My MIDI controller is an M-Audio Axiom 49. It has 8 "rotary controllers" which
can output continuous controller messages. This may be my way out of the 4-bit
hole, and allow me to control parameters in PD with finer than 128 discreet
steps.
Are th
Jerome Tuncer wrote:
> Merhaba Batuhan,
>
> To my knowledge, there are ways to do that in GEM.
>
> - Loading images to see them in a window comes in pretty easy. Just use
> the [pix_image] and/or [pix_multiimage} to actually load the stuff (I
> personnaly use the tiff format for uncompressed imag
13 matches
Mail list logo
