The followin list include all the release candidates published so far for the 1.3.0 version:/Galicaster].
Download the lattest and try it.
The following list includes the most important improvements on this new release. During the release candidate testing process we will be updating the documentation both in the code (at docs/) and in this wiki regarding these changes. Anyway, use the usual channels for any questions or suggestion - email, github, community.
- New RTP device module - to support RTP network devices as Axis cameras (mpeg4 and h264)
- New Custom device module - to test new sources within Galicaster using GStreamer syntax(advanced users)
- External scripts in profiles for devices configuracion
- Configurable encoder and muxer.
- Close session and shutwdown option on UI.
- Save crashed recordings on restart
- Ruled Vu-meter
- Configurable Side-by-side layout
- New Pop-ups decoration
- Configurable resolution for UI
- Configurable logger - location, syslog, rotation ...
- Improved metadata treatment
- Updated REST endpoint
New or improved Plugins
- New Check_Repository_plugin: To start missed scheduled recordings on startup
- Screen_Saver_Plugin: improved screensaver control for Ubuntu 12.04
- No_audio_dialog_plugin: general improvement, more comfigurable
New documentation has been included on the code (docs/ folder) as well as in this wiki. This documentation is both partial and provisional but is already useful. Following the release process we will be updating it.
- V4l2 device module
- Pulse device module
- Epiphan device module
- Datapath device module
- Hauppauge device module
- Blackmagic device module
- Firewire device module
- RTP device module
- [Galicaster:Custom device module]
[Capture card table]
- Logitech webcams
- Revolabs wireless microphones
- Epiphan framegrabbers
- Datapath video capture cards
- NCast cards
- Blackmagic capture cards
- Hauppauge capture cards
- Osprey Cards
- [Galicaster:Bluecherry H.264 PCIe cards]
User and administrator guide:
From 1.3 every profile can establish 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 is full path on the profile data section
Configure a Logitech c920 to a power line frequency of 50Hz
Most of the device plugins of Galicaster are now able to configure the encoder and muxer where the data will be stored.
- Hauppauge cannot define the encoder nor the muxer.
- RTP only allows to define the muxer
Parameters and examples:
- x264enc quantizer=22 speed-preset=2 profile=1
- xvidenc bitrate=50000000
- ffenc_mpeg2video quantizer=4 gop-size=1 bitrate=10000000
- lamemp3enc target=1 bitrate=192 cbr=true
Note: Pulse parameter is encoder not audioencoder, this denomination will be modified for the next RC.
To know more of the paramaters of each muxer and encoder consult the Gstreamer documentation. Consult us for instructions to configure your custom encoder and muxer.
Configure a Logitech c920 to encode a 720p, H264+MP4 video:
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 on ACC or MP3.
This plugin has been extensively tested over several 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 it back to the community list.
Consult the plugin configuration and contact us for troubleshooting.
This feature is meant for advanced users. Defining a custom bin allow to test new sources within Galicaster.
In this version, specifying where the logs are stored, the minimum level showed and whether the logs rotate or not is very simple:
Galicaster can also use the system log (syslog) instead:
The REST endpoint plugin for Galicaster is a module to provide an experimental endpoint interface to access some parameters and features of Galicaster.
If activated, the REST plugin will response in the localhost address through the 8080 port.
Current endpoints include:
- /state : show some state values,
- /repository : list mp keys ,
- /repository/:id : get mp manifest (XML)
- /metadata/:id : get mp metadata (JSON)
- /start : starts a manual recording
- /stop : stops 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 screenshoot of the active
Activating this plugin as simple as:
To test the plugin we recommend using add-ons on your browser to visualize JSON data.
Before Galicaster 1.3, only some metadata was collected, specially on Series metadatata where only name and identifier where preserved.
After study and discuss the current situation on metadata regarding Matterhorn and Galicaster we've made the following modifications on the behavior on Galicaster's side:
- All metadata is captured, both in episode and series.
- If custom parameters are included on the Matterhorn schedule they are conserved through Galicaster.
- The only parameters that can be modified are: title, presenter, language, description and Series
- A change on Series makes all series parameters change at once
- Empty parameters are not included on the files.
Unfortunately Matterhorn overwrittes the metadata of a returning mediapackage, so modifications have to be made in order to preserve any changes on the capturer. However, if a mediapackage is ingested a second time the metadata - but the identifier - will be preserved.