skrasms

Someone asked me on another message board to post this, and I was hesitant because it was just created as a proof-of-concept rough draft. It is very inefficient as-is, but I originally made it in about an hour without efficiency in mind ; )

On the other hand, people aren't posting enough Max patches! So here it is in all its CPU-hungry glory. There are many ways it can be made better/faster/stronger, this is just the basic idea.

The idea is a "2D" oscillator based on taking a drawn curve and creating oscillator waveforms from the x and y projections. It is too difficult to explain without pictures, so I put a video showing it in action on my development blog at skrasoft.com/blog

The Max/MSP files can be downloaded from skrasoft.com/blog/blogfiles/2DOscPatcher.zip

sharing-is-caring-a-2d-oscillator-concept-patch

that's pretty sweet. really cool idea and i especially love hearing it spin. and you are definitely right: people do need to post more of their work. thanks for posting this.

Man, that's addictive. So much for getting other stuff done today, I've been messing with that for hours. Really interesting concept there... I understand most of what's happening, though I sure learned a lot by deciphering the patch and the javascript. It gave me some great ideas, thanks for that!

I added some things to expand it, like an X/Y graph (which generally sounds pretty crunchy due to the division, but can be interesting), speed and direction controls for the spin, and a filtergraph~ that can be bypassed and recorded. This helps get more out of the original waveforms, especially the X/Y one with its distortions and square edges. Plus there's more pretty colors for the graphs :)

Again, that's really something. I encourage everyone to check it out. The zip here is my version with those additions, but the underlying patch is all *skrasms*. Great stuff!

I added some things to expand it, like an X/Y graph (which generally sounds pretty crunchy due to the division, but can be interesting), speed and direction controls for the spin, and a filtergraph~ that can be bypassed and recorded. This helps get more out of the original waveforms, especially the X/Y one with its distortions and square edges. Plus there's more pretty colors for the graphs  :)

Quote: seejayjames wrote on Sun, 10 August 2008 13:51

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

> Again, that's really something. I encourage everyone to check it out. The zip here is my version with those additions, but the underlying patch is all *skrasms*. Great stuff!

This patch hits 100% CPU when I turn on the audio and then Max eventually crashes. I'm testing on Windows XP with Max 5.0.4.

Quote: seejayjames wrote on Sun, 10 August 2008 13:51
----------------------------------------------------
>
> Again, that's really something. I encourage everyone to check it out. The zip here is my version with those additions, but the underlying patch is all *skrasms*. Great stuff!
>
> --CJ
----------------------------------------------------

This patch hits 100% CPU when I turn on the audio and then Max eventually crashes. I'm testing on Windows XP with Max 5.0.4.


No problems here, 5.0.2, XP. Possibly something with the audio card?

One element that might be problematic is the "spin rate", I allowed the ms to go to 1, which is a lot of processing thru the js... but still I have no problems. It's not optimized for fast spins this way---better to have bigger steps in the js rather than faster bangs, but again, this is just experimental.

That's really, really cool. I especially like the "spin" filtering. Thanks for sharing that - I rely on hardware for sound generation, but you're making me reconsider!

I finally have some time to work on Max 5 and I'm rebuilding a large 

app. I use a mixture of bpatchers, and sub-patchers opened with 

thispatcher. For the sub-patchers I get rid of the whole window frame. 

Well, I'd like to. I can hide everything except the menu bar at the 

bottom of the window, which is going to really mess up the look of my 

I couldn't find anything about this by searching the forum, and I 

can't see a message in the help file that will hide the lower bar.

What's going on with this? How can I get a frameless window for my 

I finally have some time to work on Max 5 and I'm rebuilding a large  
app. I use a mixture of bpatchers, and sub-patchers opened with  
thispatcher. For the sub-patchers I get rid of the whole window frame.  
Well, I'd like to. I can hide everything except the menu bar at the  
bottom of the window, which is going to really mess up the look of my  
patch.

I couldn't find anything about this by searching the forum, and I  
can't see a message in the help file that will hide the lower bar.

What's going on with this? How can I get a frameless window for my  
subpatchers?

I couldn't find the answer to this in the docs or the inspector...

Can I have a different background colour in presentation and patching 

mode? (I know I can have different colours locked and unlocked).

Why? Well, I want a black bg in locked presentation mode, and I want 

to be able to see my wiring in locked patcher mode! I could do it 

with messages to [bgcolor] if I could detect whether the patcher is in 

presentation or patching mode, but there doesn't seem to be a way of 

I couldn't find the answer to this in the docs or the inspector...
Can I have a different background colour in presentation and patching  
mode? (I know I can have different colours locked and unlocked).

Why? Well, I want a black bg in locked presentation mode, and I want  
to be able to see my wiring in locked patcher mode!  I could do it  
with messages to [bgcolor] if I could detect whether the patcher is in  
presentation or patching mode, but there doesn't seem to be a way of  
doing that. ?

I just discovered that, but then there doesn't seem to be a way to get 

the Toolbar back without changing the flag back, closing and re- 

opening the patch - which is a bit cumbersome!

So if I think I've finalised a sub-patch, and unchecked "show toolbar 

on open", but then discover I want to change something in the 

On 22 Aug 2008, at 12:40, Emmanuel Jourdan wrote:

> Open the patcher inspector, and uncheck the "Show Toolbar on Open" 

I just discovered that, but then there doesn't seem to be a way to get  
the Toolbar back without changing the flag back, closing and re- 
opening the patch - which is a bit cumbersome!
So if I think I've finalised a sub-patch, and unchecked "show toolbar  
on open", but then discover I want to change something in the  
subpatcher quickly ....
What to do?

On 22 Aug 2008, at 12:40, Emmanuel Jourdan wrote:
>
> Open the patcher inspector, and uncheck the "Show Toolbar on Open"  
> option.
>
> HTH,
> ej
>


> I could do it with messages to [bgcolor] if I could detect whether 

> the patcher is in presentation or patching mode, but there doesn't 

Then you can do it if you use the (presentation $1) message to 

[thispatcher] instead of clicking the toolbar when you trigger 

(BTW, it would be nice to be able to *not* have this toolbar by default 

David Stevens wrote:
>  I could do it with messages to [bgcolor] if I could detect whether 
> the patcher is in presentation or patching mode, but there doesn't 
> seem to be a way of doing that. ?

Then you can do it if you use the (presentation $1) message to 
[thispatcher] instead of clicking the toolbar when you trigger 
presention mode.

(BTW, it would be nice to be able to *not* have this toolbar by default 
on all patches...)

Thanks for that - an undocumented message! (Well, I couldn't find it 

>> I could do it with messages to [bgcolor] if I could detect whether 

>> the patcher is in presentation or patching mode, but there doesn't 

> Then you can do it if you use the (presentation $1) message to 

> [thispatcher] instead of clicking the toolbar when you trigger 

> (BTW, it would be nice to be able to *not* have this toolbar by 

Thanks for that - an undocumented message! (Well, I couldn't find it  
anywhere).

> David Stevens wrote:
>> I could do it with messages to [bgcolor] if I could detect whether  
>> the patcher is in presentation or patching mode, but there doesn't  
>> seem to be a way of doing that. ?
>
> Then you can do it if you use the (presentation $1) message to  
> [thispatcher] instead of clicking the toolbar when you trigger  
> presention mode.
>
> (BTW, it would be nice to be able to *not* have this toolbar by  
> default on all patches...)
>
> Ciao


Sharing is Caring: a 2D Oscillator Concept Patch