A Max package providing a modular standard for structuring patches, following the Model-View-Controller design pattern (aka MVC). It is very similar to (and inspired by) libossia and Jamoma, but based on vanilla-Max objects.
-
get and install the latest release from Max at https://cycling74.com ;
-
get the latest release from MVC package at the release page
- (or if you are more confident : clone it or fork it from this page);
-
put it in your Max document folder (
home/Documents/Max 8/Packages); -
that's it.
-
Now start Max;
-
Select file > Show package manager and check if the MVC package is there (in the installed packages);
-
click it and click the "Launch" button to open the
mvc.overview.maxpatand see the list of available objects.
See also the example folder.
- No externals are used in this package. It's all Vanilla Max! :)
- Nevertheless, the brace expansion used throughout MVC components runs in a node script that relies on the braces package. This package is automatically fetched and installed on the first use of
mvc.device.
- If you really have no idea, watch this short video.
- If you want more details on the guts, check this document.
- See help patchers (and references!), they are your best friends.
This repository adopt follows a hybrid "GitFlow" and trunk-based workflow.
Essentially this means that :
- unstable development happens in the
developbranch - the
developbranch is merged to themainbranch once it is stable, like before a release. - a release branch is made from the
mainbranch - a release is made from a
release/v.x.x.xbranch (with v.x.x.x being the release version number tag), so that any hotfix on this release will be made on that specific branch (and most probably be brought back to the development too, but not to the master).
TLDR;
Better use the main branch as much as possible during development.
Use the latest release branch if you (temporarily) want a frozen branch.