best thing i've done in 3 years...it's nearly 30 minutes long though//// get yourself a beer or spliff

38meg download.

but, as always...100% pure data for the construction, 100% "stolen" loops for the audio//// 100% realtime

http://www.m-pi.com/this-is-serious-mum.mp3

hi brett, that track is still up on my site. for some reason the link comes out as a .pd file not an .mp3

http://www.m-pi.com/this-is-serious-mum.mp3

just cut and paste that and it will work.

also heaps of stuff here: http://www.m-pi.com/remixes

>It's weird that many ppl seem to be using pd but that the output~ page in the forum still has threads in it from 2004 in the top page!! <

it took me a few months of solid patching (a few hours every day) to get a workable setup for actually making tracks. it's certainly no small undertaking.

>I'm pretty new to pd and just working my way through tutorials at the moment, but do you have any tips with regard to actually going about customising your own setup?<

you are on the right track going through the tutorials. the way i did it was first to build stuff to cut up and effect samples, and then secondly make a system to control those processes live. mine was all based on the [key] command, and i just triggered everythign from my laptop's qwerty keyboard. this was nice when i was travellign as it meant i didn't need to cart any gear around. also good for playing live cos i could pick my computer up and jam on the dancefloor. there are a few options though, especially triggering stuff with sensors and such. but i'm sticking with the bare bones keyboard approach cos it works for me well enough.

> like whether to keep lots of separate instruments or try to keep everything under one roof...<

i try to keep my stuff in one patch as much as possible. a couple of reasons for that, but the main one for me was that i kept modifying abstractions and then other patches that relied on those abstractions would stop working. generally much easier just to have one or two or a few patches to do everythign you need. even if you incorporate everything you make into one patch it doesn't get too big. usually well under 1 meg.

>I think I will tend to mainly use samplers and control structures for controlling my external Midi gear, but in a live setup, not sure how to integrate it into Logic Pro?<

my thinking on this is that if you have a guitar it has 4 or 5 strings, and you manipulate those strings in a variety of ways to make most of the sounds you need. if you listen to my audio..all of that is just 2 or at most 3 channels! so i always have only 2 or 3 samples playing at once. my stuff from back then was a bit light..not really hard hitting on a dancefloor (which is what i'm interested in) ..but i think you do what to keep everythign as minimal as possible. as far as live performance goes, i wouldn't go anywhere near something like logic audio.

if you have midi gear, then def work on triggering that with pd. i'm working on synthesis within pd now, rather than the sample based stuff...but it's a constant battle to keep cpu usage to a minimum. triggering external devices will be no problem for pd and will leave you heaps of cpu for doing sample mashing.

can't stress enough though. KEEP IT AS SIMPLE AS POSSIBLE. for live music, traditional musicians only play one instrument at once. if you want to make whole songs live, then you are going to have to do the beats and bass and interesting stuff all at one time, so you want to keep it as simple as possible so that you can inject a lot of liveness into it. generally, the more channels of audio you have going at once, the less room there is for jamming out in an impromptu fashion....unless you have magic fingers.

>Look forward to hearing your stuff if possible.<

cool, thanks. quick background on my stuff..."this_is_serious_mum" is a live jam recorded in one take. just 2 channels of audio driving all the sounds from small sample loops being cut up in realtime by me pressing keys on the keyboard. it's a super simple setup, but i think the reason why it works ok is that i spent more time actually playing and practicing than i spent on coding the bastard. i toured across europe and japan and australia playing this stuff and it was generally well recieved. at really good gigs it was the biggest rush ever.

so yeah. good luck. grab the bull by the horns and just go for it.

Cheers,

matt

Jesus on a spacehopper Hardoff! That's the nuttiest most barmy half hour of full on processing,
fx and synthesis I've heard in a long time, and the fact it's Pd, wow.. is making me dance.
I bet the room is loving it when you play your set, amazing stuff!

>> It's weird that many ppl seem to be using pd but that the output~ page
>> in the forum still has threads in
>> it from 2004 in the top page!! <

> it took me a few months of solid patching (a few hours every day) to get a workable
> setup for actually making tracks. it's certainly no small undertaking.

It was months and months after I started patching before I had anything that sounded like music,
and I had a bit of a headstart from using other tools. Once I cracked the surface it started to flow pretty quick though, so hang in there and post up your embryonic tracks warts and all, there are always interesting sounds in early work and they make great for starting off a discussion, or sample them for use in later stuff.

> can't stress enough though. KEEP IT AS SIMPLE AS POSSIBLE. for live music,

I think this is very valuable advice.

Andy

Thanks very much guys for your valuable advice.

Matt, your nutty jam helped me get through this morning at work, while most other people are having a day off. I hope I can share some stuff with you guys too before too long!

Keeping things simple has got to be my main priority from now on. I think over-complication has been my biggest problem for years - always trying to cram too much into a small space.

holy shit

you're my new hero

Just Downloaded your 28 Minute PD session... I am very impressed thanks for the Music... Keep up the good work!!!

Any tips for beginners on how to make this kind of a piece???

I love it!!!

here's what i did:

figured out a whole bunch of things to do to one loop of audio:

ie..stutter, freeze, distort, pitch change, shuffle, reverse, feedback..

assign qwerty keyboard keys to these actions.

repeat the same process again and use the asdfgh keys for one more channel of audio.

mix it all up live.

256 fuck love this is great, really! I so want to get smashed now.

in that case i hope you have some dixieland records.

..ever see that movie 'killing zoe'?

the bit in that where they go downstairs and smoke opium. lovely.

Fantastic

Just listened to that in the office and it had everyone interested! I really need to learn more about PD!

great track !

hey, by the way to anyone else in the future who finds this thread:

here is a link to the patch so you can make your own:

http://puredata.hurleur.com/sujet-1275-live-patch

Awesome!

I listened to this mp3 a while back on headphones when I was in kind of a hypnagogic state, and it was an excellent experience.

Fucking awesome! Just "discovered" the ouput~ thread, i see this was posted 3 years ago, still kicks ass though!

amazing!!!
im gona study your work very well.
congrats!

I also love how a Google search for "puredata forum" shows the "fuck i love pd" thread as the second hit. That's when you know you've made some waves.

fuck yeah, that's fan-fucking-tastic.

Great work. Can you summarize your stutter technique (objects used, etc.)?

@newlin said:

Great work. Can you summarize your stutter technique (objects used, etc.)?

yeah, the speed control, stuttering, pitch, all that stuff is quite easily controlled once you get your head round [tabread4~]

basically, what that object does, is play back your sample at the position you tell it to.

so, to playback normally, you`d send a constant stream of numbers into [tabread4~] at the samplerate of your sample. like this:

[0, 44100 1000(
|
[line~]
|
[tabread4~ mysample]

so what just happened, is i told the [line~] object to make a ramp from 0 to 44100 in 1000 ms. since most samples i use are 44100hz samplerate, that would play back 1 second of the sample in 1 second.

if i wanted to play it back twice as fast, i could send this to the ]line~]:

[0, 44100 500(

if i wanted to play back at normal speed, starting at 1 second into the sample, then i could send this:

[44100, 88200 1000(
|
[line~]

anyway, have a play round with [tabread4~] and read its help document and you~ll figure it out.

once you learn how to use that, then it~s just a case of doing the calculations to convert samplerate to millisends, and cut your sample into 4,8,16 sections etc.

also, its important to ramp the volume down before sending new messages [tabread4~], and then ramp the volume back up after sending them. a ramp time of about 5ms down and 5ms up has little effect on your sample playback, but stops a lot of clicking noise.

hope that helps. it"s abviously not as simple as just adding a [stutter~] object to your patch. but once you can figure out how all that works, you"re well on the way to learning and implementing all sorts of sample manipulation procedures.

good luck. matt

reviving this topic...

Cant'say enough thank you's for sharing your patch and explaining what you did. I was learning Pd a few years back and just stopped studying. Now I'm back on track and this is helping me figure out lots of stuff.

>can't stress enough though. KEEP IT AS SIMPLE AS POSSIBLE.

this is just a great piece of advice, since what you did on your live set it's way complex, but made it in a simple way, and maybe that is your great trick. I needed to read that

Now I'm digging your patch in order to make it work with another one (to control only beats) and everything put together in a Monome. Hopefully I'll achieve good results, and for sure will post here.