-
Notifications
You must be signed in to change notification settings - Fork 6
/
faq.html
39 lines (35 loc) · 1.92 KB
/
faq.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>libmapper: a library for connecting things</title>
<link rel="icon" type="image/x-icon" href="/images/favicon.ico">
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<script type="text/javascript" src="./javascripts/jquery-3.5.1.min.js"></script>
</head>
<body>
<div class="wrapper">
<div id="header">
</div>
<section>
<h2>Frequently-Asked Questions</h2>
<p>Q. Does my software have to support OSC in order to use libmapper?<br />
A. No - libmapper provides its own OSC interface through a dependency on liblo, so your device/program doesn't need separate OSC support.</p>
<p>Q. My software already supports OSC - isn't it overkill to add another OSC-based interface?<br />
A. Remember that libmapper signals are only sent over the network when they have been connected to a destination - libmapper effectively throttles the signals before they hit the network. This means that adding calls to the libmapper signal update function will consume only minimal resources (and no network bandwidth) unless the libmapper functionality is actually being used for mapping.</p>
<p>Q. Why are my libmapper devices not showing up on my Windows machine?<br />
A. Windows Firewall may block libmapper's OSC multicast messages when on a Public network, which can be avoided by either marking any of your Public networks as Private with the 'Network profile' property or by turning off the firewall completely (at your own risk).</p>
</section>
</div>
</body>
<script>
window.onload = function() {
$("#header").load("./sidebar.html");
};
</script>
</html>