The student workflow

During the term: record each lecture (with permission — most universities allow personal-use recording; check your institution's policy). After class, drop the audio file into MDisBetter, get back structured Markdown with ## H2 sections at topic shifts. Save into your notes vault organised by course (notes/cs101/lecture-09-inheritance.md). During revision: grep across the term's lectures for the concept you're studying. The Markdown surfaces the exact lecture, the exact section, the exact words used. Jump back to the audio if tone or emphasis matters; otherwise the text is sufficient. Before exams: feed the per-lecture Markdown to an LLM with a "make me 20 flashcards covering the key concepts" prompt. Drop into Anki for spaced-repetition review.

Structured output for academic content

Lectures are typically single-speaker (the lecturer) with occasional questions from students. The Markdown output reflects this: no speaker labels by default for cleaner reading (you can pass a parameter to enable them if there's a Q&A component), section headings at topic shifts matching how the lecturer organised the material, timestamps at major sections for jump-back. For lectures with technical vocabulary (organic chemistry, advanced math, specialised terminology), accuracy is high in standard subjects and occasionally needs spot-checking for rare terms — the timestamp lets you verify quickly.

Cross-link tip

Lecture slides as PDF? Run them through PDF to Markdown and store next to the lecture transcript in the same folder. You end up with a complete searchable record of each lecture: spoken content (transcript), visual content (slide deck text), and any handouts or readings (also convertible via PDF or URL tools). The whole semester's material as one searchable Markdown library is what makes pre-exam revision realistic.