DISTRHO
/
JUCE
mirror of https://github.com/DISTRHO/JUCE
1
0
Fork 0
Code Releases 1 Activity
The JUCE cross-platform C++ framework, with DISTRHO/KXStudio specific changes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
659 Commits
11 Branches
450MB
Tree: 480c1f018d
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '480c1f018d'
${ noResults }
JUCE/extras/audio plugins/How to use this framework.txt

292 lines
18KB
Raw Blame History 

  1. 

  2.                             The Juce Polymorphic Plugin Project!

  3.                             ====================================

  4. 

  5. (c) 2008 by Raw Material Software, visit www.rawmaterialsoftware.com for more info.

  6. 

  7. -----------------------------------------------------------------------------------------------------

  8. 

  9. The purpose of this framework is to make is simple to write an audio plugin in a generic

  10. way, which can then be compiled as a VST, AudioUnit, RTAS, or any combination of these. 

  11. 

  12. It's "polymorphic" because the output is a single binary module that acts as all of the 

  13. different plugin formats at the same time. This means that you only need to maintain one 

  14. project, and only need to perform one build to create a multi-format plugin.

  15. 

  16. Also included are some helper classes that make it easy to create a stand-alone app to

  17. run your plugin without a host. This might be useful in its own right, but can also be very 

  18. handy when developing your plugin, because you can build, test and debug it without needing

  19. to keep restarting a 3rd-party host.

  20. 

  21. 

  22.                                     How does it work?

  23.                                     =================

  24. 

  25. To create your plugin, you just create a subclass of the AudioPluginInstance class to 

  26. perform the processing. And your plugin UI is written like any normal Juce UI component.

  27. 

  28. All the platform-specific code is hidden away in wrapper classes that you just add to 

  29. your project - you should (hopefully) never need to even see the inner workings of these.

  30. 

  31. 

  32.                                     Licensing issues

  33.                                     ================

  34. 

  35. Juce is released under the GPL (Gnu Public License) - this means that you're free to use

  36. and redistribute it as long as your products are also released under the GPL. Basically

  37. this means that if you use it, you also have to give away your source code. 

  38. If you want to release a closed-source application, you can buy a commercial license 

  39. that lets you avoid this restriction - see http://www.rawmaterialsoftware.com/juce for more info, 

  40. or see the comments at the top of all the Juce source files.

  41. 

  42. If you're building the VST projects or releasing a VST, you'll need have a look at Steinberg's 

  43. developer site to see what licensing rules apply these days. Their website's at

  44. http://www.steinberg.net

  45. 

  46. If you're building an RTAS then you'll need to sign Digidesign's developer license to get

  47. their SDK. Visit http://www.digidesign.com for more info.

  48. 

  49. 

  50. 

  51.                                     Getting Started

  52.                                     ===============

  53. 

  54. There's also a 'demo' folder - this contains an example plugin which can be built in all

  55. the different formats.

  56. 

  57. Have a look at the demo classes to see how it works, and then to create a real plugin, 

  58. you'll need to replace the demo files with your own code.

  59. 

  60. I've tried to add helpful comments where you might run across common compile errors, to

  61. help describe what you might be doing wrong, as getting a build set-up for some of these 

  62. formats can be a bit of a pain. Please let me know if you find there's anything missing

  63. from these instructions or anything I could change to help smooth the build process along

  64. a bit.

  65. 

  66. I'd recommend NOT putting your own plugin code inside the demo plugin directory - it's 

  67. much neater to keep it somewhere separate and to alter the projects to point to your 

  68. files instead of the demo ones. That way when new versions of this library come out, it'll 

  69. make it easier to update to the latest code.

  70. 

  71. -----------------------------------------------------------------------------------------------------

  72. 

  73.                             Prerequisites for building a VST

  74.                             ================================

  75. 

  76. - Visit http://www.steinberg.net and jump through whatever hoops are necessary to download 

  77.   and install the VST SDK.

  78. - Make sure your include path contains an entry for the "vstsdk2.4" folder containing the SDK.

  79. 

  80. -----------------------------------------------------------------------------------------------------

  81. 

  82.                             Prerequisites for building an RTAS

  83.                             ==================================

  84. 

  85. - Contact Digidesign, ask to become a Digidesign Development Partner, sign the relevent

  86.   agreements and NDAs.

  87. - From the Digidesign website, download their latest Plug-In SDK

  88. - Install the SDK and build some of the demo plugins to make sure it all works.

  89. - In Visual Studio: Add all of these to your include path:

  90.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\EffectClasses

  91.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\ProcessClasses

  92.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\ProcessClasses\Interfaces

  93.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\Utilities

  94.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\RTASP_Adapt

  95.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\CoreClasses

  96.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\Controls

  97.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\Meters

  98.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\ViewClasses

  99.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\DSPClasses

  100.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\PluginLibrary\Interfaces

  101.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\common

  102.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\common\Platform

  103.     c:\yourdirectory\PT_73_SDK\AlturaPorts\TDMPlugins\SignalProcessing\Public

  104.     c:\yourdirectory\PT_73_SDK\AlturaPorts\SADriver\Interfaces

  105.     c:\yourdirectory\PT_73_SDK\AlturaPorts\DigiPublic\Interfaces

  106.     c:\yourdirectory\PT_73_SDK\AlturaPorts\Fic\Interfaces\DAEClient

  107.     c:\yourdirectory\PT_73_SDK\AlturaPorts\NewFileLibs\Cmn

  108.     c:\yourdirectory\PT_73_SDK\AlturaPorts\NewFileLibs\DOA

  109.     c:\yourdirectory\PT_73_SDK\AlturaPorts\AlturaSource\PPC_H

  110.     c:\yourdirectory\PT_73_SDK\AlturaPorts\AlturaSource\AppSupport

  111.     c:\yourdirectory\PT_73_SDK\AvidCode\AVX2sdk\AVX\avx2\avx2sdk\inc

  112. - In Visual Studio: Using the Digidesign demo projects in the SDK, make sure you've compiled 

  113.   debug and release versions of the following static libraries:

  114.     DAE.lib, DigiExt.lib, DSI.lib, PlugInLib.lib.

  115. - In XCode: After installing the Digidesign SDK, make sure you've run the config_SDK_for_Mac 

  116.   command in the SDK's root directory. This sets up some of the tools that it needs.

  117. 

  118. 

  119. -----------------------------------------------------------------------------------------------------

  120.                         Choosing the formats to build

  121.                         =============================

  122.                         

  123. Each plugin project needs to contain a JucePluginCharacteristics.h file, which holds all the

  124. plugin-specific build details. In here, there are three macros that you can set to enable each

  125. of the available formats:

  126. 

  127. #define JucePlugin_Build_VST     1

  128. #define JucePlugin_Build_RTAS    1

  129. #define JucePlugin_Build_AU      1

  130. 

  131. You can set these to 0 to disable the formats that you don't want to build, and this will avoid

  132. any compilation problems if, for example, you don't have the appropriate SDK for a particular format.

  133. 

  134. -----------------------------------------------------------------------------------------------------

  135. 

  136.                         Creating a PC VST/RTAS plugin in Visual Studio

  137.                         ==============================================

  138. 

  139. 

  140. - First try loading the VST demo project in JuceAudioPlugin/demo/build. Hopefully this

  141.   should build correctly.

  142. - Create a new, empty, win32 project using Visual Studio. Choose "DLL" as the type of 

  143.   product to build

  144. - If building an RTAS, add to your project all the juce_RTAS_*.cpp files from the wrapper/RTAS folder.

  145. - If building a VST, add to your project all the juce_VST_*.cpp files from the wrapper/VST folder.

  146. 

  147. - Create yourself a JucePluginCharacteristics.h file, starting with a copy of the one in the

  148.   demo project. Go through each item inside it carefully, and set them to the appropriate value

  149.   for your plugin.

  150. 

  151. - Under "Additional Include Directories", add the folder in which you're going to put 

  152.   your JucePluginCharacteristics.h file.

  153. 

  154. - If you're doing an RTAS, change these project settings (these can all be ignored if you're only doing a VST):

  155.     - Set "C++/Code Generation/Runtime Library" to be "Multi-threaded DLL" or "Multi-threaded Debug DLL"

  156.     - Set the "Linker/Input/Module Definition file" to point to "wrapper/RTAS/juce_RTAS_WinExports.def"

  157.     - Under "Linker/Input/Delay loaded DLLs", add the following: 

  158.         "DAE.dll; DigiExt.dll; DSI.dll; PluginLib.dll; DSPManager.dll"

  159.     - You may (or may not) need to add "libcmtd.lib; libcmt.lib" to the "Linker/Input/Ignore Specific Library" setting.

  160.     - For ONLY the following files:

  161.         juce_RTAS_Wrapper.cpp, juce_RTAS_DigiCode1.cpp, juce_RTAS_DigiCode2.cpp, juce_RTAS_DigiCode3.cpp,

  162.       change their "C++/Advanced/Calling Convention" property to "__stdcall". All other files should 

  163.       be left with the default calling convention of "__cdecl"

  164.     - Set the "Linker/General/Output File" property to "$(OutDir)\$(ProjectName).dpm" (If you're building 

  165.       a polymorphic VST/RTAS, then you can simply copy or rename the finished .dpm file to a .dll, and 

  166.       it'll function as a VST)

  167.     - Under "Custom build step", add the following command:

  168.         copy /Y "\yourdirectory\juce\extras\audio plugins\wrapper\RTAS\juce_RTAS_WinResources.rsr" "$(TargetPath)".rsr

  169.       The corresponding "Outputs" setting for this must be set to "$(TargetPath)".rsr

  170.       (This will copy and rename the juce_RTAS_WinResources.rsr file to sit next to the finished .dpm file. It's

  171.       a dummy resource file, but PT will refuse to load the plugin unless it has a corresponding .rsr file)

  172.     - Because the RTAS code duplicates some win32 constants, you might need to force it to link correctly

  173.       by adding "/FORCE:multiple" to the linker's additional command line options.

  174.     - You might want to change the output directory to "\Program Files\Common Files\Digidesign\DAE\Plug-Ins\"

  175.       if you want the built plugin to go directly into the PT plugins folder

  176.     - When setting properties, remember to change them for both your debug and release builds!

  177. 

  178. - Create your actual plugin classes and add them to the project. Obviously this is the hard bit!

  179. 

  180. - Add the amalgamated juce source file to the project - have a look at the demo app for neat ways of doing this.

  181. 

  182. - NOTE: on Windows, because RTAS uses the altura mac-style code, there are annoying clashes caused if

  183.   you also include the Apple QuickTime headers, so you might need to turn off quicktime by setting the

  184.   juce config macro: #define JUCE_QUICKTIME 0

  185. 

  186. - NOTE: If you're using MSVC2005 to build your plugin, the users will need to

  187.   have the Microsoft VC8 Runtime installed on their machines, otherwise the DLL will 

  188.   silently fail to load. You should probably add the runtime to your plugin's installer, 

  189.   and you can get a copy of it here:

  190.   http://www.microsoft.com/downloads/details.aspx?FamilyID=32bc1bee-a3f9-4c13-9c99-220b62a191ee&DisplayLang=en

  191. 

  192. 

  193. 

  194. -----------------------------------------------------------------------------------------------------

  195. 

  196.                             Creating a Mac AU/VST/RTAS plugin in XCode

  197.                             ==========================================

  198. 

  199. 

  200. - For an AU, make sure that the JucePlugin_Build_AU is enabled in your JucePluginCharacteristics.h

  201. - In XCode, create a new project based on the "Audio Unit Effect" template

  202. - XCode will create a bunch of template source files for you - you can remove all of these from the project

  203.   and delete them

  204. - In the target settings, clear the "Exported Symbols File" setting. The exports are specified by directives

  205.   within the wrapper code, so don't need to be listed explicitly.

  206. - All all the Apple frameworks that Juce normally requires to the "External Frameworks" list

  207. - Add all the juce_AU_* files from the /wrapper/AU directory to your project

  208. - The template project creates an AUPublic group that contains lots of AudioUnit source files. But

  209.   it leaves out files that it thinks you might not need, e.g. if you chose an "Audio Unit Effect" project,

  210.   then it won't add the classes for handling MIDI. So you'll probably need to go into this folder

  211.   and check that it contains AUMIDIBase.cpp, AUMidiEffectBase.cpp, MusicDeviceBase.cpp, etc

  212. - As for the PC, you'll need to make sure your project contains a correctly set-up JucePluginCharacteristics.h

  213.   file - start with a copy of the one in the demo plugin project, and go through it making sure that

  214.   all the values make sense for your plugin.

  215. - Create your actual plugin classes and add them to the project. Obviously this is the hard bit!

  216. 

  217. You should now be able to build a functional AU! If you want VST support as well, then read on...

  218. 

  219. - Make sure that the JucePlugin_Build_VST is enabled in your JucePluginCharacteristics.h

  220. - For VST support, add all the juce_VST_* files from /wrapper/VST

  221. - In your target info settings, add the vstsdk2_4 folder to your "Header Search Paths" list

  222. - Make sure that in your Info.plist, the "Bundle Name" value is correctly set to the name of your plugin.

  223. 

  224. Now, if you compile, the resulting bundle should work as both a VST and AU - you can simply copy or rename it,

  225. changing the suffix to ".vst", and put it in your VST folder.

  226. 

  227. If you also want to build an RTAS, then carry on reading...

  228. 

  229. 

  230. - Make sure that the JucePlugin_Build_RTAS is enabled in your JucePluginCharacteristics.h

  231. - After installing the Digidesign SDK, make sure you've run the config_SDK_for_Mac command in

  232.   its root directory. This sets up some of the tools that it needs.

  233. - Add the files from /wrapper/RTAS to your project. Obviously a couple of these are for Windows, so

  234.   you shouldn't add those

  235. - In the Digi SDK, in /AlturaPorts/TDMPlugins/common/mac, there are two config files:

  236.     CommonDebugSettings.xconfig and CommonReleaseSettings.xconfig

  237.   These contain lots of Digi hackery to get their stuff to compile, so you should add them to your project

  238.   and change your project's settings to use these files as their base config. Even so, it's all a bit of a mess, 

  239.   and you may need to tweak them a bit to get it to work on your system.

  240. - In your target settings, add a custom build setting called "MacBag", and set this to the path where the 

  241.   "MacBag" folder of the Digi SDK lives.

  242. - Add the following to your "Header Search Paths" setting (it's easiest to copy-and-paste this setting from 

  243.   the demo project):

  244.     "$(MacBag)/../AlturaPorts/TDMPlugIns/PlugInLibrary/**"

  245.     "$(MacBag)/../AlturaPorts/TDMPlugIns/DSPManager/**"

  246.     "$(MacBag)/../AlturaPorts/TDMPlugIns/SupplementalPlugInLib/Encryption"

  247.     "$(MacBag)/../AlturaPorts/TDMPlugIns/SupplementalPlugInLib/GraphicsExtensions"

  248.     "$(MacBag)/../AlturaPorts/TDMPlugIns/common"

  249.     "$(MacBag)/../AlturaPorts/TDMPlugIns/common/PI_LibInterface"

  250.     "$(MacBag)/../AlturaPorts/TDMPlugIns/PACEProtection/**" 

  251.     "$(MacBag)/../AlturaPorts/OMS/Headers" 

  252.     "$(MacBag)/../AlturaPorts/Fic/Interfaces/**" 

  253.     "$(MacBag)/../AlturaPorts/Fic/Source/SignalNets" 

  254.     "$(MacBag)/../AlturaPorts/DSIPublicInterface/PublicHeaders" 

  255.     "$(MacBag)/../DAEWin/Include"

  256.     "$(MacBag)/../AlturaPorts/DigiPublic/Interfaces"

  257.     "$(MacBag)/../AlturaPorts/DigiPublic"

  258.     "$(MacBag)/../AlturaPorts/NewFileLibs/DOA"

  259.     "$(MacBag)/../AlturaPorts/NewFileLibs/Cmn"

  260.     "$(MacBag)/../AlturaPorts/TDMPlugIns/SignalProcessing/**" 

  261.     "$(MacBag)/../AvidCode/AVX2sdk/AVX/avx2/avx2sdk/inc" 

  262.     "$(MacBag)/../AvidCode/AVX2sdk/AVX/avx2/avx2sdk/utils"

  263. - If you get include errors compiling some of the DigiDesign code, you may need to 

  264.   add "/Developer/Headers/FlatCarbon" to your header search path.

  265. - In the SDK, find the PluginLibrary.xcodeproj file, and add this to your "External frameworks and Libraries".

  266.   If you've already compiled this library, you can open its item in your XCode project treeview, to find 

  267.   the "libPluginLibrary.a" item inside it. Drag this subitem down to your Target/"Link Binary With Libraries" 

  268.   build stage and drop it there to add it to the link process.

  269. - In your Info.plist, change the "Bundle OS Type Code" to "TDMw", and the "Bundle Creator OS Type Code" to

  270.   "PTul".

  271. - You may need to remove the "OTHER_CFLAGS = -x c++" from the RTAS settings file to stop it complaining about 

  272.   obj-C code

  273. 

  274. You should now be able to build an RTAS! Again, just renaming the finished bundle to ".dpm" and

  275. putting it in your RTAS folder should be do the trick.

  276.   

  277. If you get any weird build problems, a good tip is to try comparing the demo plugin's build settings with your 

  278. own - this should usually show up what's missing.

  279. 

  280. 

  281. Note about exported symbols: 

  282.   When XCode builds the plugin, I've had unpredictable results when trying to stop it from exporting 

  283.   all of the internal functions as public symbols. There are some flags that are supposed to turn this

  284.   off, but sometimes they don't seem to have any effect, and using an explicit exports file also

  285.   seems a bit hit-and-miss. (If anyone knows better and can get this working, please let me know!)

  286.   Anyway, as well as being wasteful and showing everyone what's inside your plugin, leaving all

  287.   the symbols in there will cause fatal crashes when used with Tracktion, or alongside any other

  288.   Juce-based plugins. A way of making sure your plugin is stripped is to use the command

  289.   "strip -x -S YourPlugin.vst/Contents/MacOS/YourPlugin" after bulding it, which removes the

  290.   unnecessary symbols (although in my experience this also doesn't seem to work all the time, 

  291.   so it's a good idea to check it using the unix "nm" command).