Puredata! (thread)


#374

The patches are really well laid out and commented, so you could always dive in and poke around.

Failing that, you could try this: https://github.com/megalon/pd-AUTOMATONISM-sampler/blob/master/README.md

I’ve had good experience with modifying regular pd patches to work with automationism, you could try that too, find a patch you like and make an automationism module :slight_smile:

If you’ve discovers a bug, drop Johan a mail, I’m sure he would appreciate it.


#375

thanks!
i wrote johan - he said it’s not designed to do accurate pitch tracking.
i also checked out the megalon version but it seems to have the same issue.
poked around in there a little, but it’s quite intimidating to a PD newb.

i’ll look around for other sample players i might be able to wedge in… wondering if there might be an inconsistency with how automatonism handles pitch values vs other patches.


#376

Hmm. Yeah I only ever dance around the edges of patches like this.

I changed the quantizer module to produce “colundi” frequencies, but that was relatively straightforward - if fairly unmusical. Generally I am totally lost when it comes to audio/sample math like the above.


#377

If you’re willing to sit through a ~15 minute video https://www.youtube.com/watch?v=boX0v54SqtU is a pretty easy to digest tutorial, however it doesn’t get super deep into how re-pitching a sample works outside of speeding up and slowing down playback speed.


#378

hi, I was thinking about what you have suggested…Are there any instructions on how to make an Automatonism module from an existing patch? Does this apply to pd-extended patches that exist?


#379

have other people made automationsm extensions before ?? I’ve been considering this as an outlet for modular ideas but torn between pd & max, leaning max


#380

Just open up the automationism patches and start poking around. They are well documented. All you need to do is copy the file and rename it.


#381

Automationism is vanilla only afaik.


#382

hi guys,
Does anyone have experience in both Puredata & SuperCollider?
I’m learning SuperCollider at the moment, but Puredata looks so fun and interesting as well. :stuck_out_tongue_closed_eyes:

I’ve just started learning SuperCollider and I’m completely new to sound synthesis in general, so it’ll probably take me a while to get comfortable enough with one first before I try something new. However, I’m just wondering if there’s any advantages in using both SuperCollider and Puredata? Do they complement each other well in some way? For example, are certain things perhaps easier to do or has a better workflow in one vs. the other? Like creating the sounds in SuperCollider but using Puredata’s graphical interface for controlling the sequencing and structuring of the song?

Note: i’m extremely new to SuperCollider, so perhaps what i’m talking about don’t even make much sense at all lol


#384

I think this is all doable via OSC messaging to communicate between the two platforms?

To answer your first question though, I think Pure Data is easier to learn if you aren’t a programmer by trade. The visual aspect of the platform lends itself more to learning high level musical concepts and then supercollider is great if you’re used to writing code. Just my two cents.


#385

Getting used to writing code has a whole lot of advantages if you have a goal of creating an instrument that you intend to maintain over a number of years.

Graphical patching languages such as Puredata are fantastic for getting simple results quickly. They start to show their constraints as your needs get more complex. But those boundaries are still pretty large. Tom Erbe and Olivier Gillet have mentioned using Puredata as a prototyping environment they like to use for working out ideas, later to be transferred to C/C++ DSP code, when the idea has taken form.


#386

a really important thing to remember to is that what you learn working in puredata, max, or supercollider isn’t knowledge gained in a vacuum. many of the concepts that you apply to one environment/language translate into others even if the api and objects you use are named differently.


#387

prac.pd (765 Bytes)
sampler.pd (6.7 KB)
I’ve linked the patch I’m working on. you’ll see inside the instance of sampler.pd within prac.pd where I’m trying to assign a row of the monome based on the number that comes after sampler (in this case 1 and 2). I’m not sure where /monome/grid/led row 0 1 0 0 can’t be /monome/grid/led row 0 $1 0 0? Many thanks


#388

On my phone at the moment, and admittedly pretty rusty with PD, but are you using $1 to pull a value into the subpatch?


#389

Hello everyone!

I following the installing instructions for Pd extended for Raspberry Pi
and when I run this command:

$ sudo dpkg -i Pd-0.43.3-extended-20121004.deb

I keep getting this error:

Selecting previously unselected package pd-extended.
(Reading database … 57768 files and directories currently installed.)
Unpacking pd-extended (from Pd-0.43.3-extended-20121004.deb) …
dpkg: dependency problems prevent configuration of pd-extended:
pd-extended depends on libfftw3-3; however:
Package libfftw3-3 is not installed.
pd-extended depends on libftgl2 (>= 2.1.3~rc5); however:
Package libftgl2 is not installed.
pd-extended depends on libglu1-mesa | libglu1; however:
Package libglu1-mesa is not installed.
Package libglu1 is not installed.
pd-extended depends on libgsl0ldbl (>= 1.9); however:
Package libgsl0ldbl is not installed.
pd-extended depends on libjack-jackd2-0 (>= 1.9.5~dfsg-14) |
libjack-0.116; however:
Package libjack-jackd2-0 is not installed.
Package libjack-0.116 is not installed.
pd-extended depends on liblua5.1-0; however:
Package liblua5.1-0 is not installed.
pd-extended depends on libmp3lame0; however:
Package libmp3lame0 is not installed.
pd-extended depends on libquicktime2 (>= 2:1.2.2); however:
Package libquicktime2 is not installed.
pd-extended depends on libspeex1 (>= 1.2~beta3-1); however:
Package libspeex1 is not installed.

dpkg: error processing pd-extended (–install):
dependency problems - leaving unconfigured
Processing triggers for man-db …
Processing triggers for menu …
Processing triggers for hicolor-icon-theme …
Processing triggers for desktop-file-utils …
Processing triggers for shared-mime-info …
Errors were encountered while processing:

Has anyone else encountered this problem?
If so, any suggestions?

thanks,
J


#390

I remember having some issues with the dependencies while installing PDl2ork. I had to install them separately. Anyway, the answer for PD-Extended is probably in this post https://lists.puredata.info/pipermail/pd-list/2012-10/098586.html

Sorry but, is there a specific reason why you want to install PD-Extended ? It’s unsupported since 2013 and now PD Vanilla has inherited a lot of its functions, including OSC etc.


#391

the monome website and the grid studies require extended : https://monome.org/docs/grid-studies/pd/


#392

I used a Monome with PureData vanilla, the OSC objects have been integrated now, you don’t even need additional plugins: I posted a patch last year and it’s available here


#393

that’s good to know, thanks! Have to see if my ‘pd grid’ eurorack/aleph port could utilise the built-in OSC now rather than the liblo hack I put in there…


#394

This looks great. I have a couple of objects that arn’t available yet what can I do about these:

09

p.s also, this should perhaps updated on the grid studies page for monome