Last modified: 2014-08-29 15:55:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71365, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69365 - Install MLT and kdenlive on tool labs
Install MLT and kdenlive on tool labs
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-10 13:14 UTC by prolineserver
Modified: 2014-08-29 15:55 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description prolineserver 2014-08-10 13:14:06 UTC
Intention:
The Media Lovin' Toolkit (melt) and Kdenlive (package kdenlive) are used to render video files. Currently, https://tools.wmflabs.org/videoconvert/ supports conversion of video files and direct upload to Commons, and the next step of the proof of concept is online rendering of edited videos composed of material from Commons while you keep the xml-based project file to be kept with the result for later editing by other users.




Reproducible: Always
Comment 1 Marc A. Pelletier 2014-08-25 17:32:13 UTC
kdenlive pulls in, basically, all of KDE and X11 and is not suitable for inclusion on normal compute nodes.  (melt is marginally better and only pulls in a faction of Qt)

Video editing seems like a worthwhile objective, but also seems to be a poor fit to tool labs' normal use pattern.  Have you considered setting up a project to do the actual transcoding and rendering, only leaving the front-end and user interface in tool labs?

Not only will this avoid issues with large package sets (or, more precisely, it will contain them better) but it means that it will be easier to allocate resources for this.
Comment 2 prolineserver 2014-08-25 21:29:08 UTC
Well, I didn't consider setting up a project since what I have right now (except for the missing package) is pretty much what I need. The user interface backend submits rendering jobs using jsub, and I don't need to bother about that part at all. So, what does a separate project in the end involve for extra work from my side? I have neither time nor motivation to duplicate labs functionality or dig into issues like puppetization.

I also had some look into the kdenlive source during the last days, and it seems melt would be sufficient. Might it be possible to compile it manually and configure with less support?
Comment 3 Marc A. Pelletier 2014-08-25 21:58:41 UTC
A separate project would be more flexible, but also considerably more work.  So I can understand your preference.

melt would be okay for inclusion, if that suffices then we're golden.
Comment 4 prolineserver 2014-08-26 06:35:57 UTC
Yes, that would be perfect. If it later turns out that the tool is heavily used and a separate project has some advantages I might have a closer look again. Thanks!
Comment 5 Gerrit Notification Bot 2014-08-26 11:09:14 UTC
Change 156259 had a related patch set uploaded by coren:
Tool Labs: add melt

https://gerrit.wikimedia.org/r/156259
Comment 6 Gerrit Notification Bot 2014-08-26 14:47:33 UTC
Change 156259 merged by coren:
Tool Labs: add melt

https://gerrit.wikimedia.org/r/156259

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links