Open Media Project

In the 2.x branch of the modules, we've added a number of admin level configuration options. We've also added a permission level to manage each feature set without having to grant admin access. To streamline the UI, we've added Manage Equipment and Manage Scheduling sections to the /admin and well as a section for Open Media System. This structure translates well for sites using the Admin Menu module and saves us time writing UI for managing different parts of the system.

All of the Open Media modules now have dev snapshots of the 2.x branches. New features are being added to these branches for BAVC so these are still very much in development and should not be used until they become the supported version. While we wanted a way to update the documentation so it is useful to BAVC's staff in April and DOM's staff after that, we didn't want to confuse 1.x users.

I think we've come up with a slick way to highlight the 2.x documentation so it can easily be merged when the 2.x modules are finished.

on /admin/build/modules it shows that channelAustin has Version 6.x-1.1 of OM Broadcast Syncronization, but I look at http://drupal.org/node/374090/release i see the latest version is Version 6.x-1.0

I'm assuming that the om_broadcast_sync version we have at channelAustin is a pre-release one with on inaccurate version number.

Should we upgrade to om_broadcast_sync 6.x-1.0?

Any issues, warnings, concerns to note?

On the Module page /admin/build/modules it doesn't show which version of Media Mover we have installed at channelAustin.

And when I look at media_mover_api.info, I get this:

; $Id: media_mover_api.info,v 1.1.2.1.2.2 2008/10/02 23:34:41 arthuregg Exp $
name = Media Mover API
description = Core of the Media Mover system
package = "Media Mover"
core = 6.x
php = 5.0
~

And when I look at media_mover_api.install, I see:

/* $Id: media_mover_api.install,v 1.1.2.16.2.4 2008/11/18 19:27:16 arthuregg Exp $ */

After looking at what Jack Brighton has been doing with FieldFrame in Expression Engine (which AFAICT is really similar to Drupal's CCK), hearing BAVC's desire to stick with PBCore, and knowing that CPB is actively working on requirements for PBCore 2.0, I took another look a PBCore. What I found was that most of the terms the beta stations wanted to include in a new standard were really similar to an existing PBCore term.

At BAVC we are introducing a new piece to the standard Open Media configuration. Similar to using an external box as the FFMPEG encoder that accepts encoding instructions from the webserver using a simple encode.php file, we are going to execute the mv and cp commands for managing files to a Samba Server. That server will be on BAVC's internal network while the website will be hosted at Media Temple (mt).

It's taken longer than we hoped to get to this point, but the #drupal-openmedia IRC channel is now an active community of Drupal developers from several stations helping each other out. This conversation between emilyf and raytiley made my week...

Our omnicon bot has been having some issues with multiple sessions, but the IRC channel is being logged here...

http://www.openmediaproject.org/bot/log/drupal-openmedia

Just wanted to shoot out a line that TelVue published their API library this morning. I can't wait to play!
http://cms.telvue.com/?page_id=46

-petepo

Tightrope has recently announced their commitment to Open Source Software by releasing several company intiatives as open source. This significant opening of the Cablecast systems means that three of the Open Media Project's beta partners (Davis, Boston and Amherst) are steps closer to integrating Drupal with their playback system.