h3. New Features description
----
{anchor:scripts}
h4. External scripts in profiles
From 1.3 every profile can set up a configuration script. The script will be executed before the profile is loaded.
Usually a script will configure a certain device but it could include any other task.
To specify the script to be executed, include its full path in the profile data section:
{code:none}
[data]
name = profile
execute = /home/user/scripts/script1.sh
{code}
*Example:*
Configure a Logitech c920 to a power line frequency of 50Hz
{code:none}
# file: /home/user/scripts/script1.sh
v4l2-ctl -d /dev/webcam -c power_line_frequency=1
{code}
{anchor:encoder}
h4. Configurable Encoder and Muxer
Most of the device plugins of Galicaster are now able to configure the encoder and muxer which will process the data.
Exceptions include:
* Hauppauge cannot define the encoder nor the muxer.
* RTP only allows to define the muxer
*Parameters and examples:*
* videoencoder
** x264enc quantizer=22 speed-preset=2 profile=1
** xvidenc bitrate=50000000
** ffenc_mpeg2video quantizer=4 gop-size=1 bitrate=10000000
* audioencoder
** lamemp3enc target=1 bitrate=192 cbr=true
* muxer
** flvmux
** avimux
** mpegtsmux
{section}
{column:width=60%}
{note}Pulse parameter is {{{_}encoder{_}}}, not {{{_}audioencoder{_}}}. This denomination will be corrected in the next RC.{note}
{column}
{column}{column}
{section}
To know more of the paramaters of each muxer and encoder consult the Gstreamer documentation.
{code:none}gst-inspect flvmux{code}
Consult us for instructions to configure your custom encoder and muxer.
*Example:*
Configure a Logitech c920 to encode a 720p, H264+MP4 video:
{code:none}
[track1]
name = Webcam
encoder = x264enc bitrate=1000 pass=5 quantizer=23
location = /dev/video0
file = CAMERA.mp4
device = v4l2
muxer = mp4mux faststart=true
caps = image/jpeg, framerate = 24/1, width=1280, height=720
flavor = presenter
{code}
{anchor:rtp}
h4. RTP device module
A new device plugin has been developed in order to provide compatibility with network cameras and other RTP-based devices. This plugin records video or video+audio encoded on MPEG4 or H264, with audio in ACC or MP3.
This plugin has been extensively tested over several [Axis network cameras|Galicaster:Axis Network Cameras], with and without audio. Other devices has been tested but in a lesser degree - Epiphan Broadcasters, for instance-. If you test this plugin on other cameras, please report your results back to the [community list|Galicaster:Community].
Consult the [plugin configuration|Galicaster:RTP device plugin] and contact us for troubleshooting.
{anchor:custom}
h4. Custom device module
This feature is meant for advanced users. You can define a custom bin to test new sources within Galicaster.
{code:none}
[track1]
name = custom
location = default
file = CAMERA.avi
device = custom
flavor = presenter
active = True
pipestr = videotestsrc name=gc-custom-src is-live=true ! video/x-raw-yuv,framerate=10/1,width=640,height=480 ! tee name=tee-vt ! queue ! ffmpegcolorspace ! xvimagesink sync=false async=false qos=false name=gc-custom-preview tee-\
vt. ! queue ! valve drop=false name=gc-custom-valve ! queue ! ffmpegcolorspace ! queue ! filesink name=gc-custom-sink async=false
{code}
{section}
{column:width=60%}
{note:title=Element naming}
The elements source (src), valve and sink must be named as those in the example, so that the program can identify them.
{note}
{column}
{column:width=40%}
{column}
{section}
{anchor:logger}
h4. Configurable logger
The log files location, the minimum log level shown and whether the logs rotate or not can be easily set up in this version:
{code:none}
[logger]
path = /var/log/galicaster/galicaster.log
level = DEBUG
rotate = True
{code}
{section}
{column:width=60%}
{note:title=Directory IO permissions}
Make sure Galicaster has write permissions in the directory where the logs are to be stored.
{note}
{column}
{column:width=40%}
{column}
{section}
Galicaster can also use the system log (syslog) instead:
{code:none}
[logger]
use_syslog = True
{code}
{anchor:rest}
h4. REST Plugin
The REST endpoint plugin for Galicaster is a module to provide an experimental REST interface to access some parameters and features of Galicaster.
If activated, the REST plugin will response at the localhost address through the 8080 port.
Current endpoints include:
|| URL || Description ||
| *{{/state}}* | Show some state values |
| *{{/repository}}* | List MP keys |
| *{{/repository/<id>}}* | Get MP manifest (XML) |
| *{{/metadata/<id>}}* | Get MP metadata (JSON) |
| *{{/start}}* | Start a manual recording |
| *{{/stop}}* | Stop current recording |
| *{{/operation/ingest/<id>}}* | Ingest MP |
| *{{/operation/sidebyside/>id>}}* | Export MP to side-by-side |
| *{{/operation/exporttozip/<id>}}* | Export MP to zip |
| *{{/screen}}* | Get a screnshot of the current desktop |
Activating this plugin is as simple as:
{code:none}
[plugins]
rest = True
{code}
{section}
{column:width=60%}
{note:title=Visualizing JSON}To test this plugin, we recommend using add-ons on your browser to visualize JSON data.{note}
{column}
{column}{column}
{section}
{anchor:metadata}
h4. Galicaster 1.3 Metadata Treatment
Before Galicaster 1.3, only some metadata was collected, specially with Series metadata, where only _name_ and _identifier_ were preserved.
After studying and discussing the current situation with metadata regarding Matterhorn and Galicaster, we have made the following modifications in the behavior on Galicaster's side:
* All metadata is captured, both in episode and series.
* If custom parameters are included in the Matterhorn schedule they are preserved through Galicaster.
* The only parameters that can be modified are: title, presenter, language, description and series.
** A change in series makes all series parameters change at once.
* Empty parameters are not included in the files.
Unfortunately Matterhorn overwrittes the metadata of a returning mediapackage, so modifications have to be made in order to preserve any changes made on the capturer. However, if a mediapackage is ingested a second time, all the metadata - but the identifier - will be preserved.
h3. Regarding device behavior on missing signal and resolution change.
We've compiled a list of the behaviour of the video devices when the signal is missing - unplugged or camera off - or the resolution changes - for VGA capturing devices.
This list was checked over Ubuntu 12.04 with newest drivers and Galicaster 1.3.0rc1
* Datapath:
** Provides configurable No signal black screen, with time counter.
** Scalate to designated resolution.
** We recommend using the newer possible driver.
* NCast:
** Provides mock signal.
** Scalates input.
* Epiphan:
** Newest drivers provides green screen on failure and scalates on resolution change.
** V4L2 device module can be used instead of epiphan's, specifying caps
* Osprey:
** provides a blue screen
* Bluecherry PV:
** provides a blue screen with caps well configurated, otherwise it may fail
* Hauppauge:
** Provides black. If configurated on Tuner it provides noise.
** Unfortunately, switch to a good input and standard requires to stop the preview. Other sources can switch on runtime (Osprey f.i.).
* *RTP: Fails*
* *Blackmagic: Fails "silently".*
** It may be a GStreamer issue since the driver works with the vendor SW.
** External HW can prevent failures.
** Doesn't allow resolution change.
* *Firewire: Fails*
* *Webcams: Fails and Galicaster crashes.*
Silently means that it won't report an error on Galicaster but the resulting MP will be erronous.
Summing up; Firewire, RTP, webcams and Blackmagic sources need continous signal.
If signal recovers, user can reload the profile except for webcams, where Galicaster needs to be restarted manually.
...