In many of our customer engagements, we find ourselves having conversations with customers who want:
1) to secure their videos (which means Youtube is not an option)
2) to use the edX video player (because they like the speed up/slow down and interactive transcript support)
3) to have the adaptive bitrate so that the videos play back optimally according to the user's device and bandwidth (which means S3 is not an option)
Afaik, these 3 things are mutually exclusive which means that our customers are stuck between foregoing the use of the edX video player and using a native player like Wistia, Brightcove or Vimeo (none of which have an interactive transcript), or using the native edX video player but risking that their videos are publicly exposed (if they use Youtube), or foregoing adaptive bitrate support (if they use S3).
I'm wondering if others have found good solutions to address these limitations. It seems like there are several options:
1) Extend the edX video player to support players other than Youtube or S3, like Wistia, Brightcove, Vimeo which all let you protect the video content by domain/IP restriction.
2) Make the edX video player able to negotiate with the client to serve an appropriate video file (HD, SD depending on the bandwidth and device). That way, you could at least upload the various renditions to S3, and the video player would figure out which one to use during playback, or at the very least, the student could manually select their preference as a profile setting.
3) Build a new XBlock video player, using something like Wistia as the backend, and use Wistia's API to:
a) send student IDs from Open edX to Wistia for reporting purposes
b) index the transcripts so that they appear in the edX search
I've already had a phone call with the CTO of Wistia (which happens to be a Boston-based company) about option #3, and he is willing to put some engineering support behind such an effort. The Wistia engineers obviously don't know Open edX, but could provide assistance on the Wistia API side.
Are there other folks on this list who would be interested in exploring one of these options, and even putting some money behind it? We can probably get a customer or two to co-fund the efforts, but it might be a lot of work, so we want to gauge demand and support before proceeding.
Nate