Difference between revisions of "Max gen~"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
In this page we'll focus on LV2 and MOD. | In this page we'll focus on LV2 and MOD. | ||
| + | '''NOTE: This is a work in progress! (specially this page!)<br> | ||
| + | Except some information to be missing.''' | ||
| − | + | == How it works == | |
| − | |||
| − | + | This works by mixing pre-existing plugin wrapper code with the gen~'s code export feature.<br> | |
| − | + | By exporting the code we can compile them together to create an LV2 plugin binary, then generate the meta-data from it. | |
== Dependencies == | == Dependencies == | ||
Revision as of 12:55, 28 October 2016
This page describes how to get Max gen~ objects working as LV2 plugins, with the purpose of running them on the MOD.
Note that the same procedure also allows for building cross-platform VST2 plugins (Linux, Mac and Windows), but without a custom graphical interface.
In this page we'll focus on LV2 and MOD.
NOTE: This is a work in progress! (specially this page!)
Except some information to be missing.
How it works
This works by mixing pre-existing plugin wrapper code with the gen~'s code export feature.
By exporting the code we can compile them together to create an LV2 plugin binary, then generate the meta-data from it.
