X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-using-the-setup-dialog.html;h=171321b06f161c1032072f769ca017d0918f1c98;hb=71afa472a61c8d63fb8932c06b3ab83bf3aecbda;hp=e7b41bca8fa83f0ce83faf6b0bd0ecc099bdd575;hpb=0fec8c5f7c5fc1fac85b40d025d230b26435579b;p=ardour-manual

diff --git a/include/osc58-using-the-setup-dialog.html b/include/osc58-using-the-setup-dialog.html
index e7b41bc..171321b 100644
--- a/include/osc58-using-the-setup-dialog.html
+++ b/include/osc58-using-the-setup-dialog.html
@@ -12,34 +12,49 @@
   Many OSC devices get their IP from a DHCP making it difficult to set
   an IP in Ardour's OSC settings. Therefore, most of the settings are
   <em>default</em> settings. Values are set and the next OSC surface to
-  send a /set_surface* message to Ardour will use those settings. An OSC
-  surface that has previously sent a message to Ardour will retain the
-  settings it already had. The <em>Clear OSC Devices</em> will reset all
-  device settings. A <em>/refresh</em> message will both reset the
-  device settings as well as set that device to any new settings. The
-  Use of <em>/set_surface</em> will override all settings except
-  <em>Port Mode</em>.
+  send an OSC message to Ardour will use those settings. Any change to a
+  setting will reset all
+  device settings. The use of <em>/set_surface</em> will override all
+  settings except <em>Port Mode</em>. <em>Port Mode</em> affects all
+  connected surfaces and so all surfaces must use either the set manual
+  port or send OSC messages from the same port they expect to receive
+  feedback on.
 </p>
 <h2>Dialog settings</h2>
 <h3>OSC setup tab</h3>
-<p>
-<img alt="the OSC configuration dialog"
-     src="/images/osc-dialog.png">
-</p>
+
+<figure>
+	<img alt="The OSC configuration dialog" src="/images/osc-dialog.png">
+	<figcaption>
+		The OSC configuration dialog
+	</figcaption>
+</figure>
+
 <h4>Connection:</h4>
 <p>
   This field is informational only. It shows where Ardour will receive
   OSC messages. The system Name and the Port are the most important parts.
+  Normally, Ardour will use 3819 as its server port. However, if some
+  other server is already using this port, Ardour will try to use the next
+  port up and will keep trying up to 10 ports up.
 </p>
 <h4>Port Mode:</h4>
+
+<figure>
+	<img alt="Port Mode Dropdown" src="/images/osc-portmode.png">
+	<figcaption>
+		Port Mode Dropdown
+	</figcaption>
+</figure>
+
 <p>
   This drop down allows the choice of Auto or Manual outbound port
-  setting. The default Auto port mode, will send OSC messages back to
+  setting. The Auto port mode, will send OSC messages back to
   the port messages from that surface are received from. This setting
   allows two surfaces on the same IP to operate independently. However,
   there are a number of OSC control surfaces that do not monitor the
   same port they send from and in fact may change ports they send from
-  as well. Manual allows the outgoing port (the port the surface will
+  as well. Manual allows the outgoing port, the port the surface will
   receive on, to be manually set. In Manual port mode only one control
   surface per IP can work. Most phone or tablet OSC controllers like
   touchOSC or Control need Manual port mode. More than one controller
@@ -55,35 +70,84 @@
   This sets the default bank size for the next surface to send a
   <em>/set_surface/*</em> OSC message. Bank size 0 (the default) sets
   no banking and allows controlling all strips included in strip_types
-  at once.
+  at once. The entry area will be bright blue for a port that is not
+  valid (ports below 1024 or 3819).
+</p>
+<h4>Send Page Size:</h4>
+<p>
+	This allows setting the size of pages for sends. In the case there are
+	more sends than controls. A size of 0 is the same as no paging and
+	all sends are directly controllable.
+</p>
+<h4>Plugin Page Size:</h4>
+<p>
+	This allows setting the size of pages for plugin controls. Some
+	plugins have hundreds of controls and so it may be necessary to page
+	the plugin controls to a limited number of physical controls. A size
+	of 0 is the same as no paging and all plugin controls are directly
+	controllable.
 </p>
 <h4>Gain Mode:</h4>
+
+<figure>
+	<img alt="Gain Mode Dropdown" src="/images/osc-gainmode.png">
+	<figcaption>
+		Gain Mode Dropdown
+	</figcaption>
+</figure>
+
 <p>
   Sets the faders (and sends faders) feedback math to position where a
   value between 0 and 1 represents the fader position of the same fader
   in the mixer GUI or dB where the feedback from fader movement will be
-  returned as a dB value. When the Gain Mode is set to position, the
+  returned as a dB value. When the Gain Mode is set to position, there
+  are also options to send the gain in dB either to the channel name,
   /*/name feedback for the channel will show dB values in text while the
-  fader is being adjusted and then return the the name text.
+  fader is being adjusted and then return the name text. It can also be
+  set to send both position and gain or just position.
 </p>
 <h4>Debug:</h4>
+
+<figure>
+	<img alt="Debug Mode Dropdown" src="/images/osc-debug.png">
+	<figcaption>
+		Debug Mode Dropdown
+	</figcaption>
+</figure>
+
 <p>
-  For debugging purposes this allows logging either good OSC messages
-  Ardour receives or invalid messages received or none.
+  For debugging purposes this allows logging either all OSC messages
+  Ardour receives or invalid messages received or none. The last option:
+  <kbd class="menu">Print surface information to Log window</kbd> prints
+  the internal information that Ardour uses to create feedback for all
+  surfaces Ardour knows about.
 </p>
 <h4>Preset:</h4>
+
+<figure>
+	<img alt="Preset Loader" src="/images/osc-preset.png">
+	<figcaption>
+		Preset Loader
+	</figcaption>
+</figure>
+
 <p>
   Ardour now allows the use of preset settings. The default settings
   used are the settings from the last session or the factory defaults
   the first time OSC is enabled. As soon as any of these settings are
   changed, the Preset will change to "User" and the new settings will be
-  save to the osc directory Ardour configuration directory as
+  save to the osc directory in the
+  <a href="@@files-and-directories-ardour-knows-about">Ardour configuration directory</a> as
   <em>user.preset</em>. This preset file can be renamed for future use.
   It is suggested to also change the name value inside to avoid confusion
   in the preset listing. Ardour will ship with some of it's own presets
   that go with some popular OSC control and map combinations.
 </p>
 <h4>Clear OSC Devices</h4>
+<p class="note">
+	This button has been removed after Ardour 5.10. Instead this action
+	is triggered by any change in the settings.
+</p>
 <p>
   This button clears operating device profiles so that Ardour will reset
   all devices settings to use the new defaults from changed settings. a
@@ -93,10 +157,14 @@
   so having correct defaults allows one "Connect" button rather than 4.
 </p>
 <h3>Default Strip Types tab</h3>
-<p>
-<img alt="the Default Strip Types tab"
-     src="/images/osc-strip-types.png">
-</p>
+
+<figure>
+	<img alt="The Default Strip Types tab" src="/images/osc-strip-types.png">
+	<figcaption>
+		The Default Strip Types tab
+	</figcaption>
+</figure>
+
 <p>
   This allows selecting which of Ardour's mixer strips will be available
   for control. The Factory default is all strips except master, monitor
@@ -109,10 +177,14 @@
   controlled by a VCA are hidden, but one of those tracks needs a tweak.
 </p>
 <h3>Default Feedback tab</h3>
-<p>
-<img alt="the Default Feedback tab"
-     src="/images/osc-feedbackdefault.png">
-</p>
+
+<figure>
+	<img alt="The Default Feedback tab" src="/images/osc-feedbackdefault.png">
+	<figcaption>
+		The Default Feedback tab
+	</figcaption>
+</figure>
+
 <p>
   This allows setting up which controls provide feedback. The Factory
   default is none. If the controller is unable to receive feedback, this