Forums > MaxMSP

standalone / vst spectrum analyzer patch and max runtime questions

Nov 15 2011 | 9:44 am

Hi all.

I want to put together a standalone spectrum analyzer patch that my friends can use via max runtime, I have several basic questions I need help with, can anyone help?

Firstly, when I open any of my patches in max runtime I only see the max patching window, why don’t I see the presentation mode screen? I don’t want my friends to see the patching obviously I want them to only see the final presentation screen. Or is this the only option? Do I need to build the patching window up so it looks like the gui I made in presentation mode?

Secondly, again when running a patch in max runtime there only appear to be basic midi routing options, where are the audio input options for my sound card etc? I intended this patch to be useable as a software insert on a board so it can be used as an aid for live work but it’s going to be unusable if I can’t select which audio channels I want it to work with, what gives? Is there a workaround that I maybe need to incorporate in to my patch?

I’ve previously been quite disappointing by the minimal scrolling speed controls available in max 5’s spectroscope inspector, a faster scroll speed would allow me/us to see more linear detail in spectroscopes display however the fastest speed setting is painfully slow and jerky. This will be (hopefully) my first patch in max 6 is there any improvement in this behavior in this edition?

Can anyone give me any tips as to how easy or difficult it is to port this sort of patch to vst platform? I’ve never done it before, I’ve heard it involves scripting am I right? If so, I’ve never written any before is it difficult?

Nov 15 2011 | 9:59 am

Is "Open in Presentation" set in the patcher inspector?

You will have to include any MIDI/Audio routing stuff that you want. The DSP options patcher could be included in your stand-alone or collective.

Nov 15 2011 | 11:10 am

oh cool, thanks for that I’ll give it a try!

Nov 15 2011 | 1:53 pm

Take a look at my GenericVST abstraction (it's part of a toolkit I've been building for live performance, you can download the latest snapshot at the bottom of (MaxMSP based Live Keyboards Rig Manager)

I've also attached a screenshot to show what it looks like. As you can see, the actual patcher is pretty trivial to create as everything pretty much exists in my toolkit already.

-- Pasted Max Patch, click to expand. --


  1. screenshot890.jpg


Nov 15 2011 | 3:40 pm

Hi, thanks.

Will this allow me to run my max patch as a vst plugins (in a daw)? like cubase? or does this a tool meant to host vst’s actually in max?

sorry to ask, what is probably an such an obvious question.

Nov 15 2011 | 3:55 pm

This is a tool intended to run VSTs inside Max. I am not aware of any way to make a max patch run as a plugin.

However, you can always use techniques such as IAC Ports to allow your DAW and Max to communicate via MIDI. Audio data can be routed with something like Soundflower, although I have not used that as these tools were ideveloped to replace apps like MainStage for live performance use as Mainstage just became too unreliable. I was less interested in capturing the output from Max back to a daw.

The intent was to make the creation of new patches for different songs as easy and as fast as possible.

Nov 16 2011 | 3:55 pm

I see, that’ll come in very handy thanks dhjdhjdhj ;)

I’ve gotten stuck on this patch, the problem is I want to use a wider spectroscope window than usual, so I’m placing two spectroscope windows side by side to make them longer, however I cant see a way to match up the audio signals that the spectroscope is view, so in this case you see double. I tried adding a delay to the audio signal, but that didn’t seem to work the way I expected, you can see this fairly obviously when running the patch, better than I can explain it at any rate.

Could anyone have have a look and maybe make some suggestions for me?



-- Pasted Max Patch, click to expand. --

Viewing 7 posts - 1 through 7 (of 7 total)

Forums > MaxMSP