Ben Bracken

In this 2-minute video, you'll find some great Max 7 tricks for working between Max abstractions and bpatchers, as well as a great way to work with attributes and arguments. It's a great way to streamline your programming workflow.

Work between Max abstractions and bpatchers, attributes and arguments to streamline your programming workflow.

The Transform Menu in Max 7

max-7s-transform-menu-revealed

Nice addition to the environment. Thanks for highlighting in this video, as I would likely have never found that otherwise. I think I will use the attribute version of this feature the most!

Nice addition to the environment. Thanks for highlighting in this video, as I would likely have never found that otherwise.  I think I will use the attribute version of this feature the most!


too bad it is not working with Beap - the examples with Vizzie work, I tried Beap, it does not give a name to the new object, does not create/remember the inputs/outputs, and basically just creates a "new object" with no name

too bad it is not working with Beap - the examples with Vizzie work, I tried Beap, it does not  give a name to the new object, does not create/remember the inputs/outputs, and basically just creates a "new object" with no name


The BEAP modules are patched differently than Vizzie.

To see the difference, add a BEAP module to your patch, select it, then control-lick on the object. From the contextual menu that appears, choose 

Do the same thing to any Vizzie module and note the difference.

The BEAP modules are patched differently than Vizzie. 

To see the difference, add a BEAP module to your patch, select it, then control-lick on the object. From the contextual menu that appears, choose Object > Open original bp.(module-name).maxpat, and watch what happens.

Do the same thing to any Vizzie module and note the difference.


Max 7's Transform Menu Revealed