View Source

{pop-away:metadata | comments | children | labels}

Galicaster is dependant on the hardware installed on the units so we provide some guides to install and configure of the most commom cards used along this software. We also include some instructions to help you fix the access to those cards and the application on the operative system.

h4. Compatible hardware

To know which Hardware is currently supported please consult the [Compatible hardware]. In it you can see which devices or cards are compatible with Galicaster, guides to install and configure their drivers and instructions on how to configure the Galicaster modules to use them.

If you are interested on trying out Hardware not included in this list, please contact Teltek Video Research to get assistance on doing so.

h4. Galicaster device modules configuration

Once the hardware and their drivers are installed and configured, it is necessary to configure the device modules to access the devices. The list of modules are available at the section [Device module configuration].

h5. Documentation

# [Hardware recommendations|Hardware recommendations]
#* [Compatible hardware]
# [Software installation|Software installation]
#* [Galicaster:Upgrading from older versions]
#* [Galicaster:Release Archive]
# [Galicaster configuration|Galicaster configuration].
#* [Galicaster:Input profiles]
#** [Device module configuration]
#* [Galicaster:Plugins]
# [User's Guide|User Guide]
#* [Recorder|Galicaster:User Guide - Recorder]
#* [Media Manager|Galicaster:User Guide - Media Manager]


h4. Rules to access the cards - UDEV rules

To fix the path to access a device is interesting to set UDEV rules on the system. On this section we provide a general approach to the set up of UDEV rules, leaving the details for the specific pages of each compatible device.

Create the file {{/etc/udev/rules.d/galicaster.rules}}, which will contain the udev rules that will be applied to the devices.

Use the following command to find out the value of *{{ATTR\{name\}}}* for a specific device:

$ udevadm info --attribute-walk --name=${device}

substituting {{"$\{device\}"}} for the device's mount point, for example:

$ udevadm info --attribute-walk --name=/dev/video0
$ udevadm info --attribute-walk --name=/dev/video1 | grep name

(e.g. {{/dev/video0}})

These are some configuration examples:

KERNEL=="video[0-9]*", ATTR{name}=="Epiphan VGA2USB #V2U19350", GROUP="video", SYMLINK+="screen"
KERNEL=="video[0-9]*", ATTR{name}=="ivtv0 encoder MPG", GROUP="video", SYMLINK+="camera"
KERNEL=="video[0-9]*", ATTR{name}=="UVC Camera (046d:0821)", GROUP="video", SYMLINK+="webcam"
KERNEL=="video[0-9]*", ATTR{name}=="ivtv0 encoder MPG", GROUP="video", SYMLINK+="haucamera"
KERNEL=="video[0-9]*", ATTR{name}=="ivtv0 encoder YUV", GROUP="video", SYMLINK+="hauprevideo"
KERNEL=="video[0-9]*", ATTR{name}=="ivtv0 encoder PCM", GROUP="audio", SYMLINK+="haupreaudio"

For newer Epiphan drivers:
KERNEL=="video[0-9]*", ATTR{name}=="vga2usb", SYMLINK+="screen"