Using OLA - Revision history

Kultex: /* How to setup an interface */

2011-12-10T18:43:06Z

‎How to setup an interface

66.92.11.32 at 22:15, 14 March 2010

2010-03-14T22:15:13Z

66.92.11.32 at 22:13, 14 March 2010

2010-03-14T22:13:52Z

Nomis52: /* How to setup an interface */

2009-08-08T21:41:14Z

‎How to setup an interface

Nomis52: /* How to setup an interface */

2009-08-03T02:09:22Z

‎How to setup an interface

Nomis52 at 02:07, 3 August 2009

2009-08-03T02:07:33Z

Nomis52: moved Using LLA to Using OLA

2009-08-03T02:02:46Z

moved Using LLA to Using OLA

216.239.45.4: /* How to start llad */

2009-03-02T19:59:25Z

‎How to start llad

Beier: Better headline

2008-11-13T09:03:24Z

Better headline

69.181.26.114 at 17:46, 13 October 2007

2007-10-13T17:46:06Z

@@ Line 86: / Line 86: @@
   Device 1: Stage Profi Device
     port 0, cap OUT, universe 1
 Finally the setup can be tested with '''ola_dmxconsole''' or '''ola_dmxmonitor''' to send or receive DMX values.

@@ Line 45: / Line 45: @@
   olad -l 3
-'''olad refused to run as root'''. If OLA doesn't work as a normal user it's due to incorrect permissions on files within /dev - look at the logs, fix the permission and try again.
+olad refuses to run as root. If OLA doesn't work as a normal user it's due to incorrect permissions on files within /dev - look at the logs, fix the permission and try again.
 === How to setup an interface ===

@@ Line 4: / Line 4: @@
 OLA consists of 4 parts:
- - the ola daemon (olad)
+* the ola daemon (olad)
- - the ola client library (libola for C++, OlaClient.py for Python)
+* the ola client library (libola for C++, OlaClient.py for Python)
- - various ola plugins (libolaX)
+* various ola plugins (libolaX)
- - example/client programs (ola_dev_info, ola_patch etc.)
+* example/client programs (ola_dev_info, ola_patch etc.)
 Most of the time you'll only need to deal with the daemon and the client programs.
@@ Line 35: / Line 35: @@
 In the general case you want to:
- - start the ola daemon
+* start the ola daemon
- - patch some output ports to universes
+* patch some output ports to universes
- - patch an input port or run a client application
+* patch an input port or run a client application
 === How to start olad ===

@@ Line 89: / Line 89: @@
 Finally the setup can be tested with '''ola_dmxconsole''' or '''ola_dmxmonitor''' to send or receive DMX values.
-Command line options can be seen [http://nomis52.net/?section=projects&sect2=lla&page=llatools here].
+Command line options are described at [[OLA Command Line Tools]].
 [[Category:Articles]]

@@ Line 49: / Line 49: @@
 === How to setup an interface ===
-Before an interface (e.g. a USB dongle) can be used, a ''port'' on the ''device'' must be ''patched'' to a ''universe''.
+Before an interface (e.g. a USB dongle) can be used, a ''port'' on the ''device'' must be ''patched'' to a ''universe''. This example uses the command line tools in the ola-examples package. If you built OLA with http support you can just use the web interface on http://localhost:9090
 First run ola_dev_info and find out what device / port the desired interface has:

@@ Line 1: / Line 1: @@
-== About LLA ==
+== About OLA ==
-[[LLA]] is a framework that allows applications to send and receive DMX using various hardware devices and DMX over IP protocols. Hardware devices and protocols can also be connected together and LLA will route the DMX between the two.
+[[OLA]] is a framework that allows applications to send and receive DMX using various hardware devices and DMX over IP protocols. Hardware devices and protocols can also be connected together and OLA will route the DMX data between the two.
-LLA consists of 4 parts:
+OLA consists of 4 parts:
-  - the lla daemon (llad)
+  - the ola daemon (olad)
-  - the lla client library (liblla)
+  - the ola client library (libola for C++, OlaClient.py for Python)
-  - various lla plugins (libllaX)
+  - various ola plugins (libolaX)
-  - example programs (lla_dev_info, lla_patch etc.)
+  - example/client programs (ola_dev_info, ola_patch etc.)
-== LLA Terminology ==
+Most of the time you'll only need to deal with the daemon and the client programs.
 ; Port (noun)
@@ Line 18: / Line 21: @@
 ; Plugin (noun)
-:A LLA plugin supports a group of physical devices or a DMX over IP protocol. Example plugins include ArtNet, ShowNet, EspNet, DmxUsbPro, OpenDmx, StageProfi, Dmx4Linux etc. On startup plugins look for the devices they are responsible for and set them up.
+:A OLA plugin supports a group of physical devices or a DMX over IP protocol. Example plugins include ArtNet, ShowNet, EspNet, DmxUsbPro, OpenDmx, StageProfi, Dmx4Linux etc. On start up the plugins look for the devices they are responsible for and set them up.
 ; Universe (noun)
@@ Line 24: / Line 27: @@
 ; Client (noun)
-: A client is another application that connects to LLA using liblla.
+: A client is another application that connects to OLA using libola.
 ; Patch (verb)
 : The act of assigning a port to a universe.
-== Using LLA ==
+== Using OLA ==
 In the general case you want to:
-  - start the lla daemon
+  - start the ola daemon
   - patch some output ports to universes
   - patch an input port or run a client application
-=== How to start llad ===
+=== How to start olad ===
-For testing run llad in non-forking, log to stdout, debug level 3:
+For testing run olad in non-forking, log to stdout, debug level 3:
-  llad -l 3
+  olad -l 3
-'''Do not run this as root'''. If LLA doesn't work as your user it's due to incorrect permissions on files within /dev - fix them and try again. I repeat do not run this as root.
+'''olad refused to run as root'''. If OLA doesn't work as a normal user it's due to incorrect permissions on files within /dev - look at the logs, fix the permission and try again.
 === How to setup an interface ===
@@ Line 48: / Line 51: @@
 Before an interface (e.g. a USB dongle) can be used, a ''port'' on the ''device'' must be ''patched'' to a ''universe''.
-First run lla_dev_info and find out what device / port the desired interface has:
+First run ola_dev_info and find out what device / port the desired interface has:
-  $ lla_dev_info
+  $ ola_dev_info
    Device 0: Art-Net Device
     port 0, cap IN
@@ Line 65: / Line 68: @@
 In this case we want to use the StageProfi device so we patch device 1, port 0 to a new universe (1)
-Then the command '''lla_patch''' can be given the numbers just found and the desired universe, so they get connected.
+Then the command '''ola_patch''' can be given the numbers just found and the desired universe, so they get connected.
-  lla_patch  -d 1 -p 0 -u 1
+  ola_patch  -d 1 -p 0 -u 1
-Running lla_dev_info again shows us the patch has been made:
+Running ola_dev_info again shows us the patch has been made:
-  $ lla_dev_info
+  $ ola_dev_info
    Device 0: Art-Net Device
     port 0, cap IN
@@ Line 84: / Line 87: @@
     port 0, cap OUT, universe 1
-Finally the setup can be tested with '''lla_dmxconsole''' or '''lla_dmxmonitor''' to set or receive DMX values.
+Finally the setup can be tested with '''ola_dmxconsole''' or '''ola_dmxmonitor''' to send or receive DMX values.
 Command line options can be seen [http://nomis52.net/?section=projects&sect2=lla&page=llatools here].
 [[Category:Articles]]

← Older revision	Revision as of 02:02, 3 August 2009
(No difference)

← Older revision		Revision as of 09:03, 13 November 2008
Line 1:		Line 1:
−	==~~= Using~~ LLA ===	+	== About LLA ==

	[[LLA]] is a framework that allows applications to send and receive DMX using various hardware devices and DMX over IP protocols. Hardware devices and protocols can also be connected together and LLA will route the DMX between the two.		[[LLA]] is a framework that allows applications to send and receive DMX using various hardware devices and DMX over IP protocols. Hardware devices and protocols can also be connected together and LLA will route the DMX between the two.