Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
wiki:composition [2013/07/13 06:05] – [Production] the_avivwiki:composition [2021/08/20 14:38] (current) – gootz
Line 1: Line 1:
 ====== The composer's toolbox ====== ====== The composer's toolbox ======
  
-This article attempts to discuss the optimal toolset and workflow for composition.+Unlike with many commercial packages on Windows or macOS, going from idea to finished audio file isn't necessarily serviced best by 1-stop-shop software in Linux (although a few do exist).  This approach may be counterintuitive to those who have used software such as Propellerhead Reason or Ableton Live to essentially be responsible for all the tasks associated with the production of music.
  
 +Instead, Linux music production can be envisioned as an assembly line where each "worker" (in this  case, program) is tasked with a different duty.
 +
 +This paradigm allows for greater flexibility and since the tasks and duties of some software is well-defined and well-confined, this allows for projects to be more or less finished and work seamlessly far in the future with devices and other parts of the assembly line.
 +
 +This integration can be done two ways
 +  * Horizontally
 +  * Vertically
 +
 +In a Vertical integration, independently written software communicates with each other through plugins. This allows one to use say, a general sequencer, take [[apps:all:zynaddsubfx|zynaddsubfx]] for example, with a number of composition programs, such as [[apps:all:lmms|lmms]].
 +
 +In a Horizontal integration, you use essentially the equivalent to the UNIX pipe ( '|' ) for music.  Pretend you had a midi keyboard.  You can route the MIDI codes to an [[apps:categories:arpeggiators|arpeggiator]] and have that software output MIDI codes which can then route to a [[apps:categories:sequencers|sequencer]] which outputs not MIDI, but audio to a [[apps:categories:mixers|mixer]] which then mixes the audio together to a [[apps:daw_apps|daw]].
 +
 +These two approaches can be used together and additional or fewer pieces can be placed between striking a key on a keyboard and hearing a sound from a speaker such as automation engines or effects plugins.
 +
 +
 +There is also an entirely different paradigm for creating music that includes musical programming languages.   Under this paradigm, a composer authors a computer program in a specialized audio language and then the computer compiles it and produces the audio output.  Some of these, such as [[apps:all:supercollider|supercollider]] and [[apps:categories:puredata|pure data]] introduce novel paradigms that permit real-time feedback. A decent article that shows this approach in practice can be found in [[http://www.csounds.com/cascone/|Recontextualizing Ambient Music in Csound]] by Kim Cascone.  The author uses the freely available [[apps:all:csound|csound]] to construct the ambient music.
 +
 +Finally, to really make things interesting, the two paradigms can work together.  There are bridges that permit both Vertical and Horizontal integration between the two ways of doing things.  This can allow one to have immense control over the finest details of a composition.
 ===== Composition ===== ===== Composition =====
  
Line 32: Line 50:
 ===== Toolset ===== ===== Toolset =====
  
 +The composer's workflow generally adheres to the following order:
 +
 +  * [[apps:notation_apps|scorewriting]]
 +  * [[apps:midi_apps|sequencing]]
 +  * [[apps:synth_apps|sampling]]
 +  * (recording)
 +  * mixing
 +  * [[apps:daw_apps|mastering]]
 +
 +\\
 +A //sound server// is used to connect all the tools together. A //session manager// is used to facilitate their setup and management.
 +
 +\\
 An example of a beginner's toolset would be: An example of a beginner's toolset would be:
  
Line 43: Line 74:
   * sample library: **ad-hoc collection**   * sample library: **ad-hoc collection**
  
-(Although it would be ideal if there was a collaborative effort to create a centralized library, for everybody to use and contribute to, in the Linux way-of-doing-business).+(Although it would be ideal if there was a collaborative effort to create a centralized library, for everybody to use and contribute to, in the Linux way-of-doing-business.)
  
 \\ \\
Line 49: Line 80:
  
 \\ \\
-As an alternative to MuseScore, Lilypond can be used in combination with Laborejo:+A very good toolset would be:
  
-  * scorewriter: **Lilypond** (**Laborejo**)+  * sound server: **JACK** (**QjackCtl**) 
 +  * session manager: **Non Session Manager** 
 +  * scorewriter-sequencer: **Lilypond** (**Laborejo**) 
 +  * sampler: **LinuxSampler** (**QSampler**) 
 +  * sample library: **Sonatina Symphonic Orchestra**, **ad-hoc collection** 
 +  * workstation: **Ardour**
  
 \\ \\
-QSampler is another LinuxSampler frontend: +The [[http://non.tuxfamily.org/|Non]] tools are popular: **Non Session Manager**, **Non Sequencer**, **Non Mixer**, **Non Timeline**
- +
-  * sampler: **LinuxSampler** (**QSampler**)+
  
 \\ \\
Line 63: Line 97:
   * sound server: **JACK**   * sound server: **JACK**
   * session manager: **Non Session Manager**   * session manager: **Non Session Manager**
-  * scorewriter: **Lilypond** (**Laborejo**)+  * scorewriter-sequencer: **Lilypond** (**Laborejo**)
   * sampler: **Calfbox** (**LisaloQt**)   * sampler: **Calfbox** (**LisaloQt**)
   * sample library: **Sonatina Symphonic Orchestra**   * sample library: **Sonatina Symphonic Orchestra**
Line 102: Line 136:
  
 //Userbase//: When selecting a tool of a certain type, weight should be given to the one with the largest userbase (as the larger the userbase, the greater the probability of reliability). What are the majority of practitioners doing? What is the standard? //Userbase//: When selecting a tool of a certain type, weight should be given to the one with the largest userbase (as the larger the userbase, the greater the probability of reliability). What are the majority of practitioners doing? What is the standard?
 +
 +===== Discussion =====
 +
 +For a discussion about the composer's toolbox, see the corresponding [[http://www.linuxmusicians.com/viewtopic.php?f=4&t=11281|forum topic]].
 +
 +===== See also =====
 +
 +  * [[wiki:instruments]]
 +
wiki/composition.1373695532.txt.gz · Last modified: by the_aviv