LFO-Robot (Max/MSP Standalone) Sneak-peak

[mannni]

hi Acolmiztli,

to achieve a "several pages" effect you can do the following:

1) make a new empty patch, place a bpatcher object in there, load your LFO patch into the bpatcher object, then adjust the size of the bpatcher so it matches the size of your LFO patch. the bpatcher is now kindofa window into your your LFO patch, and by sending the bpatcher "offset x,y" messages you can define which part of your LFO is visible.

2) go back to your original LFO patch and add more modules, like to the right or to the bottom. figure out how how large and high a row of modules is in pixels. lets assume you added a second row of 4 modules below the exisiting ones, and that the modules are 150px high. save the LFO patch, go back to to your bpatcher patch, and send the message "offset 0,150" (or -150, not sure) to the bpatcher and you will see that your second row of LFO becomes visible. send "offset 0,0" to go back to the first row. makes sense? read about bpatchers in the reference manual on p.74.

bottom line is you have to lay out all of your pages in one patcher next to each other, load this patcher into a bpatcher and use offset to "scroll" to particular pages.

in your case an alternative could be to dynamically change the numbers of the LFOs 1-4 when the user clicks a button, and put in the correct values for speed etc which you must have previously stored in a coll object or something like this. this would be a little more intricate and might require to change a few things in your original patch.

concerning the standalone thing, an alterntive would be to save it as an application from within MAX, which puts the runtime and your patch into a single application file, so people dont have to bother getting the free runtime seperatly. drawback: You can only build app-files for your own OS.

good luck

[Amberience]

Hey thanks Manni!

[audio/fault]

Also, GUIs do matter. People don't want just the functionality, they want an inspiring gui as well. Suckers, eh?

i must say i really love the standart max/msp gui, and think it's very inspiring to my. can't explain why.

@Acolmiztli: i'll want to try it soon, but i have some probs with my pc(killed himself) so i'm going completely mac at the moment. but then i'll try

andreas

[mannni]

I also have a Q ... are you on OSX or PC? i was wondering about the "midi loopback" thing you mentioned allowing to use it as plug-in. what do you mean that, or maybe i misunderstood this... afaik, when you build plugs using pluggo, you cannot make these plugs output midiCC because hosts just dont support this function. is that correct, or do you know how to get this to work?

m.

[stefancrs]

Bang looked good

[Amberience]

I also have a Q ... are you on OSX or PC? i was wondering about the "midi loopback" thing you mentioned allowing to use it as plug-in. what do you mean that, or maybe i misunderstood this... afaik, when you build plugs using pluggo, you cannot make these plugs output midiCC because hosts just dont support this function. is that correct, or do you know how to get this to work?

m.

I'm on PC.

There are many hosts that support outputting of CC events - EnergyXT is one of them, and its the one I use.

But obviously I'm not able to make plugins from Max yet, so I'm stuck in standalone.

So for me to use them, I set my ctlout objects to output their data to a MidiYoke driver, which In turn then feeds into Ableton Live, or EnergyXT.

The only thing is that currently with my LFO-Robot plugin, it hogs the ASIO driver, so I can't load it up as well as EnergyXT - However Live is fine because I can rewire.

I'm trying to work out how to get my lfo's to work without hogging my asio driver.

[mannni]

ok I see,

im on OSX and energyXT is PC only, i dont think thers OSX hosts that support it ... actually it would be cool if Live supported it, but i read from your post that you need to do the midiyoke thing when using live, and i guess this will be valid for both platforms.

im not sure about this ASIO issue, especially when u mention u use your patch as a plugin. using your patch as a plug in would mean converting it to a pluggo, which can be run in any host as long as u have the free pluggo runtime installed. is this what you are doing?

turning your patches into pluggos has become much easier since maxmsp 4.5, you should check it out if you havent tried it yet. i havent tried because i own MAX only, not MSP, and even though i wouldnt want to process audio with my plugs (but midiCC instead), i must have a few basic MSP audio I/O objects in the plug to actually make it work. hmm, i think i need to checkthat out again actually ...

m

[Amberience]

Nah, I've not got Pluggo yet, I'm buying it soon though from ttoz. At the moment I'm not running my patches as plugins, I'm running them in rewire mode, but I am planning to run them as plugins when I can turn them into plugins. I have Max 4.5.2, but I'm not sure how to make a pluggo without Pluggo itself.

[dreammaka]

I don't know about PC version but mac has 4.5.4 version.
and since 4.5.3 you can build vst directly from max/msp.

you will need to buy pluggo if you want AU and RTAS too.(I think)

[mannni]

you dont need to buy the commercial pluggo-plugs from c74 to use your own plugs as OSX AU or RTAS. you build your plug once and can then use it via the pluggoruntime which you can dl for free in whatever plugformat that is supported. if you install the free runtime and install some freeware pluggos they will work in any plug-format.

all this applies to the OSX version at least

[mannni]

... just checked c74 site. even though the free runtime installs all you need to let your selfbuilt or freeware pluggos be used in any format (AU,VST,RTAS), it makes sense to dl and install the full demo of pluggo. this is the only way to get hold of the Develeopment Guide and tutorial patches. you can then just trash the commercial actual pluggo-plugs, if you dont plan to buy them. The DevGuide should have all the answers regarding making your own pluggos ...

m