About Friedrich-Alexander-University Erlangen-Nuremberg
Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU)  is a strong research university and one of the largest universities in Germany, with more than 40,000 students, 244 degree programmes, 4,000 academic staff (including over 580 professors), 180 million euros third-party funding (as of 2014), and 500 partnerships with universities
all over the world.
The Multimedia Department at RRZE (the University IT service provider) has a long history of using professional lecture capture technology, and the first lecture capture video was published in 2002 . In 2009, RRZE announced the launch of an online web video platform  as the official publication channel for all University video material. Today the department has one manager, four employees for capture and editing, two employees for team and management administration, one developer, and five to six student assistants every semester. The video portal hosts more than 18,000 educational resources online.
Why did you decide to use Opencast?
- Cost = Open source project, therefore no license costs.
- Scalability = Opencast offered the ability to fit to our plans.
- Community = Supported by large universities and individuals all over the world.
- Adoptability = Use of open standards (e.g. REST API)
Use case: Creating video files to fit our needs.
We decided to keep our video portal as a publication channel and use Opencast servers for video transcoding. We achieved a level of integration in our daily department workflow by using Opencast servers to generate certain video files for the video portal, fau.tv. The standards for almost 97 percent of our recordings are:
- One audio file
- Three camera files with different resolutions, 320×180, 640×360 and 1280x720p (with an FAU logo watermark)
- One combined file for camera and computer signal (picture 1)
- Same quality and encodings, such as the files being processed by professional video editing software (FinalCut Pro)
- Intro-outro videos for all video-audio formats Picture 1
Video portal default combined layout. Post editing with Adobe Photoshop and Finalcut Pro
the total workload per person for a recording, after the capturing, dropped to 2 minutes for trimming the recording in the Opencast video editor.
Videos are published in our video portal admin area using the Opencast REST API, without the need for Opencast GUI interaction.
This winter semester 2015/2016, a clip  was produced exclusively by Opencast 2.0.1 and captured with Galicaster 1.4.1. The combined video file used dynamic Opencast metadata rendering.
Opencast Ubuntu 14.04 server nodes (October 2015)
- 1 x Opencast 2.0.1 admin node (2 cores, 4 GB RAM)
- 2 x Opencast 2.0.1 worker nodes (8 cores, 8 GB RAM)
- 1 x Opencast 2.0.1 engage node (2 cores, 4 GB RAM)
- 1 x Mysql database
- Shared NAS
+ Nagios and munin monitoring
5 Galicaster CA1.4.1 (with Ubuntu 12.04) and 4 NCast PR-720M
Depending on the layout of the room, we have different capture agents set up with a mix of automatic and scheduled recordings.
In the current semester we are capturing and processing 44 lectures per week. 33 percent of them use Opencast. This translates to around 24 to 28 hours per week.
- Deploy Opencast 2.1
- Improve processing times (current workflow for a 1h 30m lecture video, camera and computer signal takes around 6 hours to complete)
- Implement an automated capture process
- Improve video quality
- Increase the number of capture agents
Stefanos Georgopoulos, RRZE Multimedia and E-learning
(firstname.lastname@example.org, +49 9131 8520190)
Michael Gräve, RRZE Multimedia and E-learning
(email@example.com, +49 9131 8528898, 8529953 )