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
jack [2015/06/02 12:11]
slackermedia
jack [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;​}dep|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}sound|]] 
  
 ====== JACK ====== ====== JACK ======
Line 18: Line 16:
 Whether or not you use JACK on a daily basis or just once a year depends on what you do with your computer. Most everyday applications are not designed to use JACK at all (ie, it has not been programmed to use be "​JACK-aware",​ but being open source, there are hacks around that), while others use JACK an an option, and still others require JACK to even launch successfully. Whether or not you use JACK on a daily basis or just once a year depends on what you do with your computer. Most everyday applications are not designed to use JACK at all (ie, it has not been programmed to use be "​JACK-aware",​ but being open source, there are hacks around that), while others use JACK an an option, and still others require JACK to even launch successfully.
  
-If you think you will use JACK because you do pro audio, then you should read this section and the related topics about the JACK frontends, [[qjackctl|qJackCtl]] (an all-in-one JACK configurator and patchbay manager), or [[patchage|Patchage]] along with the session manager [[ajsnapshot|aj-snapshot]]. You should learn JACK, how to use it effectively and efficiently,​ and how to integrate it with your system. ​+If you think you will use JACK because you do pro audio, then you should read this section and the related topics about the JACK frontends, [[qjackctl|qJackCtl]] (an all-in-one JACK configurator and patchbay manager), or [[patchage|Patchage]] along with the session manager [[aj|aj-snapshot]]. You should learn JACK, how to use it effectively and efficiently,​ and how to integrate it with your system. ​
  
 If you do not intend to use JACK, you can skip this section, but install ''​Jack2''​ from [[http://​slackbuilds.org]] just in the unlikely event that it's a soft requirement for some other applications that you may use later. Jack is not terribly large and it won't get in the way unless you manually start it, so it's worth having. If you do not intend to use JACK, you can skip this section, but install ''​Jack2''​ from [[http://​slackbuilds.org]] just in the unlikely event that it's a soft requirement for some other applications that you may use later. Jack is not terribly large and it won't get in the way unless you manually start it, so it's worth having.
Line 33: Line 31:
   *Whenever you see the requirement of "​jack-audio-connection-kit"​ on Slackbuilds.org,​ rest easy in the knowledge that you have the ''​jack''​ dependency resolved.   *Whenever you see the requirement of "​jack-audio-connection-kit"​ on Slackbuilds.org,​ rest easy in the knowledge that you have the ''​jack''​ dependency resolved.
  
-JACK is a tool that you start and stop in the unix shell, so it will not appear in your K-menu.+JACK is a tool that you start and stop in the unix shell, so it will not appear in your **Menu**.
  
 ====== Starting JACK ====== ====== Starting JACK ======
Line 132: Line 130:
 Which makes the capture device (sound input) ''​card 2''​ and the playback device (sound output); the USB microphone and the analogue speakers, respectively. Which makes the capture device (sound input) ''​card 2''​ and the playback device (sound output); the USB microphone and the analogue speakers, respectively.
  
 +===== Adding missing devices to JACK =====
 +
 +If a device isn't available in JACK, you can add it using the ''​alsa_in''​ command along with the device designation you get from the ''​aplay -l | grep card''​ output.
 +
 +<​code>​
 +$ alsa_in -d hw:2 &
 +</​code>​
 +
 +Now the device is available to JACK.
  
 ===== Routing JACK ===== ===== Routing JACK =====
Line 142: Line 149:
   *[[qjackctl|QJackCtl]]:​ a full command center with access to sound routing, JACK configuration,​ patchbays, and sessions.   *[[qjackctl|QJackCtl]]:​ a full command center with access to sound routing, JACK configuration,​ patchbays, and sessions.
   *Cadence: a diverse and multi-purposed control center from [[http://​kxstudio.sourceforge.net|KXstudio]]   *Cadence: a diverse and multi-purposed control center from [[http://​kxstudio.sourceforge.net|KXstudio]]
- 
  
 {{ muse.jpg?​700 }} {{ muse.jpg?​700 }}
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}sound|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}dep|]]+This section covered, in great detail, the way JACK routes sound and how ALSA lists peripherals. That means that you are equipped to use JACK to route signals in and out of the //​computer//​ but you have not actually tried routing sound in and out of the //​software//​ running on the computer yet.  
 + 
 +<WRAP tip> 
 +Each individual sound application covered in this handbook will address typical routing schemes, so if you're feeling a little lost or like you have an incomplete picture of what routing sound actually entails, don't worry. Any JACK-aware application in this handbook will be accompanied by advise on how to route the application (but really you'll be able to figure it out on your own). 
 +</​WRAP>​ 
 + 
 +Read the sections on [[qjackctl|QJackQtl]] and [[patchage|Patchage]] to learn about routing signals to and from the JACK-aware software you use. 
 + 
 +Read the [[midi|MIDI]] appendix for detailed information on routing MIDI signals in a meaningful way. 
 + 
 +<WRAP centeralign>​ 
 +<wrap fa>​[[colour|R]]</​wrap>​ <wrap fa>​[[start|S]]</​wrap>​ <wrap fa>​[[sound|Q]]</​wrap>​ 
 +</​WRAP>​