Plug-ins come in many different shapes, sizes and sounds, but what makes one different from another? The coding of audio and the development of the graphical User Interface (GUI) play a major part in how the plugin sounds and how it functions. This paper details methods of developing a reverb plugin by comparing different programming methods based around the Faust meets JUCE framework launched in February of 2017. The methods include: Faust direct to a plugin, Faust meets JUCE compiled with different architectures, and C++ with JUCE Framework. Each method has its benefits; some are easier to use while others provide a better basis for customization.
Click to purchase paper as a non-member or you can login as an AES member to see more options.
No AES members have commented on this paper yet.
To be notified of new comments on this paper you can
subscribe to this RSS feed.
Forum users should login to see additional options.
If you are not yet an AES member and have something important to say about this paper then we urge you to join the AES today and make your voice heard. You can join online today by clicking here.
