New Media Features Gadget

by
Translate this post

I would like to announce that some of the new media features are now available in gadget form on Wikimedia Commons and the English Wikipedia. These include a new ogg player, the add media wizard, and firefogg upload support. I hope having these components in gadget form will enable some more testing and feedback 🙂
Getting Started to enable these components you must turn on the mwEmbed gadget. You can turn it on by visiting your preferences page. Once you enable the gadget you should shift reload to ensure you have a fresh copy of the JavaScript. (note you will need to enable the gadget for each wiki you want to test (ie both for wikimedia commons and Wikipedia). Once enabled you can check out the following features:
Disclaimer You can always turn off the gadget the same way you turned it on. These components are still under development so your millage may vary.
New Video Player ( discuss / bug ) the new ogg video player provides a consistent interface for various player plugin types. Most of the player features are yet to be exposed, like timed text, and remote embedding. The new player is show anywhere an embed video appears.
Firefogg Uploading ( discuss / bug ) Firefogg has been previously discussed on this blog. Aside from general bug fixes new features with Firefogg include: real time preview and integration with the recently deployed upload-api. The upload api enables Firefogg to upload videos in 1 meg chunks which are more friendly to http POST requests. You can do test uploads on test.wikimedia.org
Add-Media-Wizard ( discuss / bug ) The add-media-wizard enables easy inclusion of media assets into pages without having to remember image insert syntax at the point of editing a page. More features like importing from remote repositories and inline uploading should be available soon once we enable uploading from remote urls on commons. You can get a sneak peek by checking it out on prototype sandbox.
Many media components are developed in an open source development partnership with Kaltura.com.

Archive notice: This is an archived post from blog.wikimedia.org, which operated under different editorial and content guidelines than Diff.

Can you help us translate this article?

In order for this article to reach as many people as possible we would like your help. Can you translate this article to get the message out?

6 Comments
Inline Feedbacks
View all comments

#1080

Great features! Hope they will be available soon! Also in the Dutch wikia’s 🙂

0
#1081

What about subtitles?
It would be awesome if sub-titles in multiple languages could be added to video and audio so they can be searched and so they can be used in different language wikis.

0
#1082

In terms of multi-lingual support I should have something ready shortly that lets us request a given language of the js via the script-loader.
In terms of subtitles… this is something I also want to get in there soon as well. I have some code to support subtitles from the metavid.org work … but the interfaces need to be updated for multi-lingual subtitle translation and contribution.

0
#1083

What encoder settings are being used for conversion by FireOgg? I uploaded the same fil to test.wikipedia and tinyvid.tv and got different file sizes (wikipedia’s was about 20% smaller).

0
#1084

the firefogg encode settings are currently:
encoder_settings:{
‘maxSize’ : ‘400’,
‘videoBitrate’ : ‘544’,
‘audioBitrate’ : ’96’,
‘noUpscaling’ : true
},
This may shift to much higher quality once we have a derivatives extension in place. That way a single File resource can be represented by several files at different bitrates.

0
#1085

What will the fallback option be if Firefogg is unable to convert the video? Also, it’ll probably be useful to log media information regarding unsuccessful encodings.

0

Meta

Posted in Labs, TechnologyTagged , , , , ,