Changes

Jump to navigation Jump to search

Using JACK and PipeWire

470 bytes added, 19:05, 12 October 2021
no edit summary
<output clientName="win10" connectPorts="output-name"/>
</audio>
<sound model="ich9">
<alias name="sound0"/>
</sound>
</syntaxhighlight>
#: <code>input-name</code> and <code>output-name</code> should be replaced with a regular expression that matches the name of the JACK input and output ports. Essentially, these are the names of microphone and speaker devices that the VM would connect to. You can get the names by looking at your patchbay, or run <code>jack_lsp</code>.#: If there is an existing <code><sound></code> block, it should be removed.
# Finally, we need to set PipeWire's runtime directory and latency. These are configured by environment variables. To do this, the following block right before <code></domain></code>:
#: <syntaxhighlight lang="xml">
<output clientName="win10" connectPorts="output-name"/>
</audio>
<sound model="ich9">
<alias name="sound0"/>
</sound>
</syntaxhighlight>
#: <code>input-name</code> and <code>output-name</code> should be replaced with a regular expression that matches the name of the JACK input and output ports. Essentially, these are the names of microphone and speaker devices that the VM would connect to. You can get the names by looking at your patchbay, or run <code>jack_lsp</code>.#: If there is an existing <code><sound></code> block, it should be removed.
# Finally, we need to set PipeWire's runtime directory and latency. These are configured by environment variables. To do this, the following block right before <code></domain></code>:
#: <syntaxhighlight lang="xml">
21

edits

Navigation menu