In this article
Code generated by RNBO from a patcher is licensed under the Cycling '74 License for Max-Generated Code for Export. Supporting files for the RNBO engine to support this custom generated code are licensed under the MIT License. Binaries generated by the cloud compiler are also subject to the Cycling '74 License for Max-Generated Code for Export.
Does the license mean that my algorithms belong to Cycling '74 after being code-exported from RNBO?
No. All of your original work in Max, which is an expression of your algorithm, belongs to you. Cycling ’74 retains the copyright over the RNBO exported source code that realizes your work with the RNBO Engine. That copyright is not a patent or any other claim on your algorithms or your RNBO patcher, but pertains to the text of the generated code.
This copyright is necessary in order for Cycling ‘74 to provide the dual non-commercial and commercial licensing terms of the Cycling '74 License for Max-Generated Code for Export. Code that is copyrighted by other authors may be used in newly copyrighted projects, according to the licenses granted by the copyright owner, so you may subsequently copyright a software work that includes the RNBO exported source code according to the license terms of the Cycling '74 License for Max-Generated Code for Export.
What are the terms of the license for commercial usage?
If you are an entity with UNDER $200k in annual revenue or funding, you DO NOT need to contact us in order to register your commercial use of code generated with RNBO version 1.X, and you do NOT have to pay any fees associated with your use of code generated with RNBO version 1.X.
If you are an entity with OVER $200k in annual revenue or funding, you WILL need to contact email@example.com in order to register your commercial use of code generated with RNBO version 1.X, but you do NOT have to pay any fees associated with your use of code generated with RNBO version 1.X.
We reserve the right to change the terms and conditions of commercial use of code generated with RNBO versions greater than 1.X.
Can I share my exported binaries?
Provided that it is for noncommercial use or you have received a license for commercial use, under the Cycling '74 License for Max-Generated Code for Export you are free to share exported source and binaries for web export, max external, rPi, Audio Unit plugin, and all other binaries except VST3 Plugins which have additional restrictions due to Steinberg’s VST3 Licensing requirements (see below). It is also worth noting that Apple binaries will require code signing to work properly on other machines without circumventing Apple security protocols (see below).
Can I share my exported VST3 plugin?
To share a VST plug-in you have two choices:
- To distribute a closed-source VST plug-in in binary form, you are required to license it through Steinberg. This involves emailing a completed license agreement to Steinberg according to the instructions in the VST3 SDK.
- To distribute an open source VST plug-in, you must use the GPLv3 license in order to comply with Steinberg’s licensing requirements. You do not have to complete a Steinberg VST licensing agreement in this case. However, since the RNBO cloud compiler does not provide you with the source code for your plug-in, you will have to export your RNBO patcher as C++ source and build the plug-in yourself using either the JUCE RNBO Template or another similar wrapper solution.
If you make a plug-in using C++ source export and JUCE, commercial distribution requires a commercial JUCE license in addition to a Steinberg VST license.
If you are only planning to use the RNBO generated VST plug-in for personal use, you don’t you don't need to release the source code or complete the Steinberg VST license agreement.
Why are my Apple binaries being blocked on other user’s machines?
Recent versions of the Macintosh OS have additional security protocols for ensuring the identity of developers for software to run, in order to avoid malware and other untrusted code from executing on the Macintosh platform. Sharing Apple binaries of any kind will require setting up an Apple Developer Program membership and codesigning the binaries with your certificate. Otherwise, your binaries will not be able to run without the user overriding security protocols.
I still have licensing related questions. Who do I contact?
Please get in touch with us at firstname.lastname@example.org — we'd be happy to field further licensing related questions about RNBO’s export feature.