THE MOST COMPLEX MAX PATCH IN THE WORLD!
Hi,
Sorry to make partially irrelevant posts but can anyone direct me to THE MOST COMPLEX MAX PATCH IN THE WORLD. It is probably hidden on some kids computer for no one to see.
I am just interested in seeing how far people have taken this software in terms of connecting mechanical,audio,video devices etc etc.
Is there any other software that goes beyond the capabilities of Max/MSP? Perhaps bridging apon military grade.....
Cheers dudes.
and a lot more, but these are good examples of serious work - only your computational power ets the limit.
---
pluggo
hipno
upmix
bla bla
Quote: Sensory Fiend wrote on Sat, 08 July 2006 07:11
----------------------------------------------------
> Hi,
>
> Sorry to make partially irrelevant posts but can anyone direct me to THE MOST COMPLEX MAX PATCH IN THE WORLD. It is probably hidden on some kids computer for no one to see.
> Cheers dudes.
----------------------------------------------------
the MAX app itself for sure is complex.
(i am not so sure about radial or pluggo)
definetly my XXXXXXXX.pat .. ... its MINE!
This is sort of like the Obfuscated C competition: just when you
think it can't get any worse, it does.
> definetly my XXXXXXXX.pat .. ... its MINE!
Or like American politics: after Nixon I didn't think it could ever
get as bad as that again.
-- P.
short main[] = {
277, 04735, -4129, 25, 0, 477, 1019, 0xbef, 0, 12800,
-113, 21119, 0x52d7, -1006, -7151, 0, 0x4bc, 020004,
14880, 10541, 2056, 04010, 4548, 3044, -6716, 0x9,
4407, 6, 5568, 1, -30460, 0, 0x9, 5570, 512, -30419,
0x7e82, 0760, 6, 0, 4, 02400, 15, 0, 4, 1280, 4, 0,
4, 0, 0, 0, 0x8, 0, 4, 0, ',', 0, 12, 0, 4, 0, '#',
0, 020, 0, 4, 0, 30, 0, 026, 0, 0x6176, 120, 25712,
'p', 072163, 'r', 29303, 29801, 'e'
};
-------------- http://www.bek.no/~pcastine/Litter/ -------------
Peter Castine +--> Litter Power & Litter Bundle for Jitter
iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de
http://www.dspaudio.com/
I may have a contender...
I currently support a very large/complex Max/MSP patch for the BEAM
Foundation. It's purpose is to enable an orgranic collaborative
ensemble computer music by coupling extended instruments via an
intelligent network. We have an electronic music trio that plays live
utilizing this patch.
It's code base is 125kB, with no audio buffers. It has been years in
development. There are over 1200 modulation destinations and about 120
sources.
You can have a look at the musicians display here:
http://www.beamfoundation.org/macias_closeup.pdf.
Learn more about the patch here:
http://www.beamfoundation.org/ComposersWorkshop.ppt.
And look at the overview video here:
http://www.beamfoundation.org/media/triometrikEPK.mp4
Enjoy.
--
barry threw :: sound | (if you would see the stars clearly,
http://www.barrythrew.com | look hard at the surrounding darkness)
bthrew(at)gmail(dot)com | -Ooka Makoto
857-544-3967 |
On 9 Jul 2006, at 19:18, Barry Threw wrote:
> I may have a contender...
Neat.
One patcher I've been working on is so massive, it has curved the
very nature of spacetime.
http://reactivesoundsystem.com/read.htm
and then select page "04" at the bottom - sorry, it's a Flash thing...
nick rothwell -- composition, systems, performance -- http://
www.cassiel.com
Interesting!
What do you think of the result? Does it work as well as announced?
What about using those sprites for Stevie?
Would it be feasible that the matrix is some kind of transparent window that
could be moved on top of other windows without hiding them?
Or is it extreme in cpu usage?
Sorry, shouldn't have been sent to the list...
To me it appears that patches that -look- complex are often pretty useless. I work on pretty big patches but all real improvements always come in the form of simplifications. I believe that any patcher with more than 20 objects needs more encapsulation.
Often I am not true to my belief however, because the main thing about our engineering process is that we want to get all kinds of experiments done in a quick and dirty way, just to see if they deserve more attention. Btw this is -the- reason why I choose Max instead of C++ with a nice set of libraries.
Mattijs
Mattijs Kneppers wrote:
> To me it appears that patches that -look- complex are often pretty
> useless. I work on pretty big patches but all real improvements
> always come in the form of simplifications. I believe that any
> patcher with more than 20 objects needs more encapsulation.
I use the appearance of complexity as my first clue that I'm doing
something wrong. My ideas aren't that complicated, so why should my
patches be complicated?
It's not that the monster patches I've made have been useless - they've
just been more difficult to maintain, and experience has shown them to
be needlessly complex in almost all cases. Encapsulation and
segmentation make simplification easier to see, and that process
encourages a positive feedback cycle.