Skip to content

Commit dab8c67

Browse files
committed
Manual updates
1 parent 965ad0c commit dab8c67

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

SarWeb/manual.html

+6
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,12 @@ <h2>Application List</h2>
4242
</ul>
4343
<p>Selecting <strong>Add</strong> or double clicking a list entry opens the application details dialog.</p>
4444
<img class="screenshot" src="images/sar_application_details.png" />
45+
<ul>
46+
<li><strong>Path</strong> is either a filesystem path or regular expression, depending on whether the "Use regular expressions" option is selected. If using regular expressions, SAR performs a substring match using ECMAScript regex syntax to determine whether a path matches the rule.</li>
47+
<li><strong>Running Applications</strong> displays a list of running applications. Selecting one will set the path to the location of the application's executable.</li>
48+
<li>Six different default endpoint settings are provided. Most applications use the "System" role, except for VoIP applications which may use Communications.</li>
49+
<li>Once a rule is defined, the applications matching the rule may need to be restarted. Make sure to apply your changes on the SAR configuration dialog before restarting your apps.</li>
50+
</ul>
4551
<h2><a name="known-issues">Known Issues / Limitations</a></h2>
4652
<p>SAR is subject to the maximum latency limitation of WaveRT, which attempts to maintain a 10ms processing interval. As such, SAR limits the buffer size that's available to the ASIO host to a maximum of 1/100th of the sample rate. This imposes a latency requirement for the system that not all machines may be able to meet. If you experience buffer underruns at the maximum supported latency, try running a latency testing program such as LatencyMon to determine the cause of the delays.</p>
4753
<p>The current version of SAR requires that the host application which is creating endpoints have admin privileges. This is due to some security concerns with allowing applications to dynamically create audio endpoints, as well as the shared memory approach used to implement the WaveRT "hardware registers". The limitation may be removed in the future.</p>

0 commit comments

Comments
 (0)