X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F10_working-with-tracks%2F05_controlling-track-ordering%2F02_track-ordering-and-remote-control-ids.html;fp=_manual%2F10_working-with-tracks%2F05_controlling-track-ordering%2F02_track-ordering-and-remote-control-ids.html;h=0000000000000000000000000000000000000000;hb=8e3b4c710683de8f44cc46d5f00d9e19c0855527;hp=f258326684b63f0eedc7b6f3f618552fe769c607;hpb=33c301104caebd44a7aa6fd09d563fc8f622764d;p=ardour-manual-diverged
diff --git a/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html b/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html
deleted file mode 100644
index f258326..0000000
--- a/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html
+++ /dev/null
@@ -1,33 +0,0 @@
----
-layout: default
-title: Track Ordering and Remote Control IDs
----
-
-
- Every track and bus in Ardour is assigned a remote control ID.
- When a control surface or any other
- remote control is used to control Ardour, these IDs are used to identify
- which track(s) or buss(es) are the intended target of incoming commands.
-
-
- By default, remote IDs will be assigned to tracks and busses in the order
- that they are created, starting from 1. The master bus and monitor section
- have their own unique IDs (318 and 319).
-
-
- Ardour provides two methods to control remote control IDs, which can be
- chosen via :
-
-
- - follows order of mixer
- - This will reset the remote control IDs to match the mixer and editor
- track order order, starting with rcID 1. Manual assignment of rcIDs is
- not possible.
- - assigned by user
- - When enabled, the remote control ID is completely independent of the
- ordering in either window, and may be changed manually by the user via the
-
- dialog in each mixer strip.
-
-