Axiom-Crux

I thought it might be fun to post a patch with the intent of allowing collaboration on the list. I would love to see what others would add/change, and if we can end up with something really cool.

1) No externals. Everything must stay part of 1 patch file using only built in Max/msp/jitter objects

2) Keep it clean. It would be nice to keep the patch organized so we can take it far as possible, meaning using subpatchers for parts and organized patch chords. Even using notes to let people know whats going on in a complex section.

3) keep it to 1024x768, so that everyone can use it without needing cinema display.

Go nuts! Let see what happens! Even post a starting one of your own if you like!

I thought it might be fun to post a patch with the intent of allowing collaboration on the list.  I would love to see what others would add/change, and if we can end up with something really cool.  

1)  No externals. Everything must stay part of 1 patch file using only built in Max/msp/jitter objects

2)  Keep it clean.  It would be nice to keep the patch organized so  we can take it far as possible, meaning using subpatchers for parts and organized patch chords.  Even using notes to let people know whats going on in a complex section.

3)  keep it to 1024x768, so that everyone can use it without needing cinema display.

Go nuts! Let see what happens!  Even post a starting one of your own if you like!


patch-remix-2006

thanks, interesting little soundamachine... I'm curious about the equation within the expression object in the engine subpatch?? Hahah semantics.... I'll have a go at chopping it up maybe make it sample accurate or something.... thanks!

thanks, interesting little soundamachine... I'm curious about the equation within the expression object in the engine subpatch??  Hahah semantics.... I'll have a go at chopping it up maybe make it sample accurate or something.... thanks!


The IDM-Making list at ampfea.org has an ongoing tradition of "exquisite 

corpses" whenever someone feels the urge to develop a set of rules and 

start one. Participation is usually enthusiastic and sufficient to 

develop a piece of typical pop length. This would be a very interesting 

concept to carry over into Max patch development. My interpretation of 

the original concept (pre-Surrealist, I think) would have Maxers specify 

a sort of API for abstractions - each receiving an API, developing a 

patch, and sending an API to the next person - and the results would be 

strung together to produce .... something new!

I would personally push for excluding Jitter since there are many more 

of us without Jitter licenses, but that decision would surely be up to 

the participants in any particular project.

This is a great direction for collaborative development in cases where a 

pure general purpose framework is not necessarily the object.

> I thought it might be fun to post a patch with the intent of allowing collaboration on the list. I would love to see what others would add/change, and if we can end up with something really cool. 

> 1) No externals. Everything must stay part of 1 patch file using only built in Max/msp/jitter objects

> 2) Keep it clean. It would be nice to keep the patch organized so we can take it far as possible, meaning using subpatchers for parts and organized patch chords. Even using notes to let people know whats going on in a complex section.

> 3) keep it to 1024x768, so that everyone can use it without needing cinema display.

> Go nuts! Let see what happens! Even post a starting one of your own if you like!

The IDM-Making list at ampfea.org has an ongoing tradition of "exquisite 
corpses" whenever someone feels the urge to develop a set of rules and 
start one.  Participation is usually enthusiastic and sufficient to 
develop a piece of typical pop length.  This would be a very interesting 
concept to carry over into Max patch development.  My interpretation of 
the original concept (pre-Surrealist, I think) would have Maxers specify 
a sort of API for abstractions - each receiving an API, developing a 
patch, and sending an API to the next person - and the results would be 
strung together to produce .... something new!

I would personally push for excluding Jitter since there are many more 
of us without Jitter licenses, but that decision would surely be up to 
the participants in any particular project.

This is a great direction for collaborative development in cases where a 
pure general purpose framework is not necessarily the object.

Nicholas C. Raftis III wrote:
> I thought it might be fun to post a patch with the intent of allowing collaboration on the list.  I would love to see what others would add/change, and if we can end up with something really cool.  
>
> Only 3 rules
>
> 1)  No externals. Everything must stay part of 1 patch file using only built in Max/msp/jitter objects
>
> 2)  Keep it clean.  It would be nice to keep the patch organized so  we can take it far as possible, meaning using subpatchers for parts and organized patch chords.  Even using notes to let people know whats going on in a complex section.
>
> 3)  keep it to 1024x768, so that everyone can use it without needing cinema display.
>
> Go nuts! Let see what happens!  Even post a starting one of your own if you like!


well we can omit jitter for now then, but as far as the abstractions, i was hoping to keep it all in one patch for ease of use.. it could get confusing with alot of abstractions and exernals.

So lets collab then! The patch is up there!

So lets collab then!  The patch is up there!


oh yeah! Weird, it shows up just fine on the mailing list... oh well, yet another bug?

Anyway, here I go pasting it in the magnificent 1 minute editing time I do have ;) :

this is so cool - I love these kinds of undertakings, even when I am usually too busy to properly participate.

I finally had time to load up the patch, Nicholas, and for me it more or less embodies the beauty of Max - a simple synth sound, with added extras that take it to the next level, combined with a custom gui and cpu usage so low it doesn't even register on my machine...!

I think I might do a pluggo of this one? Something sweet with a lot of intermodulation or something... hmm... Audio input?

Thank you for sharing, Nicholas.
Cheers,
Andreas.


i don't understand why when i doownload sometimes attached files, theyare corrupted.

i don't understand why when i doownload sometimes attached files, theyare corrupted.
macosX3.9-pb1,25GHz

here's a part of the cotent (the post didn't take the last text part):

here's a picture (impossible to paste the text in the message area)

> Go nuts! Let see what happens! Even post a starting one of your own

Sorry, the patch doesn't open on my Powerbook, could you send it in text 

Nicholas C. Raftis III wrote:
> Go nuts! Let see what happens!  Even post a starting one of your own
> if you like!

Sorry, the patch doesn't open on my Powerbook, could you send it in text 
format?

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


> i don't understand why when i doownload sometimes attached files, 

It's not really corrupted, it's just lacking a file extension.

If you add ".mxb" to the end of the filename, it should be recognized 

as a Max binary and open with a double-click. Worked for me.

> i don't understand why when i doownload sometimes attached files,  
> theyare corrupted.
> macosX3.9-pb1,25GHz

If you add ".mxb" to the end of the filename, it should be recognized  
as a Max binary and open with a double-click.  Worked for me.

http://www.daevlmakr.com
http://www.2secondfuse.com

here my first contribution, nothin' too fancy.

added [pattrstorage] for storing and recalling presets on sliders, bpm and volume. no interpolations yet ( to come ).

added a little bang next to each multislider that calls random values for the sliders.

i hope to add other functions for curve shaping...hasta luego

Quote: Axiom-Crux wrote on Thu, 28 December 2006 19:27

----------------------------------------------------

here my first contribution, nothin' too fancy.
added [pattrstorage] for storing and recalling presets on sliders, bpm and volume. no interpolations yet ( to come ).
added a little bang next to each multislider that calls random values for the sliders.
i hope to add other functions for curve shaping...hasta luego
bonne annee.

Quote: Axiom-Crux wrote on Thu, 28 December 2006 19:27
----------------------------------------------------
> I thought it might be fun to post a patch with the intent of allowing collaboration on the list.  I would love to see what others would add/change, and if we can end up with something really cool.  
>


impossible to open patches posted expect by text.

maybe the best is to post patch with attchment on .txt.

cannot use the "cadavrxquis#1.mxb" because couldn't open it.

just introduce temo ration for each part.

i'm sorry, i supposed you work on pc.
impossible to open patches posted expect by text.

maybe the best is to post patch with attchment on .txt.
no ?

here's my contribution.
cannot use the "cadavrxquis#1.mxb" because couldn't open it.
sorry.

just introduce temo ration for each part.


ok.
with the "cadavrxquis#1.mxb" include.

This is a very interesting post, and I wish I was advanced enough to add to this, but I have downloaded this, and will use it to help me learn more about creating instruments.

This is a very interesting post, and I wish I was advanced enough to add to this, but I have downloaded this, and will use it to help me learn more about creating instruments.
Thanks!


we from solid 110 works are happy to announce our 

latest product, "nil weaver", is available now

nil weaver brings sounddesign to a new level, as

we mannaged to create an audio program without

the main improvement over competitors like "wave weaver"

is that we no longer use any max objects.

it is a collectiv, so that you can not steal the code

we from solid 110 works are happy to announce our 
latest product, "nil weaver", is available now
in your local ebay store.

nil weaver brings sounddesign to a new level, as
we mannaged to create an audio program without
any signal processing.

the main improvement over competitors like "wave weaver"
is that we no longer use any max objects.

it is a collectiv, so that you can not steal the code
we removed from axioms original patch.

ooops Roman posted before me, did not have achnce to check Roman's post out yet.

here is a a slight update where left-right panning become 2 sequencers as well...

setTempo.txt from previous posts is still needed

ooops Roman posted before me, did not have achnce to check Roman's post out yet.
here is a a slight update where left-right panning become 2 sequencers as well...
setTempo.txt from previous posts is still needed


Not only does NilWeaver bring sound design to a new level, but also almost brought John Cage back to life for 2 milliseconds ;)

i am not sure how to read the "nth" degree of your post Roman but i remain confident that i will soon get some clues from the 110 hihghly acrobatic team ;)

Quote: Roman Thilenius wrote on Tue, 02 January 2007 22:28

> we from solid 110 works are happy to announce our 

> latest product, "nil weaver", is available now

> nil weaver brings sounddesign to a new level, as

> we mannaged to create an audio program without

> the main improvement over competitors like "wave weaver"

> is that we no longer use any max objects.

> it is a collectiv, so that you can not steal the code

Quote: Roman Thilenius wrote on Tue, 02 January 2007 22:28
----------------------------------------------------
> we from solid 110 works are happy to announce our 
> latest product, "nil weaver", is available now
> in your local ebay store.
>
> nil weaver brings sounddesign to a new level, as
> we mannaged to create an audio program without
> any signal processing.
>
> the main improvement over competitors like "wave weaver"
> is that we no longer use any max objects.
>
> it is a collectiv, so that you can not steal the code
> we removed from axioms original patch.
>
>
> minimal regards
>
> your solid 110 works team
----------------------------------------------------


this is starting to get interesting. I was curious if someone wanted to try out some modification to the actual sound engine? New waveforms perhaps?

By the way, just to give people a heads up I spent the last 4 days developing an intense sound design suite loosely based on my waveweaver, though its completely evolved into a huge project for me, and sounds, looks and acts very different. I may end up making that patch into a marketed application, as it has quite alot of sound potential within it. Ill post more on this as it comes to light.

this is starting to get interesting.  I was curious if someone wanted to try out some modification to the actual sound engine?  New waveforms perhaps?

By the way, just to give people a heads up I spent the last 4 days developing an intense sound design suite loosely based on my waveweaver, though its completely evolved into a huge project for me, and sounds, looks and acts very different.  I may end up making that patch into a marketed application, as it has quite alot of sound potential within it.  Ill post more on this as it comes to light.


Quote: Axiom-Crux wrote on Wed, 03 January 2007 00:08

> my favorite so far is definately the Nil

hum... i guess i missed something . when i opened nil weaver i had only a black window (max 4.5.5 ox 10.4.4 ), which explains my previous comment on nil weaver.

it does not open at all with max 4.6.2 on my machine ( ppc laptop 1.33Ghz )...

i get " error: nil weaver v0.mxb : error -1 opening file " error message...

Quote: Axiom-Crux wrote on Wed, 03 January 2007 00:08
----------------------------------------------------
> my favorite so far is definately the Nil
>

hum... i guess i missed something . when i opened nil weaver i had only a black window (max 4.5.5 ox 10.4.4 ), which explains my previous comment on nil weaver.
it does not open at all with max 4.6.2 on my machine ( ppc laptop 1.33Ghz )...
 i get " error: nil weaver v0.mxb : error -1 opening file " error message...


> here my first contribution, nothin' too fancy. added [pattrstorage]

> for storing and recalling presets on sliders, bpm and volume. no

> interpolations yet ( to come ). added a little bang next to each

> multislider that calls random values for the sliders. i hope to add

> other functions for curve shaping...hasta luego bonne annee.

This doesn't open here, please repost in text format.

I would like to know why this happens, I am using Thunderbird as mail 

karl-otto von oertzen wrote:
> here my first contribution, nothin' too fancy. added [pattrstorage]
> for storing and recalling presets on sliders, bpm and volume. no
> interpolations yet ( to come ). added a little bang next to each
> multislider that calls random values for the sliders. i hope to add
> other functions for curve shaping...hasta luego bonne annee.

This doesn't open here, please repost in text format.
I would like to know why this happens, I am using Thunderbird as mail 
client...

> This doesn't open here, please repost in text format.

> I would like to know why this happens, I am using Thunderbird as mail 

i got the same problem when using firefox.

> This doesn't open here, please repost in text format.
> I would like to know why this happens, I am using Thunderbird as mail 
> client...

i got the same problem when using firefox.
it works fine with "mail" (osX3.9).

it opens when downloaded from safari as well.

anyway here is the requested patch in text format, i hope the issue will be sorted out.

Quote: Stefan Tiedje wrote on Wed, 03 January 2007 13:56

> > here my first contribution, nothin' too fancy. added [pattrstorage]

> > for storing and recalling presets on sliders, bpm and volume. no

> > interpolations yet ( to come ). added a little bang next to each

> > multislider that calls random values for the sliders. i hope to add

> > other functions for curve shaping...hasta luego bonne annee.

strange.
i am posting via safari (2.0.3).
it opens when downloaded from safari as well.
ill post from firefox next time .
anyway here is the requested patch in text format, i hope the issue will be sorted out.

Quote: Stefan Tiedje wrote on Wed, 03 January 2007 13:56
----------------------------------------------------
> karl-otto von oertzen wrote:
> > here my first contribution, nothin' too fancy. added [pattrstorage]
> > for storing and recalling presets on sliders, bpm and volume. no
> > interpolations yet ( to come ). added a little bang next to each
> > multislider that calls random values for the sliders. i hope to add
> > other functions for curve shaping...hasta luego bonne annee.
>
> This doesn't open here, please repost in text format.
> I would like to know why this happens, I am using Thunderbird as mail 
> client...
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>
>
----------------------------------------------------


Patch Remix~ 2006