Hippie Patching
maybe i´m just mad, but right before falling to sleep i had the idea of a user chain patch. means, we patch together. without any great concept, just for fun.
rules:
- the patch is posted and carried in this thread
- if you add something, post the newest version and make a short comment
- ONLY 5 new objects (asides triggers and math objects) and 15 messages per run
- you can have a new run when at least 2 other users added something after your last turn
- you can modify under the same conditions (5 objects/15msg - but it is stolen from your ADD NEW-credits, means like you can add only 2 new when modifying 3 objects etc.)
- don´t think
anyone? then start it!
I may have been a bit liberal with the definition of messages and objects (particularly with regards to what a number/float qualifies as). I counted my five as dac~, phasor~, pong~, matrixctrl, and number~.
A simple timing mechanism, scalable to any time frame (0-1), integers or floats, able to be wrapped and stuttered via pong~, for now hooked up to matrixctrl for a clicky interface.
Let's see what folk make of it.
Cheers
Edit: Added my tags.
@ Orkester
Hmm, the problem is that with no comments, it's not clear to me what your patch is supposed to do, or how to get it to do it.
Here's a simple patch that at least makes a sound:
Maybe there's a way of joining the two up.
Nice idea, I just put the two first together and tried to stick to the limit of 5 for each. But in general I think the limit should be higher... Especially if the patches need to be corrected to make sense at all...;-)
I think also, that encapsulation allows to be counted as one.
Maybe a limit to stick to just one conceptual change without a limit for the number of changed objects would be better.
Stefan
P.S. the patch of raja slipped in before, I still stick to what I made...
Stefan
@stefantiedje I can't get your patch to do anything but a bunch of clicks.
@everyone I think it would be good to add comments to our patching so others can get a bit of an idea of what's going on and what to play with. Short labels should be quite enough most of the time.
@stefantiedje : newobj: mod: No such object :)
I think it's better to stick to standard objects
@stefan
well, the excitement gets lost when anyone just adds tons of functions. the key is reduction, so the only rule i´d regret by now is the advice to not think. but that wasn´t serious. its okay to add one or two more, but the principle is... reduction. sure there is a temptation to fight which wants to grow etc.
regarding subpatching/encapsulating as one object - i think that´s way pointless.
and yeah, it should be very obvious to use only standard objects for this.
I followed on from Raja's .... I think I added 6 objects but one was a comp~ on the master which well - sort of doesn't count. I put in 3 presets I hope they work.
Grindy. Cool idea, xh9o.
I tagged the thread [hippie, patch] last night...if there's gonna be any more threads this style, we can just tag them the same, and have an easy improvved patch search.
Hehe bagpipes from Hell!
(Oh wait - bagpipes already are from Hell.)
just added some mushrooms.
// edited to remove [loadbang]
i agree on eliminating m4l from this since a lot of hippies don't use live. they use patchouli.
patchouli?
so old school hippie....
Organic Brown Rice, tofu, Dr. Bronner's, and Humboldt County Ganja, maybe.....
err, people, there is absolutely NO 'm4l' specificness whatsoever about grizzle's patch. live.gui objects are standard in all versions of max since 5.1.x series. or are you wanting compatibility to max 4 ?!?! we should not use 'zl sum' either then?!
5 objects not enough? putting omx.comp in at this stage is ridiculous.
cool project! it will fail of course, but cool project!
I removed the M4L object from Driftpatterns patch (from mine originally) and I added some more presets couldn't help it :) It will stop at some point PID but we could have a go again and next time we add our 5 objects in a patcher or something like driftpattern did with his panel and your allowed a gain structure for free(doesn't cost against yr objects used).
eheh.. thats a cool idea! give to the patch some visuals from jitter lands! long live to the hippie patches!
Brilliant Carsol - love it :)
Great idea!
I've added a new timing mechanism - moves between presets and re-triggers the master phasor~. Would love to see someone make this better, I kind of ran out of objects..
You need to start the transport btw..
its too young to die.
i believe i am still within the rules since math objects aren't counted.
I really am enjoying this thread. Some of the sounds coming from that patch are brilliant - I hope others give it a go. I'd be up for one of these a month - even if it's a small number of people - if we record the output we could put it on vimeo as a community album or something.
I noticed I had to remove and recreate the toggle to the metro's at the top. It was included in one of the presets and was stopping the transport from doing it's thing when the preset turned it off.
Oooh; lots of noisy shenanigans, so I added some more - a little sah~ driven modulation of the bagpipes' frequencies.
Brendan
learning a lot here. no time now, I'll add soon. I may just clean up the patch and add presentation mode as my contribution... and something else
I hope I played by the rules here. Added fiddle and used the last output to oscbank. If someone feels like quantizing the tones to something tonal, I don't have enough energy yet.
Have refined my original additions. Much more variation now.
Out of curiosity, anyone know a way of having preset output which presets are active?
Brilliant my turn again :)
I added a few bits around the place. A master transport, a random ramp for Brendans SAH~ and a jit.vcr to record the proceedings and the active preset number :) I was very tempted to add a [yafr] onto driftpatterns raw file (which I knew you could do but never did so excellent learned something) but I guess the [yafr]is cheating.
`
I was zeroed in all the presets... not to be self centered or anything :-)
Hah! Knew screw something up! Theres no standard partial tracker I'm on a train late for a flight. Maybe I'll think something else up and replace it.
i think if you are going to add a feature like a auto-random preset switcher, you should make a way that it can be enabled/disabled as desired. cool addition though.
Out of curiosity, anyone know a way of having preset output which presets are active?
second outlet from the left on the preset object does the trick.
@raja
true, not everyone has [fiddle~]; is there anything in the 74/examples folder that can replace it?
Brendan
@driftpattern
Fair call, it was quite an all-encompassing addition.
As for my question about preset, I think I didn't express it correctly. What I was after was a way of obtaining numbers of all the presets which contained stored data. The problem with the random preset switcher is that if you added presets beyond number 12 then they could not be switched to automatically, as this was controlled by the Random 12.
Any thoughts?
@Mark Durham
not sure how we can get the presets that have been written to. yeah, that would be great to have especially now since there are some gaps in the presets. love the results with that feature.
now the mushrooms are less static (when the added toggle is checked) and edited some of the existing presets to make use of the new feature. also added new presets 41-45 and an inspirational quote from a forum member. check the toggle to activate the transport for the randomizer.
canceled flight. crazy day. you guys can just pull my part off this. I'll work on the next one by the rules.
Good job :D During the game, the patch added a few objects red ))
i thought hippies were using pd ?
This thing is sick!!! Love it!
@tep maybe, but if I'm not mistaken, both Max and PD have strong Californian Roots ; )
It's not Neil Young, is it?
Wow... Love those new presets, they really make nice use of the delay. Inspired me to LFO the pitch adjuster - see presets 57-64, 58's the one for me though...
@raja seems the li tag is the issue. its listed as allowed markup but things got weird ever since i used it above. think i edited my post then accidentally deleted the closing tag. not sure if ben and alanna are aware.
it´s really getting the the hippie sound monster.
ok i like this patch. it produces an large array of crazy sounds and has enough parameters for hours of enjoyment. so unless anybody else has something special to add, i suggest we consider this the final feature set of sound-generating objects and just make it more useable. in other words, lets actually *finish* this patch so we can move on. agree?
"I'd be up for one of these a month - even if it's a small number of people - if we record the output we could put it on vimeo as a community album or something."
yeah like the mcrp from monome.org. additionally, we could build the patch as a collective and/or stand-alone executable for mac+pc. …except i'm not sure about redistributing fiddle~. miller puckette's LICENSE.txt indicates its ok as long as license is included but it seems to not be included in Ted Apel/David Zicarelli msp port.`
| lets actually *finish* this patch so we can move on. agree?
I´d second that, it is really cool the way it is. A little bit of cleanup and user-friendliness and well, then it´s pretty much perfect for what it should become.
BIGGEST THANKS so far, I really must hide a tear. Such a beautiful hippie monster baby :)
I'd like to propose that the next one should have a rule That everyone should either use a separate dac or at least add a gain. I think everyone ended up competeting for the attention of the distortion if you know what I mean
It has bits of an fx engine, the idea was maybe a bit more towards communication of the elements than addition of new elements over the others. But that´s creative euphoria which shouldn´t be limited or controlled too much or too early. Btw. it gets a lot more concrete if you just limit some of the number fields to a certain range.
So it´s very fine chaos with lots of potential for ending up as a good software. When I find the time I´ll seperate and re-connect the pieces a little bit (besides some fixed ranges e.g. a control surface with switches for audio routing options) to give it a more constructive flow and glue. And I think about adding a sequencer from where to sequence the presets more rhythmically into a groove than random could. Maybe next week.
I tidied it up a little - I might do a bit more tomorrow but I am not sure how to label some of the controls... if someone wants to have a look and try to label them that'd be good. I added a few amp controls around the place or made what was there better with line~.
@raja thanks for the heads up on the forum formatting. it was an issue with an unclosed li tag in a post. it's fixed now.
I put a basic presentation on it and it is starting to look like something I could use. I put in a jit.window so as it can go fullscreen. I also put size maessages on both arrays.
There are some issues - the shroom is rate is attached to the number box going into phasor~ rather than the transport or output from the phasor~. Maybe an envelope of some kind on the Osc Section. Preset management needs work - is it worth setting up a pattr system for morphing presets???
In [jit.catch] added configuration -framesize- )
In [jit.catch] -downsample- tuning is needed too)
Another change in the patch, I added jitter)
guys, another version of the patch, updating jitter)
guys, I've done that would at randomization included all ready presets)
i thought for sure hippies would be nowhere to be found when it was time for actual work. nice job by all!
stored preset data is currently a mess. lots of presets were saved before many objects existed - intentions of the preset authors no longer clear. all need to be re-saveed.
excluded more objects from presets. no time to decipher what is going on with all those metros for the jitter stuff. maybe some of those should also be excluded. calling preset 1 at load instead of loadmess/loadbang where appropriate. pattr storage w/ interp would be great but we probably won't be able to use @autoname and thats a lot of scripting names to enter.
found license for fiddle~.mxo in header of source code. ok to distribute for non-commercial use.
There are some issues - the shroom is rate is attached to the number box going into phasor~ rather than the transport or output from the phasor~
not an issue but an intentional choice. the rate just changes in relation to the phasor rate (not phase). most of the shroom anumation comes from the "track+rm" option which was my intention from the begining but couldn't at add right away due to 5 obj limit. if you want, add a selector.
Nice Rapoon,
A bit more Jitter was need - and colour now :)
I added a little more (it's more than 5 object but there is no way to do certain UI type stuff with only 5 at a time) - basically I added the ability to randomize or set measures on the matrixctl.
I am going to start breaking this into an M4L now.
added my changes (from 2 posts above) to grizzle's update.
sorry about that driftpattern - I missed it - there is a lot of code in this post now :)
We fell off the first page of threads. Time to do a new one? :-)
Congrats on this thread - and may there be many more
Even though I didnt feel I had much to add, It is quite educational for us noobs to see more experienced max programmers developing patches in such an open way :)
Is this a good second starter? Sorry, I'm kind of amped about this idea
Doo-hude!
Simplicity is King, this rocks, I love it! I will treat it with the respect it deserves and add some stuff later. Perhaps a new thread is warranted. I'm sure all contributors will agree: keep the GUI simple, clear and effective.
Brendan
Here's my contribution, AudioMatt.
peter, that is, as ever, awesome.
oh shit, i cannot believe i am doing this...
Cool, one quick fix to avoid sending DC offset to your speakers: (the biquad~ is a highpass filter with a very low frequency)
Thanks for starting the thread again!
I added a transport system locked to the speed of the groove~ object. I put in an example noise hat to show the rhythm working but it is just an example please delete it. I ran out of my 5 objects but wanted to show something. I added fair few messages and a bit of math about the place to make sure that groove~ locked right to the transport and phasor~. If you replace the sample you need to restart the transport to reclock the beat.
NB - Patch had to be saved to my harddrive and then opened for it to work (at least for me.)
Sleep time now or about 2 hours ago ;)
I added one more thing but it is not intrusive. I just added a beat lock for the presets and phasor~ rate so they only go at the end of a bar - in order to keep the timing in. It was being messed up when you changed presets manually. If you change presets with the dial it should stay in time. So just functional stuff.
I wish you could edit your posts - you need to connect the [exclude from preset] out of the [preset] object to the preset [dial] or it can cause trouble. I hope that's it.
grizzle, just got to checking this out. Very cool!!! I may make the envelope list variable length later so we don't have such a static beat.
ps you can edit your posts but there's a time limit
So nobody seems to be biting so I changed my contribution (I wasn't too happy with it and it's not going to affect anybody). I worked on from Peters contribution. I added M4L objects - but they are standard in Max 5 so it seems arbitrary not to use it when all the code being posted is in Max 5.
I'm at work on a phone but maybe when I get home I'll start a new thread. I tend to tune out of massive threads...
Figured if I was going through in the step fader, I might as well put in the step filter...
Peter, -I hope you don't mind if I call you Peter- that's f**king awesome.
To the new thread!