Good tools for reviewing videos?

Special beta-tests
#1

Mostly for @khinsen but anyone else should feel free to chime in, I am curious given your previous MOOC experience if you have any feed-back about tools or general tips to review videos (we are so spoiled with version control for code):

  • find quickly typos without having to watch the full videos (I guess writing a script dumping frame each second could be a good first step but we have many many more important things to do before the MOOC starts …)
  • review what has changed since the previous version
  • give feed-back, for now writing an email with things like below is very frustrating
    03:45 the animation is weird (predicting each class in turn it should all happen at once)

In my recent experience looking reviewing videos is very painful … I thought maybe just maybe someone somewhere had found a way to make it more palatable but maybe not …

#2

I am not sure I understand the problem. The typos would be in the slides, and you should have those in a more convenient format to proof-read.

In the RR MOOC we also had to proof-read subtitles, which was a bit of a pain, but we had them in text files as well. I don’t remember ever watching a video to search for typos.

#3

BTW, it would be nice to make the slides available for download on the course site as well (we did for the RR MOOC). They are also helpful for students as a quick reminder of what they saw in the videos.

#4

I guess maybe a good screenshoting with editing would already be a good step. I see that you are making a lot of useful screenhots with suggestions for the beta ? What screenshot tool do you use?

About making the slides available, I think there was another question asking for the same thing and indeed we should do it.

For more context about my original question: they tweaked our slides either because the slides had a typo or more recently to add some animation. In the animation, they got the column name wrong (so now the trust is kind of broken slightly I have to admit). So I had to watch the full video to figure out where they changed things (it’s not like they send you a diff where they edited things).

Maybe that was the big mistake we should have stuck to our slides, this is a lot safer. Lessons learned for later.

And now they will send us an updated version of the video and I have to make sure that the fixes were correctly applied. I wrote down all the problems with timings but that takes time and maybe I missed some problems …

#5

MacOS has a built-in screenshot facility, so that’s what I use. It’s convenient for reporting stuff because I just take screenshots as I go along and annotate/submit them later.

Outsourcing work is always risky. For the RR MOOC, we were more lucky with the video editing, but the outsourced translations (we did a bilingual MOOC) were often more funny than useful. It pays to keep things simple, to the point that you can do it yourself.

For checking the edited videos, perhaps a diffing tool (see e.g. https://stackoverflow.com/questions/25774996/how-to-compare-show-the-difference-between-2-videos-in-ffmpeg) could be useful, but I have no personal experience with this.

#6

Thanks a lot for the tips!

#7