...that deal with pure data
You are not logged in.
best thing i've done in 3 years...it's nearly 30 minutes long though//// get yourself a beer or spliff
but, as always...100% pure data for the construction, 100% "stolen" loops for the audio//// 100% realtime
I really enjoyed that, top work!
I am now dancing under the voice a the japenese (?) girls (in the first part?) ... while the singular value decomposition substructuring technique is passing under my hands ...
Oh god, I am at my office, and I look damn crazy dancing like this!
What is yoru hardware for such hardtime-robust-audio-live PD project?
Thanks for this good piece!!
this is outrageously cool hardoff!
you rock sir...
Seriously tho, what spec is your machine to cope with all that sample mangling without once glitching?
Well I guess even if it did glitch, we might not notice through all the purposeful glitching.
Did you make sure all the samples would loop in time before you loaded them into this monster project? or was it all very skillfully mixed beforehand?
It is damned funky no matter what, I once saw someone do a similar thing to this at a local open-mic night - he used max/msp tho... you could very well have started a whole new level of DJing, a whole new era unfolds before you...
When can I hear more?
ha ha , you guys are so nice.
come to beijing on july 25th! i'm playing in a pool bar with panda twin.
the patch takes care of the sample looping. of course i had to cut all my samples so that they were exactly 4 , 8 , 16 , 32...etc beats long, but the actual looping is controlled by the patch. ....you just do calculations based on the sample length output by soundfiler to determine the speed each sample needs to be played at.
the reasons it doesn't glitch:
1) the samples (about 70 samples at a total of 20meg i guess) are preloaded into arrays. this means no glitch from loading new samples mid set.
2) every time a "cut" is made, a line~ object sends the signal to zero for about 10 ms...this stops the pop sound you get when you randomly splice two pieces of audio together.
my mac is 800mhz, but the processes in that patch only use a fraction of cpu.
by the way zenpho, i have posted other tracks in this forum...older ones...should be in the output: feed ears section still. i just hope i still have them online.
thanks for the positive feedback. i'll let you guys know how my china gig goes.
I know this was from 2 years back, but do you have an updated link to your track? I'm interested to hear it, and also some newer 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!!
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? like whether to keep lots of separate instruments or try to keep everything under one roof...
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?
Look forward to hearing your stuff if possible.
hi brett, that track is still up on my site. for some reason the link comes out as a .pd file not an .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.
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.
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.
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!!!
Last edited by davesherlock (2007-06-07 20:59:05)
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.
Just listened to that in the office and it had everyone interested! I really need to learn more about PD!
Fucking awesome! Just "discovered" the ouput~ thread, i see this was posted 3 years ago, still kicks ass though!
im gona study your work very well.
fuck yeah, that's fan-fucking-tastic.
Great work. Can you summarize your stutter technique (objects used, etc.)?