Wikimedia Commons mailing list - the shared media repository for all Wikimedia projects

headers Daniel Schwen | 1 Jul 16:51

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l

On Wed, Jul 1, 2009 at 10:51 AM, Daniel Schwen<lists@...> 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_wizard.js');
>
> 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:
>
> http://firefogg.org/make/index.html

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 Schwen<lists@...> wrote:
> Try this:
>>
>> http://firefogg.org/make/index.html
>
> 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 Schwen<lists@...> 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.

All,

I'm very happy to announce that the Ford Foundation has awarded a
$300,000 grant to the Wikimedia Foundation to improve our interfaces
and workflows for multimedia uploading. Press release here:

http://wikimediafoundation.org/wiki/Press_releases/Wikimedia_Ford_Foundation_Grant_July_2009

For the first time we're also sharing a full grant proposal, with
permission of the Ford Foundation. You can find it here:

http://upload.wikimedia.org/wikipedia/foundation/f/f9/WMF_Ford_Multimedia_Participation_Project.pdf

It should give you a good idea about what we can do within the scope
of this project. As a brief recap, Michael Dale has already done some
good work on external repository searches and transfers, and
integration of uploading into the editing UI, so we're hoping to build
on top of this to really get the workflow for
licensing/upload/review/embedding of media files nailed.

We've also been having initial discussions with some of the Wikimedia
chapters about possible models for working together on the execution
of this. For example, we want to make sure that we can facilitate
fruitful face-to-face meetings with Commons practitioners, and there
is plenty of technical work to be done that can be decentralized and
shared. Exciting projects like Wikimedia Germany's investment in
multilingual search are already underway, so hopefully over the next
year, we'll see lots of useful activity culminating in genuine
improvements for Commons and beyond.

Big thanks to Sara Crouse and Naoko Komura for their work on this
grant proposal, and of course to the Ford Foundation for funding it.
 Wikimedia Commons deserves to grow to many more millions of free
educational media files, and hopefully this strategic investment will
help us to get there.

All best,
Erik
--

-- 
Erik Möller
Deputy Director, Wikimedia Foundation

Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate

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_wizard.js'<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@...
> https://lists.wikimedia.org/mailman/listinfo/commons-l
>   

http://arstechnica.com/open-source/news/2009/07/decoding-the-html-5-video-codec-debate.ars

Huh, I got quoted (from the WHATWG list), and my quote even got
illustrated with a lolcat:

    In an e-mail on the WHATWG list, Wikimedia Foundation volunteer
media contact David Gerard said that the organization is also
interested in helping Mozilla to raise general awareness of the
advantages that unencumbered video would bring to the Internet.

    "I'd also point out that Wikimedia has vast publicity abilities in
this direction," he wrote. "And we're watching the progress of Theora
and Dirac on a day-by-day basis, for obvious reasons. So if you need
large charitable organisations to help you with making this the
obvious publicity choice for a happy Internet with cute fluffy
kitties, I can tell you we'll be right there!"

    [image of cute fluffy kittie]

(The "we" I was thinking of was Foundation staff and volunteers
interested in the video efforts, and Commons regulars.)

Greg Maxwell and I have been posting to the mailing list to push Ogg
Theora. I mean, H.264 is technically marvellous and it'd be a lovely
choice, but it's known patent encumbrances - and that MPEG-LA enforce
them - make it *radioactive* for our purposes.

It's IMO futile pushing much harder on the list - Hixie's the editor,
it's his decision, he's an honorable fellow and he's decided he really
can't honestly put Ogg Theora in the spec at present. So it goes back
to pushing Ogg Theora as the de facto format for the web.

- d.

2009/7/7 Platonides <Platonides@...>:

> Do you know what's the state about IE? (not from MS, but I suppose
> someone will be doing/have made some IE plugin)

The best anyone's come up with is browser-sniffing IE then a
workaround (Flash, Java, existing plugin, etc).

- d.

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

3	February 2012
6	January 2012
19	December 2011
16	November 2011
60	October 2011
41	September 2011
23	August 2011
20	July 2011
38	June 2011
207	May 2011
14	April 2011
39	March 2011
93	February 2011
13	January 2011
7	December 2010
16	November 2010
105	October 2010
39	September 2010
29	August 2010
39	July 2010
39	June 2010
87	May 2010
16	April 2010
67	March 2010
62	February 2010
39	January 2010
5	December 2009
51	November 2009
31	October 2009
93	September 2009
60	August 2009
31	July 2009
164	June 2009
40	May 2009
24	April 2009
102	March 2009
48	February 2009
99	January 2009
103	December 2008
82	November 2008
36	October 2008
86	September 2008
145	August 2008
79	July 2008
47	June 2008
100	May 2008
51	April 2008
110	March 2008
84	February 2008
164	January 2008
157	December 2007
209	November 2007
202	October 2007
162	September 2007
335	August 2007
368	July 2007
101	June 2007
112	May 2007
122	April 2007
147	March 2007
153	February 2007
119	January 2007
119	December 2006
261	November 2006
133	October 2006
94	September 2006
149	August 2006
56	July 2006
134	June 2006
44	May 2006
53	April 2006
4	March 2006
6	February 2006
7	January 2006
9	December 2005
2	November 2005
20	October 2005
41	September 2005
3	August 2005
5	July 2005
30	May 2005
3	April 2005
6	March 2005
7	February 2005
8	January 2005
9	December 2004
5	November 2004

Re: firefogg local encode & new-upload branch update.

Re: firefogg local encode & new-upload branch update.

Re: firefogg local encode & new-upload branch update.

Re: firefogg local encode & new-upload branch update.

Re: firefogg local encode & new-upload branch update.

Re: firefogg local encode & new-upload branch update.

$300K grant for Wikimedia Commons

Re: firefogg local encode & new-upload branch update.

Ars Technica on HTML5 video

Re: Ars Technica on HTML5 video