Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
synths [2015/07/15 10:42]
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;​}synfig|]] 
- 
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}trelby|]] 
  
 ====== Soft Synths ====== ====== Soft Synths ======
Line 582: Line 579:
 If you are running Vex as a stand-alone unit with [[jalv]], then there is no inbuilt way to save the state of Vex. 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 ====== ====== WhySynth DSSI ======
  
Line 671: Line 668:
  
  
 +{{anchor:​yoshimi}}
 ====== Yoshimi ====== ====== Yoshimi ======
  
Line 678: Line 675:
 </​wrap>​ </​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 roundso while you may read and hear about ZynAddSubFX ​in your researchthere 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 forkedbut it seems that Yoshimi ​may have buffered against a slight lull in ZynAddSubFX'​s development. Both are active projects nowhowever, 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 andquite 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 synthesisonboard effects, voice parameter settings, filters, and modulators enough ​to fill a screen.+Currentlythe clearest development path is with ZynAddSubFX. Since that'​s ​the original codebaseit makes sense to place documentation under the [[synths#​zynaddsubfx]] heading.
  
-[{{ yoshimi.jpg?​666 | It's not exaggerating to say that Yoshimi ​is all+ 
 +{{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 synth you'll ever need. }}]
  
-To begin, launch ​yoshimi ​from the **K Menu** or from a terminal. When launching from a terminal, give it a unique name:+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>​ <​code>​
-yoshimi ​-N foo+zynaddsubfx ​-N foo
 </​code>​ </​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 | Top-quality presets; amaze your friends! }}] [{{ 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 ===== ===== 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 is serious about being able to be the only+[{{ yoshimi_routing.jpg | ZynAddSubFX (or Yoshimiis serious about being able to be the only
 synth you use. }}] 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:  To create a new part: 
Line 714: Line 744:
   - Put a tick mark in the **Enabled** checkbox.   - Put a tick mark in the **Enabled** checkbox.
  
-[{{ yoshimi_midi.jpg | Set the MIDI channel of each Yoshimi ​instance. }}]+[{{ 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 ===== ===== 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: 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. 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 733: Line 763:
  
 <​code>​ <​code>​
-yoshimi ​-N foo -S ~/​myproject/​sound/​synths/​yoshimi.state+zynaddsubfx ​-N foo -S ~/​myproject/​sound/​synths/​yoshimi.state
 </​code>​ </​code>​
  
  
-====== ZynAddSubFX ====== +<WRAP centeralign>​ 
- +<wrap fa>[[synfig|R]]</​wrap>​ <wrap fa>[[start|S]]</​wrap>​ <wrap fa>[[trelby|Q]]</​wrap>​ 
-The [unmaintainedorigin of the Yoshimi synth. Yoshimi is maintained; use it. +</​WRAP>​
- +
- +
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}trelby|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}synfig|]]+