Service, software and legal status checked through 2026-07-11. 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.

In June 2022 I gave a presentation at the Tag der Lehre 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 skeptical 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 Court’s 2020 Schrems II judgment invalidated the Privacy Shield and imposed requirements on other transfer mechanisms. Since July 2023, transfers to participating US organisations can also rely on the EU–US Data Privacy Framework adequacy decision. 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 is designed to maximise watch time. 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 project of the Digitale Hochschule NRW — a cooperative of North Rhine-Westphalian universities building shared digital infrastructure. The concept is a state-wide video service, run by universities for universities, for the recording, processing, management, and distribution of video content in teaching and research. The platforms calls itself “Hochschul-YouTube”, which is both accurate and slightly underselling what makes it different.

The HfMT Köln participates as a user institution, 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. 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 records in three modes: screen only, camera only, or screen and camera simultaneously as a synchronised multi-stream. That last option — Presentation and Presenter as separate streams, played back with the viewer switching focus between them, or as picture-in-picture — 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 supports simultaneous recording from two camera perspectives — a wide shot and a detail shot, say, or a front view and a hands view for a piano performance. The viewer can switch between them in playback, or the institution can set a default presentation. 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: upload to the video platform, embed in ILIAS on pages, in learning modules, or as standalone video objects, all from within ILIAS.

Access rights. Opencast supports access-control lists and LMS integration. The exact public, institution, course, group and individual roles depend on the deployment, and protected presentation pages do not by themselves secure media streams unless stream security is configured. A graduation concert, course recording and individual feedback clip therefore need separately tested rights and publication workflows.

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 is an example of the alternative model: public institutions sharing infrastructure built on open-source software. Its current governance, hosting, accessibility, feature set and service levels must be checked in current service documentation rather than inferred from the 2022 presentation. 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. For educast.nrw setup at HfMT Köln, contact the IT department.

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).