My Granular patch: Dronerator!
Hello All!
This is my first generative and/or granular patch,
a short demo can be viewed here: http://www.youtube.com/watch?v=TXpD5fHmluU (subsciptions welcome, i plan to make many MSP related videos)
As much as it is granular it can also be considered additive as the 'grain' lengths can vary between 1ms and 10 seconds,
any feedback welcomed,
the second patch here is the patch contained in the poly~,
many thanks,
CC
Grain Generator:
clicking on the first message at the right of your first patch has just crashed my 5.1.2 max inside live 8.1.1
I mean, max for live.
:-(
all the same in max
I guess I missed something
don't see why it should do that, especially that particular message,
i havn't had any problems on any of the machines ive used it on,
i don't use m4l, try opening it MaxMSP
let me know if it happens again,
cheers :-)
It works for me, sounds pretty cool too!
thanks Tim, glad im not the only one to appreciate the noise lol
I did...
i7 720QM
windows7 64bit
4Go RAM
my max and maxforlive/live configuration is very stable.
strange..
(I want to listen this drone!)
yer very strange, the only thing that i can think of is that i made that on a Mac,
sorry for this inconvenience,
Christopher, I'm sure I made a mistake, but where ? :(
you pasted 2 patches.
how do they go together?
save the main patch, then save the poly~ patch as graingen_curve2_001lite, into the same folder then close both patches, then open main patch...
the copy paste of the first one give me an error in the max window:
poly~: no patcher graingen_curve2_001lite
this is strange, it worked for Tim, maybe he knows the solution?
Sounds like you need to have a read up on abstractions (Max tutorial 15). Open the second patch CC posted and save it as graingen_curve2_001lite. Then open the first patch, save it and re-open. All this is doing is making sure that both patches are saved into the search path of MaxMSP, so that when you try to instantiate a patch as an abstraction or inside a poly~ Max can find the named patch for you. Then you'll probably have to reconnect the [targe $2, $3 ] message to the right inlet of poly~ and patch the output into gain~. It *will* work if you do that.
Only thing I will say about the patch is that because of the way you've designed it, you'll have 100 or 200 metros banging away at fast speeds all at the same time, which starts to make the patch respond quite slowly. There are quite a few threads about clogging the schedular with huge amounts of timing-specific data and ways to avoid it.
I wish we could still upload/attach zipped files to the forum, then we wouldn't have to faff around with the saving/reopening etc.........
:)
thanks for the advice Tim, i think in future ill upload my patches somewhere and post a link,
lately i have been using phasor~ objects instead of metro for timing, which should remove that problem?
many thanks for your time,
CC
@ julien
the first patch is the main one, the second is the subpatch for the poly~ object. Save the second one to your HD and name it: graingen_curve2_001lite , then save the first main patch in the same location. Noodling with it right now.
I know about abstraction, but more about abstraction in data flow, I mean, not in MSP...
I never used poly~
I just use objects quoted there:
http://www.julienbayle.net/diy/protodeck/#m4L
thanks!
it works :)
I like generator like that.
I love metaphysical function from Reaktor.
cool im glad you got it to work, thanks for your time, i hope you enjoy it, plenty more like that to come,
watch this space.
CC
hi CC,
got it to work but it doesn't sound anything like the one you posted on youtube. sounds like a fly wearing knights armour in a blender.
any suggestions? i just click everything on and voila?
daniel
nyce