• ### How do I progress in learning PD?

I'm in High School so I lack calculus knowledge, and not that much math above Trig. In that respect, it's hard for me to read very technical books about sound design...like this for instance.

http://profs.sci.univr.it/~rocchess/htmls/corsi/SoundProcessing/SoundProcessingBook/vsp.pdf

I've gone through most of the guides and tutorials on the Wiki, and am about 3/4 done with Andy Farnell's sound design book which has helped me immensely. So I'm familiar with the elementary stuff.

It's just at this point I'm not sure where I can go for a more in depth understanding of Pd. Is there more reading I should do? Should I just study people's patches, because in all honesty, with some of the abstractions I download from this forum I really only understand the half of the logic in the dataflow.

Thanks

• Posts 6 | Views 3998
• my 2 cents: i think if you have gone through andy's book and the tutorials, you have a great base already. Best advice i could give is to just jump into some serious patches of your own. You'll learn a lot (and be able to teach yourself a lot) by making things and solving problems as you go.

• I am in a similar position to you; I just finished up my first year of college and I'm trying to become more comfortable with PD and audio processing in general. I only have taken a semester of calculus, so the math needed for DSP (linear algebra, differential equations, etc.) is all stuff that I am trying to teach myself (it's not happening very quickly).

The thing that I will say, though, is that the most interesting results you will get in audio are probably from experimentation, though. Knowing the math will help you do some crazy, professional sounding things with patience, but as mod said you are going to learn a lot by just trying new things and exploring patches.

Some really great results can come out of fairly simple processes. For example, I am trying to process guitar arpeggios that I recorded in different ways. So far I have sampled the original recording at normal, half, and double speeds and layered them together, then convolved them with white noise (I used [partconv~] it sort of blurs the different frequencies together and can create a nice drone-type sound).

Finally I played this audio back in a new patch and filtered it with [vcf~] objects tuned to different notes in the original arpeggio and triggered on and off with a simple sequencer. With a little delay and reverb, I ended up building a sound I really like and can probably use as the basis for a track.

I guess my point is that I barely have any idea what I'm doing, but I am enjoying myself and learning new, potentially useful techniques. I think the fact that you are already working with PD and reading pretty advanced material shows that you have passion and are learning quickly.

Sorry if I'm not really helping, but just realize that if even you only understand half of the logic behind this stuff, someone else like me only understands a quarter. Keep reading, asking questions, and experimenting.

• Thanks so much Mod and Ovaltine,

What you're doing with the guitar arpeggios sounds interesting, I'm going to play with [vcf~] a little today.

I will keep experimenting and will post my patches in a few months when I feel more confident.

• Just ask God that works for me and don't stop using of pd and know I know how to use synth edit and other things like that and keep up with math and find a dps class if you can. It's sad to say this but I really whont to move to c sound because its more complex and I am tying to find classes for Dps my self and I missed out while I was in high school how important math was I wish I would have just learned more math. And also think out side of the box will help you to make things that will blow people away.

• @ShawnPD said:

It's sad to say this but I really whont to move to c sound because its more complex

I would say "more complicated." Csound has more sound generators and high-level objects than Pd, so there is more DSP coding already done for you. But I find the text-based coding, lack of real-time interpreter, and no event-based messaging very frustrating.

Posts 6 | Views 3998
Internal error.

Oops! Looks like something went wrong!