Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sound [2015/07/08 04:29] slackermedia |
sound [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;}jack|]] | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}ffmpeginstall|]] | ||
| Line 23: | Line 21: | ||
| {{anchor:alsajack}} | {{anchor:alsajack}} | ||
| ===== ALSA JACK Bridge ===== | ===== ALSA JACK Bridge ===== | ||
| + | |||
| + | **Skill Level:** | ||
| + | //This is an intermediate solution, and the recommended Slackermedia solution.// | ||
| The first method, outlined on [[http://jackaudio.org/faq/routing_alsa.html]], is to create a dummy ALSA "loopback" device that can be used from within JACK. This means that while JACK is running, a non-JACK application can still play through your system sound cards by piping its way through JACK via an ALSA tunnel, of sorts. | The first method, outlined on [[http://jackaudio.org/faq/routing_alsa.html]], is to create a dummy ALSA "loopback" device that can be used from within JACK. This means that while JACK is running, a non-JACK application can still play through your system sound cards by piping its way through JACK via an ALSA tunnel, of sorts. | ||
| Line 212: | Line 213: | ||
| {{anchor:jackjack}} | {{anchor:jackjack}} | ||
| ===== Always-On JACK Daemon ===== | ===== Always-On JACK Daemon ===== | ||
| + | |||
| + | |||
| + | **Skill Level:** | ||
| + | //This is a complex solution and requires advanced skills.// | ||
| The second option is to run JACK all the time, no matter what. This is a more complex setup but it has your computer being an active JACK session all the time, meaning that you can route or hijack any sound to or from any device or application at a moment's notice. | The second option is to run JACK all the time, no matter what. This is a more complex setup but it has your computer being an active JACK session all the time, meaning that you can route or hijack any sound to or from any device or application at a moment's notice. | ||
| Line 449: | Line 454: | ||
| {{anchor:jacktime}} | {{anchor:jacktime}} | ||
| ===== JACK Enabled Apps ===== | ===== JACK Enabled Apps ===== | ||
| + | |||
| + | |||
| + | **Skill Level:** | ||
| + | //This is the easiest solution; it requires no skill, but its limitations can be annoying.// | ||
| The simplest solution, in terms of effort, is to just use JACK-enabled applications whilst you are running an active JACK session. It seems almost too simple, but in practise, depending on your workflow, it ends up being quite realistic. | The simplest solution, in terms of effort, is to just use JACK-enabled applications whilst you are running an active JACK session. It seems almost too simple, but in practise, depending on your workflow, it ends up being quite realistic. | ||
| Line 463: | Line 472: | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}ffmpeginstall|]][[{arrowp.png|border:0;background:none;width:0;float:right;}jack|]] | + | <WRAP centeralign> |
| + | <wrap fa>[[jack|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[ffmpeginstall|Q]]</wrap> | ||
| + | </WRAP> | ||