It will be a lot easier to import from YouTube once Timed media handler adds support for webm to commons. If you check out the wikivideo-l and commons lists for some recent example YouTube to commons scripts. I know this is not super useful info right this second, but there is hope on the horizon.
peace, --michael
----- Reply message ----- From: "Itzik Edri" itzik@infra.co.il To: "Wikimedia Foundation Mailing List" foundation-l@lists.wikimedia.org Subject: [Foundation-l] Tragedy: videos and slides from presentations Wikimanias (lately 2011 in Haifa) Date: Sat, Sep 3, 2011 2:40 pm
Hi,
As I said before - all Wikimania sessions had been recorded (in HD format!). As everyone who work with video know, to produce 120 hours of HD videos, is not an easy thing at all.
We had to finish a lot of administrative work which related to Wikimania, and we just back to take care for this issue - to edit, decode and upload. Videos are already on their way online to Youtube and we hope to upload all of them until the end of the month. After we will finish that, we will need to find more time again to decode them and compress them so we can upload to Commons (every decode file who been uploads right now to youtube is about 3-4GB).
All the footage are backup on two hard drive, one that belong to Wikimedia Israel and one which will be sent to WMF for archive. So we have all the data, and it is only matter of time. Be patients please.
Itzik
On Sat, Sep 3, 2011 at 12:02 PM, Jan Kucera (Kozuch) garbage5@seznam.czwrote:
Hi there,
I think WMF should set up some "quality measures" to make sure there actually is some reasonable online output from every Wikimedia conference. There might be thousands of editors not being able to attend but wanting to watch what was going on. Now you have to dig and beg for any slides or video on Commons. I do not know the decision process for a location but so far almost every host failed miserably to deliver some reasonable online content like videos and slides from the presentations.
Kozuch
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
_______________________________________________ foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
On 4 September 2011 21:44, Michael Dale mdale@wikimedia.org wrote:
It will be a lot easier to import from YouTube once Timed media handler adds support for webm to commons. If you check out the wikivideo-l and commons lists for some recent example YouTube to commons scripts. I know this is not super useful info right this second, but there is hope on the horizon.
How's Timed Media Handler (which will also allow WebM/VP8) going? ETA?
- d.
On Sun, Sep 4, 2011 at 1:49 PM, David Gerard dgerard@gmail.com wrote:
On 4 September 2011 21:44, Michael Dale mdale@wikimedia.org wrote:
It will be a lot easier to import from YouTube once Timed media handler
adds support for webm to commons. If you check out the wikivideo-l and commons lists for some recent example YouTube to commons scripts. I know this is not super useful info right this second, but there is hope on the horizon.
How's Timed Media Handler (which will also allow WebM/VP8) going? ETA?
The code exists and has been revamped a few times in response to reviews, but I'm not sure whether there are actually any assigned resources for pushing it to production at this time.
Robla, Erik, can you clarify state on this? Is TMH deployment on the radar for the next few months, or does it still need to get put on the map? There's some notes on http://www.mediawiki.org/wiki/TimedMediaHandler/statusabout earlier discussion of a September-ish production test, but not sure if that's current.
-- brion
On Tue, Sep 6, 2011 at 11:02 AM, Brion Vibber brion@pobox.com wrote:
The code exists and has been revamped a few times in response to reviews, but I'm not sure whether there are actually any assigned resources for pushing it to production at this time.
Yes, there are. Ian and Neil are scheduled to do a code review of TMH, once remaining high priority issues with UploadWizard have been resolved, later this month. Before we've done an initial assessment of the code, it's hard to give a realistic deployment estimate -- there may be parts that need to be rewritten or taken out. So I won't commit us to a public date just yet, just to say that it's definitely something I'd like to see user-visible progress on this calendar year.
Whatever remaining bugbears are lurking in the code, TMH definitely represents the key set of features that are needed to make video in Wikimedia projects suck significantly less (multi-codec and multi-bitrate derivatives generation; a non-ugly player skin; subtitle support). This is really a baseline feature set that we have to get done (this and better large file upload support) to not give users an embarrassingly bad video experience.
On Tue, Sep 6, 2011 at 3:15 PM, Erik Moeller erik@wikimedia.org wrote:
On Tue, Sep 6, 2011 at 11:02 AM, Brion Vibber brion@pobox.com wrote:
The code exists and has been revamped a few times in response to reviews, but I'm not sure whether there are actually any assigned resources for pushing it to production at this time.
Yes, there are. Ian and Neil are scheduled to do a code review of TMH, once remaining high priority issues with UploadWizard have been resolved, later this month. Before we've done an initial assessment of the code, it's hard to give a realistic deployment estimate -- there may be parts that need to be rewritten or taken out. So I won't commit us to a public date just yet, just to say that it's definitely something I'd like to see user-visible progress on this calendar year.
All good news!
The player support is definitely a lot nicer -- and I think we've been running extra JS stuff from that on Commons for a while.
The generation & handling of derivative files looks like the biggest candidate for potential breakage / rewriting from what I recall (it's still pretty basic in terms of managing processes, so if anything goes wrong it may be tricky to recover).
Simply being able to upload larger files will be a big help as well; audio and video clips from eg conference talks are routinely hard to upload to Commons because of the 100mb limit we still have in place for plain HTTP uploads and limited access to upload-by-URL.
The upload size limit could be bumped a bit more, but can only be bumped so far before it starts using too much memory during upload -- but there's been work on incremental uploads too, which for many modern browsers will be able to kick in automatically and will bypass that side of the limits, provide better upload progress feedback, and be more reliable in the case of flaky connections or having to put your laptop to sleep!
IIRC the incremental uploads aren't part of TMH directly, but is also in Michael's sphere of awesome projectness. :)
-- brion
Comments inline:
On 09/06/2011 03:33 PM, Brion Vibber wrote:
All good news!
The player support is definitely a lot nicer -- and I think we've been running extra JS stuff from that on Commons for a while.
Yea the js has been running as a gadget for a while. But I have forked away from the gadget as it was reworked for the new ResourceLoader / TMH extension and reworked for other use cases of the library such as the Internet Archive player, the Adobe Dremweaver widget and to support the Kaltura platform mobile feature set across hundreds of deployments. More info on html5video.org
The generation & handling of derivative files looks like the biggest candidate for potential breakage / rewriting from what I recall (it's still pretty basic in terms of managing processes, so if anything goes wrong it may be tricky to recover).
I did address all the bugs you outlined a while back. I don't know if you have gotten a chance to review the latest, but you do get a detailed status on every transcode job, its failure message, time of failure, amount of time spent transcoding, all with a db back end and "managed" memory / time ffmpeg shell calls with wfShellExec and nice. End web users with the 'reset-transcode' permission can use a web interface to reset any given transcode job.
The transcode job runner has been running on http://prototype.wikimedia.org/timedmedia ( it has been heavily taxed ) but its been up for about month and a half, unmanaged and is still accepting and running new jobs.
That being said, looking forward to more testing and review to identify anything we can do to improve the robustness of the system.
IIRC the incremental uploads aren't part of TMH directly, but is also in Michael's sphere of awesome projectness. :)
Yes that work was done by Jan Gabber who is helping out as well. Upload Wizard has support in trunk for incremental uploads, awaiting review and to flip the configuration flag to turn it on. This would let us accept much larger files since they would come in 1 meg at a time.
peace, --michael
wikimedia-l@lists.wikimedia.org