$ python -c "import pygst; pygst.require('0.10')"
$ python -c "import pycurl"
$ python -c "import icalendar"
$ gst-launch-0.10 videotestsrc num-buffers=25 ! video/x-raw-yuv,width=800,height=600,framerate=24/1 ! ffmpegcolorspace ! xvimagesink
$ gst-launch-0.10 videotestsrc num-buffers=25 ! video/x-raw-yuv,width=800,height=600,framerate=24/1 ! ffmpegcolorspace ! x264enc pass=5 quantizer=22 speed-preset=4 profile=1 ! queue ! avimux ! filesink location=out.avi
$ file out.avi
out.avi: RIFF (little-endian) data, AVI, 800 x 600, ~24 fps, video: H.264 X.264 or H.264
$ rm out.avi
{code}
{anchor:download}
h6. 3.\- Download software
_By downloading, you agree to the_ _[non-commercial license|http://creativecommons.org/licenses/by-nc-sa/3.0/]__. (Commercial licenses also available under request)_ _[!http://i.creativecommons.org/l/by-nc-sa/3.0/80x15.png|width=80!|http://creativecommons.org/licenses/by-nc-sa/3.0/]_
Download the software from [this site|http://webfiler.teltek.es/webfiler/galicaster/galicaster-1.1.1.tgz].
Uncompress it using tar:
{code}
$ wget http://webfiler.teltek.es/webfiler/galicaster/galicaster-1.2.0.tgz
$ tar xzf galicaster-1.2.0.tgz
$ cd galicaster-1.2.0
{code}
_Recommendation: Move galicaster-1.2.0 folder to a familiar location_
{anchor:config}
h6. 4.\- Configure Galicaster
Galicaster configuration is in the files {{conf-dist.ini}} and {{conf.ini}}. \*Any duplicated value on {{conf.ini}} will prevail over the same ones on {{conf-dist.ini}}.
All the application parameters can be set up in these files, such as:
* Operation mode of the application: I.e. whether Galicaster will work as [Galicaster Class|Galicaster:Galicaster Class], designed to be used in a classroom environment, or as [Galicaster Mobile|Galicaster Mobile], a portable recording station.
* Devices used in the capturer, and their configuration.
* Server information to ingest.
* User privileges to control the recorder.
The simplest way to get started with Galicaster is dowloading any of the pre-existing files for any of the reference configurations proposed: *leaving {{conf-dist.in}} *unchanged as a reference, and make any modification you need on* {{conf.ini}}*:
* Operation mode [Galicaster Class|Galicaster:Galicaster Class]:
** [Video Capture Card configuration|Hardware recommendations#videocapturecard] \- [conf.ini|http://webfiler.teltek.es/webfiler/galicaster/configs/hau_class/conf.ini]
** [WebCam USB configuraion|Hardware recommendations#webcamusb] \- [conf.ini|http://webfiler.teltek.es/webfiler/galicaster/configs/webcam_class/conf.ini]
* Operation mode [Galicaster Mobile|Galicaster Mobile]:
** [Video Capture Card configuration|Hardware recommendations#videocapturecard] \- [conf.ini|http://webfiler.teltek.es/webfiler/galicaster/configs/hau_mobile/conf.ini]
** [WebCam USB configuraion|Hardware recommendations#webcamusb] \- [conf.ini|http://webfiler.teltek.es/webfiler/galicaster/configs/webcam_mobile/conf.ini]
In the Section [Galicaster Configuration] you will find a description of all section of {{conf.ini}} file.
{anchor:matterhorn}
h6. 5.\- Opencast Matterhorn Connection
One of the key features of Galicaster is the connection to the publishing platform. If you are using Matterhorn as your media publishing and distribution system, you need to configure Galicaster to work as a Capture Agent and connect it to your core machine. Here are some tips to do so:
* Your Galicaster unit needs access to your Matterhorn Core network.
* Use a valid *host* URL. It may be a fully-qualified name or simply an IP address.
* If your Matterhorn Core is not running in the default port (80), then you need to explicitly include it in the URL (i.e. {{http://<host_name_or_ip>:8080}}).
* The use of the {{http://}} prefix is mandatory.
* You need to use a Matterhorn account which authenticates via Digest (usually, this account is set up in the {{config.properties}} file in your Matterhorn server). A regular account will not work.
* Remember to activate the connection in Galicaster (in the configuration file, section {{ingest}}, value {{active}}).
* A wrong workflow will raise an error in Matterhorn. Please make sure you use a workflow name that exists in the machine you connect Galicaster to.
* *Workflow parameters are available but optional. A unexisting or wrong parameter won't affect the process, a mistaken value will be considered as "False".*
* Check your Galicaster unit is registered as a Capture Agent in the Admin Tools section of your Matterhorn installation.
** The log (in {{/tmp/galicaster.log}}) will record any problem occurring on the connection to the Matterhorn server.
If your Galicaster is registered as a Capture Agent you should be able to receive the recording schedule, if any, and ingest any recordings in Galicaster to the Matterhorn Core. If this is not so, please review all the steps above and try again. The logs in Matterhorn and Galicaster will give you the hints to know what is failing.
{anchor:running}
h6. 6.\- Run Galicaster
Galicaster Class is launched with the command:
{code:none}
$ ./run_galicaster.py
{code}
The [Galicaster:User Guide] section contains Galicaster's user manual. Should you have any questions, please visit the [F.A.Q.|Galicaster:FAQ] section where some common questions are already answered.
...