Service, software and legal status checked through 2026-10-28; Opencast details follow the documentation of 20.x, the stable release. Feature and access details vary by Opencast release and institutional configuration; this is an infrastructure argument, not legal advice or a current HfMT service catalogue.

Status note: on 12 July 2023 the educast.nrw project announced that it would end with its funding period on 31 December 2023, saying it saw no long-term prospect of a permanent service; participating institutions could use it until 31 March 2024, and no services have been provided since 1 April 2024 [[1]] [[2]]. The University of Bonn’s IT centre reported that the Digitale Hochschule NRW (DH.NRW) had decided not to fund it further [[3]]. Present-tense descriptions of educast.nrw below give its state in June 2022; statements about Opencast follow its current documentation.

In June 2022 I gave a presentation at the Tag der Lehre (“teaching day”) at the Hochschule für Musik und Tanz Köln on video-supported teaching with educast.nrw. Presenting something to colleagues who already use ILIAS every day and are broadly sceptical of yet another platform is a useful discipline. You have to answer the obvious question fast: why should we care about this, when YouTube works fine?

The short answer is that YouTube does not work fine, for reasons that matter specifically to universities. The longer answer is what this post is about.

What Is Wrong with YouTube

YouTube offers enormous reach, automated processing and a familiar player. For individual creators seeking a public audience, it is genuinely hard to beat.

For universities it fails in at least three important ways.

Data protection. Uploading identifiable teaching material and requiring students to use a commercial platform creates processing that the university must map and justify: controller/processor roles, legal basis, contracts, retention, telemetry, user accounts and any international transfers. The CJEU’s 2020 Schrems II judgment invalidated the Privacy Shield and imposed requirements on other transfer mechanisms [[4]]. Since 10 July 2023, transfers to US organisations that participate in the EU–US Data Privacy Framework can also rely on the Commission’s adequacy decision. The General Court dismissed an action for its annulment in September 2025 [[5]]; the applicant appealed to the Court of Justice on 31 October 2025 (C-703/25 P; current status not verified) [[6]]. The Commission still lists the decision in October 2026 [[7]]. That development makes the old blanket statement “US server equals unlawful” wrong; it does not remove the need for a concrete institutional assessment of YouTube’s actual data flows and settings.

Platform logic. YouTube was designed to maximise watch time: in 2016 its engineers described their final ranking objective as “generally a simple function of expected watch time per impression” [[8]]. Its recommendation algorithm is not neutral. It will recommend whatever comes after your lecture, and what comes after your lecture is not under your control. For educational content — especially sensitive material, or content that should remain in a defined pedagogical context — this is a real problem. The platform is not indifferent to what is hosted on it; it shapes how it is consumed.

Institutional fragility. YouTube is free until it isn’t. Platform terms change; monetisation policies change; content is demonetised or removed based on automated systems with imperfect appeal mechanisms. Building institutional infrastructure on a free commercial service is a bet that the commercial incentives of that service will remain aligned with your needs. That bet has a poor historical record.

None of this means that individual instructors should never use YouTube. It means that universities should not make YouTube their default institutional solution.

educast.nrw: A Cooperative Model

educast.nrw is a joint project (Kooperationsvorhaben) of the DH.NRW [[9]], an alliance of North Rhine-Westphalian universities and the state’s Ministry of Culture and Science that builds shared digital infrastructure [[10]]. The state funds it, and a consortium of the universities of Münster (which leads it), Cologne and Duisburg-Essen runs it [[9]] [[11]]. The concept is a state-wide video service, run by universities for universities, for the recording, processing, management, and distribution of video content for study and teaching. The project’s FAQ said in 2021 that all data were stored in Germany, in particular in North Rhine-Westphalia, at the consortium’s universities, and that the service cost the state’s public universities nothing [[12]].

Hochschul-YouTube (“university YouTube”) is a fair nickname that undersells what makes it different; the project’s own strapline is plainer, Der landesweite Videoservice für Hochschulen (“the state-wide video service for universities”) [[9]]. Unlike YouTube, it is not a portal: its FAQ leaves features such as comments and links to further videos to the portal that shows the videos, such as ORCA.nrw, and says that educast.nrw offers only the player [[12]]. In the Opencast world that portal layer is a separate project, Tobira [[13]].

The HfMT Köln participates as a user institution [[11]], which is where I come in as the IT contact for setting it up on our end.

The technical foundation is Opencast, an open-source video-management system developed by an academic community [[14]]. Source access and institutional operation make different governance choices possible; neither open source nor a German hosting location automatically proves GDPR compliance. Licensing, publication and retention still depend on rights, consent and the local service configuration.

What It Can Do

The feature set covers the actual use cases of a university, not the use cases of a content creator trying to build a following.

Recording. The Opencast Studio browser app, reached through the LMS plugins, records in three modes: screen only, camera only, or screen and camera simultaneously as a synchronised multi-stream [[15]] [[16]]. That last option — Presentation (the screen) and Presenter (the camera) as separate streams, which educast.nrw’s player shows side by side [[17]] — is the format that works for a lecture. You get the slides and the speaker in the same video, but the viewer can choose which to focus on. That flexibility is not something you get from a simple screen recording uploaded to YouTube.

Multi-perspective video. For a music university this is the feature that changes things. A concert or a masterclass is not well-served by a single camera angle. The platform plays two video tracks of one recording side by side — a wide shot and a detail shot, say, or a front view and a hands view for a piano performance. Opencast Studio does not record them: it captures a screen and at most one camera [[16]]. The two angles can come, in principle, from a dual-stream lecture-hall recorder, which educast.nrw documents for the Extron SMP 351 and 352 [[18]], or from two separately recorded files uploaded into the two slots, which Opencast labels presenter and presentation [[17]]. The labels are not neutral: the presentation track is analysed for slide changes [[17]], so a camera angle placed there is processed as if it were slides. Opencast’s current player, Paella, can also swap the views or show picture-in-picture [[19]]. This is infrastructure that makes the teaching use of concert recordings actually feasible, not just technically possible.

Formats. Opencast workflows can generate multiple resolutions and bitrates, but codecs, audio parameters, upload limits and player behaviour are configured per deployment and release. Music institutions should verify the complete capture, transcode and playback chain with their own source material rather than infer audible superiority from nominal sample rates.

ILIAS integration. This is the practical hinge. Video that lives in a separate platform is video that students may or may not find. Video embedded directly in the ILIAS course page, in the learning module, at the point in the curriculum where it is relevant — that is video that is part of the course rather than adjacent to it. The integration between educast.nrw and ILIAS is direct: an Opencast object in a course holds one series for upload, management and viewing, and single videos can be embedded on any page built with the ILIAS page editor, learning modules included [[20]] [[21]].

Access rights. Opencast attaches an access-control list (ACL) to each series and video: the roles allowed to read or write, with everything not listed denied [[22]]. LMS integration maps course membership onto such roles. Opencast’s LTI module is one mechanism: a student in a course receives a role formed from the course ID and Learner, and adding that role to a video’s ACL opens the video to the course [[23]]. Which mechanism educast.nrw’s ILIAS and Moodle plugins used is not established here. The project’s FAQ promises every gradation from nobody through selected people to everyone [[12]], and the ILIAS object can set rights per recording [[20]]. The exact public, institution, course, group and individual roles depend on the deployment.

The ACL protects the player page, not necessarily the video file (Fig. 1). Opencast’s engage service, which delivers player pages, checks the ACL before it serves the player and metadata, but the files come from download and streaming servers that, in the documentation’s words, “have no knowledge about the current user and its permissions”, so “nothing prevents an authorized user from passing on the actual video and image URLs to the public” [[24]]. Stream security closes that gap with signed URLs: each request for a file must carry a policy with an expiry time (two hours by default in Opencast 20.x, optionally tied to the viewer’s IP address) and a signature that the file server verifies [[24]]. A leaked signed URL still works until it expires, and an authorised viewer can still download and republish the file, because stream security is not DRM [[24]]. educast.nrw’s ILIAS object also had a “streaming only” switch that disables the download button [[20]]; on its own, that does not stop an authorised viewer from extracting the stream URL. A graduation concert, course recording and individual feedback clip therefore need separately tested rights and publication workflows.

Figure 1. Two separate checks: Opencast’s engage service tests the access-control list before serving the player page (steps 1–2); the file server tests only a URL signature, and only with stream security (steps 3–4). From the Opencast 20.x stream-security documentation [[24]].

Use Cases in a Music University

The general university use case — lecture recording, video tutorial, self-study module — applies at HfMT as much as anywhere. But a music and dance university has some specific ones.

Concert recordings. HfMT Köln runs performances at its sites. Recording and selectively publishing them still requires file, rights, performer-consent and publication workflows. An institutionally operated platform can support those workflows; it does not remove copyright or neighbouring-rights duties.

Stage presence as a reflective tool. Reviewing a performance can support reflection. An appropriately configured platform can enable restricted student/teacher feedback, but its access controls must be tested and any effect on participation or learning evaluated rather than assumed.

Theory and practice. This is the institutional argument I made in the presentation and stand by: video infrastructure that works for a lecture also works for a concert. The same system that stores the introduction to music theory also stores the masterclass by a visiting artist. This is not incidental — it is the point of a shared infrastructure. You do not need to choose a platform for academic content and a different one for performance content. The platform works for both.

The Argument Behind the Argument

There is a broader principle at work here that extends beyond video platforms. Public universities are funded by public money. The infrastructure they build with that money — software, platforms, data, content — should be under their control, governed by their values, and ideally available to other public institutions. The commercial platform model inverts this: you get free hosting in exchange for your data, your students’ attention, and your institutional dependence.

educast.nrw was an example of the alternative model: public institutions sharing infrastructure built on open-source software. It was also a funded project: its FAQ said in 2021 that funding ran to the end of 2023 and that permanent funding would be sought if the service proved used and needed [[12]]. None followed. The software outlasted the service: the University of Bonn, for one, announced that videos uploaded to educast.nrw up to 2 February 2024 would move to its own Opencast platform [[3]]. My judgment is that the cooperative model is the right direction, not that every implementation choice is automatically better.

The question of who owns the video infrastructure of a university is the same question as who owns its email, its learning management system, its student data. The answer should be: the university, operating under law, answerable to its students and to the public that funds it.


The slides from the Tag der Lehre 2022 presentation are available on request. In 2022 the contact for educast.nrw setup at HfMT Köln was the IT department.


References

[1] educast.nrw. educast.nrw (project page, provided by ORCA.nrw since April 2026). Retrieved 28 October 2026 from https://educast.nrw/de/

[2] educast.nrw. (2023, 12 July). Beendigung des Projekts educast.nrw [End of the educast.nrw project]. Archived 26 September 2023 at https://web.archive.org/web/20230926195047/https://educast.nrw/de/blog/2023/07/beendigung-des-projekts-educast.nrw/

[3] University of Bonn, University IT and Data Center. (2023, 1 December). Migration of “Educast.NRW” to eCampus Video. Retrieved 28 October 2026 from https://www.hrz.uni-bonn.de/en/news/migration-von-educast-nrw-zu-ecampus-video

[4] Court of Justice of the European Union. (2020, 16 July). The Court of Justice invalidates Decision 2016/1250 on the adequacy of the protection provided by the EU-US Data Protection Shield (Press release No 91/20, Case C-311/18, Data Protection Commissioner v Facebook Ireland and Maximillian Schrems). https://curia.europa.eu/jcms/upload/docs/application/pdf/2020-07/cp200091en.pdf

[5] General Court of the European Union. (2025, 3 September). Data protection: the General Court dismisses an action for annulment of the new framework for the transfer of personal data between the European Union and the United States (Press release No 106/25, Case T-553/23, Latombe v Commission). https://curia.europa.eu/jcms/upload/docs/application/pdf/2025-09/cp250106en.pdf

[6] Appeal brought on 31 October 2025 by Philippe Latombe against the judgment of the General Court (Tenth Chamber, Extended Composition) delivered on 3 September 2025 in Case T-553/23, Latombe v Commission (Case C-703/25 P). (2025, 22 December). Official Journal of the European Union, C/2025/6610 (CELEX 62025CN0703). http://data.europa.eu/eli/C/2025/6610/oj

[7] European Commission. Adequacy decisions. Retrieved 28 October 2026 from https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en

[8] Covington, P., Adams, J., & Sargin, E. (2016). Deep neural networks for YouTube recommendations. In Proceedings of the 10th ACM Conference on Recommender Systems (pp. 191–198). DOI: 10.1145/2959100.2959190

[9] educast.nrw. Der landesweite Videoservice für Hochschulen (home page) and Über uns (about page). Archived 24 June 2022 and 28 January 2022 at https://web.archive.org/web/20220624225426/https://educast.nrw/de/ and https://web.archive.org/web/20220128053238/https://educast.nrw/de/about/

[10] Digitale Hochschule NRW. Akteure [Actors]. Retrieved 28 October 2026 from https://www.dh.nrw/akteure

[11] educast.nrw. Hochschulen [Institutions] (last changed 24 January 2022). Archived 28 January 2022 at https://web.archive.org/web/20220128050056/https://educast.nrw/de/institutions/

[12] educast.nrw. FAQ (last changed 6 October 2021). Archived 28 January 2022 at https://web.archive.org/web/20220128054208/https://educast.nrw/de/docs/faq/

[13] Opencast. Tobira (Administration Guide, release 20.x). Retrieved 28 October 2026 from https://docs.opencast.org/r/20.x/admin/configuration/tobira/; Tobira video portal: https://tobira.opencast.org/

[14] Opencast. Open Source Video Management. Retrieved 28 October 2026 from https://opencast.org/

[15] educast.nrw. Studio (documentation, last changed 1 October 2021). Archived 28 January 2022 at https://web.archive.org/web/20220128051346/https://educast.nrw/de/docs/recording/studio/

[16] Opencast Studio. Source code, src/steps/video-setup/source-select.tsx and src/opencast.tsx, commit 1b6981c (26 October 2026). https://github.com/opencast/studio; public deployment: https://studio.opencast.org/

[17] educast.nrw. Videos hochladen [Uploading videos] (documentation, last changed 1 October 2021). Archived 28 January 2022 at https://web.archive.org/web/20220128055927/https://educast.nrw/de/docs/management/videos/upload/

[18] educast.nrw. Extron SMPs (documentation, last changed 16 December 2021). Archived 28 January 2022 at https://web.archive.org/web/20220128061609/https://educast.nrw/de/docs/lecture_room_setup/capture_agents/extron/

[19] paella-core, the core library of Paella Player 7 and later. Video layout (doc/video_layout.md, section “User interaction”). Retrieved 28 October 2026 from https://github.com/polimediaupv/paella-core/blob/main/doc/video_layout.md; Paella 7 is the default player of Opencast 20.x: https://docs.opencast.org/r/20.x/admin/configuration/player/player.overview/

[20] educast.nrw. Objekt erstellen [Creating the object] and Videos einbetten [Embedding videos], ILIAS documentation (last changed 24 January 2022). Archived 28 January 2022 at https://web.archive.org/web/20220128062959/https://educast.nrw/de/docs/ilias/object/ and https://web.archive.org/web/20220128051309/https://educast.nrw/de/docs/ilias/embed/

[21] opencast-ilias. OpenCast, OpencastPageComponent and OpencastEvent: Opencast plugins for ILIAS. Retrieved 28 October 2026 from https://github.com/opencast-ilias

[22] Opencast. Access Control List Configuration (Administration Guide, release 20.x). Retrieved 28 October 2026 from https://docs.opencast.org/r/20.x/admin/configuration/acl/

[23] Opencast. Integrating Opencast using LTI (Administration Guide, release 20.x). Retrieved 28 October 2026 from https://docs.opencast.org/r/20.x/admin/configuration/ltimodule/

[24] Opencast. Stream Security (overview) and Configuration of Stream Security (Administration Guide, release 20.x). Retrieved 28 October 2026 from https://docs.opencast.org/r/20.x/admin/configuration/stream-security/stream-security-overview/ and https://docs.opencast.org/r/20.x/admin/configuration/stream-security/stream-security-config/


Changelog

  • 2026-07-11: Updated the post-2023 EU–US transfer context; removed the blanket US-server compliance claim and stale codec/quota specifications; made access, stream security, licensing and pedagogical benefits configuration- and evidence-dependent.
  • 2025-08-18: Corrected the capitalisation of “OpenCast” to “Opencast” throughout (matching the project’s official spelling on opencast.org).
  • 2026-10-03: Added a status note that the educast.nrw project ended on 31 December 2023 and its services were discontinued on 1 April 2024 (per the project page), so the present-tense descriptions are marked as the June 2022 state; replaced the stale setup-contact line with a dated one; defined “Court” as the CJEU for Schrems II; fixed the typo “platforms calls”.
  • 2026-10-28: Corrected the multi-perspective claim: Opencast Studio records a screen and at most one camera, so two camera angles can come, in principle, from a dual-stream capture agent or from two uploaded files in the presenter and presentation slots, the second of which is processed for slide changes. Replaced “the institution can set a default presentation” and the switching and picture-in-picture description with the side-by-side view that educast.nrw documented, noting what Opencast’s current player adds. Narrowed “standalone video objects” in ILIAS to the Opencast object, which holds one series. Corrected “teaching and research” to study and teaching, as the project stated it. Reworded “the platform calls itself ‘Hochschul-YouTube’”, for which no source was found, as a nickname, with the project’s own strapline beside it. Dated and sourced the end of the service (announced 12 July 2023, usable until 31 March 2024), updated the summary, and replaced the obsolete advice to check current service documentation with the 2021 FAQ’s funding plan and the University of Bonn’s migration to its own Opencast platform. Added the DH.NRW, state funding, the consortium, the FAQ’s statements on data location and cost, and that educast.nrw was a player rather than a portal (Tobira); how ACLs, LMS roles and stream security divide protection between player page and media file (Fig. 1); YouTube’s 2016 watch-time ranking objective; the 2025 General Court ruling on the Data Privacy Framework and the appeal against it; and numbered references in place of the link list.