Mediasite, now part of Enghouse Video, captures lectures and delivers them: room recorders, personal capture, scheduled recording tied to your timetable, a video portal and LMS integration. Annoto is what happens on top of that video, where students answer graded questions, argue at the second in question, submit and review work, and leave comprehension evidence behind.
Annoto is a video platform too. It hosts and streams natively, and it overlays the platforms institutions already run, so a Mediasite estate can gain an engagement layer without a migration and keep it through any future infrastructure change.
Institutions that run Mediasite have already solved the hard logistics: rooms are wired, recordings start on schedule, and the video reaches students reliably. The complaint that follows is different. Attendance data says students watched, and exam results say they did not learn much.
Enterprise lecture capture and video management. Room recorders and personal capture, recording scheduled against campus timetabling, transcoding and streaming, a searchable video portal, accessibility support, and integration with the major LMS platforms. It is infrastructure, and it is judged on reliability at scale.
The teaching layer on the recorded lecture. Graded in-video quizzes authored by Lumo AI across Bloom's taxonomy, discussion anchored to a timestamp, polls, reflection points, notes with AI recaps, peer review, video assignments, and attention and comprehension analytics per learner and per moment.
No. Annoto attaches to the player rather than the archive, so recordings stay in place with their permissions and captions intact, and the capture schedule your AV team runs does not change. Annoto also hosts and streams natively if a department wants to run without a separate video platform.
That question matters more than usual here, because Mediasite moved from Sonic Foundry to Enghouse Video. An engagement layer that sits above the player keeps working across Panopto, Kaltura, YouTube and Vimeo, so the course designs your faculty built are not tied to a vendor relationship. See Annoto for any video host.
In Canvas, Moodle, Blackboard or Brightspace, an admin registers Annoto as an LTI 1.1 or 1.3 tool and the standard carries sign-on, rosters and grade passback. On a video portal or custom page, one script tag and a client ID attach the layer through the JavaScript SDK, with a REST API and webhooks for reporting and automation.
Flipped and blended courses with accountability for pre-class viewing, formative assessment landing in the gradebook, collaborative learning through anchored discussion, skills practice through video assignments and peer review, and Regular and Substantive Interaction evidence for online programmes. Capture infrastructure produces none of that on its own.
Very little, which is the point. Room bookings, recorder profiles, the capture scheduled against your timetable, transcode settings and retention rules all stay under Mediasite’s control, and nobody touches the archive. The work moves to two other desks. An LMS administrator registers Annoto once as an LTI tool, and courses inherit it after that without a per-course ticket. An instructional designer or the instructor decides where questions and reflection points sit on the timeline. Because Annoto reads the player rather than the file, captions, access rules and unlisted settings carry over as they are, and a lecture that is later re-cut or replaced keeps its layer. No re-encode job, no bulk export, and no second copy of your media library to keep in sync. See how the integrations fit together.
Start narrow, and pick the courses where the gap between watching and learning is already visible: large gateway lectures, flipped modules that depend on pre-class viewing, and anything where the exam post-mortem says students skimmed. One department for one term is enough to produce a defensible read. Existing recordings are the raw material, so there is no content to build first. Lumo AI drafts in-video quizzes from the transcript across Bloom’s levels and the instructor edits and approves them, which is an hour of review per lecture rather than a redesign. Timeline discussion goes in on the same pass. Where a course already asks students to demonstrate a skill, video assignments and peer review replace the submission workflow instead of adding one beside it.
Portal reporting answers whether a video was played and for how long, which is exactly why the disagreement between attendance data and results goes unexplained. The engagement analytics answer a different question: which second of the lecture learners rewound or abandoned, which quiz items failed and at which level of the taxonomy, where discussion clustered because an explanation did not land, and which students never reached the concept the exam tested. Scores and completion sync back through LTI 1.3, so that evidence sits in the gradebook rather than in a separate report nobody opens. For programme review or an accreditation file, it turns “the recordings were available” into a per-learner record of what each student attempted, answered and discussed.
Different jobs, and stronger together.
Mediasite keeps its checkmarks on capture. The point is what the two cover together.
Compared against each vendor's published documentation, August 2026. Both products ship often, so confirm the current detail with each vendor before you decide.
Annoto goes live on top of your existing Mediasite recordings. Nothing moves and nothing re-encodes.
Your LMS admin registers Annoto as an LTI 1.1 or 1.3 tool. On a video portal or custom page, one script tag and a client ID.
Rooms record as they always have. Annoto attaches to the player, so the AV workflow and the archive stay untouched.
Quiz scores and completion sync to the gradebook, and comprehension data reaches programme review.
Side-by-sides with the platforms and tools institutions ask about most.
Twenty minutes on your own content, your portal and your LMS. Bring a lecture students struggle with.
Book A Demo