Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Web Development

Audio Applications and Effects Made Easy


From the Beginning ...

Installing SynthMaker is a breeze. The program is downloaded as a ZIP file which contains the installation program as an EXE file. Clicking on the EXE performs the installation. When you first start up SynthMaker, you're presented with a schematic containing "a very simple synth built completely from high-level modules." SynthMaker projects are in the form of multi page hierarchical schematics which are stored in ".osm" files. Figure 1 shows the SynthMaker UI.

[Click image to view at full size]
Figure 1: SynthMaker User Interface

On the left side of the UI are filters that are used to organize the 75+ modules that come standard with SynthMaker. Clicking on a filter causes the modules of that category to be displayed in the next column of the display. The majority of the UI is for display of the schematic (bottom-right) and the hierarchical schematic browser (top-right). Figure 1 shows the UI of the example software synthesizer. To see the functionality behind the sleek brushed aluminum front panel, click on the module to give it focus and then click the page down key. This opens the next lower level of the schematic hierarchy for view. Use the page up key or click on the high level schematic in the browser to return to the top level. Modules can be made up of many other modules each with many levels.

An important thing to notice about the high-level display is that the example synthesizer is setup for interactive testing. The Midi In module allows the computer's keyboard to act as a Midi controller for driving the synthesizer. The link (connection) from the Midi In module to the synthesizer's Midi input routes the Midi codes. On the output side, the two outputs (left and right) from the synthesizer are connected to the DS Out (DirectSound) module which allows the sounds produced by the synthesizer to be heard via the computer's audio subsystem. Pressing keyboard keys causes the synthesizer to do its thing. All buttons and knobs on the synthesizer are active and any changes made will be heard in real time. Pretty neat.

To develop your own instruments or effects, you select the modules you need from the left side of the UI and drag them onto your schematic. Modules are connected by dragging a link from the output connector of a module to the input connector of the next. Once you have your creation working you can convert it into a module that is managed by SynthMaker just like standard modules. I've created a module category called mine that I put all modules I create into. If SynthMaker doesn't have the functionality you need in a standard module and that functionality cannot be created by combination of the standard modules you can create a code or assembler module and code it up. The language syntax is explained in the documentation.

SynthMaker enforces correct signal routing between modules by only allowing links to be made between input and output connectors of compatible types. SynthMaker supports over 30 different types of data with each type having a unique connector symbol. All data types fall into one of two categories: stream or triggered.

Quoting from the SynthMaker User's Guide:

Stream data covers all digital audio and control signals. These signals are fluctuating at sampling rate and so any components which process them will also perform calculations at sampling rate. Components that process stream data are where all the digital signal processing occurs. Triggered data works in a completely different way. Whereas stream data is continuously flowing, triggered data only flows in response to some event. Usually the event is a user interaction or data arriving from some external source like MIDI or a timer". Commonly used data types include: integer, float, stream, UI events, midi, mono and poly data.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.