Differences

This shows you the differences between two versions of the page.

--- synths [2015/07/03 20:17]
slackermedia
+++ synths [2021/06/03 19:48] (current)
@@ Line 1: / Line 1: @@
-[[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}trelby|]]
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}sphinx|]]
 ====== Soft Synths ======
@@ Line 55: / Line 52: @@
 To help categorise each synth, the following icons are being used (none of these are exclusive of another, and this is an imprecise taxonomy and should be used for quick reference only. The only way to know a synth is to use it.):
-  * <typo ff:icono;fs:1.33em;>D</typo> DSSI plugin
+  * <typo ff:icono;fs:1.33em;>D</typo> DSSI plugin; requires ''dssi'', available from [[http://slackbuilds.org]]
-  * <typo ff:icono;fs:1.33em;>L</typo> LADSPA plugin
+  * <typo ff:icono;fs:1.33em;>L</typo> LADSPA plugin; requires ''ladspa_sdk'', available from [[http://slackbuilds.org]]
-  * <typo ff:icono;fs:1.33em;>V</typo> LV2 plugin
+  * <typo ff:icono;fs:1.33em;>V</typo> LV2 plugin; requires ''lv2'' and ''slv2'', available from [[http://slackbuilds.org]]
+  * <typo ff:icono;fs:1.33em;>T</typo> VST plugin; those listed here do not require additional installs of the VST sdk
   * <typo ff:icono;fs:1.33em;>A</typo> Stand-alone application
   * {{gearshift.png}} a synth for knob tweakers
@@ Line 104: / Line 102: @@
 <WRAP indent>
-LADSPA effects can be loaded into ''ams'' as nodes, meaning you can use the outputs of filters to drive the sounds of the signals generating sound. Create a LADSPA node from the **Module** menu → **Show LADSPA Browser**. Select any LADSPA plugin from the browser and click the **Create Plugin** button at the bottom of the window.
+LADSPA effects can be loaded into ''ams'' as nodes, meaning you can use the outputs of filters to drive the sounds of the signals generating sound. Create a LADSPA node from the **Module** menu  **Show LADSPA Browser**. Select any LADSPA plugin from the browser and click the **Create Plugin** button at the bottom of the window.
 <WRAP tip>
@@ Line 124: / Line 122: @@
 <WRAP indent>
-{{ams_disconnect.jpg }}
+[{{ams_disconnect.jpg | Clickable area.}}]
 To break a connection between two nodes, click the //label// of the input port you want to "unplug" and select **Disconnect**. You must click on the //label// of the port, not the cable, not the node; right-click the //label//. It can be a little tricky, so be precise.
 </WRAP>
@@ Line 131: / Line 129: @@
 <WRAP indent>
-{{ams_config.jpg }}
+[{{ ams_config.jpg| Clickable area.}}]
 To see configuration options for a node, right-click within dead space in the node.
 </WRAP>
@@ Line 144: / Line 142: @@
 ===== Sessions =====
-ALSA Modular Synth is a stand-alone synth, so you are responsible for any work that you do inside of it. Save your patches in **File** → **Save As**, and make sure you store them in a logical location. You might save patches into a standard location so that you can use them in other projects, or you might save them to each project individually; either way, you are responsible for your own data, so keep track of it so that you don't lose your hard work.
+ALSA Modular Synth is a stand-alone synth, so you are responsible for any work that you do inside of it. Save your patches in **File**  **Save As**, and make sure you store them in a logical location. You might save patches into a standard location so that you can use them in other projects, or you might save them to each project individually; either way, you are responsible for your own data, so keep track of it so that you don't lose your hard work.
 ===== Documentation =====
@@ Line 171: / Line 169: @@
 [{{ amsynth.jpg | Amsynth ships with plenty of banks, but also heaps of knobs.}}]
-When you first start amsynth as a stand-alone unit, it may be set to use ALSA by default. If you are using JACK, this needs to be changed in **Config** → **Audio&MIDI**. The only MIDI driver available is ALSA, but since you [should be] using the ''seq'' MIDI driver in [[jack|JACK]], the ALSA MIDI signals are echoed to JACK MIDI. Set the audio output to JACK.
+When you first start amsynth as a stand-alone unit, it may be set to use ALSA by default. If you are using JACK, this needs to be changed in **Config**  **Audio&MIDI**. The only MIDI driver available is ALSA, but since you [should be] using the ''seq'' MIDI driver in [[jack|JACK]], the ALSA MIDI signals are echoed to JACK MIDI. Set the audio output to JACK.
 [{{ amsynth_pref.jpg | Adjust the configuration for JACK.}}]
-Load presets (patches) from the **Preset** menu → **Import Preset**.
+Load presets (patches) from the **Preset** menu  **Import Preset**.
-Load banks of presets from **File** menu → **Open Bank** and select individual patches from the drop down menu in the top toolbar.
+Load banks of presets from **File** menu  **Open Bank** and select individual patches from the drop down menu in the top toolbar.
 ===== Sessions =====
-Save your custom patches in **Preset** menu → **Export Preset**. This selection exports a single Synth preset file (a single patch).
+Save your custom patches in **Preset** menu  **Export Preset**. This selection exports a single Synth preset file (a single patch).
-If you are building your own bank of patches, save your work from the **File** menu → **Save Bank As...**
+If you are building your own bank of patches, save your work from the **File** menu  **Save Bank As...**
 If you are using amsynth as a stand-alone application, you are responsible for your own custom modifications. Any tweak of any knob will be lost if you close amsynth without saving your work.
@@ Line 223: / Line 221: @@
 <code>
-$ startBristal -jack -arp2600 &
+$ startBristol -jack -arp2600 &
 </code>
@@ Line 251: / Line 249: @@
 There are two popular DX7 emulators, one of which (Hexter) is installed by default with the Slackermedia queue file.
+{{anchor:dexed}}
 ===== Dexed =====
-A DX7 emulator
+<wrap left>
+<typo ff:icono;fs:1.33em;>V</typo> <typo ff:icono;fs:1.33em;>T</typo> {{gearshift.png | Tweaked }} {{speaker.png | Digit }}
+</wrap>
+[[http://distrho.sourceforge.net/ports|Dexed]] is an LV2 and VST plugin that emulates the DX7 with a far more complex control panel than the original synth for quick and easy customisation of patches. Dexed ships with several inbuilt banks, but is accurate in its emulation and can load original DX7 banks.
+[{{ dexed.jpg | Maybe not as pretty as the original, but easier to customise.}}]
+Loading patches is a complex thing that mirrors hardware. There are three levels in loading a patch:
+  * Cartridge ("cart") stores banks
+  * Banks store patches
+  * Patches are instrument presets
+Most patch interaction occurs along the top of the dexer window:
+  * **Cart** loads cartridges. There are several pre-loaded into dexed.
+  * **Load** imports banks from the file system via SysEx.
+  * **Save** exports the current bank to a file on your hard drive.
+  * The drop-down menu is a quick and easy way to select a patch.
+  * **Store** saves a patch to the current bank.
+==== Install ====
+Install DX7 from [[http://slackbuilds.org]]. It is part of the **distrho-ports** package.
+==== Sessions ====
+Dexed is designed as a plugin, and should be run as a plugin. As a plugin, the DAW hosting it will manage its sessions, so you don't have to.
+If you do run it as a stand-alone synth, store save the state of Dexer from the **File** menu  **Save**.  This saves the state of Dexer in a directory on your file system. To load those settings back into the synth, launch it with the ''-l'' option:
+<code>
+$ jalv.gtk $(lv2ls | grep -i dex) -l ~/mysettings/
+</code>
-http://distrho.sourceforge.net/ports
@@ Line 291: / Line 322: @@
 **Import Banks:**
-To import a bank of patches, use the **File** menu → **Import Patch Bank**. Open any valid DX7 patch file.
+To import a bank of patches, use the **File** menu  **Import Patch Bank**. Open any valid DX7 patch file.
 {{ hexter_import.jpg }}
@@ Line 301: / Line 332: @@
 **Edit Patches:**
-Hexter not being an actual original DX7, it gains the ability to provide a user-friendly interface to patch editing. Any patch you load can be customised through **Edit** menu → **Edit Patch**.
+Hexter not being an actual original DX7, it gains the ability to provide a user-friendly interface to patch editing. Any patch you load can be customised through **Edit** menu  **Edit Patch**.
 {{ hexter_edit.jpg }}
@@ Line 314: / Line 345: @@
 Whether you have customised anything or not, **write down** in a text editor or on a physical notepad which DX7 bank and patch you use for a song, and keep this note with your project files. Believe it or not, this is exactly how synth users before computers and DAWs kept track of this sort of information. Welcome to true vintage synthesis.
+{{anchor:fluidsynth}}
 ====== Fluidsynth Players ======
@@ Line 333: / Line 364: @@
 {{ fluidsynth.jpg }}
-===== Routing =====
+==== Routing ====
 If being used as a DAW plugin, there is no routing necessary aside from whatever your DAW requires.
@@ Line 339: / Line 370: @@
 Any DSSI plugin can also be used as a stand-alone unit by using the ''jack-dssi-host'' application bundled with the DSSI install.
-===== Sessions =====
+==== Sessions ====
 If being used as a DAW plugin, you do not need to save sessions. Its settings are handled by your DAW.
-===== QSynth =====
+===== Qsynth =====
 <wrap left>
-<typo ff:icono;fs:1.33em;>S</typo>
+<typo ff:icono;fs:1.33em;>S</typo> {{speaker.png | Plug n Play }}
 </wrap>
@@ Line 353: / Line 385: @@
 {{ qsynth.jpg }}
 ==== Install ====
-Install QSynth from [[http://slackbuilds.org]].
+Install Qsynth from [[http://slackbuilds.org]].
 ==== Usage ====
-An instrument in QSynth occupies one channel. Load a Soundfont into the first channel (labelled "QSynth1" by default)
+Along the bottom edge of Qsynth are tabs (there is only one active by default). Each tab is a Qsynth "engine", which can have 16 MIDI channels. This means that if you are using a DAW or sequencer, one Qsynth instance can receive 16 separate channels of MIDI and play, therefore, 16 instruments.
-{{ qsynth_sf.jpg }}
-{{ qsynth_channel.jpg }}
+To configure your currently running Qsynth engine, right-click the first tab (labelled "Qsynth1" by default) and select **Setup**.
+[{{ qsynth_channel.jpg | Configuring Qsynth.}}]
+In the **MIDI** tab, set the MIDI driver, if it is not already, to **alsa_seq** so that all Qsynth MIDI ports are echoed into the JACK system.
+In the **Audio** tab, set the audio driver to **JACK**.
+In the **Soundfont** tab, load a soundfont. You can load many soundfonts, but just choose one for now.
-====== Ingen ======
+Click the **OK** button to apply the changes.
-http://drobilla.net/software/ingen/
+In the main Qsynth window, click the **Channels** button on the left. This displays all 16 MIDI channels available in that engine tab. Double-click a channel to assign a patch from your Soundfont bank.
+The Soundfonts that you load into the engine become the sources of individual patches in the **Channels** window. In this way, you have simultaneous access to banks upon banks of Soundfonts.
+[{{ qsynth_sf.jpg | Load a soundfont patch into a channel.}}]
+==== Sessions ====
+The greatest weakness of Qsynth is its session management; essentially, there is none, except that each tab can "remember" its latest state.
+You can save channel configurations:
+  - Click on the **Channels** button.
+  - Type a name for your channel setup in the top text field.
+  - Click the **Save** button.
+But if you later remove a soundfont bank from a Qsynth engine, the channel it was assigned to silently forgets its original assignment and swaps it out with a patch from a different bank. The reverb and chorus effects are saved with an engine when you close Qsynth, but if you change it and then want to revert back to the way you had it, there's no way to restore from a previous state.
+In other words, Qsynth mostly remembers how you //left// it when you last used it, but any change after a launch is automatically taken as the new master state.
+There is only one practical way to deal with this; treat the Qsynth configuration file as a dynamic, disposable file. When you want to take a snapshot of Qsynth settings so that your music project maintains its integrity, copy the Qsynth configuration file from ''~/.config/rncbc.org/Qsynth.conf'' to your project directory. If you need to restore your master settings, copy the conf file from your project directory back to ''~/.config/rncbc.org/Qsynth.conf''.
+{{anchor:obxd}}
 ====== Obxd ======
-An Ob-x, Ob-a, and Ob-8 emulator.
+<wrap left>
+<typo ff:icono;fs:1.33em;>V</typo> <typo ff:icono;fs:1.33em;>T</typo> {{gearshift.png | Twisted }}
+</wrap>
+[[http://distrho.sourceforge.net/ports|obxd]] is an Ob-x, Ob-a, and Ob-8 emulator. It features two oscillators, ADSR controls for both the filter and envelope, modulation, and more.
+==== Install ====
+Install obxd from [[http://slackbuilds.org]]. It is part of the **distrho-ports** package.
+{{ obxd.jpg?666 | Thrice the OB all in one synth. }}
+==== Sessions ====
+If you use obxd as a plugin, your sessions are managed for you. You can export your work for safe-keeping:
+Save individual patches from the **Presets** menu.
+Save a session from the **File** menu.
+{{anchor:synthv1}}
+====== Synthv1 ======
+<wrap left>
+<typo ff:icono;fs:1.33em;>V</typo> {{gearshift.png | Cleanse, Fold,
+and Manipulate }}
+</wrap>
+[[http://synthv1.sourceforge.net|Synthv1]] is a polyphonic stereo four
+oscillator synthesizer with filter control, ADSR, LFO, effects, and
+more.
+Synthv1 is set up with two "synthesizer" tabs, each containing two
+oscillators. The two synths can be mixed together and the sum of the
+two is piped through a global effect unit.
+[{{ synthv1.jpg?666 | Tweak, twist, turn, drag, drop. }}]
+Launch Synthv1 as a stand-alone application from the **K Menu** or from a terminal:
+<code>
+$ synthv1_jack
+</code>
+It is also an LV2 plugin, available within most any DAW of your choice.
+Its control scheme is particularly nice, using both knobs and
+drag-and-drop graphs when modelling particularly important aspects of
+your sound. It ships with no presets, so it was made for knob tweakers.
+==== Install ====
+Install Synthv1 from [[http://studioware.org]], from the
+''audio/synthesizers'' group.
+==== Sessions ====
+If you are using Synthv1 as a plugin, your DAW manages all of your session data for you.
+If you are using it as a stand-alone application, then sessions can (and should) be saved along with any project data used in your current musical composition. The drop-down menu at the top of the Synthv1 window serves as the Save and Load interface.
+To save a preset, type in a name and click the **Save** button.
-http://distrho.sourceforge.net/ports
+To load a preset, click the **Open** button.
@@ Line 388: / Line 508: @@
 The Roland TB-303 was originally released in the early ' 80s but became iconic after its re-birth as //the// rhythm section for electronic music in the '90s and early '00s. It is a monophonic analog bass synthesizer with an in-built step sequencer. It had just one oscillator with just two waveforms to choose from, but featured enough control over resonance, cut-off, envelope, tuning, to make it a proper synth and not just a bassline generator.
-There are two popular 303 emulators, one of which (Nekobee) is installed by default along with the DSSI package.
+There are two popular 303 emulators:
@@ Line 394: / Line 514: @@
 <wrap left>
-<typo ff:icono;fs:1.33em;>D</typo> {{speaker.png | Plug n Play }}
+<typo ff:icono;fs:1.33em;>D</typo> {{gearshift.png | Plug n Tweak }}
 </wrap>
-Nekobee is a DSSI plugin that emulates the TB-303. It blah blah blah.
+The [[https://github.com/gordonjcp/nekobee|Nekobee]] TB-303 clone is a simple, mono synth, with 8 knobs to control oscillator, resonance, and other aspects of the sound. It isn't the fanciest synthesizer out there, and it only emulates a few aspects of the TB-303, but it has great tone and a unique sound.
+[{{ nekobee.jpg | The nekobee TB-303 clone.}}]
+==== Install ====
+Install Nekobee from [[http://slackbuilds.org]].
+==== Sessions ====
+Running Nekobee as a plugin, all of your settings are saved within the DAW you use.
+If you are running Nekobee as a stand-alone unit with ''jack-dssi-host'', then there is no inbuilt way to save the state of Nekobee.
+{{anchor:nekobi}}
 ===== Nekobi =====
 <wrap left>
-<typo ff:icono;fs:1.33em;>S</typo> {{speaker.png | Plug n Play }}
+<typo ff:icono;fs:1.33em;>V</typo> <typo ff:icono;fs:1.33em;>T</typo> {{gearshift.png | Plug n Twist }}
 </wrap>
-A stand-alone homage to the Roland TB-303  or LV2
+[[http://distrho.sourceforge.net/ports|Nekobi]] is an LV2 and VST homage to the Roland TB-303. It isn't the fanciest synthesizer out there, and it only emulates a few aspects of the TB-303, but it has great tone and a unique sound.
-http://distrho.sourceforge.net/ports
+[{{ nekobi.jpg | The nekobi TB-303 clone.}}]
+==== Install ====
+Nekobi is available from [[http://slackbuilds.org]] as part of the ''distrho-ports'' package.
+==== Sessions ====
+Running Nekobi as an LV2 or VST plugin, all of your settings are saved within the DAW you use.
+If you are running Nekobee as a stand-alone unit with [[jalv]], then there is no inbuilt way to save the state of Nekobi.
+{{anchor:vex}}
 ====== Vex ======
-Vex is a 3 oscillator subtractive waverom synth
+<wrap left>
+<typo ff:icono;fs:1.33em;>V</typo> <typo ff:icono;fs:1.33em;>T</typo> {{gearshift.png | Plug n Twist }}
+</wrap>
-http://distrho.sourceforge.net/ports
+[[http://distrho.sourceforge.net/ports|Vex]] is a 3 oscillator subtractive waverom synth. Each oscillator has a variety of preset profiles to choose from, plus a dedicated filter, ADSR envelope, amp envelope, LFO, and effects. These can be combined and mixed.
+[{{ vex.jpg?666 | Don't be vexed by all these knobs, it's more fun than it looks.}}]
+==== Install ====
+Vex is available from [[http://slackbuilds.org]] as part of the ''distrho-ports'' package.
+==== Sessions ====
+Running Vex as an LV2 or VST plugin, all of your settings are saved within the DAW you use.
+If you are running Vex as a stand-alone unit with [[jalv]], then there is no inbuilt way to save the state of Vex.
+{{anchor:whysynth}}
 ====== WhySynth DSSI ======
 <wrap left>
-<typo ff:icono;fs:1.33em;>D</typo> {{speaker.png | Plug n Play }}
+<typo ff:icono;fs:1.33em;>D</typo> {{speaker.png | Plug n Play }} {{gearshift.png | It is not ours to ask why, but only to do and tweak. }}
 </wrap>
-WhySynth combines bits from [[http://dssi.sourceforge.net|Xsynth-DSSI]] (classic-analog VCO, VCF, and VCA synthesis), [[synths|hexter]], Csound, and various other programs, with
+[[http://smbolton.com/whysynth.html|WhySynth]] combines bits from [[http://dssi.sourceforge.net|Xsynth-DSSI]] (classic-analog VCO, VCF, and VCA synthesis), [[synths|hexter]], Csound, and various other programs, with inspiration from hardware synths like the Matrix 6, ESQ-1, K4, plus several other sources and models. All of this results in two things: a great synth plugin with heaps of ready-to-use patches, as well as a rich customisation layer underneath if you prefer to take the time to model your own sounds.
-inspiration from hardware synths like the Matrix 6, ESQ-1, K4, plus several other sources and models. All of this results in two things: a great synth plugin with heaps of ready-to-use patches, as well as a rich customisation layer underneath if you prefer to take the time to model your own sounds.
+WhySynth can even import K4 patch files.
+{{ whysynth.jpg?666 | Why Synth? Why not? }}
+**Editing Patches:**
+Create your own custom patches from the **Edit** menu  **Edit Patch**. Don't let the basic front-end fool you; the patch editor gives you access to //four// oscillators, filters, effects, LFO, five output envelope filters, and much much more.
 ===== Install =====
@@ Line 434: / Line 601: @@
 Install from [[http://slackbuilds.org]].
-{{ whysynth.jpg }}
+===== Sessions =====
+Running WhySynth as a plugin in a DAW manages your settings for you, but you should back up any custom patches you create.
-===== Routing =====
+Save and open patch banks from the **File** menu.
-plugin vs jack host
-In the event that you do create sounds that you might want to use in other songs, you can export them by ....
-blah blah
+{{anchor:wolpertinger}}
+====== Wolpertinger ======
+<wrap left>
+<typo ff:icono;fs:1.33em;>T</typo> {{gearshift.png | Sliders. }}
+</wrap>
-====== Wolpertinger ======
+[[http://distrho.sourceforge.net/ports|Wolpertinger]] is a subtractive, antialiased polyphonic software synthesizer. There appears to be a minor bug in the LV2 implementation (it fails to announce itself to the LV2 system), so run it as a (Linux Native) VST until resolved.
+{{ wolpertinger.jpg | Listen to the growl. }}]
+Wolpertinger itself is a fairly basic synth, with waveform controls,
+ADSR, resonance, plus a few unique controls like "velocity" and
+"inertia". It ships with no preests, so it's definitely a knob (or
+slider) tweaker's synthesizer.
+==== Install ====
+Wolpertinger is available from [[http://slackbuilds.org]] as part of the ''distrho-ports'' package.
+==== Sessions ====
+Running Wolpertinger as a VST plugin, all of your settings are saved within the DAW you use.
+If you are running it as a stand-alone unit with [[jalv|jalv.gtk]], then there is no inbuilt way to save the state of Wolpertinger.
-Wolpertinger is a subtractive, antialiased polyphonic software synthesizer, now working as a LV2 plugin.
-http://distrho.sourceforge.net/ports
 ====== XSynth DSSI ======
+<wrap left>
+<typo ff:icono;fs:1.33em;>D</typo> {{speaker.png | Easy. }}
+</wrap>
 A classic-analog style DSSI softsynth based on Steve Brooke's **Xsynth** code. More than just a DSSI frontend for XSynth, this plugin features polyphonic operation, band-limited oscillators, an improved filter mode, and velocity-sensitive envelopes.
-{{ xsynth.jpg }}
+The nice thing about XSynth is that it's a good intermediate synth; it
+has heaps of presets like WhySynth (indeed, WhySynth takes many of its
+presets from XSynth), and its editing panel is full-featured but not
+too intimidating. It's a good step up from something basic without
+venturing into complete DIY synthesis.
+{{ xsynth.jpg | Easy to use, but with just enough controls to make it
+powerful too. }}
+===== Install =====
+Install from [[http://slackbuilds.org]].
+===== Sessions =====
+Running XSynth as a plugin in a DAW manages your settings for you, but you should back up any custom patches you create.
+Save and open patch banks from the **File** menu.
+{{anchor:yoshimi}}
 ====== Yoshimi ======
@@ Line 465: / Line 675: @@
 </wrap>
-[[http://sourceforge.net/projects/yoshimi/files|Yoshimi]] is a fork of the well-known and respected ZynAddSubFX synthesizer. It inherits all features from ZynAddSubFX and improves it all round, so while you may read and hear about ZynAddSubFX in your research, there is no need for it since Yoshimi.
+[[http://sourceforge.net/projects/yoshimi/files|Yoshimi]] is a fork of the well-known and respected ZynAddSubFX synthesizer. It inherits all features from ZynAddSubFX and adds some of its own. From the information provided on the websites, it is unclear why the project was forked, but it seems that Yoshimi may have buffered against a slight lull in ZynAddSubFX's development. Both are active projects now, however, and they can both be installed and coexist on you system. Realistically, you'll probably only need one or the other.
-Yoshimi is a stand-alone synthesizer and, quite possibly, it is the //only// soft synth you'll ever need. Its capabilities are staggering. It contains oscillators for additive synthesis as well as subtractive synthesis, onboard effects, voice parameter settings, filters, and modulators enough to fill a screen.
+Currently, the clearest development path is with ZynAddSubFX. Since that's the original codebase, it makes sense to place documentation under the [[synths#zynaddsubfx]] heading.
-{{ yoshimi.jpg?666 }}
-To begin, launch yoshimi from the **K Menu** or from a terminal. When launching from a terminal, give it a unique name:
+{{anchor:zynaddsubfx}}
+====== ZynAddSubFX ======
+<wrap left>
+<typo ff:icono;fs:1.33em;>S</typo> {{gearshift.png | Knobby }} {{speaker.png | Plug n Play }}
+</wrap>
+ZynAddSubFX (or its Yoshimi fork) is a stand-alone synthesizer and, quite possibly, it is the //only// soft synth you'll ever need. Its capabilities are staggering. It contains oscillators for additive synthesis as well as subtractive synthesis, onboard effects, voice parameter settings, filters, and modulators enough to fill a screen.
+[{{ yoshimi.jpg?666 | It's not exaggerating to say that ZynAddSubFX is all
+the synth you'll ever need. }}]
+The latest version of ZynAddSubFX is known as ZynFusion. It is the same great Zyn backend combined with a modern frontend:
+{{:zyn-fusion-osc.png?666|}}
+The developer of ZynFusion asks that you pay $59 for a license. It's well worth the money, and the money supports the developer so it's money well-spent. If you purchase a copy, you download a file containing an installer; follow its instructions to install the synth.
+If you have no money, you can still use the old versions for $0, without the prettier "skin".
+To begin, launch Zyn (or Yoshimi) from the **K Menu** or from a terminal. When launching from a terminal, give it a unique name:
 <code>
-$ yoshimi -N foo
+$ zynaddsubfx -N foo
 </code>
-To choose a patch to start with, click the **Edit** button next to the patch name:
+In addition to unique names for each synth instance, you can choose a patch to start with, click the **Edit** button next to the patch name:
-{{ yoshimi_sounds.jpg }}
+[{{ yoshimi_sounds.jpg | Top-quality presets; amaze your friends! }}]
-Choose your synth bank and patch from the window that appears. Feel free to edit any aspect of any patch; Yoshimi knows no limitations.
+Choose your synth bank and patch from the window that appears. Feel free to edit any aspect of any patch; ZynAddSubFX and Yoshimi know no limitations.
+==== Command Alias ====
+If you're using Yoshimi, the command is obvious (''yoshimi'') but you might find "zyn-add-sub-fx" less memorable. In Linux, commands can be aliased. To create a simpler alias:
+<code>
+$ echo "alias zynsynth='zynaddsubfx'" >> ~/.bashrc
+$ source ~/.bashrc
+</code>
+From then on, launch ZynAddSubFX with your simpler command:
+<code>
+$ zynsynth -N foo
+</code>
 ===== Routing =====
-Basic routing in your patchbay is straight-forward; send **System Capture** MIDI to Yoshimi and send Yoshimi audio to **System Playback**.
+Basic routing in your patchbay is straight-forward; send **System Capture** MIDI to ZynAddSubFX or Yoshimi and send your synth audio to **System Playback**.
-{{ yoshimi_routing.jpg }}
+[{{ yoshimi_routing.jpg | ZynAddSubFX (or Yoshimi) is serious about being able to be the only
+synth you use. }}]
-If you are using multiple instances of Yoshimi, you must set the MIDI channel that each Yoshimi listens to for instructions .
+If you are using multiple instances of ZynAddSubFX, you must set the MIDI channel that each running instance of your synth monitors for instructions.
-Each Yoshimi instance has the potential to play 16 separate parts. By default, all settings in Yoshimi fall into **Part 1**, on MIDI channel 1.
+Each ZynAddSubFX or Yoshimi instance has the potential to play 16 separate parts. By default, all settings in ZynAddSubFX/Yoshimi fall into **Part 1**, on MIDI channel 1.
 To create a new part:
@@ Line 500: / Line 744: @@
   - Put a tick mark in the **Enabled** checkbox.
-{{ yoshimi_midi.jpg }}
+[{{ yoshimi_midi.jpg | Set the MIDI channel of each instance. }}]
-Your MIDI controller will still trigger each part on Yoshimi because all MIDI signals are being routed through the System **MIDI Thru** port. To restrict what is being sent to which Yoshimi part, use a good sequencer or DAW, such as [[seq24|Seq24]] or [[qtractor|Qtractor]] (or any other sequencer or DAW recommended by Slackermedia).
+Your MIDI controller still triggers each part on ZynAddSubFX/Yoshimi because all MIDI signals are being routed through the System **MIDI Thru** port. To restrict what is being sent to which ZynAddSubFX/Yoshimi part, use a good sequencer or DAW, such as [[seq24|Seq24]] or [[qtractor|Qtractor]] (or any other sequencer or DAW recommended by Slackermedia).
 ===== Sessions =====
-Since Yoshimi is only a stand-alone synth, no other application will ever manage its settings. This means that if you load a patch, compose a song, and shutdown your computer, the next time you launch your project (in whatever sequencer or DAW you are using), Yoshimi will not launch unless you launch it manually, nor will it remember what patch you had loaded into it.
+Since ZynAddSubFX and Yoshimi are stand-alone synths, no other application will ever manage their settings. This means that if you load a patch, compose a song, and shutdown your computer, the next time you launch your project (in whatever sequencer or DAW you are using), ZynAddSubFX/Yoshimi do not launch unless you launch it manually, and more importantly **do not** remember what patch you had loaded into it.
 This means you should do two things:
-  - Save your Yoshimi **state**
+  - Save your ZynAddSubFX or Yoshimi **state**
-  - Store the Yoshimi **state** file with other project files
+  - Store the ZynAddSubFX or Yoshimi **state** file with other project files
 Save the **state** of Yoshimi from the **State** menu → **Save**. A //state// save is a snapshot of all parts and all settings at the time of the save.
@@ Line 519: / Line 763: @@
 <code>
-$ yoshimi -N foo -S ~/myproject/sound/synths/yoshimi.state
+$ zynaddsubfx -N foo -S ~/myproject/sound/synths/yoshimi.state
 </code>
-====== ZynAddSubFX ======
+<WRAP centeralign>
+<wrap fa>[[synfig|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[trelby|Q]]</wrap>
-The [unmaintained] origin of the Yoshimi synth. Yoshimi is maintained; use it.
+</WRAP>