wiki.openlighting.org - User contributions [en]

OLA Device Specific Configuration

2019-05-22T20:31:38Z

DeepSymmetry: /* Mac */

==Anyma uDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the anyma dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="plugdev"
</pre>

==ArtNet ==

If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:

always_broadcast = true
==Streaming ACN / E1.31==

===All Platforms===
Some older networking gear only supports an old revision of E1.31 Called Revision 20. To use this older version you need to change a line in ola-e131.conf. Change this line
<pre>
revision = 0.46
</pre>
to this line
<pre>
revision = 0.2
</pre>
Only do this if the older gear cannot accept the standardized version of E1.31.

===Linux===
If you are planning to receive large amounts of multicast traffic 20+, you will need to adjust the maximum amount of igmp memberships.
Use the following command:
<pre>
echo <number_of_memberships> | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

For example this command sets the maximum number of igmp memberships to 256:
<pre>
echo 256 | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

==Eurolite USB DMX512 PRO==

===Linux===

Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like "Cannot claim device" and/or "another process has device opened for exclusive access". To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.

You may also need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04d8",ATTRS{idProduct}=="0xfa63", MODE="0660", GROUP="plugdev"
</pre>

===Mac===

Install the [http://code.google.com/p/open-lighting/downloads/detail?name=euroliteusbshield.dmg&can=2&q=#makechanges KEXT].

== General Purpose I/O ==

This has only been tested on a Raspberry Pi device. You can find information about the GPIO features on a Pi at [http://elinux.org/RPi_Low-level_peripherals elinux.org]

===Linux===

You'll need to export the GPIO pins. For example, to use pin 23, as root run:

<pre>
$ echo 23 > /sys/class/gpio/export
</pre>

You'll also need to ensure that the user olad runs as has permission to change the level of the Pins. Each of the following files should be writeable:

<pre>
/sys/class/gpio/gpio23/direction
/sys/class/gpio/gpio23/value
</pre>

You could for example do this by running the following as root (assuming olad is in the plugdev group, which you can check with "groups olad"); on later Raspberry Pi builds, this may fail, instead just add the olad user to the gpio group.
<pre>
chgrp plugdev /sys/class/gpio/gpio23/direction
chmod g+w /sys/class/gpio/gpio23/direction
chgrp plugdev /sys/class/gpio/gpio23/value
chmod g+w /sys/class/gpio/gpio23/value
</pre>

== Ja Rule ==

===Linux===

You need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules
<pre>
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="aced", GROUP="plugdev" MODE="660"
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="acee", GROUP="plugdev" MODE="660"
</pre>
== OSC ==

The message types are described in the [http://opensoundcontrol.org/spec-1_0 OSC Spec] .

=== Receiving DMX ===

The OSC plugin accepts a number of message formats:

{| border=1 cellspacing="0"
! Path !! OSC Message Type !! Data !! Comments
|-
|| /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| /path/N || 'i' || Slot value from 0 to 255 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path/N || 'f' || Slot value from 0.0 to 1.0 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path || 'ii' || Slot number from 0 to 511, slot value from 0 to 255 || Update a single slot.
|-
|| /path || 'if' || Slot number from 0 to 511, slot value from 0.0 to 1.0 || Update a single slot.
|}

=== Sending DMX ===

The following formats are available for sending data:

{| border=1 cellspacing="0"
! Config Option !! Path !! OSC Message Type !! Data !! Comments
|-
|| blob || /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| float_array || /path || N * 'f' || Slot values from 0.0 to 1.0 || Not quite as efficient as the blob type.
|-
|| int_array || /path || N * 'i' || Slot values from 0 to 255 || Not quite as efficient as the blob type.
|-
|| individual_float || /path/N || 'f' || Slot value from 0.0 to 1.0 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|-
|| individual_int || /path/N || 'i' || Slot value from 0 to 255 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|}

==Open DMX USB / FTDI RS485 ==

There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.

The Open DMX Plugin requires the dmx_usb kernel module, which means it's Linux only. The FTDI driver can be used on either Mac or Linux. See [https://www.openlighting.org/ola/get-help/ola-faq/#What_is_the_difference_between_the_different_USB_plugins here] for more info.

If you're having issues with the device failing to transmit DMX, these links might help:
*[http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/ http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/]
*[http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877 http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877]

=== Linux, Open DMX Kernel Module ===

Make sure the opendmx plugin is enabled.
Make sure the dmx_usb kernel module is loaded.

===Mac FTDI ===

You must have libftdi-dev installed before you run ./configure. Otherwise the FTDI DMX plugin won't show up in the list of OLA plugins.

Enable the FTDI driver (ola-ftdidmx ) and disable the USB Serial and Open DMX drivers (ola-usbserial.conf & ola-opendmx.conf)

=== Linux, FTDI ===

Same as Mac, but you also need to make sure that you add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules:

<pre>
# udev rules for ftdi devices
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev"
</pre>

==Scanlime Fadecandy==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the Scanlime Fadecandy device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1d50", ATTRS{idProduct}=="607a", GROUP="plugdev"
</pre>

== SPI ==

This plugin is designed for the Raspberry Pi. It may work on other hardware, but that's up to you. For instructions on the hardware side of things see [[OLA LED Pixels]].

Enable the spi-bcm2708 module, depending on the version of Raspbian you're running it will either be via Device Tree or by editing /etc/modprobe.d/raspi-blacklist.conf.

For recent versions you can use raspi-config's Advanced Options then SPI, see here for more info:
https://www.raspberrypi.org/documentation/configuration/raspi-config.md

Or alternatively by manually enabling the SPI Device Tree by uncommenting the dtparam=spi=on line in /boot/config.txt as explained here:
https://www.raspberrypi.org/documentation/configuration/device-tree.md

For older machines, edit /etc/modprobe.d/raspi-blacklist.conf and comment out the "blacklist spi-bcm2708" line. The file should look something like this:

<pre>
# blacklist spi and i2c by default (many users don't need them)

#blacklist spi-bcm2708
blacklist i2c-bcm2708
</pre>

In both cases, to allow non-root access, add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/99-spi.rules

<pre>
SUBSYSTEM=="spidev", MODE="0666"
</pre>

==StageProfi==

This comes in two flavors, a USB model and an Ethernet/IP model.

device = /dev/ttyUSB0
device = 192.168.1.250

==UART native DMX==

===Linux===

====Raspberry Pi====

First stop anything else using the serial port; either use raspi-config (Advanced Options, Serial) or follow the instructions here:

[http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port]

To make this work, you will also need to raise the Pi's UART clock, because the default one maxes out at 115kbaud. So you will need to add

<pre>
init_uart_clock=16000000
</pre>

to the /boot/config.txt file on the system. This won't affect any other user of the serial port provided you have a recent kernel.

Another useful link is [http://fw.hardijzer.nl/?p=138 http://fw.hardijzer.nl/?p=138].

=====Raspberry Pi 3=====
For the Raspberry Pi 3 you need to disable Bluetooth and reclaim the PL011 UART from it.

Add:
dtoverlay=pi3-disable-bt
to your config.txt file in the /boot directory.

According to this, you can also swap them, so Bluetooth uses the software UART:
[http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/ http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/]

If you use this instead:
dtoverlay=pi3-miniuart-bt

==USB Pro (including EntTec)==

===Mac===

Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm

After a restart run:

ls /dev/cu.usbserial-*

Make sure your ~/.ola/ola-usbserial.conf file matches the path above:

device_dir = /dev
device_prefix = ttyUSB
device_prefix = cu.usbserial-

i.e. Look for devices at /dev/ttyUSB* , /dev/cu.usbserial-*

<blockquote>Note that, at least in MacOS Mojave, it may be necessary to reboot if you ever disconnect the DMX interface and want to use it another time. There has been at least one incident of the /dev/cu.usbserial-* device disappearing until reboot under 10.14.5 on a 2018 MacBook Pro.</blockquote>

OLA also comes with a tool to update the firmware on a USB Pro:

./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f <firmware_file>

==DMXter4 RDM and MiniDMXter 4==
Navigate to "RDM Controller" in the menu. Then press <LEFT> and <RIGHT> together, then also press <YES/Q>, then release <YES/Q>, finally release <LEFT> and <RIGHT>. It will then show USB DONGLE MODE and be discoverable in OLA.

==USBDMX2==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the usbdmx2 dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0962", GROUP="plugdev"
</pre>

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

===Mac===

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

==Velleman VM166 / K8062==

===Mac===

If you're installed from source you'll need the codeless KEXT which is available for [http://downloads.openlighting.org/Velleman%20kext.dmg OS X 10.9 and above] or [http://code.google.com/p/open-lighting/downloads/detail?name=libdmxusbshield.dmg OS 10.8 and below]. If you installed OLA from the mac binary package this is already included.

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the velleman dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="8062", GROUP="plugdev"
</pre>

Then make sure the user olad runs as is a member of plugdev.

Some people have reported issues with the K8062 on Ubuntu 14.04.
Symptoms: When you plug in your K8062, Ubuntu responds with Kernel Panic.
Problem: comedi and vmk60xx kernel modules are loaded and crash the kernel.
Solution: WARNING! Attempt at your own risk.
# Blacklist comedi and vmk60xx in /etc/modprobe.d/blacklist.conf, see [https://wiki.debian.org/KernelModuleBlacklisting https://wiki.debian.org/KernelModuleBlacklisting]
# Reboot and then run lsusb in the terminal. (Make sure K8062 is connected.)
# After a short hang, the K8062 should come up as "Velleman Components, Inc."

==KarateLight, KarateDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/81-karate.rules

<pre>
# udev rules file for the karate-device
KERNEL=="ttyACM?", ATTRS{product}=="DMX2USB simple", SYMLINK+="kldmx0"
</pre>
Then make sure the user olad runs as is a member of 'dialout' which is the default group owning ttyACM?.

OLA Device Specific Configuration

2019-05-21T18:18:42Z

DeepSymmetry: /* Mac */

==Anyma uDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the anyma dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="plugdev"
</pre>

==ArtNet ==

If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:

always_broadcast = true
==Streaming ACN / E1.31==

===All Platforms===
Some older networking gear only supports an old revision of E1.31 Called Revision 20. To use this older version you need to change a line in ola-e131.conf. Change this line
<pre>
revision = 0.46
</pre>
to this line
<pre>
revision = 0.2
</pre>
Only do this if the older gear cannot accept the standardized version of E1.31.

===Linux===
If you are planning to receive large amounts of multicast traffic 20+, you will need to adjust the maximum amount of igmp memberships.
Use the following command:
<pre>
echo <number_of_memberships> | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

For example this command sets the maximum number of igmp memberships to 256:
<pre>
echo 256 | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

==Eurolite USB DMX512 PRO==

===Linux===

Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like "Cannot claim device" and/or "another process has device opened for exclusive access". To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.

You may also need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04d8",ATTRS{idProduct}=="0xfa63", MODE="0660", GROUP="plugdev"
</pre>

===Mac===

Install the [http://code.google.com/p/open-lighting/downloads/detail?name=euroliteusbshield.dmg&can=2&q=#makechanges KEXT].

== General Purpose I/O ==

This has only been tested on a Raspberry Pi device. You can find information about the GPIO features on a Pi at [http://elinux.org/RPi_Low-level_peripherals elinux.org]

===Linux===

You'll need to export the GPIO pins. For example, to use pin 23, as root run:

<pre>
$ echo 23 > /sys/class/gpio/export
</pre>

You'll also need to ensure that the user olad runs as has permission to change the level of the Pins. Each of the following files should be writeable:

<pre>
/sys/class/gpio/gpio23/direction
/sys/class/gpio/gpio23/value
</pre>

You could for example do this by running the following as root (assuming olad is in the plugdev group, which you can check with "groups olad"); on later Raspberry Pi builds, this may fail, instead just add the olad user to the gpio group.
<pre>
chgrp plugdev /sys/class/gpio/gpio23/direction
chmod g+w /sys/class/gpio/gpio23/direction
chgrp plugdev /sys/class/gpio/gpio23/value
chmod g+w /sys/class/gpio/gpio23/value
</pre>

== Ja Rule ==

===Linux===

You need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules
<pre>
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="aced", GROUP="plugdev" MODE="660"
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="acee", GROUP="plugdev" MODE="660"
</pre>
== OSC ==

The message types are described in the [http://opensoundcontrol.org/spec-1_0 OSC Spec] .

=== Receiving DMX ===

The OSC plugin accepts a number of message formats:

{| border=1 cellspacing="0"
! Path !! OSC Message Type !! Data !! Comments
|-
|| /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| /path/N || 'i' || Slot value from 0 to 255 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path/N || 'f' || Slot value from 0.0 to 1.0 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path || 'ii' || Slot number from 0 to 511, slot value from 0 to 255 || Update a single slot.
|-
|| /path || 'if' || Slot number from 0 to 511, slot value from 0.0 to 1.0 || Update a single slot.
|}

=== Sending DMX ===

The following formats are available for sending data:

{| border=1 cellspacing="0"
! Config Option !! Path !! OSC Message Type !! Data !! Comments
|-
|| blob || /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| float_array || /path || N * 'f' || Slot values from 0.0 to 1.0 || Not quite as efficient as the blob type.
|-
|| int_array || /path || N * 'i' || Slot values from 0 to 255 || Not quite as efficient as the blob type.
|-
|| individual_float || /path/N || 'f' || Slot value from 0.0 to 1.0 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|-
|| individual_int || /path/N || 'i' || Slot value from 0 to 255 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|}

==Open DMX USB / FTDI RS485 ==

There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.

The Open DMX Plugin requires the dmx_usb kernel module, which means it's Linux only. The FTDI driver can be used on either Mac or Linux. See [https://www.openlighting.org/ola/get-help/ola-faq/#What_is_the_difference_between_the_different_USB_plugins here] for more info.

If you're having issues with the device failing to transmit DMX, these links might help:
*[http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/ http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/]
*[http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877 http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877]

=== Linux, Open DMX Kernel Module ===

Make sure the opendmx plugin is enabled.
Make sure the dmx_usb kernel module is loaded.

===Mac FTDI ===

You must have libftdi-dev installed before you run ./configure. Otherwise the FTDI DMX plugin won't show up in the list of OLA plugins.

Enable the FTDI driver (ola-ftdidmx ) and disable the USB Serial and Open DMX drivers (ola-usbserial.conf & ola-opendmx.conf)

=== Linux, FTDI ===

Same as Mac, but you also need to make sure that you add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules:

<pre>
# udev rules for ftdi devices
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev"
</pre>

==Scanlime Fadecandy==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the Scanlime Fadecandy device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1d50", ATTRS{idProduct}=="607a", GROUP="plugdev"
</pre>

== SPI ==

This plugin is designed for the Raspberry Pi. It may work on other hardware, but that's up to you. For instructions on the hardware side of things see [[OLA LED Pixels]].

Enable the spi-bcm2708 module, depending on the version of Raspbian you're running it will either be via Device Tree or by editing /etc/modprobe.d/raspi-blacklist.conf.

For recent versions you can use raspi-config's Advanced Options then SPI, see here for more info:
https://www.raspberrypi.org/documentation/configuration/raspi-config.md

Or alternatively by manually enabling the SPI Device Tree by uncommenting the dtparam=spi=on line in /boot/config.txt as explained here:
https://www.raspberrypi.org/documentation/configuration/device-tree.md

For older machines, edit /etc/modprobe.d/raspi-blacklist.conf and comment out the "blacklist spi-bcm2708" line. The file should look something like this:

<pre>
# blacklist spi and i2c by default (many users don't need them)

#blacklist spi-bcm2708
blacklist i2c-bcm2708
</pre>

In both cases, to allow non-root access, add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/99-spi.rules

<pre>
SUBSYSTEM=="spidev", MODE="0666"
</pre>

==StageProfi==

This comes in two flavors, a USB model and an Ethernet/IP model.

device = /dev/ttyUSB0
device = 192.168.1.250

==UART native DMX==

===Linux===

====Raspberry Pi====

First stop anything else using the serial port; either use raspi-config (Advanced Options, Serial) or follow the instructions here:

[http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port]

To make this work, you will also need to raise the Pi's UART clock, because the default one maxes out at 115kbaud. So you will need to add

<pre>
init_uart_clock=16000000
</pre>

to the /boot/config.txt file on the system. This won't affect any other user of the serial port provided you have a recent kernel.

Another useful link is [http://fw.hardijzer.nl/?p=138 http://fw.hardijzer.nl/?p=138].

=====Raspberry Pi 3=====
For the Raspberry Pi 3 you need to disable Bluetooth and reclaim the PL011 UART from it.

Add:
dtoverlay=pi3-disable-bt
to your config.txt file in the /boot directory.

According to this, you can also swap them, so Bluetooth uses the software UART:
[http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/ http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/]

If you use this instead:
dtoverlay=pi3-miniuart-bt

==USB Pro (including EntTec)==

===Mac===

Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm

After a restart run:

ls /dev/cu.usbserial-*

Make sure your ~/.ola/ola-usbserial.conf file matches the path above:

device_dir = /dev
device_prefix = ttyUSB
device_prefix = cu.usbserial-

i.e. Look for devices at /dev/ttyUSB* , /dev/cu.usbserial-*

<blockquote>Note that, at least in MacOS Mojave, it may be necessary to re-install the drivers after installing a system update from Apple. There has been at least one incident of the /dev/cu.usbserial-* device disappearing when updating to 10.14.5.</blockquote>

OLA also comes with a tool to update the firmware on a USB Pro:

./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f <firmware_file>

==DMXter4 RDM and MiniDMXter 4==
Navigate to "RDM Controller" in the menu. Then press <LEFT> and <RIGHT> together, then also press <YES/Q>, then release <YES/Q>, finally release <LEFT> and <RIGHT>. It will then show USB DONGLE MODE and be discoverable in OLA.

==USBDMX2==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the usbdmx2 dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0962", GROUP="plugdev"
</pre>

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

===Mac===

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

==Velleman VM166 / K8062==

===Mac===

If you're installed from source you'll need the codeless KEXT which is available for [http://downloads.openlighting.org/Velleman%20kext.dmg OS X 10.9 and above] or [http://code.google.com/p/open-lighting/downloads/detail?name=libdmxusbshield.dmg OS 10.8 and below]. If you installed OLA from the mac binary package this is already included.

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the velleman dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="8062", GROUP="plugdev"
</pre>

Then make sure the user olad runs as is a member of plugdev.

Some people have reported issues with the K8062 on Ubuntu 14.04.
Symptoms: When you plug in your K8062, Ubuntu responds with Kernel Panic.
Problem: comedi and vmk60xx kernel modules are loaded and crash the kernel.
Solution: WARNING! Attempt at your own risk.
# Blacklist comedi and vmk60xx in /etc/modprobe.d/blacklist.conf, see [https://wiki.debian.org/KernelModuleBlacklisting https://wiki.debian.org/KernelModuleBlacklisting]
# Reboot and then run lsusb in the terminal. (Make sure K8062 is connected.)
# After a short hang, the K8062 should come up as "Velleman Components, Inc."

==KarateLight, KarateDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/81-karate.rules

<pre>
# udev rules file for the karate-device
KERNEL=="ttyACM?", ATTRS{product}=="DMX2USB simple", SYMLINK+="kldmx0"
</pre>
Then make sure the user olad runs as is a member of 'dialout' which is the default group owning ttyACM?.

OLA Device Specific Configuration

2019-05-21T17:38:24Z

DeepSymmetry: /* USB Pro (including EntTec) */

==Anyma uDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the anyma dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="plugdev"
</pre>

==ArtNet ==

If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:

always_broadcast = true
==Streaming ACN / E1.31==

===All Platforms===
Some older networking gear only supports an old revision of E1.31 Called Revision 20. To use this older version you need to change a line in ola-e131.conf. Change this line
<pre>
revision = 0.46
</pre>
to this line
<pre>
revision = 0.2
</pre>
Only do this if the older gear cannot accept the standardized version of E1.31.

===Linux===
If you are planning to receive large amounts of multicast traffic 20+, you will need to adjust the maximum amount of igmp memberships.
Use the following command:
<pre>
echo <number_of_memberships> | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

For example this command sets the maximum number of igmp memberships to 256:
<pre>
echo 256 | sudo tee /proc/sys/net/ipv4/igmp_max_memberships
</pre>

==Eurolite USB DMX512 PRO==

===Linux===

Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like "Cannot claim device" and/or "another process has device opened for exclusive access". To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.

You may also need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04d8",ATTRS{idProduct}=="0xfa63", MODE="0660", GROUP="plugdev"
</pre>

===Mac===

Install the [http://code.google.com/p/open-lighting/downloads/detail?name=euroliteusbshield.dmg&can=2&q=#makechanges KEXT].

== General Purpose I/O ==

This has only been tested on a Raspberry Pi device. You can find information about the GPIO features on a Pi at [http://elinux.org/RPi_Low-level_peripherals elinux.org]

===Linux===

You'll need to export the GPIO pins. For example, to use pin 23, as root run:

<pre>
$ echo 23 > /sys/class/gpio/export
</pre>

You'll also need to ensure that the user olad runs as has permission to change the level of the Pins. Each of the following files should be writeable:

<pre>
/sys/class/gpio/gpio23/direction
/sys/class/gpio/gpio23/value
</pre>

You could for example do this by running the following as root (assuming olad is in the plugdev group, which you can check with "groups olad"); on later Raspberry Pi builds, this may fail, instead just add the olad user to the gpio group.
<pre>
chgrp plugdev /sys/class/gpio/gpio23/direction
chmod g+w /sys/class/gpio/gpio23/direction
chgrp plugdev /sys/class/gpio/gpio23/value
chmod g+w /sys/class/gpio/gpio23/value
</pre>

== Ja Rule ==

===Linux===

You need the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules
<pre>
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="aced", GROUP="plugdev" MODE="660"
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="acee", GROUP="plugdev" MODE="660"
</pre>
== OSC ==

The message types are described in the [http://opensoundcontrol.org/spec-1_0 OSC Spec] .

=== Receiving DMX ===

The OSC plugin accepts a number of message formats:

{| border=1 cellspacing="0"
! Path !! OSC Message Type !! Data !! Comments
|-
|| /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| /path/N || 'i' || Slot value from 0 to 255 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path/N || 'f' || Slot value from 0.0 to 1.0 || Update a single slot. N is the slot number from 1 - 512.
|-
|| /path || 'ii' || Slot number from 0 to 511, slot value from 0 to 255 || Update a single slot.
|-
|| /path || 'if' || Slot number from 0 to 511, slot value from 0.0 to 1.0 || Update a single slot.
|}

=== Sending DMX ===

The following formats are available for sending data:

{| border=1 cellspacing="0"
! Config Option !! Path !! OSC Message Type !! Data !! Comments
|-
|| blob || /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.
|-
|| float_array || /path || N * 'f' || Slot values from 0.0 to 1.0 || Not quite as efficient as the blob type.
|-
|| int_array || /path || N * 'i' || Slot values from 0 to 255 || Not quite as efficient as the blob type.
|-
|| individual_float || /path/N || 'f' || Slot value from 0.0 to 1.0 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|-
|| individual_int || /path/N || 'i' || Slot value from 0 to 255 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this.
|}

==Open DMX USB / FTDI RS485 ==

There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.

The Open DMX Plugin requires the dmx_usb kernel module, which means it's Linux only. The FTDI driver can be used on either Mac or Linux. See [https://www.openlighting.org/ola/get-help/ola-faq/#What_is_the_difference_between_the_different_USB_plugins here] for more info.

If you're having issues with the device failing to transmit DMX, these links might help:
*[http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/ http://stevenbreuls.com/2014/04/dmx-rs485-wrong-board-fix/]
*[http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877 http://falconchristmas.com/forum/index.php/topic,858.msg9877.html#msg9877]

=== Linux, Open DMX Kernel Module ===

Make sure the opendmx plugin is enabled.
Make sure the dmx_usb kernel module is loaded.

===Mac FTDI ===

You must have libftdi-dev installed before you run ./configure. Otherwise the FTDI DMX plugin won't show up in the list of OLA plugins.

Enable the FTDI driver (ola-ftdidmx ) and disable the USB Serial and Open DMX drivers (ola-usbserial.conf & ola-opendmx.conf)

=== Linux, FTDI ===

Same as Mac, but you also need to make sure that you add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules:

<pre>
# udev rules for ftdi devices
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev"
</pre>

==Scanlime Fadecandy==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the Scanlime Fadecandy device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="1d50", ATTRS{idProduct}=="607a", GROUP="plugdev"
</pre>

== SPI ==

This plugin is designed for the Raspberry Pi. It may work on other hardware, but that's up to you. For instructions on the hardware side of things see [[OLA LED Pixels]].

Enable the spi-bcm2708 module, depending on the version of Raspbian you're running it will either be via Device Tree or by editing /etc/modprobe.d/raspi-blacklist.conf.

For recent versions you can use raspi-config's Advanced Options then SPI, see here for more info:
https://www.raspberrypi.org/documentation/configuration/raspi-config.md

Or alternatively by manually enabling the SPI Device Tree by uncommenting the dtparam=spi=on line in /boot/config.txt as explained here:
https://www.raspberrypi.org/documentation/configuration/device-tree.md

For older machines, edit /etc/modprobe.d/raspi-blacklist.conf and comment out the "blacklist spi-bcm2708" line. The file should look something like this:

<pre>
# blacklist spi and i2c by default (many users don't need them)

#blacklist spi-bcm2708
blacklist i2c-bcm2708
</pre>

In both cases, to allow non-root access, add the following [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/99-spi.rules

<pre>
SUBSYSTEM=="spidev", MODE="0666"
</pre>

==StageProfi==

This comes in two flavors, a USB model and an Ethernet/IP model.

device = /dev/ttyUSB0
device = 192.168.1.250

==UART native DMX==

===Linux===

====Raspberry Pi====

First stop anything else using the serial port; either use raspi-config (Advanced Options, Serial) or follow the instructions here:

[http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port]

To make this work, you will also need to raise the Pi's UART clock, because the default one maxes out at 115kbaud. So you will need to add

<pre>
init_uart_clock=16000000
</pre>

to the /boot/config.txt file on the system. This won't affect any other user of the serial port provided you have a recent kernel.

Another useful link is [http://fw.hardijzer.nl/?p=138 http://fw.hardijzer.nl/?p=138].

=====Raspberry Pi 3=====
For the Raspberry Pi 3 you need to disable Bluetooth and reclaim the PL011 UART from it.

Add:
dtoverlay=pi3-disable-bt
to your config.txt file in the /boot directory.

According to this, you can also swap them, so Bluetooth uses the software UART:
[http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/ http://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/]

If you use this instead:
dtoverlay=pi3-miniuart-bt

==USB Pro (including EntTec)==

===Mac===

Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm

After a restart run:

ls /dev/cu.usbserial-*

Make sure your ~/.ola/ola-usbserial.conf file matches the path above:

device_dir = /dev
device_prefix = ttyUSB
device_prefix = cu.usbserial-

i.e. Look for devices at /dev/ttyUSB* , /dev/cu.usbserial-*

OLA also comes with a tool to update the firmware on a USB Pro:

./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f <firmware_file>

==DMXter4 RDM and MiniDMXter 4==
Navigate to "RDM Controller" in the menu. Then press <LEFT> and <RIGHT> together, then also press <YES/Q>, then release <YES/Q>, finally release <LEFT> and <RIGHT>. It will then show USB DONGLE MODE and be discoverable in OLA.

==USBDMX2==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the usbdmx2 dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0962", GROUP="plugdev"
</pre>

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

===Mac===

There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.

==Velleman VM166 / K8062==

===Mac===

If you're installed from source you'll need the codeless KEXT which is available for [http://downloads.openlighting.org/Velleman%20kext.dmg OS X 10.9 and above] or [http://code.google.com/p/open-lighting/downloads/detail?name=libdmxusbshield.dmg OS 10.8 and below]. If you installed OLA from the mac binary package this is already included.

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules

<pre>
# udev rules file for the velleman dmx device
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="8062", GROUP="plugdev"
</pre>

Then make sure the user olad runs as is a member of plugdev.

Some people have reported issues with the K8062 on Ubuntu 14.04.
Symptoms: When you plug in your K8062, Ubuntu responds with Kernel Panic.
Problem: comedi and vmk60xx kernel modules are loaded and crash the kernel.
Solution: WARNING! Attempt at your own risk.
# Blacklist comedi and vmk60xx in /etc/modprobe.d/blacklist.conf, see [https://wiki.debian.org/KernelModuleBlacklisting https://wiki.debian.org/KernelModuleBlacklisting]
# Reboot and then run lsusb in the terminal. (Make sure K8062 is connected.)
# After a short hang, the K8062 should come up as "Velleman Components, Inc."

==KarateLight, KarateDMX==

===Linux===

You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/81-karate.rules

<pre>
# udev rules file for the karate-device
KERNEL=="ttyACM?", ATTRS{product}=="DMX2USB simple", SYMLINK+="kldmx0"
</pre>
Then make sure the user olad runs as is a member of 'dialout' which is the default group owning ttyACM?.

OLA Install Using MacPorts

2016-01-05T23:01:41Z

DeepSymmetry: Update Xcode download instructions, mention Homebrew alternative

Installing [[OLA]] using MacPorts is very easy. It can take a while the first time because you may need to download XCode and the OLA dependencies.

: If you are not already using MacPorts for other reasons, you may want to consider using the more modern Homebrew package manager instead, and see [[OLA Install Using Homebrew]]. Homebrew is simpler to install and maintain, especially across OS upgrades, and tends to have a better selection and more up-to-date packages.

* Install [http://developer.apple.com/technology/xcode.html Xcode]. Recent releases have returned to being free downloads.
* Install [http://www.macports.org/install.php MacPorts], by following the instructions on the MacPorts site. You don't need to install X11.
* Install OLA and all the dependancies by running

sudo port install ola

This will take a while the first time as it downloads and installs everything. Once it's complete you can continue to [[Using OLA]]
== Variants ==

There are different features that can be turned on or off. In the MacPorts world these are known as [http://guide.macports.org/#development.variants variants]. The default is to enable all of the commonly used features so you shouldn't need to change this. You can see what variants are available for ola by running

port variants ola

For 0.8.18 this is what you get:

<pre>
[+]http: Build with embedded web server
[+]libusb: Build with libusb support
python26: Enable the Python 2.6 API
* conflicts with python27
[+]python27: Enable the Python 2.7 API
* conflicts with python26
universal: Build for multiple architectures
</pre>

The + sign means the variant is enabled. In this instance the ola port will be built with support for the web interface, libusb support and the Python 2.7 client libraries.

== Updating ==

You can subscribe to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting-announce Open Lighting Announce] list to be notified of new releases. To update simply run:

<pre>
sudo port selfupdate
sudo port upgrade outdated
</pre>

OLA Install Using Homebrew

2016-01-05T22:52:10Z

DeepSymmetry: Macintosh install instructions using the Homebrew package manager

Installing [[OLA]] on the Mac using Homebrew is very easy. It can take a while the first time because you may need to download XCode and the OLA dependencies, which is true regardless of the installation approach you choose. But from then on, updating to new releases is very fast.

* If you don’t already have Homebrew, you will need to start by [http://brew.sh installing that]
* Install OLA and all its dependencies by running:
<pre>
brew install ola
</pre>

This will take a while the first time as it downloads and installs everything. Once it's complete you can continue to [[Using OLA]].

== Updating ==

You can subscribe to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting-announce Open Lighting Announce] list to be notified of new releases. To update simply run:

<pre>
brew update
brew upgrade --all
</pre>

Afterglow

2015-08-10T03:52:24Z

DeepSymmetry:

[[Image:Afterglow-logo.png|right|frameless|128px]]

Afterglow on GitHub: https://github.com/brunchboy/afterglow#afterglow 
Afterglow [https://github.com/brunchboy/afterglow/blob/master/doc/README.adoc#afterglow-documentation documentation],
[http://deepsymmetry.org/afterglow/doc/index.html API documentation], and [https://github.com/brunchboy/afterglow/wiki wiki] 
Clojars library page: https://clojars.org/afterglow 
Current version: 0.1.2 

{{Features|osx=yes|linux=yes|win=yes|tx=yes|free=yes|midi=yes|osc=yes}}
 

An environment supporting [https://en.wikipedia.org/wiki/Live_coding live coding] for the creation of light shows in [http://clojure.org/ Clojure] with the help of [[OLA]].

== Target Audience ==

Afterglow is aimed at people who want to be able to craft light shows by designing and tweaking algorithms in real time while the show is running. Beyond being designed to allow you to inject your own code right into the frame rendering process, there are several ways that Afterglow differs from other lighting control software you may have encountered. The early stages of its [https://github.com/brunchboy/afterglow/blob/master/doc/rendering_loop.adoc#the-rendering-loop rendering loop] can work with higher levels of abstraction than the typical DMX [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#channel-effects channel value] or [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#function-effects fixture function] (although those are well supported too):

== Features ==

* You can express your desired results in terms of an abstract [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#color-effects color], including support for the hue-saturation-lightness model, which is great for algorithmic looks, and have it translated to whatever color channels (or color wheel) your fixture supports.

* Groups of moving heads can be told to face particular [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#direction-effects directions] by specifying parameterized vectors, or to [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#aim-effects aim] at a particular point in space, and Afterglow figures out how to translate that into DMX control values given its understanding of the [https://github.com/brunchboy/afterglow/blob/master/doc/fixture_definitions.adoc#fixture-definitions fixture] and [https://github.com/brunchboy/afterglow/blob/master/doc/show_space.adoc#show-space where], and at what angle, you hung it.

* There are a variety of [https://github.com/brunchboy/afterglow/blob/master/doc/oscillators.adoc#oscillators oscillators] which can efficiently drive effect parameters.

* You can also create [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#complex-effects complex effects], with [https://github.com/brunchboy/afterglow/blob/master/doc/parameters.adoc#dynamic-parameters adjustable parameters] that can be controlled through a rich binding to an [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#using-ableton-push Ableton Push] controller. There is also a [https://github.com/brunchboy/afterglow/blob/master/doc/README.adoc#the-embedded-web-interface web interface] for show control, and lower-level bindings can be created via [[MIDI]] and [[OSC]]. Rich bindings to other control surfaces will be added as development progresses, and are welcomed from others.

* The timing of effects is pervasively influenced by a deep notion of [https://github.com/brunchboy/afterglow/blob/master/doc/metronomes.adoc#metronomes musical time], with support for synchronization via [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#syncing-to-midi-clock MIDI clock] or Pioneer [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#syncing-to-pro-dj-link Pro DJ Link] beat grids.

* You can even host Afterglow within [https://cycling74.com/ Cycling ‘74’s Max] visual interactive environment, through the related [https://github.com/brunchboy/afterglow-max#afterglow-max afterglow-max] project.

== Diving In ==

As suggested by its version number, Afterglow is still at an early stage of development, and is growing rapidly. It is already able to create beautiful effects, and the experience of controlling them through the pressure sensitive pads on the Push, while tweaking them through a REPL, is quite a trip. If anyone is interested in exploring it, the author is eager to help with the setup process and the creation of new fixture definitions for early adopters. Feedback about the documentation or any aspect of the system is warmly welcomed.

== Related Projects ==
* [[OLA]]
* [https://github.com/brunchboy/afterglow-max#afterglow-max afterglow-max]

[[Category:Controllers]]

LanBox-LCX

2015-08-08T20:08:09Z

DeepSymmetry: Fix broken link

Link: http://www.lanbox.com/products/LCXDataSheet.html 
Made by: [[CDS Advanced Technology bv]] 
{{Features|tx=yes|rx=yes|midi=yes}}
[[Image:Wf240.jpg|right]]

The LanBox-LCX is an extremely versatile DMX controller suited for nearly any [[DMX512-A]] lighting application. Whether it should run a show stand-alone, controlling up to 6 universes (3072 DMX channels) using an Ethernet network, synchronized via MIDI or connected to a notebook via USB, with the LanBox-LCX it's all possible!

The LanBox-LCX has USB, Ethernet and MIDI ports which can be used for communication with e.g. LCedit+, but also for show control using [[MIDI]]. The DMX input can be used to grab and/or merge the DMX data from your favorite lighting console.

[[Category:Other]]

DMX Music Visualization

2015-08-08T20:05:08Z

DeepSymmetry: Fix broken link

This software uses internationally patented technology for controlling lighting technology by audio signals (LTCA). It can cleverly control all of the lighting technology direcly by music. The most widespread DMX512 protocol is used to control the lighting technology. Version of Music Visualization that allows for controlling the first 10 DMX channels is available for download for free.

For Music Visualization to be fully functional any ordinary PC with a sound card and USB port is entirely sufficitent. Music analysis is done in the backround from any input or output (e.g. microphone input, line input or any application such as Windows Media Player, WinAmp and others). The software is primarily targeted at clubs, discos and live music. There is no need for any adjustments during the whole of music performance. The software can distinguish different music genres, styles and changes of tempo. Only good initial setting of the software and the configuration of the connected lighting technlogy is necessary for the variations in music to become visual. The control and the whole scene can be manually adjusted using for example DJ buttons or wireless controller.

Works with interfaces:

* [[DMX PIPE]]
* [[USB-DMX512 Module]]
* [[Open DMX USB]] (only free version)
* [[ArtNet]]

Link: http://www.soh.cz/en/download/music-visualization

[[Category:Controllers]]

Afterglow

2015-08-08T19:53:52Z

DeepSymmetry: Create initial page

[[Image:Afterglow-logo.png|right|frameless|128px]]

Afterglow on GitHub: https://github.com/brunchboy/afterglow#afterglow 
Afterglow [https://github.com/brunchboy/afterglow/blob/master/doc/README.adoc#afterglow-documentation documentation],
[http://deepsymmetry.org/afterglow/doc/index.html API documentation], and [https://github.com/brunchboy/afterglow/wiki wiki] 
Clojars library page: https://clojars.org/afterglow 
Current version: 0.1.1 

{{Features|osx=yes|linux=yes|win=yes|tx=yes|free=yes|midi=yes|osc=yes}}
 

An environment supporting [https://en.wikipedia.org/wiki/Live_coding live coding] for the creation of light shows in [http://clojure.org/ Clojure] with the help of [[OLA]].

== Target Audience ==

Afterglow is aimed at people who want to be able to craft light shows by designing and tweaking algorithms in real time while the show is running. Beyond being designed to allow you to inject your own code right into the frame rendering process, there are several ways that Afterglow differs from other lighting control software you may have encountered. The early stages of its [https://github.com/brunchboy/afterglow/blob/master/doc/rendering_loop.adoc#the-rendering-loop rendering loop] can work with higher levels of abstraction than the typical DMX [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#channel-effects channel value] or [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#function-effects fixture function] (although those are well supported too):

== Features ==

* You can express your desired results in terms of an abstract [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#color-effects color], including support for the hue-saturation-lightness model, which is great for algorithmic looks, and have it translated to whatever color channels (or color wheel) your fixture supports.

* Groups of moving heads can be told to face particular [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#direction-effects directions] by specifying parameterized vectors, or to [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#aim-effects aim] at a particular point in space, and Afterglow figures out how to translate that into DMX control values given its understanding of the [https://github.com/brunchboy/afterglow/blob/master/doc/fixture_definitions.adoc#fixture-definitions fixture] and [https://github.com/brunchboy/afterglow/blob/master/doc/show_space.adoc#show-space where], and at what angle, you hung it.

* There are a variety of [https://github.com/brunchboy/afterglow/blob/master/doc/oscillators.adoc#oscillators oscillators] which can efficiently drive effect parameters.

* You can also create [https://github.com/brunchboy/afterglow/blob/master/doc/effects.adoc#complex-effects complex effects], with [https://github.com/brunchboy/afterglow/blob/master/doc/parameters.adoc#dynamic-parameters adjustable parameters] that can be controlled through a rich binding to an [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#using-ableton-push Ableton Push] controller. There is also a [https://github.com/brunchboy/afterglow/blob/master/doc/README.adoc#the-embedded-web-interface web interface] for show control, and lower-level bindings can be created via [[MIDI]] and [[OSC]]. Rich bindings to other control surfaces will be added as development progresses, and are welcomed from others.

* The timing of effects is pervasively influenced by a deep notion of [https://github.com/brunchboy/afterglow/blob/master/doc/metronomes.adoc#metronomes musical time], with support for synchronization via [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#syncing-to-midi-clock MIDI clock] or Pioneer [https://github.com/brunchboy/afterglow/blob/master/doc/mapping_sync.adoc#syncing-to-pro-dj-link Pro DJ Link] beat grids.

* You can even host Afterglow within [https://cycling74.com/ Cycling ‘74’s Max] visual interactive environment, through the related [https://github.com/brunchboy/afterglow-max#afterglow-max afterglow-max] project.

== Diving In ==

As suggested by its version number, Afterglow is still at an early stage of development, and is growing rapidly. It is already able to create beautiful effects, and the experience of controlling them through the pressure sensitive pads on the Push, while tweaking them through a REPL, is quite a trip. If anyone is interested in exploring it, the author is eager to help with the setup process and the creation of new fixture definitions for early adopters. Feedback about the documentation or any aspect of the system is warmly welcomed.

== Related Projects ==
* [[OLA]]
* [https://github.com/brunchboy/afterglow-max#afterglow-max afterglow-max]

[[Category:Controllers]]

File:Afterglow-logo.png

2015-08-08T19:06:23Z

DeepSymmetry: The Afterglow logo, a mashup of the OLA and Clojure logos, with a rainbow of light beams coming out of the bottom of the lambda.

The Afterglow logo, a mashup of the OLA and Clojure logos, with a rainbow of light beams coming out of the bottom of the lambda.