\\
{anchor:ossetup}
h3. C. Operative System setup
----
{anchor:start}
h4. Autostart
By default, Galicaster is started automatically as the operative system is loaded. To change this do the following:
* Press Win and write _Startup Applications_,
* Check out Galicaster to disable the autostart
* Repeat the operation to re-stablish the autostart
You may want to do it using the terminal:
* Delete \~/.config/autostart/galicaster.desktop
To re-stablish the autostart:
* cp /usr/share/applications/galicaster.desktop \~/.config/autostart/
{anchor:shortcuts}
h4. Shortcuts
To configure the operative system supporting Galicaster you may exit Galicaster or change the current desktop. To do so:
a. If the _admin mode_ is activated you can quit on the welcome page, on the quit button on the bottom right corner.
* To access the welcome page you can't be recording
b. If the _admin mode_ isn't active then you can use a keyboard shortcut Ctrl+Shift+Q, to do so the Num Block has to be activated.
c. You may not want to exit Galicaster and still change configuration on the OS, use the combination Ctrl+Alt+Left/RightArrow to switch between desktops (usually four).
To run Galicaster once closed use the Shortcut in the Desktop or press Win and write Galicaster to look for the application launcher.
{anchor:net}
h4. Network Configuration
To change your IP settings, pleas read this [official Ubuntu guideline|https://help.ubuntu.com/10.04/internet/C/connecting-wired.html].
The Network Manager is on the top right corner, Right-button click on the double arrow icon.
!netmanager.png|align=left!\\
{anchor:gcconf}
h3. D. Capture Devices configuration
----
Galicaster configuration are specified by two types files: configuration and input profiles.
Depending on your needs you may set different parameters. Consult the [Profile Section|Galicaster:Input Profiles] to know the meaning and possible values of each parameters.
Galicaster records multiple devices synchronously. Each device and its configuration is called a _track_. A Input Profile is a group of tracks to be recorded together. The most common profiles are:
* Webcam + Slides + Microphone: class.ini
* Webcam + Slides + Microphone + Backup Audio: class_audio_backup.ini
* Video Camera (audio included) + Slides: camera_slides.ini
* HD input (audio included) + Slides: hd_slides.ini
* HD camera + HDMI slides: hd_unit.ini
In these examples, we suppose two streams of video. If you don't want to record the slides, create a new profile without the slides track and remember to change the name of the profile, to avoid confusion.
Now, it's time to configure the cards you've selected and the audio. More information about this matter is available [here|Galicaster: Cookbook].
{anchor:epi}
h4. D.1 Epiphan configuration
EXPLAIN the behaviour of the Switcher, input and output resolution, blask strips ...
{anchor:webcam}
h4. D.2 Webcam configuration
Logitech c920 is an HD webcam with optic lens and automatic behaviour - white balance, autofocus, auto-aperture.
It records 24 fps at 720p. The default configuration is:
* power-line-frequency:50Hz
* cappabilities: image/jpeg,framerate=24/1,width=1280,height=720
*Back to 4:3*
If you want you can _cut_ part of the video to record a non-panoramic video including in the configuration:
* videocrop-left=160
* videocrop-right=160
_The value is in pixels_
To set manual values on the parameters of the webcam use a tool called guvcview:
* Open a terminal and run:
{code:none}
guvcview -o
{code}
{anchor:bm}
h4. D.3 Blackmagic configuration
To list the input standards and formats supported by Blackmagic cards run the following line in a shell:
{code:none}
gst-inspect-0.10 decklinksrc | grep Enum -A 20
{code}
Once you identified the format you want to capture, edit the _conf.ini_ file you've just downloaded. Search for the _track_ Blackmagic and change the parameters _input_ and _input_type_ for their right values. Some try-and-error may be neccessary since maybe you can't gather all the information from your video source.
The _p_ in 1080p stands for _progressive_
The _i_ in 1080i stands for _interlaced_
{anchor:hau}
h4. D.4 Hauppauge configuration
Before running Galicaster you may have to configure your Hauppauge card. Connect your camera and do the following:
*Standard selection*
You have to choose between a list of standards. To list and select the standard, run in a shell:
{code:none}
v4l2-ctl -d /dev/haucamera --list-standards | grep Index -A 2
v4l2-ctl -d /dev/haucamera -s 0
{code}
*Input selection*
Depending on the input you are using you have to choose between S-Video (4-pin) and Composite (RCA). To list and select the input, run in shell:
{code:none}
v4l2-ctl -d /dev/haucamera -n | grep Input -A 1
v4l2-ctl -d /dev/haucamera -i 2
{code}
Inputs 1 and 3 are for 4-pin.
Inputs 2, 4 and 5 are for RCA.
{anchor:sound}
h4. D.5 Sound configuration
To have the best audio feedback on your interface you should configure your audio inputs properly. First of all, go to the Sound Manager (speaker icon on the top right corner of the desktop)
*Headphones output*
Regulate this slide bar to a comfortable sound level.
*Pulse input ( Line in):*
_If you are using the Hauppauge card please skip this section_
Select the input you are using and set the values to 100% volume, no amplification.
Later, if you have distortion on your audio input, edit the conf.ini and set _amplification = 1.0_ in the AudioSource device.
_Recommendation_
On the pulse track of your conf.ini, don't leave the value _location_ as \_default. List the inputs and set it. This way you won't need to check it every time you switch on your unit. To do that, run in a shell:
{code:none}
pactl list | grep Source -A 2
{code}
Identify the input you want to use, for example
{code:none}
alsa_input.pci-0000_00_1b.0.analog-stereo
{code}
Use the _name_ as _location_ on the _conf.ini_ pulse track
{code:none}
[track3]
name = AudioSource
device = pulse
flavor = presenter
active = True
*location = alsa_input.pci-0000_00_1b.0.analog-stereo*
file = sound.mp3
amplification = 2.0
vumeter = True
player = True
{code}
----
\\
*Galicaster Vumeter*
Add this section in the _conf.ini_ file.
{code:none}
[audio]
min = -60
max = 0
{code}
If the NO SOUND dialog is coming in and out constantly, set a higher value on _min_, for example \-40.
\\
*Alsa Advanced configuration*
If you still experience problems after configuring the Sound Manager and your Mixer or Sound input device, you should take a look to ALSA.
Run _alsamixer_ on a shell and ensure that your device is not being amplified.
* Press F6 to select the input and F4 to go to the Capture section.
* You can chec|| \# || Port || Description ||
| A1 | *VGA output* | To connect the monitor of the computer. |
| A2 | *HDMI output* | To connect the monitor of the computer. |
| A3 | *DVI output* | To connect the monitor of the computer. |k the real Gain on _Item_ on the top left corner of the screen.
{anchor:revo}
h3. E. Revolabs wireless microphone instructions
----
{section}
{column: 69 %}
Revolabs xTag is a wireless microphone with noise cancelling capabilities. It's base works as receptor and as charging bay.
A complete manual is available [here|http://revolabs.com/Documents/xTag-USB/xtag_manual_v1-5.pdf]. The instructions above are based on this manual.
h5. Pairing
To pair the Microphone to the Base:
* Make sure the Microphone is turned OFF (no LED activity). If the unit is ON, press and hold the MUTE button for 10 seconds until the LED turns solid RED then release.
* Enable the pairing mode by holding the Microphone’s Mute button down for eight seconds. The LED will turn solid GREEN and then solid RED. Release the Mute button. The Microphone unit is now in pairing mode.
* Push and hold the Charger Base’s Mute button for eight seconds to enter into pairing mode then release.
{column}
{column: 29 %}
!revolabas.png|align=center,border=1,width=200!
{column}
{section}
The LED will be solid RED until pairing is complete, as indicated by double flashing RED on both the Microphone and the Base (paired and muted audio). If pairing fails at the end of one minute on either unit, the LED will flash alternately GREEN and RED for a few seconds and turn OFF. If this happens, repeat these steps.
h5. Mute
The button on the front of the Microphone mutes it as well as the one on the Base. Press it just for a moment to mute/unmute the Microphone.
h5. Attachment
The Microphone should be attached on the clothing about 15 to 30 cm from the mouth, with the top of the microphone facing up. It must never be use on the hand or on the furniture, since vibrations will mess up whit the noise cancelling mechanism.
h5. Battery
A fully charged Revolabs xTag last 8 hours working. The battery charges from fully depleted to fully charged in approximately two hours, however, it is “quick-charged” to 80% capacity in 45 minutes. Then, it's recommended to place the microphone back to the base during long breaks.
To charge the batteries place the microphone into the bay properly. During charging, the Microphone status LED indicator changes from solid RED to solid GREEN as charging completes. The Charger Base status indicator remains off during charging.The Microphone is always muted while in the Charger Base.
Before using the Microphone for the first time, charge for 8 hours or overnight in the base (until microphone LED turns solid GREEN).
When the Microphone LED begins flashing alternating YELLOW and RED or YELLOW and GREEN, the battery needs recharging.
h5. Range
Revolabs xTag works in a range of 20m. If the microphone is moved out of range of the Base Station (~65 feet or 20m) the connection will be
dropped (LED flashes all colors) and the microphone will mute.
After 15 seconds the microphone will beep 5 times, and will continue beeping every 30 seconds to remind the user to return the microphone to the room. If the microphone is moved back into range within 15 minutes the connection will automatically be re-
established to its original state, and the beeping will cease. If not, the microphone will turn off.
h5. LED status indications
|| LED pattern || Description ||
| {highlight:red}Solid RED{highlight} | Pairing mode, or confirmation of powering-down, or battery charging. |
| {highlight:green}GREEN{highlight} flash every 1.5 seconds | Microphone paired, connected and *un-muted*. |
| Two {highlight:red}RED{highlight} {highlight:red}flashes{highlight} every 1.5 seconds | Microphone paired, connected and *muted*. |
| {highlight:yellow}YELLOW{highlight} and {highlight:green}GREEN{highlight} flashes alternating. | Microphone paired, connected, un-muted and *battery low*. |
| {highlight:yellow}YELLOW{highlight} flash alternating with two {highlight:red}RED{highlight} {highlight:red}flashes{highlight} | Microphone paired, connected, muted and *battery low*. |
| Alternating {highlight:red}RED{highlight}, {highlight:green}GREEN{highlight} | Microphone is not paired to this Base Station. |
| Rapid {highlight:red}RED{highlight} {highlight:red}flashes{highlight} continuing for more than a few seconds | Radio congestion – it is not possible to make a radio connection because there are already too many nearby users of the RF band, or there is heavy radio interference. |
| Groups of five {highlight:red}rapid{highlight} {highlight:red}RED{highlight} {highlight:red}flashes{highlight} | Unit is faulty. Please contact your place of purchase for advice on return. |
| *Microphone only* | |
| {highlight:green}Solid GREEN{highlight} | Confirmation of power-up or battery reaching full charge. |
| Alternating {highlight:red}RED{highlight}, {highlight:yellow}YELLOW{highlight},{highlight:green}GREEN{highlight},{highlight:yellow}YELLOW{highlight} | Searching for a connection, or out of radio range. The Microphone will try to re-establish the link for about 15 minutes, and then turn off automatically. The Microphone will beep five times every 30 seconds. |
{anchor:mh}
h3. F. Opencast Matterhorn related configuration
----
If you have a OC-Matterhorn running you have to ask your Matterhorn system administrator for some information.
First of all, You need the admin host address, including the port. For example:
{code:none}
host = http://fakeadmin.matterhorn.com:80
{code}
You also need a *digest user* \- a regular one won't work. There is a default digest account that should be replaced with your own values.
{code:none}
username= matterhorn_system_account
password= CHANGE_ME
{code}
You also need to set up a default workflow and its parameters. Scheduled recordings will have his own workflow and parameters, defined in the scheduling operation, but the recordings started manually won't. The usual parameters you have to set up are *captions* and *trimHold*, which default to *False*. The normal configuration is:
{code:none}
workflow = full
workflow-parameters = trimHold:true
{code}
If you set up more than one parameter:
{code:none}workflow-parameters = trimHold:true;captions=True{code}
Finally, you have to decide if your recordings will be recorded automatically or not. If you want to do so, set *default* to True. All the configuration together will look like:
{code:none}
[ingest]
...