interesting short thread/idea here, regarding the "play icon" overlay on
video thumbnails. To somehow make it less dominating:
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28idea_lab%29#Less_in…
I think this has been discussed before, but I forget where. Perhaps someone
here could summarize the options and pros/cons, or can find links to older
threads?
I've gotten some great review feedback from Gilles on the desktop-web
integration of my ogv.js JavaScript & Flash compatibility layers for Ogg
Theora/Vorbis media files -- thanks Gilles!
* libraries: https://gerrit.wikimedia.org/r/#/c/165477/
* desktop integration: https://gerrit.wikimedia.org/r/#/c/165478/
These are getting pretty close to ready to land, I think.
I would love to get some review on the mobile overlay I've whipped up as
well. This supports both native WebM playback (Android Chrome, Android
Firefox, Firefox OS) and ogv.js playback (iOS 7/8 Safari).
* mobile overlay: https://gerrit.wikimedia.org/r/#/c/165479/
* Live demo: https://ogvjs-testing.wmflabs.org/
A few open questions:
1) Is this the right way to do mobile overlay code? (It's basically a rip
of the existing photo viewer overlay in MobileFrontend, but lives in
TimedMediaHandler.) Is the overlay interface stable enough for other
extensions to use it for mobile-specific features? (I had to make updates
for object-model and template things that changed since this summer.)
2) Is the inline icon too huge/ugly here for audio files? Should it be
arranged differently, or display the player inline instead of as an overlay
for audio?
3) Should more controls be added to the overlay's bottom toolbar, such as
manual resolution selection or an 'Open in VLC' link to support HD playback
on iOS?
4) Should we autoplay when opening the overlay, or require a second tap?
5) How should we handle devices with no native playback that are either too
slow (iOS 6 Safari) or lack necessary features needed for the player
(Windows Phone)?
Current known bugs in the mobile overlay:
* CPU speed check not yet integrated to force to lowest resolution for old
iPhones/iPads (this exists on the desktop integration, just needs to be
moved to common code)
* autoplay doesn't seem to work with native playback right now
-- brion
---------- Forwarded message ----------
From: "Alessio Treglia" <alessio(a)debian.org>
Date: Oct 22, 2014 1:42 PM
Subject: Bits from the Debian Multimedia Maintainers
To: <debian-devel-announce(a)lists.debian.org>
Cc:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
> Ciao!
>
> The Debian Multimedia Maintainers have been quite active since the
> Wheezy release, and have some interesting news to share for the Jessie
> release. Here we give you a brief update on what work has been done and
> work that is still ongoing.
>
> Let's see what's cooking for Jessie then.
>
>
> Frameworks and libraries
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> * Support for many new media formats and codecs.
>
> The codec library libavcodec, which is used by popular media playback
> applications including vlc, mpv, totem (using gstreamer1.0-libav), xine,
> and many more, has been updated to the latest upstream release version
> 11 provided by Libav [libav]. This provides Debian users with HEVC
> playback, a native Opus decoder, Matroska 3D support, Apple ProRes, and
> much more. Please see [libav-changelog] for a full list of functionality
> additions and updates.
>
> * libebur128
>
> libebur128 is a free implementation of the European Broadcasting Union
> Loudness Recommendation (EBU R128), which is essentially an alternative
> to ReplayGain. The library can be used to analyze audio perceived
> loudness and subsequentially normalize the volume during playback.
>
> * libltc
>
> libltc provides functionalities to encode and decode Linear (or
> Longitudinal) Timecode (LTC) from/to SMPTE data timecode.
>
> * libva
>
> libva and the driver for Intel GPUs has been updated to the 1.4.0
> release. Support for new GPUs has been added. libva now also supports
> Wayland.
>
> * Pure Data
>
> A number of new additional libraries (externals) will appear in Jessie,
> including (among others) Eric Lyon's fftease and lyonpotpourrie, Thomas
> Musil's iemlib, the pdstring library for string manipulation and pd-lua
> that allows to write Pd-objects in the popular lua scripting language.
>
>
> JACK and LADI
> ~~~~~~~~~~~~~
>
> LASH Audio Session Handler was abandoned upstream a long time ago in
> favor of the new session management system, called ladish (LADI Session
> Handler). ladish allows users to run many JACK applications at once and
> save/restore their configuration with few mouse clicks.
>
> The current status of the integration between the session handler and
> JACK may be summarized as follows:
> * ladish provides the backend;
> * laditools contains a number of useful graphical tools to tune the
> session management system's whole configuration (including JACK);
> * gladish provides a easy-to-use graphical interface for the session
> handler.
>
> Note that ladish uses the D-Bus interface to the jack daemon, therefore
> only Jessie's jackd2 provides support for and also cooperates fine
> with it.
>
>
> Plugins: LV2 and LADSPA
> ~~~~~~~~~~~~~~~~~~~~~~~
>
> Debian Jessie will bring the newest 1.10.0 version of the LV2 technology
> [lv2]. Most changes affect the packaging of new plugins and extensions,
> a brief list of packaging guidelines is now available [lv2-packaging].
>
> A number of new plugins and development tools too have been made
> available during the Jessie development cycle:
>
> * LV2 Toolkit
>
> LVTK provides libraries that wrap the LV2 C API and extensions into easy
> to use C++ classes. The original work for this
> was mostly done by Lars Luthman in lv2-c++-tools.
>
> * Vee One Suite
>
> The whole suite by Rui Nuno Capela is now available in Jessie, and
> consists of three components:
> drumkv1: old-school drum-kit sampler synthesizer
> samplv1: polyphonic sampler
> synthv1: analog-style 4-oscillator substractive synthesizer
> All three are provided in both forms of LV2 plugins and stand-alone JACK
> client. JACK session, JACK MIDI, and ALSA MIDI are supported too.
>
> * x42-plugins and zam-plugins
>
> LV2 bundles containing many audio plugins for high quality processing.
>
> * Fomp
>
> Fomp is an LV2 port of the MCP, VCO, FIL, and WAH plugins by Fons
> Adriaensen.
>
> Some other components have been upgraded to more recent upstream versions:
>
> * ab2gate: 1.1.7
> * calf: 0.0.19+git20140915+5de5da28
> * eq10q: 2.0~beta5.1
> * NASPRO: 0.5.1
>
> We've packaged ste-plugins, Fons Adriaensen's new stereo LADSPA plugins
> bundle.
> A major upgrade of frei0r [frei0r], namely the standard collection for
> the minimalistic plugin API for video effects, will be available in
> Jessie.
>
>
> New multimedia applications
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> * Advene
>
> Advene (Annotate Digital Video, Exchange on the NEt) is a flexible video
> annotation application.
>
> * Ardour3
>
> The new generation of the popular digital audio workstation will make
> its very first appearance in Debian Jessie.
>
> * Cantata
>
> Qt4 front-end for the MPD daemon.
>
> * Csound
>
> Csound for jessie will feature the new major series 6, with the improved
> IDE CsoundQT. This new csound supports improved array data type
> handling, multi-core rendering and debugging features.
>
> * din
>
> DIN Is Noise is a musical instrument and audio synthesizer that supports
> JACK audio output, MIDI, OSC, and IRC bot as input sources. It could be
> extended and customized with Tcl scripts too.
>
> * dvd-slideshow
>
> dvd-slideshow consists of a suite of command line tools which come in
> handy to make slideshows from collections of pictures. Documentation is
> provided and available in `/usr/share/doc/dvd-slideshow/'.
>
> * dvdwizard
>
> DVDwizard can fully automate the creation of DVD-Video filesystem. It
> supports graphical menus, chapters, multiple titlesets and
> multi-language streams. It supports both PAL and NTSC video modes too.
>
> * flowblade
>
> Flowblade is a video editor - like the popular KDenlive based on the MLT
> engine, but more lightweight and with some difference in editing concepts.
>
> * forked-daapd
>
> Forked-daapd switched [forked-daapd] to a new, active upstream again
> dropping Grand Central Dispatch in favor of libevent. The switch fixed
> several bugs and made forked-daapd available on all release
> architectures instead of shipping only on amd64 and i386. Now nothing
> prevents you from setting up a music streaming (DAAP/DACP) server on
> your favorite home server no matter if it is based on mips, arm or x86!
>
> * harvid
>
> HTTP Ardour Video Daemon decodes still images from movie files and
> serves them via HTTP. It provides frame-accurate decoding and is main
> use-case is to act as backend and second level cache for rendering the
> videotimeline in Ardour.
>
> * Groove Basin
>
> Groove Basin is a music player server with a web-based user interface
> inspired by Amarok 1.4. It runs on a server optionally connected to
> speakers. Guests can control the music player by connecting with a
> laptop, tablet, or smart phone. Further, users can stream their music
> libraries remotely.
> It comes with a fast, responsive web interface that supports keyboard
> shortcuts and drag drop. It also provides the ability to upload songs,
> download songs, and import songs by URL, including YouTube URLs. Groove
> Basin supports Dynamic Mode which automatically queues random songs,
> favoring songs that have not been queued recently.
> It automatically performs ReplayGain scanning on every song using the
> EBU R128 loudness standard, and automatically switches between track and
> album mode. Groove Basin supports the MPD protocol, which means it is
> compatible with MPD clients. There is also a more powerful Groove Basin
> protocol which you can use if the MPD protocol does not meet your needs.
>
> * HandBrake
>
> HandBrake, a versatile video transcoder, is now available for Jessie. It
> could convert video from nearly any format to a wide range of commonly
> supported codecs.
>
> * jack-midi-clock
>
> New jackd midiclock utility made by Robin Gareus.
>
> * laborejo
>
> Laborejo, Esperanto for "Workshop", is used to craft music through
> notation. It is a LilyPond GUI frontend, a MIDI creator and a tool
> collection to inspire and help music composers.
>
> * mpv
>
> mpv [mpv] is a movie player based on MPlayer and mplayer2. It supports a
> wide variety of video file formats, audio and video codecs, and subtitle
> types. The project focuses mainly on modern systems and encourages
> developer activity. As such, large portions of outdated code originating
> from MPlayer have been removed, and many new features and improvements
> have been added [mpv-changelog]. Note that, although there are still
> some similarities to its predecessors, mpv should be considered a
> completely different program (e.g. lacking compatibility with both
> mplayer and mplayer2 in terms of command-line arguments and
> configuration).
>
> * smtube
>
> SMTube is a stand-alone graphical video browser and player, which makes
> YouTube's videos browsing, playing, and download such a piece of cake.
> It has so many features that, we are sure, will make YouTube lovers
> very, very happy.
>
> * sonic-visualiser
>
> Sonic Visualiser Application for viewing and analysing the contents of
> music audio files.
>
> * SoundScapeRenderer
>
> SoundScapeRenderer (aka SSR) is a (rather) easy to use render engine for
> spatial audio, that provides a number of different rendering algorithms,
> ranging from binaural (headphone) playback via wave field synthesis to
> higher-order ambisonics.
>
> * Videotrans
>
> videotrans is a set of scripts that allow its user to reformat existing
> movies into the VOB format that is used on DVDs.
>
> * XBMC
>
> XBMC has been partially rebranded as "XBMC from Debian" [xbmc-debian] to
> make it clear that it is changed to conform to Debian's Policy. The
> latest stable release, 13.2 Gotham will be part of Jessie making Debian
> a good choice for HTPC-s.
>
> * zita-bls1
>
> Binaural stereo signals converter made by Fons Adriaensen
>
> * zita-mu1
>
> Stereo monitoring organiser for jackd made by Fons Adriaensen
>
> * zita-njbridge
>
> Jack clients to transmit multichannel audio over a local IP network made
> by Fons Adriaensen
>
> * radium-compressor
>
> Radium Compressor is the system compressor of the Radium suite. It is
> provided in the form of stand-alone JACK application.
>
>
> Multimedia Tasks
> ~~~~~~~~~~~~~~~~
>
> With Jessie we are shipping a set of multimedia related tasks [tasks].
> They include package lists for doing several multimedia related tasks.
> If you are interested in defining new tasks, or tweaking the current,
> existing ones, we are very much interested in hearing from you.
>
>
> Upgraded applications and libraries
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> * Aeolus: 0.9.0
> * Aliki: 0.3.0
> * Ams: 2.1.1
> * amsynth: 1.4.2
> * Audacious: 3.5.2
> * Audacity: 2.0.5
> * Audio File Library: 0.3.6
> * Blender: 2.72b
> * Bristol: 0.60.11f
> * C* Audio Plugin Suite: 0.9.23
> * Cecilia: 5.0.9
> * cmus: 2.5.0
> * DeVeDe: 3.23.0-13-gbfd73f3
> * DRC: 3.2.1
> * EasyTag: 2.2.2
> * ebumeter: 0.2.0
> * faustworks: 0.5
> * ffDiaporama: 1.5
> * ffms: 2.20
> * gmusicbrowser: 1.1.13
> * Hydrogen: 0.9.6.1
> * IDJC: 0.8.14
> * jack-tools: 20131226
> * LiVES: 2.2.6
> * mhWaveEdit: 1.4.23
> * Mixxx: 1.11.0
> * mp3fs: 0.91
> * MusE: 2.1.2
> * Petri-Foo: 0.1.87
> * PHASEX: 0.14.97
> * QjackCtl: 0.3.12
> * Qtractor: 0.6.3
> * rtaudio: 4.1.1
> * Rosegarden: 14.02
> * rtmidi: 2.1.0
> * SoundTouch: 1.8.0
> * stk: 4.4.4
> * streamtuner2: 2.1.3
> * SuperCollider: 3.6.6
> * Synfig Studio: 0.64.1
> * TerminatorX: 3.90
> * tsdecrypt: 10.0
> * Vamp Plugins SDK: 2.5
> * VLC: Jessie will release with the 2.2.x series of VLC
> * XCFA: 4.3.8
> * xwax: 1.5
> * xjadeo: 0.8.0
> * x264: 0.142.2431+gita5831aa
> * zynaddsubfx: 2.4.3
>
>
> What's not going to be in Jessie
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> with the aim to improve the overall quality of the multimedia software
> available in Debian, we have dropped a number of packages which were
> abandoned upstream:
>
> * beast
> * flumotion
> * jack-rack
> * jokosher
> * lv2fil (suggested replacement for users is eq10q or calf eq)
> * phat
> * plotmm
> * specimen (suggested replacement for users is petri-foo - fork of
> specimen)
> * zynjacku (suggested replacement for users is jalv)
>
> We've also dropped mplayer, presently nobody seems interested in
> maintaining it.
> The suggested replacements for users are mplayer2 or mpv. Whilst the
> former is mostly compatible with mplayer in terms of command-line
> arguments and configuration (and adds a few new features too), the
> latter adds a lot of new features and improvements, and it is actively
> maintained upstream.
>
> Please note that although the mencoder package is no longer available
> anymore, avconv and mpv do provide encoding functionality. For more
> information see [avconv-man], [avconv-documentation] and [mpv-encoding].
>
>
> Broken functionalities
> ~~~~~~~~~~~~~~~~~~~~~~
>
> rtkit under systemd is broken at the moment. [bug747568]
>
>
> Activity statistics
> ~~~~~~~~~~~~~~~~~~~
>
> More information about team's activity are available at [team-stats].
>
>
> Where to reach us
> ~~~~~~~~~~~~~~~~~
>
> The Debian Multimedia Maintainers can be reached at
> pkg-multimedia-maintainers AT lists.alioth.debian.org for packaging
> related topics, or at debian-multimedia AT lists.debian.org for user and
> more general discussion.
>
> We would like to invite everyone interested in multimedia to join us
> there. Some of the team members are also in the #debian-multimedia
> channel on OFTC.
>
>
> Cheers!
>
>
> Alessio Treglia
> on behalf of the Debian Multimedia Maintainers
>
>
>
> [bug747568] https://bugs.debian.org/747568
> [forked-daapd] http://bit.ly/1rqwAW1
> [frei0r] http://frei0r.dyne.org/
> [libav] http://libav.org
> [libav-changelog] http://bit.ly/1DB3MTo
> [lv2] http://lv2plug.in/
> [lv2-packaging] https://wiki.debian.org/DebianMultimedia/Policy/LV2
> [mpv] http://mpv.io/
> [mpv-changelog] http://bit.ly/1tLqV4i
> [mpv-encoding] http://bit.ly/1tcgE0f
> [avconv-man] http://bit.ly/1s8QKE5
> [avconv-documentation] https://libav.org/avconv.html
> [tasks] http://blends.debian.org/multimedia/tasks/index
> [team-stats] http://blends.debian.org/multimedia/
> [xbmc-debian] http://balintreczey.hu/blog/introducing-xbmc-from-debian/
>
>
> - --
> Alessio Treglia | www.alessiotreglia.com
> Debian Developer | alessio(a)debian.org
> Ubuntu Core Developer | quadrispro(a)ubuntu.com
> 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBCgAGBQJUR+wTAAoJEOikiuUxHXZadN8P/RqWC6LKNXUrUNGk3J1zRQx9
> Op1HzPv7dvhWjpRiYkSHKw1P9Q7Dm6cSVCp3sjtH9FYmBMz8CTA0/agsSMMPvgXU
> NuRAlvILCjCuHAJ0PqySBb8buIpVWkz/vHCmV10CiWK7eK5NhcJdbUH5tQkG8bQy
> IfYYWlivt7DTMePz3JkWozFNTMwELCS3qhmQE7Mh+FhU3I8PXA5+k/SU7bRH6Nfv
> I6hlYsri+SmB9bhA1O9Lvrzqy/A6nZx8C4iq/yfj/4jw2uwIZ5pskzgd29yNaAPX
> 0H48IfaHhaHqu5q7fAtZ7N2iuEK35rK2OOkcSOmBJNvEeAPB/kHzXnMfQHzIlekY
> os0gENSpG2woKuxeQVw1/nWx/ItutfE0OMvRyKMllW7TubAelN2MvIgYMEjU2nJ/
> QssXjC4HGOazeH7Q7biluAo10UVQ0jE5yoaOoMvn/qQ/TWc/BX8LvK+x+erkac90
> R1PHcfQmYZMhQMgLTwT5VK0/hcWGlSJCqcuPO16Y4JmEh3Q95ZQ9XXmniLkVW491
> XAo0ql02z6K2hciK8F7K9CbSpNGGJUqB9yRbyFAPTA2J9Z/Kn4u6KP/vR1SXxtOE
> XhrFUA5TRcsRJdIypzizYwey4cq9hXV6/92XomUgHUwXMvm99Fi+3veV9vWIel1j
> cIj8TILYs7cst2c9D/ts
> =N7zp
> -----END PGP SIGNATURE-----
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-announce-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster(a)lists.debian.org
> Archive: https://lists.debian.org/5447EC14.2070502@debian.org
>
Hi everyone,
We just released a few more improvements to Media Viewer, based on community feedback:
* An easier way to disable Media Viewer for personal use
* Re-enable Media Viewer from a file page
* Rename File page button: "Open in Media Viewer"
* Make MediaViewer text larger in Monobook
These features are now live on Wikimedia Commons and sister projects (1), and will be deployed on all Wikipedias this Thursday by 20:00 UTC.
The new Disable/Enable features make it much easier to turn Media Viewer on or off, by clicking on a prominent 'cogs' icon, as described in the Help FAQ (2).
Next, we are working on this last big 'must-have’ improvement for this release:
* a caption or description right below the image
These improvements are based on the most frequent requests from our recent community consultation (3) and user research (4). Learn more about these features on the Media Viewer Improvements page (5), and please let us know what you think of these new features on the Media Viewer talk page (6).
Many thanks to all the community members who suggested these improvements. Our user research so far confirms that they provide a better experience for readers and casual editors, our target audience for Media Viewer.
We will send one more update in mid-November, once all these improvements has been released and tested one more time.
Regards as ever,
Fabrice and the Multimedia Team
(1) Pictures of the Day on Commons:
https://commons.wikimedia.org/wiki/Commons:Picture_of_the_day#mediaviewer/F…
(2) Help page:
https://www.mediawiki.org/wiki/Help:Extension:Media_Viewer#How_can_I_turn_o…
(3) Community suggestions:
https://meta.wikimedia.org/wiki/Community_Engagement_(Product)/Media_Viewer…
(4) User Research:
https://www.mediawiki.org/wiki/Media_Viewer_Research_Round_2_(August_2014)
(5) Improvements page:
https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Improvements
(6) Talk page:
https://www.mediawiki.org/wiki/Extension_talk:Media_Viewer/About#Media_View…
_______________________________
Fabrice Florin
Product Manager, Multimedia
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:Fabrice_Florin_(WMF)
Minutes and slides from Thursday's quarterly review meeting of the
Foundation's Multimedia team are now available at
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
.
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
Tilman Bayer
Senior Operations Analyst (Movement Communications)
Wikimedia Foundation
IRC (Freenode): HaeB
I've just met with Jean-Baptiste and Felix from the VLC media player
project about integrating their player as a library that we can drop into
the iOS Wikipedia app to get Ogg and WebM audio/video playback working.
This will be *a lot* easier than maintaining our own media player library
(which I'm already doing with ogv.js in JavaScript to get things working in
Safari and IE, so that saves me having to duplicate the work in
Objective-C!) Using the player is just a few lines of code and will take
very little time to integrate once the clean library build is available.
I'll whip up a provisional patch on the weekend after we've landed some
general app refactoring which is currently higher-priority.
*= Performance =*
Native code playback is much faster than my JavaScript solution, so the app
will be able to play back high-definition WebM files that we can't play in
Safari. Nice!
*= Patents =*
Felix is working right now on adjusting the build scripts to make a
"free-codecs only" build easy, which thus won't have any patent concerns.
(They've done it before manually for consulting customers, but it'll soon
be a simple switch on the build script.)
Once this is set up it should be very easy for me to make a local build
with the options we need, without having to maintain a fork or anything. We
can then just drop the pre-built library into our app.
*= Copyright licensing =*
libvlc/VLCKit is LGPL-licensed, and between the VLC team's interpretation
and our legal team's interpretation (thanks Luis!) and Apple's de-facto
treatment of existing VLC-based apps, we're pretty sure this should not be
a problem for our open-source app.
(The individual codec libraries are mostly BSD-ish licensed.)
-- brion
Hi all,
We set up some data collection a few weeks back to look at the distribution
of actual screen size, viewport size and media viewer canvas size on
sampled users. This will ultimately be used to come up with a better choice
of thumbnail size buckets for Media Viewer.
I had some spare time and figured I'd try to generate a visualization of
that data, which we haven't analyzed yet.
Here are the results:
https://upload.wikimedia.org/wikipedia/commons/8/82/Screen_heatmap.pnghttps://upload.wikimedia.org/wikipedia/commons/2/2f/Viewport_heatmap.pnghttps://upload.wikimedia.org/wikipedia/commons/d/d3/Canvas_heatmap.png
(Media Viewer-specific)
I think it shows quite strikingly how screen size really doesn't matter
much compared to the actual available viewport. Hopefully this data will be
useful for other folks too, since I don't believe we tracked that
information before. And given media viewer's traffic, it should be pretty
representative of wikis in general.
The data used to generate those images is all the data we've collected so
far. I haven't looked at differences between wikis, etc. For people with
analytics access, the EL table I dug that data from is
MultimediaViewerDimensions_10014238
Note that this is mostly desktop, since it's very unusual to run Media
Viewer on mobile devices, considering it hasn't been made for it and
themobile site has its own MV-like lightbox.
The code used to generate these is this quick and dirty Processing script I
hacked together: https://phabricator.wikimedia.org/P39
Especially @pginer, but others can chime in -
The disable/enable dialog is coming, but we need to be able to display
errors. Is there a decent way to show errors in the dialog(s)? Do we need
a new design for that? I don't think there's any particularly prevalent
error we need to worry about, but I'd rather not get caught without info
when people do get errors for whatever reason.
Thanks,
--
Mark Holmquist
Software Engineer, Multimedia
Wikimedia Foundation
mtraceur(a)member.fsf.org
https://wikimediafoundation.org/wiki/User:MHolmquist
Hi Multimedia and mobile folks,
I have found that I like MV on mobile, particularly when browsing galleries.
I have a request. While I can zoom in on an image that is loaded in MV on
mobile, I can't pan the zoomed image. Is that a feature in the queue?
Thanks,
Pine
*This is an Encyclopedia* <https://www.wikipedia.org/>
*One gateway to the wide garden of knowledge, where lies The deep rock of
our past, in which we must delve The well of our future,The clear water we
must leave untainted for those who come after us,The fertile earth, in
which truth may grow in bright places, tended by many hands,And the broad
fall of sunshine, warming our first steps toward knowing how much we do not
know.*
*—Catherine Munro*
Hi folks,
Here's a quick update on the Structured Data project, which proposes to make multimedia data easier to search, view, edit, curate and re-use on Wikimedia Commons.
Today, information about media files on Wikimedia sites is stored in unstructured formats that cause a range of issues: for example, file information is hard to search, some of it is only available in English, and it is difficult to edit or re-use files to comply with their license terms.
Last week, a first bootcamp was held in Berlin to discuss this project and explore possible solutions, based the same technology as the one developed for Wikidata. Participants included community volunteers, as well as the Wikidata and Multimedia teams. This blog post gives an overview of what was discussed and accomplished. (1)
Some good ideas came out from this event, but many questions remain unanswered. We would now like to invite more community members to help plan next steps for this project: everyone is welcome to join the discussion and/or subscribe to the newsletter on the new Structured data hub on Commons. (2)
We also invite you to join tomorrow's live IRC chat about Structured Data: this Thursday, October 16 at 18:00 (UTC), on #wikimedia-office (3). The development teams would love to discuss this project with you.
Going forward, our community liaison Keegan Peterzell will be managing communications for this project. You will be hearing from him about our next discussions and other ways you can get involved in this important initiative.
We look forward to working with you to better support the needs of our users and modernize our multimedia infrastructure together.
Best regards,
Fabrice -- for the Structured Data team
(1) https://commons.wikimedia.org/wiki/Commons:Structured_data/Berlin_Bootcamp
(2) https://commons.wikimedia.org/wiki/Commons:Structured_data
(3) https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
_______________________________
Fabrice Florin
Product Manager, Multimedia
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:Fabrice_Florin_(WMF)
