As you may know I have been working on firefogg integration with mediaWiki. As you may also know the mwEmbed library is being designed to support embedding of these interfaces in arbitrary external contexts. I wanted to quickly highlight a useful stand alone usage example of the library:
http://www.firefogg.org/make/advanced.html
This "Make Ogg" link will be something you can send to a person so they can encode source footage to a local ogg video file with the latest and greatest ogg encoders (presently the thusnelda theora encoder & vorbis audio). Updates to thusnelda and other free codecs will be pushed out via firefogg updates.
For commons / wikimedia usage we will directly integrate firefogg (using that same codebase) You can see an example of how that works on the 'new-upload' branch here: http://sandbox.kaltura.com/testwiki/index.php/Special:Upload ... hopefully we will start putting some of this on testing.wikipedia.org ~soonish ?~
The new-upload branch feature set is quite extensive including the script-loader, jquery javascript refactoring, the new upload-api, new mv_embed video player, add media wizard etc. Any feedback and specific bug reports people can do will be super helpful in gearing up for merging this 'new-upload' branch.
For an overview see: http://www.mediawiki.org/wiki/Media_Projects_Overview
peace, --michael
Hey Michael, hey List!
A few months ago we had the possibility of testing the AddMediaWizzard by including a script in our monobook.js:
importScriptURI(' http://mvbox2.cse.ucsc.edu/wiki/extensions/MetavidWiki/skins/add_media_wizar...'http://mvbox2.cse.ucsc.edu/wiki/extensions/MetavidWiki/skins/add_media_wizard.js%27 );
This URL is now dead. Is there still a way to get a sneak peek at the current status. I'm asking because I'd like to set it up for a user who has severe problems transcoding his video for upload.
Daniel -- [[User:Dschwen]]
On Wed, Jul 1, 2009 at 10:51 AM, Daniel Schwenlists@schwen.de wrote:
A few months ago we had the possibility of testing the AddMediaWizzard by including a script in our monobook.js:
importScriptURI('http://mvbox2.cse.ucsc.edu/wiki/extensions/MetavidWiki/skins/add_media_wizar...');
This URL is now dead. Is there still a way to get a sneak peek at the current status. I'm asking because I'd like to set it up for a user who has severe problems transcoding his video for upload.
Try this: http://firefogg.org/make/index.html
It's the same firefogg transcoder (you need Firefox 3.5), but it saves the output on the user's computer rather than directly uploading it, and the output can then be uploaded to Commons manually.
-Sage (User:Ragesoss)
Try this:
Yeah, thanks, I knew that one already.
In fact I earlier today changed the german translation of [[Help:Converting_video]] to solely refer to this page. It was a horrible clutter of complicated platformspecific solutions, more confusing than helpful for a newbie.
On Wed, Jul 1, 2009 at 5:23 PM, Daniel Schwenlists@schwen.de wrote:
Try this:
Yeah, thanks, I knew that one already.
In fact I earlier today changed the german translation of [[Help:Converting_video]] to solely refer to this page. It was a horrible clutter of complicated platformspecific solutions, more confusing than helpful for a newbie.
It would be helpful if the help pages also directed people to a place to report files that won't convert.
I've had a number of people complaint to me that the ffmpeg decoder in ffmpeg2theora is insufficiently forgiving of the vulgarities of files found in the real world... but I've had little luck in actually collecting a set of files that don't work.
It would be helpful if the help pages also directed people to a place to report files that won't convert.
Where should we direct them. Just to their respective Village Pump? I know, a bugtracker (firefogg?) would be appropriate, especially if people could attach original files. But then again, those are likely to be very large.
On Wed, Jul 1, 2009 at 5:59 PM, Daniel Schwenlists@schwen.de wrote:
It would be helpful if the help pages also directed people to a place to report files that won't convert.
Where should we direct them. Just to their respective Village Pump? I know, a bugtracker (firefogg?) would be appropriate, especially if people could attach original files. But then again, those are likely to be very large.
Ultimately input-side bugs need to be reported to FFMPEG, but they need to be qualified against the latest FFMPEG source code, and the ffmpeg bug tracker is a decidedly not user friendly place to send firefogg users.
Village pump would be a good start.
The new url is: http://metavid.org/w/js2/remoteMwEmbed.js
But I recommend you use the firefogg.org site version since the integration is been redesigned to work with the new-upload branch and does not work so well with the old POST at once upload system. If we expect more delays with the new-upload integration or people want to use firefogg with old version of mediaWiki I can revisit the fall-back post-at-once support should just be very minor adjustments to get it working again.
--michael
Daniel Schwen wrote:
Hey Michael, hey List!
A few months ago we had the possibility of testing the AddMediaWizzard by including a script in our monobook.js:
importScriptURI(' http://mvbox2.cse.ucsc.edu/wiki/extensions/MetavidWiki/skins/add_media_wizar...'http://mvbox2.cse.ucsc.edu/wiki/extensions/MetavidWiki/skins/add_media_wizard.js%27 );
This URL is now dead. Is there still a way to get a sneak peek at the current status. I'm asking because I'd like to set it up for a user who has severe problems transcoding his video for upload.
Daniel
[[User:Dschwen]]
Commons-l mailing list Commons-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/commons-l