Video

Media Mover 2 and Drupal Queue

With folks using Media Mover to transcode larger and larger video files, cron time outs have become somewhat of a problem as Drupal waits for FFmpeg to complete its processing. With Media Mover one, configurations are run from cron by default (not required, but out of the box) which means that cron runs as long as the Media Mover configuration takes. While it is possible to limit cron runs, the reality of transcoding a gigabyte file is that it takes time regardless of how much horsepower you can throw at it. Media Mover one was setup to be friendly to multi-machine systems, but the system left some things to be desired.

Media Mover S3 CDN Improvements

The S3 module for Media Mover just got updated to make the CDN integration easier. As files come through the system, files which already reside on S3 will have $file->s3_uri set which allows theming functions to display the local URI if it is present or the S3 URI if the file is already on S3.

Make that $file->s3_data which is a serialized array of data from the S3 file. This allows for the generation of private urls.

Drupal S3 API Module

Heshan Wanigasooriya just let me know that he has started developing an API module for S3. This means that for modules that are implementing S3 functionality, we can all use a single API module instead of reinventing the wheel every time. Basic get/put functionality is already in place and support for query string authenticated files is coming quickly.

Media Mover's S3 implementation will likely transition to this quite quickly. I suspect we'll be doing a stream wrapper implementation in the near future....

YouTube Support for Media Mover

Alexandru Badiu just emailed me to let me know that he has released a new YouTube module that allows files to be stored to YouTube from a standard Media Mover configuration. Awesome!

Media Mover 6.2x API changes

In an attempt to improve the workflow of Media Mover, I'm going through the process of refining the main API aspect. The main reason for this is to move away from the 4 step model (harvest, process, store and complete) to a chainable set of definable actions.

These are some notes to self as I'm going through the process, but feedback is of course appreciated

function hook_media_mover() {
  return array(
    '#name' => t('My Media Mover module description'),
    '#actions' => array(
      array(
        // give each action in your module a unique id 
        '#action' => 'operation_1',
        // give your action a description
        '#description' => t('Do something with a file!'),
        // harvesting files is a special case. You only need

Media Sprint End of Day 3

Here's a quick report back on work that got accomplished today. Lots of code, coffee, and keyboards.

Media Sprint Day 3

Here's the report back from the beginning of the third day of the media sprint here in NYC. You can see some improvements to the GUI. Today we're going to be working on several pieces- admin, formaters and stream wrappers.

Media Sprint prototyping

This is a quick demo of the functionality that we've been developing here at the media sprint. This is obviously not polished, but it does show some of the pieces of functionality that we want to finish- functionality that we outlined earlier today on the uploader proposal on the interface group.

International Human Rights Day- Drupal plays a small part

The 60th anniversary of the United Nations Universal Declaration of Human Rights has brought to the fore the work of many organizations who are utilizing the web (and Drupal) to fight for human rights across the word.

Pages