Both sides previous revisionPrevious revisionNext revision | Previous revision |
wiki:composition [2017/01/13 21:57] – kristopolous | wiki:composition [2021/08/20 16:38] (current) – gootz |
---|
====== The composer's toolbox ====== | ====== The composer's toolbox ====== |
| |
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 may be foreign 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. | 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. | Instead, Linux music production can be envisioned as an assembly line where each "worker" (in this case, program) is tasked with a different duty. |
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 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 muxes the audio together to a [[apps:daw_apps|daw]]. | 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. | 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. |