search

microsoft / xblock-azure-media-services

xblock-azure-media-services
Other
14 stars 19 forks source link

How about the milestone of this project? #28

Open tedzhao opened 7 years ago

tedzhao commented 7 years ago

How about the milestone of this project? I see this xBlock is still at an experimental stage, when does release its first normal version?

sdolenc commented 7 years ago

Thanks for reaching out Ted! We've been using this xBlock in our production instance of openedx so this xBlock is functional and ready for community experimentation, but there are at least three issues that we'd like to resolve before moving this out of the experimental beta phase.

  1. The project unfortunately lacks automated test coverage (and continuous integration test runs). We have the work scheduled to accomplish this. We'd be happy to collaborate with the community to get this done faster.
  2. We rely on azuremediaplayer.min.js for video transcript parsing, but there appears to be a bug that impacts recent versions of Firefox. We've been working directly with the team that owns the azuremediaplayer.js library to hopefully get this resolved in an upcoming release. (We created a simple repro of the issue here demo: http://rawgit.com/sdolenc/vtt_repro/master/broken.html code: https://github.com/sdolenc/vtt_repro/blob/master/broken.html )
  3. Finally, we'd like to migrate to a version greater than 2.0 of azuremediaplayer.js . This will bring accessibility fixes and features like adjustable playback speed. This move requires a lot of testing so we're hoping we can make this version move after the bug impacting Firefox is resolved

There are other goals on our roadmap that'll make this xBlock even better, but those are the urgent issues we'd like to fix soon.

In any event, let me know if you have any difficulty installing or using the xBlock. I'd be happy to help and update our documentation accordingly.

mamigot commented 7 years ago

Hey @sdolenc ,

Do you have an estimate of the timelines for each of these issues (especially the second one)?

Really looking forward to trying this out as well!

Thanks,

sdolenc commented 7 years ago

Thanks for the reaching out @mamigot ! It's unfortunately difficult to give a precise estimate for the fix to "Issue 2" at this time.

We don't currently have an ETA for when the vtt fix for Firefox will be included as part of azuremediaplayer.js . Our next meeting with the team that owns the library is next week.

We'll then need to fix "Issue 3" to consume a version of azuremediaplayer.js that includes the fix. As mentioned before, this requires testing and code changes on our end. We have to balance that work against our other high priority tasks so it's hard to give the exact timeline, but we'd be happy to collaborate with the community to accelerate this as well.

I apologize we don't have a better answer yet, but we'll will ping this thread as soon as we have more information. In the meantime, feel free to reach out if you encounter any problems with the xBlock

mamigot commented 7 years ago

No worries, @sdolenc ! Looking forward to it, and thanks!

sdolenc commented 7 years ago

(update @mamigot and @tedzhao )

I submitted pull request https://github.com/Microsoft/xblock-azure-media-services/pull/34 to fix the firefox bug (issue 2 mentioned above that is now also impacting recent versions of chrome)

Feel free to hop on the review if you have feedback/ideas.

We're also working on the true fix in azuremediaplayer.js as we speak. That'll be a better, cleaner longterm fix

Thanks for the continued patience as we get this work scheduled/completed