This folder contains example patches and demos kindly submitted for inclusion by users of Jitter.  All material in this folder remains the copyright of the author, and Cycling'74 assumes no responsibility for this software.  Please read on if you'd like to share, too!

How to submit 3rd Party Examples and Demo Patches for Jitter.

If you are working with Jitter and want to share some of your work with others, you are encouraged to submit your patches for inclusion in the 3rd Party folder of the Jitter release distribution.  Everyone who downloads or purchases a copy of Jitter will get to see what wonderful work you've been doing.

We're categorizing the 3rd Party content into two kinds of Max patches: examples, and demos.  Examples are meant to show existing Max users some of the cool things you've done with Jitter.  Demos are fully-usable patches with a complete screen interface that work out of the box and can be understood and used by anyone who might take an interest in them.

Examples should:

- use a Jitter aspect/technique in a creative way
- be clearly laid-out and documented
- show good programming style
- be designed so as to be recycled by others
- include only stock max/msp/jitter objects
- be neither a tutorial nor a help patch

Demos should:

- show a complete application built in Max/Jitter.  The submission should still be in the form of Max patches, however, not compiled runtime applications.
- run 'out-of-the-box', i.e. no special knowledge of Max required.
- be documented for an audience of users, as opposed to your Max co-developers (though you can do this as well, if you want your patch to be incorporated into others' work).
- include only stock max/msp/jitter objects, or external objects authored by you (which will be included with the demo).

No collectives, shareware/commercial applications, or material copyrighted by parties other than the author of the patch will be accepted.
 
Submissions can be sent as e-mail attachments to jitter-share@cycling74.com.  Archive files (.sit on Mac, .zip on PC) are the preferred method for sending files, even if the submission is only one file.

Make sure to include anything the patch needs to run (e.g. any required abstractions, media files, etc.).  Make sure to include your name, contact info (if desired), and any copyright information you want included (either in the patch or in a README file).