Collective Editor
Opening the collective editor
- With your top-level patcher as the active window, choose Build Collective / Application... from the File menu. The collective editor will appear.
The Collective editor window includes a script area and a number of buttons that you use when creating a collective. The script contains a list of files to include in the collective. The first entry in the script — open thispatcher — is added for you. This tells the collective to include the patcher that was the topmost window when the collective editor was opened. The open keyword means that the patcher will be opened when the collective file is opened.
Any Max objects or abstractions used in the patch be included automatically in the collective, so you won’t need to add them. Certain Max objects, such as js and fpic , will automatically copy files they use into the collective for you (the js object copies its script file, but not files the script uses).
A toplevel patcher window opens when the collective opens. You can have more than one toplevel patcher (you need at least one, however).
Adding toplevel patchers to your collective
- Click the Toplevel Patcher... button in the Collective editor and choose a patcher file from the open file dialog that appears.
- Once you select the file, a new line using the open keyword is added to the script.
If you were to open this collective, both of the files listed with the open keyword would initially be visible.
If there are other files used by a toplevel patcher in the collective, you may need to add them explicitly in the following cases:
- Objects in your patch load data from files. Although some objects handle inclusion of their files for you, in many cases, the object has no idea what you will load into it, because you use a message to load the file while the patch is running.
- Your patch loads additional patchers dynamically (with a load message to the pcontrol object). If you want the loaded patcher's dependencies analyzed, use the Patcher... button (specifying the patcher keyword). If you do not want the patcher to be analyzed, use the Include File... button (specifying the include keyword).
Adding files to a collective
- Click the Include File... button in the Collective editor window and select the file you want to add from the open file dialog.
- The full path of the file chosen will be added to the build script preceded by the include keyword.
If you have an entire folder of data files you want to include, you can include all the files at once.
Including all files in a folder in a collective
- Click the Include Folder... button in the Collective editor window and select the folder you want to add from the open file dialog.
- The full path of the folder chosen will be added to the build script preceded by the include keyword.
Note: Including a folder will only include files in the folder itself . Folders inside the folder you select will not be included.
Editing a collective script to include a large number of files and folders can be time consuming. To avoid repeating the process, you can save a collective build script .
Building a collective
- Click the Build button in the Collective editor window, choose Max collective from the Format pop-up menu in the file dialog box that appears, and type in a unique name for your collective.
- As your collective is built, a listing of the objects and files being included will be printed in the Max Console.
To ensure they can be properly opened, collective files should have the .mxf extension.
See Also
| Name | Description |
|---|---|
| Sharing Max Patchers | Sharing Max Patchers |